Revision 5465
Added by Aaron Marcuse-Kubitza almost 12 years ago
test.xml.ref | ||
---|---|---|
70 | 70 |
</party_id> |
71 | 71 |
<taxonconcept_id> |
72 | 72 |
<taxonconcept> |
73 |
<canon_concept_id>
|
|
73 |
<matched_concept_id>
|
|
74 | 74 |
<taxonconcept> |
75 | 75 |
<creator_id> |
76 | 76 |
<party> |
... | ... | |
101 | 101 |
</_alt> |
102 | 102 |
</identifyingtaxonomicname> |
103 | 103 |
</taxonconcept> |
104 |
</canon_concept_id>
|
|
104 |
</matched_concept_id>
|
|
105 | 105 |
<author>$Autor (revised)</author> |
106 | 106 |
<creator_id> |
107 | 107 |
<_simplifyPath> |
... | ... | |
170 | 170 |
<isoriginal>true</isoriginal> |
171 | 171 |
<taxonconcept_id> |
172 | 172 |
<taxonconcept> |
173 |
<canon_concept_id> |
|
173 |
<family>$Field family</family> |
|
174 |
<genus>$Field name</genus> |
|
175 |
<matched_concept_id> |
|
174 | 176 |
<taxonconcept> |
175 | 177 |
<creator_id> |
176 | 178 |
<party> |
... | ... | |
185 | 187 |
</_join_words> |
186 | 188 |
</identifyingtaxonomicname> |
187 | 189 |
</taxonconcept> |
188 |
</canon_concept_id> |
|
189 |
<family>$Field family</family> |
|
190 |
<genus>$Field name</genus> |
|
190 |
</matched_concept_id> |
|
191 | 191 |
<parent_id> |
192 | 192 |
<taxonconcept> |
193 | 193 |
<parent_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