Revision 5138
Added by Aaron Marcuse-Kubitza about 12 years ago
test.xml.ref | ||
---|---|---|
116 | 116 |
</party_id> |
117 | 117 |
<taxonpath_id> |
118 | 118 |
<taxonpath> |
119 |
<canon_taxonpath_id> |
|
120 |
<taxonpath> |
|
121 |
<datasource_id><party><organizationname>TNRS</organizationname></party></datasource_id> |
|
122 |
<identifyingtaxonomicname> |
|
123 |
<_join_words> |
|
124 |
<1> |
|
125 |
<_alt> |
|
126 |
<1>$ScientificName</1> |
|
127 |
<2> |
|
128 |
<_join_words> |
|
129 |
<1>$Family</1> |
|
130 |
<2>$Genus</2> |
|
131 |
<3>$Species</3> |
|
132 |
<4>$Subspecies</4> |
|
133 |
</_join_words> |
|
134 |
</2> |
|
135 |
</_alt> |
|
136 |
</1> |
|
137 |
<2>$ScientificNameAuthor</2> |
|
138 |
</_join_words> |
|
139 |
</identifyingtaxonomicname> |
|
140 |
</taxonpath> |
|
141 |
</canon_taxonpath_id> |
|
119 | 142 |
<author>$ScientificNameAuthor</author> |
120 | 143 |
<class>$Class</class> |
121 | 144 |
<family>$Family</family> |
122 | 145 |
<genus>$Genus</genus> |
123 |
<identifyingtaxonomicname> |
|
124 |
<_join_words> |
|
125 |
<1> |
|
126 |
<_alt> |
|
127 |
<1>$ScientificName</1> |
|
128 |
<2> |
|
129 |
<_join_words> |
|
130 |
<1>$Family</1> |
|
131 |
<2>$Genus</2> |
|
132 |
<3>$Species</3> |
|
133 |
<4>$Subspecies</4> |
|
134 |
</_join_words> |
|
135 |
</2> |
|
136 |
</_alt> |
|
137 |
</1> |
|
138 |
<2>$ScientificNameAuthor</2> |
|
139 |
</_join_words> |
|
140 |
</identifyingtaxonomicname> |
|
141 | 146 |
<kingdom>$Kingdom</kingdom> |
142 | 147 |
<order>$Order</order> |
143 | 148 |
<phylum>$Phylum</phylum> |
... | ... | |
222 | 227 |
</path> |
223 | 228 |
</_simplifyPath> |
224 | 229 |
</VegBIEN> |
225 |
Inserted 26 new rows into database |
|
230 |
Inserted 29 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.