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

Differences between RDA-DMP-Standard and RDMO-DMP-Standard #77

Open
Sabine-Schoenau opened this issue Dec 11, 2024 · 0 comments
Open

Differences between RDA-DMP-Standard and RDMO-DMP-Standard #77

Sabine-Schoenau opened this issue Dec 11, 2024 · 0 comments

Comments

@Sabine-Schoenau
Copy link

Sabine-Schoenau commented Dec 11, 2024

Hi,
For a national DMP service in Germany we decided to use the developed RDA-DMP standard as a basis for a template framework we
develop for the RDMO DMP tool. We noticed some differences in our approach and have some suggestions, see the list below.
We are interested in an exchange and would be pleased if we could meet virtually at the end of January/beginning of February. We will write you a seperate email.
Yours sincerely,
(commissioned by) Sabine Schönau

  • Make "project" the root element (instead of "DMP")
  • Provide the following children elements to "project": id, contact, coordinator
  • Assign the following children elements to "project" (instead of "DMP"): "cost", "contact" and "contributor"
  • Provide the following children elements to "dataset": contact, contributor, publisher, license, date_created, date_modified, date_published
  • Assign the following children elements to "dataset" (instead of "DMP"): "metadata"
  • Provide the following children elements to "DMP": publisher, license, date_published
  • Remove all information which falls under the responsibility of external sources/services/hosts, e.g. most children of "distribution", apart from "access_url"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant