Revision 5465
Added by Aaron Marcuse-Kubitza over 11 years ago
| test.xml.ref | ||
|---|---|---|
| 9 | 9 |
<taxondetermination> |
| 10 | 10 |
<taxonconcept_id> |
| 11 | 11 |
<taxonconcept> |
| 12 |
<canon_concept_id>
|
|
| 12 |
<matched_concept_id>
|
|
| 13 | 13 |
<taxonconcept> |
| 14 | 14 |
<creator_id> |
| 15 | 15 |
<party> |
| ... | ... | |
| 19 | 19 |
</creator_id> |
| 20 | 20 |
<identifyingtaxonomicname>$scientificName</identifyingtaxonomicname> |
| 21 | 21 |
</taxonconcept> |
| 22 |
</canon_concept_id>
|
|
| 22 |
</matched_concept_id>
|
|
| 23 | 23 |
<taxonomicname>$scientificName</taxonomicname> |
| 24 | 24 |
</taxonconcept> |
| 25 | 25 |
</taxonconcept_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