Revision 5136
Added by Aaron Marcuse-Kubitza about 12 years ago
vegbien.my.sql | ||
---|---|---|
839 | 839 |
CREATE TABLE taxonpath ( |
840 | 840 |
taxonpath_id int(11) NOT NULL, |
841 | 841 |
datasource_id int(11) NOT NULL, |
842 |
plantcode text,
|
|
842 |
identifyingtaxonomicname text,
|
|
843 | 843 |
canon_taxonpath_id int(11), |
844 | 844 |
taxon_id int(11), |
845 | 845 |
taxonomicname text, |
... | ... | |
871 | 871 |
|
872 | 872 |
|
873 | 873 |
-- |
874 |
-- Name: COLUMN taxonpath.plantcode; Type: COMMENT; Schema: public; Owner: -
|
|
874 |
-- Name: COLUMN taxonpath.identifyingtaxonomicname; Type: COMMENT; Schema: public; Owner: -
|
|
875 | 875 |
-- |
876 | 876 |
|
877 | 877 |
|
... | ... | |
4140 | 4140 |
|
4141 | 4141 |
|
4142 | 4142 |
-- |
4143 |
-- Name: taxonpath_unique_within_datasource_by_code; Type: INDEX; Schema: public; Owner: -; Tablespace:
|
|
4143 |
-- Name: taxonpath_unique_within_datasource_by_identifying_name; Type: INDEX; Schema: public; Owner: -; Tablespace:
|
|
4144 | 4144 |
-- |
4145 | 4145 |
|
4146 | 4146 |
|
Also available in: Unified diff
schemas/vegbien.sql: taxonpath: Renamed plantcode to identifyingtaxonomicname so that it can be used to store the concatenated taxonomicname that gets scrubbed. This enables ignoring the name components when the full name is specified, so that when a TNRS submitted name's matched components are included in its taxonpath, this will not prevent a datasource's concatenated name (without the matched components) from matching up with the corresponding TNRS submitted name.