Revision 6759
Added by Aaron Marcuse-Kubitza almost 12 years ago
| test.xml.ref | ||
|---|---|---|
| 11 | 11 |
<taxonoccurrence> |
| 12 | 12 |
<aggregateoccurrence> |
| 13 | 13 |
<plantobservation> |
| 14 |
<sourceaccessioncode>$STEMCOUNT_ID</sourceaccessioncode>
|
|
| 14 |
<sourceaccessioncode>$STEMLOCATION_ID</sourceaccessioncode>
|
|
| 15 | 15 |
<stemobservation> |
| 16 | 16 |
<authorstemcode>$stemCode</authorstemcode> |
| 17 | 17 |
<sourceaccessioncode>$STEMLOCATION_ID</sourceaccessioncode> |
| ... | ... | |
| 19 | 19 |
<yposition_m>$stemYPosition</yposition_m> |
| 20 | 20 |
</stemobservation> |
| 21 | 21 |
</plantobservation> |
| 22 |
<sourceaccessioncode>$STEMCOUNT_ID</sourceaccessioncode> |
|
| 22 | 23 |
</aggregateoccurrence> |
| 23 |
<sourceaccessioncode>$STEMCOUNT_ID</sourceaccessioncode> |
|
| 24 | 24 |
</taxonoccurrence> |
| 25 | 25 |
</locationevent> |
| 26 | 26 |
</location> |
Also available in: Unified diff
inputs/CVS/: Joined together taxonImportance and stemCount tables to create stemCount_, because stemCount actually stores stem abundance by size, rather than grouping stems by organism (http://vegbankdev.nceas.ucsb.edu/vegbank/views/dba_tabledescription_detail.jsp?view=detail&wparam=stemcount&entity=dba_tabledescription&where=where_tablename), and is thus an AggregateOccurrence-related table along with taxonImportance