VegBank

This is a duplicate of a bug that was fixed by Gabe in early Jan. 2002.

This bug actually deals with the implementation of the new XML that has yet to
be designed.

This bug should be marked resolved when the new XML is implemented and working
with the VegBank system.

Sorry for the lack of clarity.

First, Michael should QA/QC the new XML loading into VegBank. Any errors
should be reported and this bug passed back to Gabe or Mark so that these
errors can be fixed.

find XML to test this here:
http://vegbank.nceas.ucsb.edu/xml/

http://vegbank.nceas.ucsb.edu/xml/vegbank-data-example-verbeta1-1.xml
is should conform to Gabe's initial design of the loader

http://vegbank.nceas.ucsb.edu/xml/vegbank_example_ver1.0.1.xml
is a simple example for the current 1.0.1 schema.

Almost no errors! REally great loader. Need to test most diverse plots, still.
First analysis:
missing in export:
project start date [in db]
3 stratumTypes::children of stratumMethod
party/address not in xml
taxonObs/reference.pubdate not in xml
<plantConcept.accessionCode>VB.92435</plantConcept.accessionCode>: not correct.
This was loaded in Vegtest- no accession code should be
made. Furthermore, this is not the right style for a plantCocnept acc code :
VB.PC.162.ACRU is right.

Some aspects of #5 addressed ...

Dates now work,
Children of Stratumeethod exported ( and coverMethod )
Format of PlantConcept and Commconcept accessionCode now correct

Also, if loading to vegtest no accessionCodes loaded, see my e-mail about this
however, as this results in other things being broken and I think there is a
better way.

need to do this again for new XML

• Bug 743 has been marked as a duplicate of this bug. ***

First run at QA on the new XML import has been completed:
--all entities were imported into the database correctly, with 2 minor bugs--

bug 1) duplications : we have duplications of stratum records, stratumType,
aux_role, etc. being added. These were avoided previously by logic that checked
for an extant record in vegbank that matched all attributes. This is not
something that we can presume, though. So, this logic removed, but the
duplications are now being added. So, a hash table or something needs to keep
track of which XML elements have already been added (using table & PK) and what
VegBank element they correspond to (PK).

bug 2) taxonInterpretation.plantNAME_ID not being populated. This field, alone
as far as I could tell, contained data in the XML upload, but was not filled in
during the import. I cannot say why that is.

Short run through of example data XML sets have worked perfectly. Should do a
detailed "every field" test, as well.

successful QA completed, focusing on FK's for each observation, compiling the
total number of related entities and comparing for source (vegbranch) and
destination (vegbank). Matches were 100% correct, except for classContribs,
which might not have been written into XML. Checking on that last aspect.

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

Original Bugzilla ID was 739