Revision 5465
Added by Aaron Marcuse-Kubitza over 11 years ago
| test.xml.ref | ||
|---|---|---|
| 99 | 99 |
</party_id> |
| 100 | 100 |
<taxonconcept_id> |
| 101 | 101 |
<taxonconcept> |
| 102 |
<canon_concept_id>
|
|
| 102 |
<matched_concept_id>
|
|
| 103 | 103 |
<taxonconcept> |
| 104 | 104 |
<creator_id> |
| 105 | 105 |
<party> |
| ... | ... | |
| 136 | 136 |
</_join_words> |
| 137 | 137 |
</identifyingtaxonomicname> |
| 138 | 138 |
</taxonconcept> |
| 139 |
</canon_concept_id>
|
|
| 139 |
</matched_concept_id>
|
|
| 140 | 140 |
<author>$scientificNameAuthorship</author> |
| 141 | 141 |
<creator_id> |
| 142 | 142 |
<_simplifyPath> |
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