Login | Datasets | Logout
Jump to... Home PLOT search PLANT search COMMUNITY search Simple search Manage datasets Tutorial About FAQ ------- Site map VegBranch Data dictionary ERD

51010

VegBank Data Dictionary: Tables

Search for a VegBank Table (enter a word, field name, etc.):    <<Hide search Match any word Match whole words only Search for VegBank Table >>

Search VegBank Fields Here

Show field labels | Show database names

DB Table Name	plantLineage
Table	Plant Lineage
Notes	This table stores tracks the lineage of plant taxon concepts.
Field DB Field Name Req'd? Data Type Misc Flag List? Definition ID PLANTLINEAGE_ID no serial PK no Database assigned value to each unique record in the plantLineage table. Child Plant Status childPlantStatus_ID required Integer FK no This is the foreign key into the plantStatus table "pointing" to a child concept. Parent Plant Status parentPlantStatus_ID required Integer FK no This is the foreign key into the plantStatus table "pointing" to a parent concept.

 

DB Table Name	plantName
Table	Plant Name
Notes	This table stores plant names
Field DB Field Name Req'd? Data Type Misc Flag List? Definition ID PLANTNAME_ID no serial PK no Database assigned value to each unique record in the plantName table. Plant Name plantName required varchar (255) n/a no The plant name. Reference reference_ID no Integer FK no Foreign key into the reference table to identify the original source of the name (usually the type description). Date Entered dateEntered no Date n/a no Field stores the date that the name was entered into the database.

 

DB Table Name	plantStatus
Table	Plant Status
Notes	This table store the status of a community concept as perceived by a party at a time.
Field DB Field Name Req'd? Data Type Misc Flag List? Definition ID PLANTSTATUS_ID no serial PK no Database assigned value to each unique record in the plantStatus table. Plant Concept PLANTCONCEPT_ID required Integer FK no Foreign key to identify the concept to which a party assigns a status Reference reference_ID no Integer FK no Link to a reference where the status was reported Plant Concept Status plantConceptStatus required varchar (20) n/a closed Status of the concept by the party (accepted, not accepted, undetermined) Start Date startDate required Date n/a no This is the date for which the status assignment by the party started. Stop Date stopDate no Date n/a no This is the date for which the status assignment by the party ended. Plant Party Comments plantPartyComments no text n/a no Comments by party providing rationale for status assignment Plant Parent plantParent_ID no Integer FK no The plantParent is a recursive key to the concept of the parent level in the classification hierarchy. For example if this plantConcept were at the genus level the plantParent would be the plantConcept that is the family level (or subfamily level). Plant Level plantLevel no varchar (80) n/a closed The classLevel attribute specifies a level in the taxonomic hierarchy that a class belongs. Party PARTY_ID required Integer FK no Foreign key that identifies the party that made the status assignment Accession Code accessionCode no varchar (100) n/a no Code that uniquely references this record, allowing reference to this record for this version of this database. Better than a primary key, which is automatically generated by a database and not globally unique. VegBank Accession codes are only generated by VegBank, and therefore data integrity can be guaranteed, unlike with a primary key (number).

 

DB Table Name	plantUsage
Table	Plant Usage
Notes	This table links a plant name with a concept.
Field DB Field Name Req'd? Data Type Misc Flag List? Definition ID PLANTUSAGE_ID no serial PK no Database assigned value to each unique record in the plantUsage table. Plant Name PLANTNAME_ID required Integer FK no This field is the foreign key into the plantName table. Usage Start usageStart no Date n/a no This is the date on which the party applied the name to the concept. Usage Stop usageStop no Date n/a no This is the date on which the party ceased to apply the name to the concept. Plant Name Status plantNameStatus no varchar (20) n/a closed This field shows the status of the application of the name to the concept by the party (standard, not standard, undetermined). Class System classSystem no varchar (50) n/a open This is the name of the classification system wherein the name is applied (e.g., EnglishCommon or Scientific). Plant Status PLANTSTATUS_ID no Integer FK no Plant Status which applies to this plantUsage.

 

DB Table Name	address
Table	Address
Notes	This table contains the postal address, email address and/or organizational affiliation for a parties at the time of a plot event.
Field DB Field Name Req'd? Data Type Misc Flag List? Definition ID ADDRESS_ID no serial PK no Database generated identifier assigned to each unique party address (note that a single party may have multiple addresses but that only one may be 'current'). Party party_ID required Integer FK no Link to the party to which this address applies Organization organization_ID no Integer FK no Link to an organization with which a party is affiliated Organization Position orgPosition no varchar (50) n/a no Position of party within organization. Email email no varchar (100) n/a no email address Delivery Point deliveryPoint no varchar (200) n/a no Address line for the location (Street name, box number, suite). City city no varchar (50) n/a no City of the location. Administrative Area administrativeArea no varchar (50) n/a no State, province of the location. Postal Code postalCode no varchar (10) n/a no Zip code or other postal code. Country country no varchar (50) n/a no Country of the physical address. Address is Current? currentFlag no Boolean n/a no This flag signifies whether the address is the current address of the party. Address Start Date addressStartDate no Date n/a no The first database date on which the address/organization information applied (have a discrete date on which address is known to applied - not necessarily the first date on which the address applied).

 

