pcplantdb

[Chad Knepp <pyg@galatea.org>]

One of the things I kind of forgot to mention is that I would like to
have a 0.x.0 release about every month or so.  How much time do we
have anyway?  IIRC dispersal was Sept.?... so we probably have until
then or so?  I'm starting to feel pressure to finish our commitments
to Threshold in time.  This summer is going to be a busy one for me as
it is.

Richard Morris writes:
 > Chad Knepp wrote:
 > 
 > > Kind of curious as to how many more features I should implement on dev
 > > before the next "stable" 0.2.0 release that will go onto the main piw
 > > site.  Any ideas on what things we really need to iron out before
 > > submitting it to the public?  A list would be nice. 
 > > 
 > > Chad
 > > 
 > OK several things. Not sure if all these should go into 0.2.0, or a 
 > later release.
 > 
 > User Login
 > ----------
 > 
 > Make the process smoother.
 > 
 > Login/Register box on from page, under search box.
 > 
 > Confirmation of login name displayed on all pages
 > when logged in - to provide feedback to user.
 > 
 > Ability to log out.

I concur.

 > Display (individual plants)
 > -------
 > 
 > Tidy up display of results/plants.
 > 
 > Use appropriate
 > (symantic) makeup of titles etc. so that they can be
 > formatted according to style sheet.
 > 
 > Cordinate with Bear-Chad for appropriate markup semantics.

Already in the tracker.

 > Display Synonyms for plants.
 > 
 > Display habitats for plants.
 >
 > Create a habitat objects (similar to Uses)
 > 
 > Display Native Range.

This is all already displayed in the [first] summary paragraph.

 > Markup book references, so clickable.

On track to occur when the PFAF notes move to comment/topic format.

 > Display (Search results)
 > ------------------------
 > 
 > Allow browsing after first 100 plants.

I'm not understanding this.  This is possible but with a 100 results
per page maximum.

 > Allow alphabetical listing. (User preference)

Ok, easy to do, but not IMO that useful/important.  Put in the tracker
so I don't forget.

 > Comments
 > --------
 > 
 > Allow comments per section. So its posible to add a comment for edible 
 > uses.

This will happen when the Notes become comments/topics... authors can
add info on the subject.

 > Allow new Botanical Synonyms to be entered. (With Author)
 > 
 > Allow new Common Names to be entered. (Poss with Language/Region)

My preference would be to push creating and editing plant objects to
0.3.0 if you don't mind.

 > Allow links to other sites to be entered.

This can already be done in the comments... did you mean
something/somewhere else.

 > Provide a Back button so user can return to plant after entering comment.

Actually after you submit a comment you should be directed to the
plant you commented on with your comment displayed.

 > Sections
 > --------
 > 
 > Allow a new section to be created (not necessarily by anonomous/logged 
 > in uses)
 > Mainly so I could expand things to allow tanplants data fields to be 
 > added for example
 > COMR - Commercial application of this plant.
 > Happy to do this by direct SQL queries (probably easiest for me).
 > 
 > This will probably need a bit of discussion on the list.

Real schema changes are d efinitely 0.3.0, although I think some of
these are comment/topic material.  If we have an edible uses section
why not a commercial uses one?

 > Relationships
 > -------------
 > 
 > Allow creation of non plant objects. Allready have a uses objects.

Not so sure about this.  One of the difficulties of a RDBMS is that
you can't really just add generic objects without some prep work.
Bear mentioned an interesting alternative way back in March, and
although interesting/intriguing I think it's a 2.0 idea.  

My object model is that a lot of the [loosely typed] data can/will be
captured by the comment/topic object.

 > Allow links back from non plant objects to linking plants.
 >
 > Specifically if click on use=Gum, it would be cool if
 > that page displayed all the plants which can be used for Gum.

This sounds like a search function.  More discussion necessary I
think... not really 0.2.0 material

 > Documentation
 > -------------
 > 
 > Add link to issue tracker.
 > 
 > Add public doc on issue tracker, describing how to use it
 > for external users.
 > 
 > Add doc for CVS access.
 > 
 > Add link to Wiki http://www.permaculture.info/wiki/index.php
 > 
 > Wiki
 > ----
 > 
 > Tidy up output.
 > 
 > -------
 > That should keep us going for a while.
 > 
 > We might want to start doing some milestones. i.e. break the above into 
 > separate groups based on priorities, so we can work incrementally to
 > final 0.2.0 release. Could for example have
 > 
 > 0.1.7 - User login complete
 > 
 > 0.1.8 - Expandable schema with comments in sections.
 > 
 > 0.1.9 - Good looking output. Feature freaze and bug checks before
 >      0.2.0 release.
 > 
 > Comments?
 > 
 > I've put most of the above on the wiki, see
 > http://www.permaculture.info/wiki/index.php?n=Main.Features
 > 
 > Rich

-- 
Chad Knepp
python -c 'import base64;print base64.decodestring("cHlnQGdhbGF0ZWEub3Jn")'