New XML export and import into the VegBank system
ML takes lead in testing. Will take a while, but critical before release.Mostly
working, but sometables not wired yet; perhaps not need all tables (eg stems)
#2 Updated by Michael Lee about 19 years ago
New XML needs to be imported into VegBank (coming directly as XML or as a
communication doc between VegBranch and VegBank).
New XML needs to be exportable from VegBank.
Whatever bits of the system are sensible to use the new XML for is also great,
though we need to be careful with memory issues and not creating giant XML docs
#3 Updated by Michael Lee about 19 years ago
there will be some minor changes to the xml doc due to minor changes in the
schema. These changes should be made ASAP and this XML updated accordingly.
Changes will be additional fields added to TaxonInterpretation, but this will
also make TaxonInterpretation sometimes, but rarely, a child of stemLocation.
Strange, but true. Also, we should probably add a "accessioncode" as an
attribute to entities like party and plantConcept, commConcept, reference,
which would allow us to link to these extant entites that are already in
VegBank (When known) with a short accessionCode, rather than the entire set of
concept/reference data. With the entire set of data, the XML is really really
large (2MB for one plot, 8MB for 2 plots according to samples I tried from