DB Table Name	aux_Role
Table	Role
Notes	This table stores valid role codes for use in contributor tables
Field DB Field Name Req'd? Data Type Misc Flag List? Definition ID ROLE_ID no serial PK no Database assigned value for a unique role code Role Code roleCode required varchar (30) n/a no constraining list of role codes for *Contributor tables Role Description roleDescription no varchar (200) n/a no Description of the role Accession Code accessionCode no varchar (100) n/a no Code that uniquely references this record, allowing reference to this record for this version of this database. Better than a primary key, which is automatically generated by a database and not globally unique. VegBank Accession codes are only generated by VegBank, and therefore data integrity can be guaranteed, unlike with a primary key (number).

 

DB Table Name	reference
Table	Reference
Notes	This table stores information about references cited within the database
Field DB Field Name Req'd? Data Type Misc Flag List? Definition ID reference_ID required serial PK no Primary key for the reference table. Short Name shortName no varchar (250) n/a no The 'shortName' field provides a concise or abbreviated name that describes the resource that is being documented. Full Text fulltext no text n/a no Full Text of the reference citation. Reference Type referenceType no varchar (250) n/a closed Describes the type of reference this generic type is being used to represent. Examples: book, journal article, web page. Title title no varchar (250) n/a no The formal title given to the work by its author or publisher. The 'title' field provides a description of the resource that is being documented that is long enough to differentiate it from other similar resources. Title Superior titleSuperior no varchar (250) n/a no A second, higher order title where appropriate, which in the case of a reference to a chapter is the Book title, and in the case of a Conference Presentation is the Name of the Conference. Publication Date pubDate no Date n/a no The 'pubDate' field represents the date that the resource was published. The format should be represented as: CCYY, which represents a 4 digit year, or as CCYY-MM-DD, which denotes the full year, month, and day. Note that month and day are optional components. Formats must conform to ISO 8601. For example: 1999-10-26 Access Date accessDate no Date n/a no The date the resource being referenced was accessed. This is useful if the resource is could be changed after formal publication, such as web sites or databases. Conference Date conferenceDate no Date n/a no The date the conference was held. Reference Journal referenceJournal_ID no Integer FK no Foreign key into the journal table to identify the journal of this reference. Volume volume no varchar (250) n/a no The volume field is used to describe the volume of the journal in which the article appears. Issue issue no varchar (250) n/a no The issue field is used to describe the issue of the journal in which the article appears. Page Range pageRange no varchar (250) n/a no The page range field is used for the beginning and ending pages of the journal article that is being documented. Total Pages totalPages no Integer n/a no The total pages field is used to describe the total number of pages in the book that is being described. Publisher publisher no varchar (250) n/a no The organization that physically put together the report and publishes it. Publication Place publicationPlace no varchar (250) n/a no The location at which the work was published. This is usually the name of the city in which the publishing house produced the work. ISBN isbn no varchar (250) n/a no The ISBN, or International Standard Book Number that has been assigned to this literature resource. Edition edition no varchar (250) n/a no The edition field is to document the edition of the generic reference type that is being described. Number Of Volumes numberOfVolumes no Integer n/a no Number of volumes in a collection Chapter Number chapterNumber no Integer n/a no The chapter number of the chapter of a book that is being described. Report Number reportNumber no Integer n/a no The report number field is used to describe the unique identification number that has been issued by the report institution for the report being described. Communication Type communicationType no varchar (250) n/a no The type of personal communication. Could be an email, letter, memo, transcript of conversation either hardcopy or online. Degree degree no varchar (250) n/a no The degree field is used to describe the name or degree level for which the thesis was completed. URL url no text n/a no A URL (Uniform Resource Locator) from which this resource can be downloaded or additional information can be obtained. DOI doi no text n/a no A Digital Object Identifier - a digital identifier for any object of intellectual property. A DOI provides a means of persistently identifying a piece of intellectual property on a digital network and associating it with related current data. (www.doi.org) Additional Information additionalInfo no text n/a no This field provides any information that is not characterized by the other resource metadata fields. Example: Copyright 2001, Robert Warner Accession Code accessionCode no varchar (100) n/a no Code that uniquely references this record, allowing reference to this record for this version of this database. Better than a primary key, which is automatically generated by a database and not globally unique. VegBank Accession codes are only generated by VegBank, and therefore data integrity can be guaranteed, unlike with a primary key (number).

 

