Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to publish metadata-only Camtrap DP datasets #2595

Open
peterdesmet opened this issue Nov 18, 2024 · 0 comments
Open

Option to publish metadata-only Camtrap DP datasets #2595

peterdesmet opened this issue Nov 18, 2024 · 0 comments
Assignees
Milestone

Comments

@peterdesmet
Copy link
Member

In the context of the Biodiversa+ project BIG_PICTURE, we're aiming to create a registry of available camera trap datasets (in Europe). We would like to do that on top of GBIF infrastructure. For example:

  • Partners describe and publish their dataset as a Camtrap DP dataset in an IPT of their choice.
  • The dataset is registered with GBIF
  • We use the registry API to know about available Camtrap DP datasets (assuming there is a mechanism to search for those)
  • We pull the dataset metadata (from the registry and source Camtrap DP dataset)

Not all partners can publish their dataset openly however. To broadcast to the registry that they have a dataset, they currently would need to create a metadata-only dataset in the IPT. Such a metadata-only dataset differs in metadata from a Camtrap DP dataset however. There is also no easy mechanism to convert a metadata-only dataset to a (Camtrap DP) dataset with public data later.

So, would it be possible to support/explore in the IPT:

  1. The publication of Camtrap DP datasets with metadata only (no CSV files)
  2. A mechanism to update such a dataset with public data (i.e. adding the CSV files) later, so it becomes a proper Camtrap DP dataset
  3. The option to upload the CSV data already and keeping those private, while the metadata is public (i.e. metadata-only with private data). Making the data publicly available would then be a matter of clicking a switch and republishing.
  4. Same as 3, but granting specific users read access to the data (I believe that is already possible)

Ping @kbubnicki @timrobertson100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants