pcplantdb

[Richard Morris <webmaster@pfaf.org>]

Stephanie Gerson wrote:
> seems like we're already getting busy!
>
> first of all, thank you to Rich for developing an initial db to play 
> around with and modify-- right on, Rich.

Thanks for that, I was getting a little worried about lack of feedback.

> 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

Yes indeed a good division. Question is how to build the task force,
I really see this as one of the major challenges, getting a system
where we can all work together.

The geography diversity is both a strong point and a week point.
Its strong as we have a world wide knowledge base, there is much
localised information about plants, completely different flowering times
dependent on hemisphere.

There are however problems with funding. The people who I've been
talking to have asked the question "how will this help the south west of 
england?" International funded projects are a little beyond their sights.

The other problem is communication, but other open source projects
have overcome this.

> 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. 

Indeed, I think if we build stuff on top of already developed open source
projects we will end up with a better system. I could easily hack 
something together myself, but  don't think it will be as robust or
as flexible as a bigger name open source project.

> 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).  

I'll have a look at TouchGraph. As its open source fewer capabilities
is not a prob, we can add them ourselves! They seem to be using good
OO design patterns so extension to our special requirements could
be easy.

> 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

Hay we could even build a library of these. Get the permaculture
map of the world!

> -build an appropriate guild

Here I can see visual approach has benefits. In building a plant list
you need to get the correct latin names of plants to establish the link.
Currently this is quite tedious. Sosphsticated interfaces
could make this easier.

> -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)

This would be very cool. There is very little info on the web which
seems to describe plant communities. I had a hard job even finding
one documented guild.

I had a lot of fun with the guild bit in the framework I did.
Its was remarkably easy to add guild, only took half an hours coding to
get the setup working, and adding a guild was a brease.

Widen the concept
and you get a very powerful thing, basically a guild can be though of as
a "group of related things". Many other things fit in this concept
I immediatly started adding "Richs backgarden" grouping all the plants
in my garden, I can see that other would want to do similar. Many other
applications of this sort of idea.


> -read about case studies of such guilds (input by other users)

User input is key!

> -get references for such guilds/guild design in their local area
> -see pictures (we can collect images- photos and drawings)

Great.

> -post quesstions to a general forum/specific forum for a specific guild

Yes essential. The logistics can be tricky, forum per plants
will be very low traffic. Cross referencing forum items to database
pages is an interesting problem.

> -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...

Yes it is all possible, and actually not to hard.

> Have MUCH more to say, but will stop here.  *sigh*
>
> So, how to proceed, folks?

Ah the hard question!

Maybe we need to write a project proposal, outlining the idea behind the 
project. Once we have that we can start showing the proposal around to
funders, programmers, contributors etc and build a group around it.

As to interfaces. Does there only need to be one! We've already got 4
interface implementations/ideas. This might not be a problem
as long as there is an open standard for data exchange. Then
different platforms can share the data.

I've been looking into xml at the moment and it seems the obvious way to
go. Lots of software can handle it and lots of work is being done
on standards for encoding data in XML. I had a quick hack about and
got a program to produce xml from the database. Its loosely based
around rdf, dublin core and rss (for exchanging news items).
Below is a sample output.

        laters

                Rich
        

<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
 xmlns="http://purl.org/rss/1.0/";
 xmlns:dc="http://purl.org/dc/elements/1.1/";
 xmlns:slash="http://purl.org/rss/1.0/modules/slash/";
 xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/";
 xmlns:admin="http://webns.net/mvcb/";
 xmlns:syn="http://purl.org/rss/1.0/modules/syndication/";
>

<channel rdf:about="http://www.ibiblio.org/pfaf/pcplantdb/";>
<title>Permaculture Plant Database</title>
<link>http://www.ibiblio.org/pfaf/pcplantdb/</link>
<description>An open source colaborative database of plants and 
guilds</description>
<dc:language>en-uk</dc:language>
<dc:rights>Copyright &amp;copy; 2003. pcplantdb</dc:rights>
<dc:date>2003-10-10T11:13:44+00:00</dc:date>

<dc:subject>Botany</dc:subject>
<dc:creator>webmaster@pfaf.org</dc:creator>
<dc:creator>
  <Agent>
      <dc:title>Ken Fern, Richard Morris</dc:title>
  </Agent>
</dc:creator>
<dc:rights>
  <Agent>
    <dc:title>Plants For A Future/Ken Fern</dc:title>
  </Agent>
