Bug #870

New XML export and import into the VegBank system

Added by Michael Lee almost 20 years ago. Updated over 17 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


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

Related issues

Blocks VegBank - Bug #740: New XML -- DESIGNResolved11/13/2002

Blocked by VegBank - Bug #739: QA for New XML (1.0.2) loading (Lee), then Fix errors in loading process (Farrell/Anderson)Resolved11/13/2002

Blocks VegBank - Bug #786: Update the Plots datamodel to allow for individual treesResolved11/13/2002

Blocks VegBank - Bug #920: add accession codes for concepts / partiesResolved12/02/2002

Blocks VegBank - Bug #1079: Revise DB model to better deal with idiosyncratic taxaResolved05/29/2003


#1 Updated by Michael Lee over 19 years ago

not sure how much work we want to put into the current XML format, given that we
recognize the need to revise the DTD and XML.

#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

#4 Updated by Gabriel Farrell almost 19 years ago

This is complete

#5 Updated by Michael Lee over 17 years ago

changed from components that are to be deleted to "misc" so that bugs don't get
deleted with component. Sorry for all the email.

#6 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 870

Also available in: Atom PDF