Data Import Fields

This page lists the possible specimen fields that can be imported into a Symbiota data portal. The type of field (text, number, etc.) is listed in the Type field. The number of characters allowed in that field is displayed in parentheses.

If the data portal is being used to displaying a “snapshot” of your data stored in your local central database, the upload file MUST have a field that serves as the unique identifier for each incoming specimen record (dbpk). This field serves a link between the source record and the snapshot record within the portal. If import is a CSV file, the first row must contain field names. Note that field names do not have to match the name used below, but there cannot be any characters ($#@&%) in the column names.

For more information about data fields, also see our Symbiota Data Fields page.

Italic = Darwin Core fields
Bold = strongly encouraged fields, though none of the fields are technically required
* = for import only, merged into another field after import

dbpkText (45)Specimen record unique identifier (primary key) of source database (record id). Barcode, occurrenceID (GUID), or a database Primary Key is ideal. Can also be catalogNumber, given that it is populated for each record and enforced as unique. Required if collection is “snapshot” of a central database. Not needed if collection is managed directly within portal.
occurrenceIdText (255)Occurrence Global Unique Identifier (GUID)
catalogNumberText (32)Barcode or Accession number
otherCatalogNumbersText (255)To take advantage of the Tag Name + Identifier system (in which you can tag an identifier/other catalog number with a specific title), enter the tag name followed by a colon and then the identifier value, e.g., “Old Accession Number: 12345”. For multiple identifiers, separate the tag name + identifiers by semicolons, e.g., “NP #: 4321; Accession #: 9876”
familyText (255)
scientificnameText (255)Scientific name w/ author; author is parsed from name
scinameText (255)Scientific name without author
genusText (255)
specificEpithetText (255)
taxonRankText (32)Rank name of infraspecific abbreviation allowed
infraspecificEpithetText (255)
scientificNameAuthorshipText (255)Author of scientific name
identifiedByText (255)
dateIdentifiedText (45)
identificationQualifierText (255)cf, aff. etc
typeStatusText (255)
recordedByText (255)Collector name
recordNumberText (45)Collector number
*recordNumberPrefixText (45)Merged into recordNumber
*recordNumberSuffixText (45)Merged into recordNumber
associatedCollectorsText (255)
eventDateDate/TimeDate collected, or earliest date when range provided
eventDate2Date/TimeLatest date collected, when a range is provided
yearInteger (4)If eventDate is null, year-month-day will be used to
monthInteger (4)build eventDate
dayInteger (4)
verbatimEventDateText (255)
substrateText (500)
occurrenceRemarksTextGeneral notes or remarks
dataGeneralizationsText (250)
informationWithheldText (250)
associatedTaxaTextAssociated species delimited by commas or semicolons
associatedMediaTextURL to jpg images, delimited by commas or semicolons
verbatimAttributesTextVerbatim description of organism (e.g. 1.5m tall, flowers white with purple tips, etc)
behaviorText (500)
reproductiveConditionText (255)e.g. sterile, flw, frt, asci, etc. Use of controlled vocabulary is preferred.
cultivationStatusInteger0 = wild, 1 = cultivated
establishmentMeansText (45)e.g. cultivated, garden escape, etc
lifeStageText (45)
sexText (45)
individualCountText (45)
samplingProtocolText (100)
samplingEffortText (200)
preparationsText (100)
countryText (64)
stateProvinceText (255)
countyText (255)
municipalityText (255)
localitySecurityInteger0=don’t hide locality details from general public, 1=hide locality
localitySecurityReasonText (100)
decimalLatitudeDouble (8)
decimalLongitudeDouble (8)For USA records, value is negative
geodeticDatumText (255)WGS84, NAD83, NAD27, etc
verbatimCoordinatesText (255)e.g. UTM: 12N 334543 5463754; 34° 25’N 113° 43’W
*verbatimLatittudeText (255)These and following fields are used to generate decimal lat/lng; merged into verbCoor.
*verbatimLongitudeText (255)
*latDegIntegerLatitude degrees
*latMinDoubleLatitude minutes
*latSecDoubleLatitude seconds
*latNSText (3)North/south hemisphere
*lngDegINTLongitude degrees
*lngMinDoubleLongitude minutes
*lngSecDoubleLongitude seconds
*lngEWText (3)East/west hemisphere
*UtmNorthingText (45)
*UtmEastingText (45)
*UtmZoningText (45)
*trsTownship,Text (45)TRS values are merge into verbCoor.
*trsRange,Text (45)
*trsSection,Text (45)
*trsSectionDetailsText (45)
georeferenceProtocolText (255)
georeferenceSourcesText (255)
georeferenceRemarksText (255)
georeferencedByText (255)
georeferenceVerificationStatusText (32)
minimumElevationInMetersIntegerIf elevation is single value, just use this field
*elevationNumberIntegerElevation number and units are concatenated into
*elevationUnitsText (45)verbatimElevation and translated into min. elev. in m.
verbatimElevationText (255)
verbatimDepthText (50)
storageLocationText (100)
dispositionText (32)
basisOfRecordText (32)
institutionCodeText (32)Populate only if different than source collection
collectionCodeText (32)Populate only if different than source collection
exsiccatiIdentifierIntegerIdentifier from exsiccati indexing table
duplicateQuantityUsed for printing labels
labelProjectUsed for printing labels
processingStatusProcessing status for digitization tasks
recordEnteredByText (250)Data entry personnel
modifiedDate/TimeDate last modified within source database
Cite this page:

Ed Gilbert, ed: Katie Pearson. Data Import Fields. In: Symbiota Support Hub (2021). Symbiota Documentation. Created on 22 Oct 2021.