</dc:rights>
<dc:type rdf:resource="http://purl.org/dc/dcmitype/Text"; />
<License rdf:about="http://creativecommons.org/licenses/by-nc-sa/1.0";>
   <requires rdf:resource="http://web.resource.org/cc/Attribution"; />
   <requires rdf:resource="http://web.resource.org/cc/ShareAlike"; />
   <permits rdf:resource="http://web.resource.org/cc/Reproduction"; />
   <permits rdf:resource="http://web.resource.org/cc/Distribution"; />
   <permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"; />
   <prohibits rdf:resource="http://web.resource.org/cc/CommercialUse"; />

   <requires rdf:resource="http://web.resource.org/cc/Notice"; />
</License>

<item>
<title>Rhus toxicodendron</title>
<link>http://www.ibiblio.org/pfaf/pcplantdb/showthing.php?BOTNAME=Rhus 
toxicodendron</link>
<botanicalauthor> L.</botanicalauthor>
<thingType>Species</thingType>
<references>11, 43, 200</references>
<botanicalSynonym>
  <name>Toxicodendron pubescens</name>
  <botanicalAuthor> Mill.</botanicalAuthor>
  <description></description>
    <footnoteref>1</footnoteref>
</botanicalSynonym>
<botanicalSynonym>
  <name>Rhus quercifolia</name>
  <botanicalAuthor> Steud.</botanicalAuthor>
  <description></description>
    <footnoteref>1</footnoteref>
</botanicalSynonym>
<commonName>
  <name>Eastern Poison Oak</name>
  <notes></notes>
  <relationship>
    <relType>Country</relType>
    <keyWord>England</keyWord>
  </relationship>
  <relationship>
  <relType>Language</relType>
  <keyWord>English (UK)</keyWord>
  </relationship>
  <footnoteref>1</footnoteref>
</commonName>
<parent>
  <type>Family</type>
  <link>showthing.php?BOTNAME=Anacardiaceae</link>
  <title>Anacardiaceae</title>
    <footnoteref>1</footnoteref>
</parent>
<parent>
  <type>Plant Guild</type>
  <link>showthing.php?BOTNAME=White+Oak%2FHazelnut+community</link>
  <title>White Oak/Hazelnut community</title>
  <notes>Unsure which is correct bot name</notes> 
<footnoteref>2</footnoteref>
</parent>


<section name="Hazards and Warnings">
  <keyWord name="Poisionious">

<link>keywords.php?SECTION=Hazards+and+Warnings&amp;KEYWORD=Poisionious</link> 
   <footnoteref>1</footnoteref>
</keyWord>
</section>

<section name="Poisionious Plants">
<description>This plant contains toxic substances and skin contact with 
it can cause severe irritation to some people[11]. The sap is extremely 
poisonous[11]. The sap contains 3-N pentadecycatechnol. Many people are 
exceedingly sensitive to this, it causes a severe spreading dermatitis. 
The toxins only reach the skin if the plant tissues have been damaged, 
but even indirect contact can cause severe problems[200].</description>
<footnoteref>1</footnoteref>
</section>

<section name="Description">
</section>

<section name="Habit">
<keyWord 
name="Shrub"><link>keywords.php?SECTION=Habit&amp;KEYWORD=Shrub</link> 
  <footnoteref>1</footnoteref>
</keyWord>
</section>

<section name="Height">
<numeric><value>0.6</value>
    <footnoteref>1</footnoteref>
</numeric>
</section>

<section name="Width">
<numeric><value>1</value>
    <footnoteref>1</footnoteref>
</numeric>
</section>

<section name="Habitat">
<keyWord name="Dry">
  <link>keywords.php?SECTION=Habitat&amp;KEYWORD=Dry</link> 
<footnoteref>3</footnoteref>
</keyWord>
<description>Dry barrens, pinelands and sands[43].</description>
    <footnoteref>1</footnoteref>
</section>

<section name="Geographical Range">
<description>South-eastern N. America - New Jersey to Delaware, south to 
Georgia, Alabama and Texas.</description>
    <footnoteref>1</footnoteref>
</section>

<section name="Growing Conditions">

</section>

<section name="Hardyness">
<numeric><value>7</value>
    <footnoteref>1</footnoteref>
</numeric>
</section>

<section name="Soil Types">
</section>

<section name="Soil weight">
<keyWord name="Likes Light 
Soil"><link>keywords.php?SECTION=Soil+weight&amp;KEYWORD=Likes+Light+Soil</link> 
   <footnoteref>1</footnoteref>

