pcplantdb

[Stephanie Gerson <sgerson@stanfordalumni.org>]

seems like we're already gettin busy!

first of all, thank you to Rich for developing an initial db to play 
around with and modify-- right on, Rich.

so I did my homework this weekend, and had a wonderful time brainstorming 
the user interface design and scripting human-computer interaction of a 
guild-building tool/plant database.  I wrote and drew A LOT in my 
journal- a bit too much to relay here.  but basically, I am super jazzed 
and think we could build a fantastic tool.  some important points though:

1.  neither of us know where each other are from!  (at least I don't)  I 
am from California, and was initially planning on developing a guild-
builder initially for California...expand throughout the US...always 
collaborating with people involved with similar projects...allowing 
people to creatively add information...until we had a valuable database 
and tool encompassing a LARGE geography.  I know Rich is from the UK, and 
I have a feeling some of you are from Australia, or other countries.  So 
how to approach this?  Perhaps we can decide together on an interface  
for creating this database (which I will briefly go into below)_and then 
split into groups on a regional/country basis, and BUILD.  (Of course, 
each region/country could use their own interface, but I think it would 
be more fruitful for cross-pollination purposes if they were 
consistent...)  Or make split into task forces, regardless of geography, 
which might be easier.  The task forces could be separated into:

-programmers 
-UI/HCI designers
-people experienced with interactive education
-people experienced with environmental education
-expert Permies--obviously, seek the expertise of local Permaculturists 
and guild designers throughout the process

What do you think?

2.  in terms of logi$tics, I definitely support the idea of going with 
open-source free code, and I don't remember who suggested it, but I think 
TouchGraph is the way to go.  It is somewhat like ThinkMap (fewer 
capabilities), and most importantly, it is FREE.  (I appreciate Rich's 
template, but I Love the visual aspect of ThinkMap, and feel that the 
user experience would be much much richer with a tool like this one...I 
am willing to discuss this, but I almost have too much to say to go into 
here).  Then I would be willing to do some grantwriting, and seek funding 
to cover overhead expenses (such as wages, that would be a dream...).  
But we would have to establish a concrete game plan- which people might 
not willing to do if they want to leave things fluid (which is 
understandable if we are building something that we are going to discover 
AS we create).  Even if we don't get funding though, I must say (and I 
think you are all with me on this) that I dig this project so much, I 
would Love to work on it regardless. 

3.  and now for the actual interface.  I have so much to say I don't even 
know *what* to say...I wish I could talk to all of you!  Perhaps I will 
just give you the basic gist, and for people who are interested in 
learning more, let me know and I will send you a more thorough 
description.  Basically, the guild-builder/plantdb serves to:

-help people in designing guilds for their specific locale, 
circumstances, and preferences
-allow practitioners to enter information, ask questions, find references 
(people, books, websites, etc.) relating to guild design-- somewhat of a 
multimedia forum and modifiable archive

I wrote different scripts for users attemtping to design a guild, and 
users seeking to enter information.  A list of what users attempting to 
design could be able to do (remember, this is a _potential_ list):
-enter information about their specific locale/preferences
-build an appropriate guild
-learn in-depth about it's components (by linking to the plant database)
-learn about the RELATIONSHIPS between it's components (with information 
we research, and is input by us or by other users)
-read about case studies of such guilds (input by other users)
-get references for such guilds/guild design in their local area
-see pictures (we can collect images- photos and drawings)
-post quesstions to a general forum/specific forum for a specific guild
-receive suggestions from the program itself (I will explain this below)

The HCI would allow *both* non-expert gardeners design guilds from 
'scratch" AND experienced permies (who already have many sophisticated 
preferences) choose one or two additional species to add to an existing 
guild.

Users seeking to enter information could be able to:
-create a visual interface of their guild, and add notes for others to 
see and learn
-add photos, contact info, and references

In terms of receiving suggestions from the program itself, someone in 
this discussion added to their "wish list" that the program be able to 
suggest guilds.  YESYESYESYESSSSSSS.  The program would learn based on 
the information we provide it.  The more relationships we enter and make 
between plants, the better the program will know what to recommend- and 
we will indirectly be developing a complex and many-factored algorithm 
for designing guilds.  All you programmers- am I completely dreaming?  
because this definitely seems possible to me...

Have MUCH more to say, but will stop here.  *sigh*

So, how to proceed, folks?

keep on keepin on...

peace
*stephanie

p.s.  John S.-- when I suggested brainstorming the ultimate plant db- it 
wasn't so we could BUILD the ultimate one now- just an exercise in 
setting goals to aspire towards.  And also, where can you do an MA in 
Designing Whole Systems?!  sounds super intruiging....


+++++++++++++++
Stephanie Gerson
sgerson@stanfordalumni.org
415.871.5683


____________________________________________________________________