Thanks for writing :-) .
At 11:43 AM 2/5/2009, you wrote:
First, "in the meantime" while deciding on how to do this in a database
fashion, you should at least be trying to store your data in a
spreadsheet or some other format that can be easily imported into a
database.
I started with text because you do not have the limitations of having to have
exact places for everything like you do with set fields. At first, I
wasn't even
sure what I needed. That is a long time ago now and I am now much more
set on what fields I need and in what order. Surprisingly, there are still
times when it comes in handy to be able to place something wherever I
want. I realize this has have stricter rules for a database driven system.
I have files in Excel and MySQL already (ie. back end files)
but not the code that ties it all together (front end) into a nice seamless
application that makes it easy to actually travel up and down the tree.
At one point, I had a friend who liked programming in File Maker and I
started coding with that ---- until I found the unreasonable and expensive
costs of hosting many files with this language.
The MySQL files are not small and are *certainly* large enough to use for
the system development. The TAXA file is still, by far, the most complete
knowledge base. I recently used a text search tool to extract out the
most recent list of Orders, Families and pretty much Genera. The
species level is just too large to bother cleaning up any list of species
right now. I would just as well care to spend that time in coding the
permanent storage and viewing application instead, ready to add in
all species once and for all.
For general viewing and maintenance of my MySQL files, I love using
phpMySQL. I foresee it being even more useful for generating SQL
statements and a shortcut to PHP code for this, too. So, I hope this
helps show that I can already view a lot of this data but only file by
file (level by level), I have decided that I should shift my emphasis
largely to:
- Get the botanical wood tree working first including easy travel
between levels for viewing data only. That alone is quite a
bit of work.
- With that done, work on an administrative panel to add, delete
and change data. Only then can I start the huge job of updating
all the data in the TAXA file into the MySQL files.
In the past, I've done this with Excel or other spreadsheets.. or even in a
text file that's formatted in such a way that you can either write a PHP
script to import or even turn the text file itself into a PHP script that
generates the INSERTs and such.
I have managed to get some data out from the TAXA file but it just is NOT
structured strict enough to be effective to use most scripts to extract a
high percentage of content and definitely not organized so orderly as to
be able to use any script imaginable to port the whole works over into
Excel, MySQL or any other format. I can and have done a lot to extract
out Orders, Families and Genera and, with more time to clean up the
Species extraction, update all these for names only, not attenuating
data for each.
The change over from still using text to being totally database driven could
not happen till I have a versatile user interface for managing all present and
future data.
Using a text editor like Crimson Editor, you can create macros to easily
I use Crimson Editor sometimes, too. Every try NoteTab? Its got a lot of
good qualities and capabilities
transform thousands of lines of data into PHP code or something useful.
Just hit RECORD, perform the predictable edits you'd need to do on a few
lines. Stop recording. Then just hold down the macro key that executes
the actions. Take a nap until it's done. Release keys. hah Yeah,
crude, but it's come in very handy a few times.
(Partial merit but it could introduce too much data error.)
Back to my original present request. I need the working wood tree first
before it is worth trying to change over all that data in TAXA.
On to coding... since what you're doing is fundamentally simiar to a
family tree and since that's a more common application, you might look
into some of the apps already made that handle people's family trees.
There's a family tree data format called "GEDCOM" you might look into and
there's at least one free PHP based family tree app called PHPGedView:
http://www.phpgedview.net/
If you really wanted to roll your own, then you could also research methods
of handling threaded conversations like on message boards, since that's
going to be a similar algorithm.. with parent and child messages/data
which also allows sibling messages (children of same parents).
Interesting thoughts --- although the parallel exists only to a point. Also,
I might muse ...... which is faster, studying a lot of code for what are other
applications or working on coding for the real need. I actually do have some
past code of a botanical tree that I am studying, too.
I had a complete system crash (not even a visible Windows directory!) last
month. I am finally back up but with all kinds of havoc to my old files.
This work is not for a paying client and I am looking for work, far from being
retired, so time can be limited and spotty on when I can work on my TAXA
project. My presence could be of necessity spotty at times. I will be
concentrating especially when I do have time on my original requirements of:
- Listings at any one level allowing to choose one
- Displaying data on that item
- Down the page, listing the next level elements that map to
that parent
item
- Each of these being active to go down to repeat this process at the
next lower level.
Once I get that far, I will be a long ways closer to actually getting
that tree made
and operational.
Best regards to all,
Bill
Good luck, however you plan on executing this. I know I didn' answer your
questions directly, but I think some of these suggestions may indirectly
answer the questions. :)
-TG