</keyWord>
<keyWord name="Likes Medium 
Soil"><link>keywords.php?SECTION=Soil+weight&amp;KEYWORD=Likes+Medium+Soil</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<keyWord name="Likes Heavy 
Soil"><link>keywords.php?SECTION=Soil+weight&amp;KEYWORD=Likes+Heavy+Soil</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<keyWord name="Grows in nutritionally poor 
soil"><link>keywords.php?SECTION=Soil+weight&amp;KEYWORD=Grows+in+nutritionally+poor+soil</link> 
   <footnoteref>1</footnoteref>

</keyWord>
<keyWord name="Requires Well Drained 
Soil"><link>keywords.php?SECTION=Soil+weight&amp;KEYWORD=Requires+Well+Drained+Soil</link> 
   <footnoteref>1</footnoteref>
</keyWord>
</section>

<section name="Soil pH">
<keyWord name="Acid 
soil"><link>keywords.php?SECTION=Soil+pH&amp;KEYWORD=Acid+soil</link> 
 <footnoteref>1</footnoteref>
</keyWord>
<keyWord name="Neutral 
soil"><link>keywords.php?SECTION=Soil+pH&amp;KEYWORD=Neutral+soil</link> 
   <footnoteref>1</footnoteref>

</keyWord>
<keyWord name="Basic 
soil"><link>keywords.php?SECTION=Soil+pH&amp;KEYWORD=Basic+soil</link> 
  <footnoteref>1</footnoteref>
</keyWord>
</section>

<section name="Soil moisture">
<keyWord name="Dry 
soil"><link>keywords.php?SECTION=Soil+moisture&amp;KEYWORD=Dry+soil</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<keyWord name="Moist 
soil"><link>keywords.php?SECTION=Soil+moisture&amp;KEYWORD=Moist+soil</link> 
   <footnoteref>1</footnoteref>

</keyWord>
</section>

<section name="Shade Tolerance">
<keyWord name="No 
Shade"><link>keywords.php?SECTION=Shade+Tolerance&amp;KEYWORD=No+Shade</link> 
   <footnoteref>1</footnoteref>
</keyWord>
</section>

<section name="Cultivation Details">
<description>Succeeds in a well-drained fertile soil in full sun[11, 
200]. Judging by the plants natural habitat, it should also succeed in 
poor acid soils and dry soils[K].
The young growth in spring can be damaged by late frosts.
Plants have brittle branches and these can be broken off in strong 
winds[200]. Plants are also susceptible to coral spot fungus[11]. Plants 
in this genus are notably resistant to honey fungus[200].
This species is a small suckering shrub, it can spread freely in 
suitable conditions[K].
There is some confusion over the correct name of this species. It is 
united with R. radicans (under that name) by some botanists whilst 
others split this species off into another genus, Toxicodendron, and 
unite it with R. radicans as Toxicodendron radicans[200].
Many of the species in this genus, including this one, are highly toxic 
and can also cause severe irritation to the skin of some people, whilst 
other species are not poisonous. It is relatively simple to distinguish 
which is which, the poisonous species have axillary panicles and smooth 
fruits whilst non-poisonous species have compound terminal panicles and 
fruits covered with acid crimson hairs[1, 4]. The toxic species are 
sometimes separated into their own genus, Toxicodendron, by some 
botanists[200].
Dioecious. Male and female plants must be grown if seed is 
required.</description>
    <footnoteref>1</footnoteref>

</section>

<section name="Propagation Details">
<description>Seed - best sown in a cold frame as soon as it is ripe. 
Pre-soak the seed for 24 hours in hot water (starting at a temperature 
of 80 - 90c and allowing it to cool) prior to sowing in order to leach 
out any germination inhibitors[200]. The stored seed also needs hot 
water treatment and can be sown in early spring in a cold frame[200]. 
When they are large enough to handle, prick the seedlings out into 
individual pots and grow them on in the greenhouse for their first 
winter. Plant them out into their permanent positions in late spring or 
early summer, after the last expected frosts.
Cuttings of half-ripe wood, 10cm with a heel, July/August in a frame[200].
Root cuttings 4cm long taken in December and potted up vertically in a 
greenhouse. Good percentage[78, 200].
Suckers in late autumn to winter[200].</description>
    <footnoteref>1</footnoteref>
</section>

<section name="Plant Uses">
</section>

<section name="Edible Uses">
<description>None known</description>
    <footnoteref>1</footnoteref>

</section>

<section name="Medicinal Uses">
<keyWord 
name="Homeopathy"><link>keywords.php?SECTION=Medicinal+Uses&amp;KEYWORD=Homeopathy</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<keyWord 
name="Irritant"><link>keywords.php?SECTION=Medicinal+Uses&amp;KEYWORD=Irritant</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<keyWord 
name="Narcotic"><link>keywords.php?SECTION=Medicinal+Uses&amp;KEYWORD=Narcotic</link> 
   <footnoteref>1</footnoteref>

