Revision 5465
Added by Aaron Marcuse-Kubitza over 11 years ago
| test.xml.ref | ||
|---|---|---|
| 115 | 115 |
</party_id> |
| 116 | 116 |
<taxonconcept_id> |
| 117 | 117 |
<taxonconcept> |
| 118 |
<canon_concept_id>
|
|
| 118 |
<matched_concept_id>
|
|
| 119 | 119 |
<taxonconcept> |
| 120 | 120 |
<creator_id> |
| 121 | 121 |
<party> |
| ... | ... | |
| 142 | 142 |
</_alt> |
| 143 | 143 |
</identifyingtaxonomicname> |
| 144 | 144 |
</taxonconcept> |
| 145 |
</canon_concept_id>
|
|
| 145 |
</matched_concept_id>
|
|
| 146 | 146 |
<creator_id> |
| 147 | 147 |
<_simplifyPath> |
| 148 | 148 |
<next>creator_id</next> |
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