You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Geocase includes 'dataset owners' and 'providers'. I assume providers are organisations providing a BioCASe installation (hosts), whch can serve one or more datasets from different dataset owners.
To connect with the envisaged DiSSCo DO infrastructure these will need to have a PID so they can be matched against DiSSCo organisations, to know which datasets are provided by DiSSCo and should be included in DiSSCo services. What would be needed: the addition of ROR (or WikiData) identifiers for both owners and providers, which should become mandatory. Note that using DataSet-Owner-OrganisationGUID is not enough: it needs to be a (resolvable) PID. These PIDS should also be served in the API. In the future we will also need PIDs for datasets, and GeoCASe should make use of the digital specimen identifiers DOIs when they become available and include them in search results.
The text was updated successfully, but these errors were encountered:
Geocase includes 'dataset owners' and 'providers'. I assume providers are organisations providing a BioCASe installation (hosts), whch can serve one or more datasets from different dataset owners.
To connect with the envisaged DiSSCo DO infrastructure these will need to have a PID so they can be matched against DiSSCo organisations, to know which datasets are provided by DiSSCo and should be included in DiSSCo services. What would be needed: the addition of ROR (or WikiData) identifiers for both owners and providers, which should become mandatory. Note that using DataSet-Owner-OrganisationGUID is not enough: it needs to be a (resolvable) PID. These PIDS should also be served in the API. In the future we will also need PIDs for datasets, and GeoCASe should make use of the digital specimen identifiers DOIs when they become available and include them in search results.
The text was updated successfully, but these errors were encountered: