Revision 5465
Added by Aaron Marcuse-Kubitza over 11 years ago
| test.xml.ref | ||
|---|---|---|
| 64 | 64 |
<taxondetermination> |
| 65 | 65 |
<taxonconcept_id> |
| 66 | 66 |
<taxonconcept> |
| 67 |
<canon_concept_id>
|
|
| 67 |
<matched_concept_id>
|
|
| 68 | 68 |
<taxonconcept> |
| 69 | 69 |
<creator_id> |
| 70 | 70 |
<party> |
| ... | ... | |
| 80 | 80 |
</_join_words> |
| 81 | 81 |
</identifyingtaxonomicname> |
| 82 | 82 |
</taxonconcept> |
| 83 |
</canon_concept_id>
|
|
| 83 |
</matched_concept_id>
|
|
| 84 | 84 |
<family>$family</family> |
| 85 | 85 |
<genus>$genus</genus> |
| 86 | 86 |
<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