Revision 5463
Added by Aaron Marcuse-Kubitza about 12 years ago
| schemas/vegbien.my.sql | ||
|---|---|---|
| 145 | 145 |
|
| 146 | 146 |
|
| 147 | 147 |
-- |
| 148 |
-- Name: taxonconcept_canon_concept_id_self_ref(); Type: FUNCTION; Schema: public; Owner: - |
|
| 148 |
-- Name: taxonconcept_0_canon_concept_id_self_ref(); Type: FUNCTION; Schema: public; Owner: -
|
|
| 149 | 149 |
-- |
| 150 | 150 |
|
| 151 | 151 |
|
| 152 | 152 |
|
| 153 | 153 |
|
| 154 | 154 |
-- |
| 155 |
-- Name: taxonconcept_canon_concept_min_fit(); Type: FUNCTION; Schema: public; Owner: - |
|
| 155 |
-- Name: taxonconcept_1_canon_concept_min_fit(); Type: FUNCTION; Schema: public; Owner: -
|
|
| 156 | 156 |
-- |
| 157 | 157 |
|
| 158 | 158 |
|
| ... | ... | |
| 4032 | 4032 |
|
| 4033 | 4033 |
|
| 4034 | 4034 |
-- |
| 4035 |
-- Name: taxonconcept_canon_concept_id_self_ref; Type: TRIGGER; Schema: public; Owner: - |
|
| 4035 |
-- Name: taxonconcept_0_canon_concept_id_self_ref; Type: TRIGGER; Schema: public; Owner: -
|
|
| 4036 | 4036 |
-- |
| 4037 | 4037 |
|
| 4038 | 4038 |
|
| 4039 | 4039 |
|
| 4040 | 4040 |
|
| 4041 | 4041 |
-- |
| 4042 |
-- Name: taxonconcept_canon_concept_min_fit; Type: TRIGGER; Schema: public; Owner: - |
|
| 4042 |
-- Name: taxonconcept_1_canon_concept_min_fit; Type: TRIGGER; Schema: public; Owner: -
|
|
| 4043 | 4043 |
-- |
| 4044 | 4044 |
|
| 4045 | 4045 |
|
| schemas/vegbien.sql | ||
|---|---|---|
| 1190 | 1190 |
-- Name: COLUMN taxonconcept.canon_concept_id; Type: COMMENT; Schema: public; Owner: - |
| 1191 | 1191 |
-- |
| 1192 | 1192 |
|
| 1193 |
COMMENT ON COLUMN taxonconcept.canon_concept_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.
|
|
| 1193 |
COMMENT ON COLUMN taxonconcept.canon_concept_id IS 'The taxonconcept containing the closest match to 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.
|
|
| 1194 | 1194 |
|
| 1195 | 1195 |
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. |
| 1196 | 1196 |
|
Also available in: Unified diff
schemas/vegbien.sql: taxonconcept.canon_concept_id: comment: Changed "accepted synonym" to "closest match", since canon_concept_id is actually a hierarchy from datasource concept -> parsed concept -> matched concept -> accepted concept