Revision 11965
Added by Aaron Marcuse-Kubitza over 10 years ago
| schema.sql | ||
|---|---|---|
| 393 | 393 |
CREATE VIEW "taxon_scrub.scrubbed_unique_taxon_name.*" AS |
| 394 | 394 |
SELECT tnrs."Name_submitted" AS scrubbed_unique_taxon_name, |
| 395 | 395 |
tnrs."Name_matched_rank" AS scrubbed_taxon_rank, |
| 396 |
tnrs."Name_matched_accepted_family" AS scrubbed_family,
|
|
| 396 |
COALESCE(tnrs."Name_matched_accepted_family", tnrs."Family_matched") AS scrubbed_family,
|
|
| 397 | 397 |
tnrs."Genus_matched" AS scrubbed_genus, |
| 398 | 398 |
tnrs."Specific_epithet_matched" AS scrubbed_specific_epithet, |
| 399 | 399 |
tnrs."Infraspecific_rank" AS scrubbed_infraspecific_rank, |
| ... | ... | |
| 404 | 404 |
|
| 405 | 405 |
|
| 406 | 406 |
-- |
| 407 |
-- Name: VIEW "taxon_scrub.scrubbed_unique_taxon_name.*"; Type: COMMENT; Schema: TNRS; Owner: - |
|
| 408 |
-- |
|
| 409 |
|
|
| 410 |
COMMENT ON VIEW "taxon_scrub.scrubbed_unique_taxon_name.*" IS 'scrubbed_family: Name_matched_accepted_family was missing from the TNRS results at one point, so Family_matched is used as a workaround to populate this. the workaround is for *accepted names only*, as no opinion names do not have an Accepted_name_family to prepend to the scrubbed name to parse.'; |
|
| 411 |
|
|
| 412 |
|
|
| 413 |
-- |
|
| 407 | 414 |
-- Name: taxon_scrub; Type: VIEW; Schema: TNRS; Owner: - |
| 408 | 415 |
-- |
| 409 | 416 |
|
Also available in: Unified diff
bugfix: inputs/.TNRS/schema.sql: scrubbed_family: Name_matched_accepted_family was missing from the TNRS results at one point, so we are now using Family_matched as a workaround to populate this. the workaround is for accepted names only, as no opinion names do not have an Accepted_name_family to prepend to the scrubbed name to parse.