BioVeL: Use API to retrieve occurrence records using any ChecklistBank taxonomy

11545
Reporter: mdoering
Type: Improvement
Summary: BioVeL: Use API to retrieve occurrence records using any ChecklistBank taxonomy
Priority: Major
Status: Open
Created: 2012-07-05 16:30:35.377
Updated: 2013-12-17 15:12:35.852
        
Description: Basic use case for BioVeL using the GBIF web services as discussed with Yde de Yong:

Background:
BioVeL uses workflow tools such as Taverna to pipe data through various web services to do scientific analysis.
Webservice formats can be converted into another by having converter services. JSON is readily supported media type.

Outline:
A scientist wants to query GBIF for occurrence records and get them in a machine readable format for further processing with a name & classification according to a reference checklist available in Checklist Bank instead of the original or nub taxonomy. Taxonomic filters might be part of the query and if present they will be according to the same reference taxonomy. A common query is to retrieve all occurrences for a particular genus as defined by the reference taxonomy or .


Present Solution - using individual service calls
0 - client determines the datasetKey of the reference taxonomy manually via website
1 - client issues a download query and is limited to nub concepts for taxonomic filters
2 - client extracts unique names in occurrences by looking at the nubUsageKey
3 - client iterates over all distinct nubUsageKeys and calls /name_usage/${nubUsageKey}/related?checklistKey=${checklistKey} to find the usageKey in the reference taxonomy
4 - client looks up the reference usage name, status and classification by calling /name_usage/${usageKey}


Could this be simplified and directly integrated into the download service?
]]>