</keyWord>
<keyWord 
name="Parasiticide"><link>keywords.php?SECTION=Medicinal+Uses&amp;KEYWORD=Parasiticide</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<keyWord 
name="Rubefacient"><link>keywords.php?SECTION=Medicinal+Uses&amp;KEYWORD=Rubefacient</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<keyWord 
name="Salve"><link>keywords.php?SECTION=Medicinal+Uses&amp;KEYWORD=Salve</link> 
   <footnoteref>1</footnoteref>

</keyWord>
<keyWord 
name="Stimulant"><link>keywords.php?SECTION=Medicinal+Uses&amp;KEYWORD=Stimulant</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<description>Poison oak has occasionally been used medicinally, though 
it is an extremely poisonous plant and great caution should be 
exercised. Any herbal use should only be undertaken under the 
supervision of a qualified practitioner. See also the notes above on 
toxicity.
A fluid extract of the fresh leaves is irritant, narcotic, rubefacient 
and stimulant[4]. It has been used with some success in the treatment of 
paralysis, obstinate herpatic eruptions, palsy and in various forms of 
chronic and obstinate eruptive diseases[4].
A mash of the leaves has been used to treat ringworm[213]. An external 
application has also been used in the treatment of herpes sores[213].
A poultice of the plant has been used to treat infectious sores on the 
lips[257].
The root has been used to make a poultice and salve in the treatment of 
chronic sores and swollen glands[257].
A homeopathic remedy is made from the fresh leaves[232]. These should be 
harvested of a night-time, during damp weather and before the plant 
flowers[232]. This remedy has a wide range of applications and is one of 
the main treatments for mumps[232], it is also used in a wide range of 
skin disorders[4].</description>
    <footnoteref>1</footnoteref>
</section>

<section name="Other Uses">
<keyWord 
name="Dye"><link>keywords.php?SECTION=Other+Uses&amp;KEYWORD=Dye</link> 
   <footnoteref>1</footnoteref>

</keyWord>
<keyWord 
name="Ink"><link>keywords.php?SECTION=Other+Uses&amp;KEYWORD=Ink</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<keyWord 
name="Mordant"><link>keywords.php?SECTION=Other+Uses&amp;KEYWORD=Mordant</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<keyWord 
name="Oil"><link>keywords.php?SECTION=Other+Uses&amp;KEYWORD=Oil</link> 
   <footnoteref>1</footnoteref>

</keyWord>
<keyWord 
name="Tannin"><link>keywords.php?SECTION=Other+Uses&amp;KEYWORD=Tannin</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<keyWord 
name="Varnish"><link>keywords.php?SECTION=Other+Uses&amp;KEYWORD=Varnish</link> 
   <footnoteref>1</footnoteref>
</keyWord>
<description>The leaves are rich in tannin. They can be collected as 
they fall in the autumn and used as a brown dye or as a mordant[169].
An oil is extracted from the seeds[4]. It attains a tallow-like 
consistency on standing and is used to make candles. These burn 
brilliantly, though they emit a pungent smoke[4].
The milky juice makes an excellent indelible marking ink for linen 
etc[4, 11]. It is also used as a varnish for boots and 
shoes[4].</description>
    <footnoteref>1</footnoteref>

</section>


<footnotes>
<footnote>
  <ref>1</ref>
  <link>userinfo.php?NICKNAME=pfafrich</link>
  <name>pfafrich</name>
  <date>04 Oct 2003 Import of Plants For A Future data</date>

</footnote>
<footnote>
  <ref>2</ref>
  <link>userinfo.php?NICKNAME=pfafrich</link>
  <name>pfafrich</name>
  <date>04 Oct 2003 Import of data from UDSA Plants Databases</date>
</footnote>
<footnote>
  <ref>3</ref>

  <link>userinfo.php?NICKNAME=pfafrich</link>
  <name>pfafrich</name>
  <date>04 Oct 2003 Data derived from Plants For A Future Data using 
some sort of pattern matching. Validity questionable</date>
</footnote>
</footnotes>
</item>
</channel>
</rdf:RDF>




--
Plants for a Future: 7000 useful plants
Web:   http://www.pfaf.org/ same as http://www.comp.leeds.ac.uk/pfaf/
Post:  1 Lerryn View, Lerryn, Lostwithiel, Cornwall, PL22 0QJ
Tel:     01208 872 963 / 0845 458 4719  
Email: webmaster@pfaf.org
PFAF electronic mailing list http://groups.yahoo.com/group/pfaf