What datasetType should Catalogue of Life subdatasets have
10794
Reporter: mdoering
Assignee: mdoering
Type: Improvement
Summary: What datasetType should Catalogue of Life subdatasets have
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-02-08 11:42:13.648
Updated: 2013-12-16 17:50:15.82
Resolved: 2012-02-23 11:17:15.872
Description: for example:
http://staging.gbif.org:8080/portal-web-dynamic/dataset/21c2e70b-5e8c-415f-8ec0-83a3f418dd4f
Right now its "Unknown" type - should it be checklist even though we don't have any service/endpoints attached?]]>
Author: trobertson@gbif.org
Created: 2012-02-08 12:06:54.353
Updated: 2012-02-08 12:06:54.353
I would propose yes, and perhaps we should think further and say something like:
type: Checklist
subtype: Global species database
Rational is:
- the type relates to the dataset, not any technical, or other, services to access it
- the GSD part is quite a specific marker about the checklist
> although I have not spent much time considering vocabularies for checklist types
Out of scope for this Jira, but related:
In the *future*, we will have to start relating datasets (e.g. agent relationships):
- A GSD "is a component part" of the CoL Global Dataset
- SAIAB Specimen Collection "is a component part" of Fishbase
- etc.
Author: mdoering@gbif.org
Comment: Agree. In order to store the (sub)types we need new fields in the registry db then I assume? Right now we derive the type from the registered services
Created: 2012-02-08 12:08:25.138
Updated: 2012-02-08 12:08:25.138
Author: trobertson@gbif.org
Created: 2012-02-08 12:13:23.464
Updated: 2012-02-08 12:13:23.464
Agree if it is missing. Subtype in the API was intended to be on the Dataset (e.g. RegistryDB.Agent)
Service was intended to have a type but that indicated things like protocol, formats etc.
Author: mdoering@gbif.org
Comment: Adding new issue to store types in db explicitly
Created: 2012-02-08 12:49:35.41
Updated: 2012-02-08 12:49:35.41