Skip to main content

Notice

We are in the process of rolling out a soft launch of the RDA website, which includes a new member platform. Existing RDA members PLEASE REACTIVATE YOUR ACCOUNT using this link: https://rda-login.wicketcloud.com/users/confirmation. Visitors may encounter functionality issues with group pages, navigation, missing content, broken links, etc. As you explore the new site, please provide your feedback using the UserSnap tool on the bottom right corner of each page. Thank you for your understanding and support as we work through all issues as quickly as possible. Stay updated about upcoming features and functionalities: https://www.rd-alliance.org/rda-web-platform-upcoming-features-and-functionalities/

updates to the metadata application profile: ready for 1.0 release?

  • Creator
    Discussion
  • #106639

    Paul Walk
    Member

    Dear DMP Common Standards Working Group,
    Since the very useful meeting in Helsinki at the RDA Plenary, we have responded to some useful feedback and made some minor changes to the metadata profile. We believe that this is now ready for an ‘official’ release as version 1.0.
    We have made the changes in a separate branch (‘2019-11’) in the Github repository, so these changes are not yet reflected on the default ‘master’ branch. However, you can see the latest version here:
    https://github.com/RDA-DMP-Common/RDA-DMP-Common-Standard/tree/2019-11
    Please have a look at this version and comment (by replying on this email list) if you see anything that looks wrong. Please note that we will not make significant changes at this point, but there is time to fix minor mistakes.
    Our plan is to release version 1.0 on Monday 18th November.
    At the bottom of this email message I have included a list of the changes made since the Helsinki RDA Plenary.
    Many thanks to all of those who have contributed to this work – this has been a great community effort!
    Best wishes,
    Paul
    On behalf of the WG Co-chairs: Tomasz Miksa, Peter Neish & Paul Walk
    ——————————————-
    Paul Walk
    http://www.paulwalk.net
    Founder and Director, Antleaf Ltd
    http://www.antleaf.com
    Antleaf provides Management Services to DCMI
    http://www.dublincore.org
    ——————————————-
    # Changes made in response to feedback from RDA Plenary 14 (Helsinki)
    There have been some minor structural changes, and several name-changes to improve the naming consistency.
    ## Expressing identifiers consistently
    Seven properties have been altered to each contain the following sub-property pair:
    * `identifier`
    * `type`
    The properties which now contain these identifier/type pairs are:
    1. `contact_id` under `contact`
    2. `contributor_id` under `contributor`
    3. `dmp_id` under `dmp`
    4. `dataset_id` under `dataset`
    5. `metadata_standard_id` under `metadata`
    6. `funder_id` under `funding`
    7. `grant_id` under `funding`
    ## The `technical_resources` property
    This no longer uses the `identifier/identifier_type` pattern. Instead it just has a `name` and a `description`, both of which are `strings`.
    ## Renamed properties
    * `dm_staff` renamed to `dm_contributor`
    * `staff_id` renamed to `contributor_id`
    * `staff_name` renamed to `name`
    * `mbox` under `contributor` renamed to `mbox`
    * `contributor_type` renamed to `role`
    * `dm_contributor` to `contributor`
    * `available_till` in `distribution` to `available_until`
    ## Data type changes
    * `type` in `dataset` has been changed from a controlled vocabulary to a free `string` property because we have been unable to identify a suitable vocabulary to constrain this property
    * the cardinality of `type` in `dataset` has been relaxed to `0..1`
    ## Host storage type
    * `storage_type` in `host` has been changed from a controlled vocabulary to a free `string` property because we have been unable to identify a suitable vocabulary to constrain this property.

Log in to reply.