Revision 5308
Added by Aaron Marcuse-Kubitza about 12 years ago
| schemas/vegbien.sql | ||
|---|---|---|
| 1164 | 1164 |
-- Name: COLUMN taxonconcept.canon_taxonconcept_id; Type: COMMENT; Schema: public; Owner: - |
| 1165 | 1165 |
-- |
| 1166 | 1166 |
|
| 1167 |
COMMENT ON COLUMN taxonconcept.canon_taxonconcept_id IS 'The taxonconcept containing the accepted synonym of this taxonconcept. taxonconcepts should be linked in a four-level hierarchy of datasource concept -> concatenated name -> parsed name -> accepted name. A previously-accepted name''s concept should be further linked to the synonym that has replaced it.
|
|
| 1167 |
COMMENT ON COLUMN taxonconcept.canon_taxonconcept_id IS 'The taxonconcept containing the accepted synonym of this taxonconcept. taxonconcepts should be linked in a four-level hierarchy of datasource concept -> parsed concept -> matched concept -> accepted concept. A previously-accepted name''s concept should be further linked to the synonym that has replaced it.
|
|
| 1168 | 1168 |
|
| 1169 | 1169 |
To indicate a synonym between taxonconcepts of different sources, choose one taxonconcept to be authoritative and point the other taxonconcept to it using this field. |
| 1170 | 1170 |
|
Also available in: Unified diff
schemas/vegbien.sql: taxonconcept.canon_taxonconcept_id: Changed four-level hierarchy to use "parsed concept" and "matched concept" instead of concatenated and parsed, because the directly-parsed name components actually go in level 2 of the hierarchy (the TNRS input name), while the name components based on the matched taxon concept go in level 3