For now, we can store data on a simple spreadsheet. Data points can be
(For each PARENT COLONY coral, have one table with entries of)
- original frag id (just some name or number, original donater can name it, just for fun)
- donater or 'parent'' reefer
- recipient reefer
- date of donatation
- size ? (just for reference)
in another table (one global table), we can track
- reefer name
- reefer ID# (to normalize tables) (if this forum has User ID numbers, that would make this simpler)
- location
- (whatever else they want).
Each donated frag (frag of original coral id #X) would have one entry, so we would track the fragged piece itself. Very easy data structure. With that data (reefers can have an arbitrary ID#) you can map the lineage, and also draw/track frag location by recipient reefer.
This is actually much easier than geneology, because frags have only one parent! If, by some crazy chance, a frag somehow sexually reproduces, we call it a new parent-colony.
Easy to implement in Excel, which is simple to later import into an actual DB (I favour MySQL for its freeness)
One person can be keeper of the Reefer Table, with reefer names and ID updated in a sticky post on this forum (that is the only global unique infor we really need) and each "chain originator" can take a copy of the spreadsheet template, kept in the same posting. If the chain originator does not want to maintain the data, that's fine, someone else can volunteer to do it (I could do it), just as a way to keep the threads from going nuts with data. We could try that to start until something more automatic evolves.
We can start a new thread in this forum with suggestions, with some sample spreadsheets. Basically an RFC thread for this purpose (Request For Vomments).
V
PS. Sorry, who was the geek again?