Actions
Bug #1862
closedtreat plantConcept and commConcept matching accCodes differently
Start date:
01/10/2005
Due date:
% Done:
0%
Estimated time:
Bugzilla-Id:
1862
Description
- Request: not crucial at the moment, but may be later
- normal behaviour: when a matching element is found, skip it in the loading
process-- don't add it or its children - requested new behaviour:
- for observation (with AccCode found in vegbank - i.e. VB.), check to see if
commClasses is in XML that are not found in VegBank (i.e. accCode != 'VB.') - for observations found, and taxonObservations found, check to see if
taxonInterpretations in XML that are not found in VegBank (have to use
Party+Concept+Date) - for plant/commConcept, check to see if commStatus is in the XML that isn't in
VegBank -- no AccCodes to match by, have to use Party+Concept+Date (sorry!)
- the new behaviour would allow people to submit a set of "party perspectives"
of a plant/comm that apply to extant concepts, as well as bulk annotate
observations as belonging to certain communities. - no xml for these yet, sorry?-- ask me when you need them
Updated by Michael Lee over 17 years ago
I don't think this would be all that complex for new commClasses of an observation -- it's just one table to look up and the commClass bit is hardcoded into loadTreeToDB. Also, could look up 2 levels to TaxonObs then TaxonInterpretation too. New AccCode needs to be setup and working for that to work.
Updated by Michael Lee over 17 years ago
observation is now handled-- you can add new taxonInterpretations and commClass records to old observations via the XML Loader. VegBranch now must export data in this fashion.
Updated by Michael Lee over 17 years ago
plantStatus and commStatus are now handled this way. These entities plus taxonInterpretation are added to userDAtasetItems on load, and are now citable.
Actions