Revision 5138
Added by Aaron Marcuse-Kubitza about 12 years ago
| test.xml.ref | ||
|---|---|---|
| 88 | 88 |
</party_id> |
| 89 | 89 |
<taxonpath_id> |
| 90 | 90 |
<taxonpath> |
| 91 |
<canon_taxonpath_id> |
|
| 92 |
<taxonpath> |
|
| 93 |
<datasource_id><party><organizationname>TNRS</organizationname></party></datasource_id> |
|
| 94 |
<identifyingtaxonomicname> |
|
| 95 |
<_join_words> |
|
| 96 |
<1> |
|
| 97 |
<_alt> |
|
| 98 |
<1>$ScientificName</1> |
|
| 99 |
<2> |
|
| 100 |
<_join_words> |
|
| 101 |
<1>$family</1> |
|
| 102 |
<2>$genus</2> |
|
| 103 |
<3>$species</3> |
|
| 104 |
<4>$Subspecies</4> |
|
| 105 |
</_join_words> |
|
| 106 |
</2> |
|
| 107 |
</_alt> |
|
| 108 |
</1> |
|
| 109 |
<2>$ScientificNameAuthor</2> |
|
| 110 |
</_join_words> |
|
| 111 |
</identifyingtaxonomicname> |
|
| 112 |
</taxonpath> |
|
| 113 |
</canon_taxonpath_id> |
|
| 91 | 114 |
<author>$ScientificNameAuthor</author> |
| 92 | 115 |
<family>$family</family> |
| 93 | 116 |
<genus>$genus</genus> |
| 94 |
<identifyingtaxonomicname> |
|
| 95 |
<_join_words> |
|
| 96 |
<1> |
|
| 97 |
<_alt> |
|
| 98 |
<1>$ScientificName</1> |
|
| 99 |
<2> |
|
| 100 |
<_join_words> |
|
| 101 |
<1>$family</1> |
|
| 102 |
<2>$genus</2> |
|
| 103 |
<3>$species</3> |
|
| 104 |
<4>$Subspecies</4> |
|
| 105 |
</_join_words> |
|
| 106 |
</2> |
|
| 107 |
</_alt> |
|
| 108 |
</1> |
|
| 109 |
<2>$ScientificNameAuthor</2> |
|
| 110 |
</_join_words> |
|
| 111 |
</identifyingtaxonomicname> |
|
| 112 | 117 |
<kingdom>$Kingdom</kingdom> |
| 113 | 118 |
<species>$species</species> |
| 114 | 119 |
<subspecies>$Subspecies</subspecies> |
| ... | ... | |
| 134 | 139 |
</path> |
| 135 | 140 |
</_simplifyPath> |
| 136 | 141 |
</VegBIEN> |
| 137 |
Inserted 23 new rows into database |
|
| 142 |
Inserted 26 new rows into database |
|
Also available in: Unified diff
mappings/VegCore-VegBIEN.csv: non-TNRS taxonpaths: Store the concatenated identifyingtaxonomicname in a separate taxonpath owned by the TNRS datasource, so that it will match up with (and create a link to) the corresponding submitted TNRS name's taxonpath. This in turn is linked to the TNRS-determined accepted name, thus creating a three-level hierarchy of datasource name -> concatenated name -> accepted name.