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

Clarifications about Data Package properties (metadata) #21

Closed
niconoe opened this issue Aug 6, 2021 · 2 comments
Closed

Clarifications about Data Package properties (metadata) #21

niconoe opened this issue Aug 6, 2021 · 2 comments
Labels
wontfix This will not be worked on

Comments

@niconoe
Copy link
Collaborator

niconoe commented Aug 6, 2021

Hey @peterdesmet, I noticed the following sentence on the metadata documentation page:

It follows the Tabular Data Package specifications and includes default Data Package properties and specific VPTS-DP properties

There are also a few of those properties listed: name, id, created, profile, sources, contributors, resources.

If I'm not mistaken, the Data Package specs only requires the resources property, so I was wondering what we should do for v1, and what you wanted to express on that page. Do we want to enforce that a vpts-dp always provides name, id, created, profile, sources, contributors attributes (in addition toresources which is already required for all data packages, and our specific properties such as radar)?

Thanks a lot!

@peterdesmet
Copy link
Member

The ones that are listed are probably a copy/paste from https://tdwg.github.io/camtrap-dp/metadata/ but only to provide a table of contents.

To really make the required, this needs to be added to vpts-dp-profile.json (see again how this is done in Camtrap DP). Regarding which ones: I need to review this, but I’m thinking created and radar. resources is already required indeed.

@peterdesmet peterdesmet added the wontfix This will not be worked on label May 6, 2022
@peterdesmet
Copy link
Member

Will not implement this, in favour of a simple flat format as described in #25.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants