This page is under construction and subject to significant revision.

• Using the GBIF Infrastructure to Develop and Use a Regional Species Checklist
• General Process
• Processing Occurrence Data for Regional Checklist information
• Cross-Reference to Checklist Bank via Client Applications using API
• Processing External Web sources
• Geo-spatially annotated Checklists not in Checklist Bank
• Metadata
• Data
• Using the Spatial Data Repository

Using the GBIF Infrastructure to Develop and Use a Regional Species Checklist

General Process

Identify data sources that contribute to building a regional species lists.

• Occurrence data identifying species reported within a country territorial.
• Type specimen occurrences
• Domain knowledge to weed outliers/false positives
• Publications
• Geo-references in data sources
• Taxonomic checklists with locality data

Identify workflow processes to

• Resolve the name to a authoritative taxonomic or nomenclatural usage
• Access resolved metadata and data and transfer to local data store
• Collate the transferred data into a new taxonomic synthesis
• Integrate data streams from multiple sources
• Publish the synthesized regional checklist to DwC Archive

Processing Occurrence Data for Regional Checklist information

1. An application allows a user to circumscribe the region of interest in the Global Data Portal.
2. GBIF data portal web service calls filter on region, basis of record, etc. Sufficient to distingush Type data from generalised Speciemen and Observation data.
1. User reviews type information.
2. User selects records for integration with the checklist process
3. Checklist records are accessed and transferred to a local data store. Source metadata is also included.
1. Specimen GUIDS would be preferred mechanism for a persistent link to the specimen
4. User reviews a summarised view of non-type specimen data. Various views provide useful criteria for selection.
5. Similar selection interfaces allow specimen data to be integrated into workflow

Goal: Specimen data is incorporated into the proto-regional checklist. Priority is given to types. Subsequent processes perform validation and cross-reference to taxon concept data in Checklist Bank.

Cross-Reference to Checklist Bank via Client Applications using API

1. An application allows a user to identify Checklist Bank resources based on a region of interest (Country)
1. Regional Information in Metadata identifies the highest priority set of resources (regional flora and faunas0
2. Data record locality data provides a secondary set of potential taxa of interest
2. Interfaces allow taxon concepts to be incorporated into the application, resolving the metadata and data into a local store.

Goal: GUID based links to authoritative and defined taxon concepts from a derived secondary checklist.

Processing External Web sources

Example: Aluka

Geo-spatially annotated Checklists not in Checklist Bank

• Taxon Tagger Applications

Metadata

Data

Using the Spatial Data Repository

SANBI PRECIS might make a good example.