Revision 5465
Added by Aaron Marcuse-Kubitza over 11 years ago
test.xml.ref | ||
---|---|---|
18 | 18 |
<taxondetermination> |
19 | 19 |
<taxonconcept_id> |
20 | 20 |
<taxonconcept> |
21 |
<canon_concept_id>
|
|
21 |
<matched_concept_id>
|
|
22 | 22 |
<taxonconcept> |
23 | 23 |
<creator_id> |
24 | 24 |
<party> |
... | ... | |
47 | 47 |
</_join_words> |
48 | 48 |
</identifyingtaxonomicname> |
49 | 49 |
</taxonconcept> |
50 |
</canon_concept_id>
|
|
50 |
</matched_concept_id>
|
|
51 | 51 |
<family>$Family</family> |
52 | 52 |
<genus>$Genus</genus> |
53 | 53 |
<parent_id> |
... | ... | |
129 | 129 |
<isoriginal>true</isoriginal> |
130 | 130 |
<taxonconcept_id> |
131 | 131 |
<taxonconcept> |
132 |
<canon_concept_id>
|
|
132 |
<matched_concept_id>
|
|
133 | 133 |
<taxonconcept> |
134 | 134 |
<creator_id> |
135 | 135 |
<party> |
... | ... | |
139 | 139 |
</creator_id> |
140 | 140 |
<identifyingtaxonomicname>$authorplantname</identifyingtaxonomicname> |
141 | 141 |
</taxonconcept> |
142 |
</canon_concept_id>
|
|
142 |
</matched_concept_id>
|
|
143 | 143 |
<taxonomicname>$authorplantname</taxonomicname> |
144 | 144 |
</taxonconcept> |
145 | 145 |
</taxonconcept_id> |
Also available in: Unified diff
schemas/vegbien.sql: taxonconcept: Renamed canon_concept_id to matched_concept_id, because this is actually the closest-match taxonconcept in the match hierarchy (datasource concept -> parsed concept -> matched concept -> accepted concept) rather than the accepted synonym, which goes in accepted_concept_id