DB Table Name	referenceAltIdent
Table	Reference Alternate Identifier
Notes	This table stores information about identifiers that can be used to indicate a particular reference.
Field DB Field Name Req'd? Data Type Misc Flag List? Definition ID referenceAltIdent_ID required serial PK no Primary key for the referenceAltIdent table. Reference reference_ID required Integer FK no Foreign key into the reference table to indicate which reference is referenced by this alternate identifier. System system no varchar (250) n/a no The data management system within which an identifier is in scope and therefore unique. This is typically a URL (Uniform Resource Locator) that indicates a data management system. All identifiers that share a system must be unique. In other words, if the same identifier is used in two locations with identical systems, then by definition the objects at which they point are in fact the same object. Example(s): http://metacat.somewhere.org/svc/mc/ Identifier identifier required varchar (250) n/a no An additional, secondary identifier for this entity. The primary identifier belongs in the reference table, but additional identifiers that are used to label this entity, possibly from different data management systems, can be listed here. Example: VCR3465

 

DB Table Name	referenceContributor
Table	Reference Contributor
Notes	This table links reference parties with references and shows how a contribution was made by the party.
Field DB Field Name Req'd? Data Type Misc Flag List? Definition ID referenceContributor_ID required serial PK no Primary key for the referenceContributor table. Reference reference_ID required Integer FK no Foreign key into the reference table to indicate which reference is referenced by this alternate identifier. Reference Party referenceParty_ID required Integer FK no Foreign key into the referenceParty table to indicate which person contributed. Role Type roleType no varchar (250) n/a closed Use this field to describe the role the party played with respect to the resource. Some potential roles include technician, reviewer, principal investigator, and many others. Position position no Integer n/a no Numerical order in which this contributor's name should be in the order of contributors, if applicable. Examples: 1 [for the first author], 2, [for the second author], etc.

 

DB Table Name	referenceParty
Table	Reference Party
Notes	This table stores information about parties that contributed to a reference.
Field DB Field Name Req'd? Data Type Misc Flag List? Definition ID referenceParty_ID required serial PK no Primary key for the referenceParty table. Reference Party Type type no varchar (250) n/a no Type of Party this record refers to: usually person or institution. Type determines rules for which fields must be completed. Position Name positionName no varchar (250) n/a no This field is intended to be used instead of a particular person or full organization name. If the associated person that holds the role changes frequently, then Position Name would be used for consistency. Note that this field, used in conjunction with 'organizationName' and 'individualName' make up a single logical originator. Because of this, an originator with only the individualName of 'Joe Smith' is NOT the same as an originator with the name of 'Joe Smith' and the organizationName of 'NSF'. Also, the positionName should not be used in conjunction with individualName unless only that individual at that position would be considered an originator for the data package. If a positionName is used in conjunction with an organizationName, then that implies that any person who currently occupies said positionName at organizationName is the originator of the data package. Example(s): Niwot Ridge Data Manager Salutation salutation no varchar (250) n/a no The salutation field is used in addressing an individual with a particular title, such as Dr., Ms., Mrs., Mr., etc. Given Name givenName no varchar (250) n/a no The given name field is used for the all names, except the surname, of the individual associated with the resource. Possible usages include: first name and middle name, first name and middle initials, first name, etc. Example(s): Jo, Jo R., Jo R.W., John Robert Peter Surname surname no varchar (250) n/a no The surname field is used for the last name of the individual associated with the resource. Suffix suffix no varchar (250) n/a no A suffix or suffix abbreviation that follows a name. Examples: Jr., Senior, III, etc. Organization Name organizationName no varchar (250) n/a no The responsible party field contains the full name of the organization that is associated with the resource. This field is intended to describe which institution or overall organization is associated with the resource being described. Note that this field, used in conjunction with 'individualName' and 'positionName' make up a single logical originator. Because of this, an originator with only the individualName of 'Joe Smith' is NOT the same as an originator with the name of 'Joe Smith' and the organizationName of 'NSF'. Also, the positionName should not be used in conjunction with individualName unless only that individual at that position would be considered an originator for the data package. If a positionName is used in conjunction with an organizationName, then that implies that any person who currently occupies said positionName at organizationName is the originator of the data package. Example(s): National Center for Ecological Analysis and Synthesis Current Name currentParty_ID no Integer FK no Recursive Foreign key into the referenceParty table to indicate the current name of the party. Accession Code accessionCode no varchar (100) n/a no Code that uniquely references this record, allowing reference to this record for this version of this database. Better than a primary key, which is automatically generated by a database and not globally unique. VegBank Accession codes are only generated by VegBank, and therefore data integrity can be guaranteed, unlike with a primary key (number).