Revision 5465
Added by Aaron Marcuse-Kubitza over 11 years ago
| test.xml.ref | ||
|---|---|---|
| 75 | 75 |
</party_id> |
| 76 | 76 |
<taxonconcept_id> |
| 77 | 77 |
<taxonconcept> |
| 78 |
<canon_concept_id>
|
|
| 78 |
<matched_concept_id>
|
|
| 79 | 79 |
<taxonconcept> |
| 80 | 80 |
<creator_id> |
| 81 | 81 |
<party> |
| ... | ... | |
| 112 | 112 |
</_alt> |
| 113 | 113 |
</identifyingtaxonomicname> |
| 114 | 114 |
</taxonconcept> |
| 115 |
</canon_concept_id>
|
|
| 115 |
</matched_concept_id>
|
|
| 116 | 116 |
<author>$scientificNameAuthorship</author> |
| 117 | 117 |
<creator_id> |
| 118 | 118 |
<_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