-
Notifications
You must be signed in to change notification settings - Fork 58
checklistData
Resource metadata —>
Checklist Data —>
Occurrence Data —>
Sampling Event Data
- Introduction
- How to transform your data into checklist data
- Templates
- Required DwC fields
- Recommended DwC fields
- Exemplar datasets
- FAQ
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 undigitised 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.
Try putting your data into the Excel template, which includes all required DwC fields and recommended DwC fields.
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.
For extra guidance, you can look at the exemplar datasets.
You can augment your table with extra DwC columns, but only DwC terms from this list.
Populate it and upload it to the IPT. Try to augment it with as many DwC terms as you can.
- kingdom - and other higher taxonomy if possible
- parentNameUsageID - in situations where a taxonomy is meant to be published
- acceptedNameUsageID - in situations where a taxonomy is meant to be published
- Database of Vascular Plants of Canada (VASCAN): DwC-A / IPT homepage
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
This IPT wiki is no longer maintained. Please refer to the IPT User Manual.
© 2021 Global Biodiversity Information Facility
The content on this site is licensed under
- Release Notes
- User Manual
- How to Publish Guide
- Best Practice Guides
- Resource metadata
- Checklist Data
- Occurrence Data (pending)
- Sampling Event Data
- FAQ
- Roadmap
- Version History
- Statistics
- How to Customize the IPT
- How to Contribute
- Other Resources & Tutorials