Resources comprising a list of species belonging to some category (e.g. taxonomic, geographic, trait-based, red list, crop wild relative) and optionally with higher classification and/or additional traits associated with each species. Examples of such datasets include global or regional taxonomic checklists, global or national red lists, catalogues of species included in undigitized collections, park checklists, etc. If sufficient information exists in the source dataset (or applies consistently to all species in the checklist), it is recommended that these datasets are presented as Occurrence Data. These datasets include the same basic descriptive information included under Resource metadata.
Ultimately your data needs to be transformed into a table structure using Darwin Core (DwC) term names as column names.
Alternatively if your data is stored in a supported database, you can write an SQL table (view) using DwC column names. Be careful to include all required DwC fields and add as many recommended DwC fields as possible.
A. Make a table of common names. The table must include a taxonID column. That way, each row can link to the (core) taxon record. You can augment your common names table with extra columns, but only using term names from this list. You can upload this table to the IPT, and map it to the Vernacular Name extension.
A. Make a table of geographic distributions of a taxon. The table must include a taxonID column. That way, each row can link to the (core) taxon record. You can augment your geographic distributions table with extra columns such as the threat status, but only using term names from this list. You can upload this table to the IPT, and map it to the Species Distribution extension.
Q. Can I update the GBIF Backbone Taxonomy with names from my checklist?
A. Yes. To do so, you must publish your checklist, make it publicly available online under a GBIF-supported license (CC0, CC-BY, CC-BY-NC) and register it with GBIF. GBIF can then manually review it to determine if it is a suitable backbone source, e.g. by looking at how its names overlap with the backbone. Ideally the checklist will provide at least a minimal classification like a kingdom and family, be of high data quality meaning it has few name usage issues, include scientificNameAuthorship of names, supplying the namePublishedIn reference, etc.