Project

General

Profile

« Previous | Next » 

Revision 4701

schemas/vegbien.sql: plantname: Added verbatimrank to store ranks of custom taxonomic levels, such as rosids. Note that even if you specify a custom verbatimrank, you must also specify a closest-match rank from the taxonrank closed list. This ensures that every taxonomic name is placed in the correct relative order in the taxonomic hierarchy.

View differences:

schemas/vegbien.my.sql
699 699
    parent_id int(11),
700 700
    scope_id int(11),
701 701
    rank text NOT NULL,
702
    verbatimrank text,
702 703
    plantname text NOT NULL,
703 704
    description text,
704 705
    accessioncode text
......
706 707

  
707 708

  
708 709
--
710
-- Name: COLUMN plantname.rank; Type: COMMENT; Schema: public; Owner: -
711
--
712

  
713

  
714

  
715

  
716
--
709 717
-- Name: plantname_ancestor; Type: TABLE; Schema: public; Owner: -; Tablespace: 
710 718
--
711 719

  
schemas/vegbien.sql
937 937
    parent_id integer,
938 938
    scope_id integer,
939 939
    rank taxonrank NOT NULL,
940
    verbatimrank text,
940 941
    plantname text NOT NULL,
941 942
    description text,
942 943
    accessioncode text
......
944 945

  
945 946

  
946 947
--
948
-- Name: COLUMN plantname.rank; Type: COMMENT; Schema: public; Owner: -
949
--
950

  
951
COMMENT ON COLUMN plantname.rank IS 'Even if you specify a custom verbatimrank, you must also specify a closest-match rank from the taxonrank closed list.';
952

  
953

  
954
--
947 955
-- Name: plantname_ancestor; Type: TABLE; Schema: public; Owner: -; Tablespace: 
948 956
--
949 957

  

Also available in: Unified diff