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/

RDA Research Data Repository Interoperability WG Case Statement

  • Creator
    Discussion
  • #83528

    RDA Admin
    Member

    Hi everyone,
    Thanks to all who attended the BoF meeting for Research Data Repository Interoperability at the 7th RDA Plenary in Tokyo. Notes from the meeting can be found on the group page on the RDA website. Unfortunately, it was not possible for us to subscribe you to the RDA group so if you are not already a member please register, login and subscribe in order to receive mails from the group mailing list, which will be the primary communication channel in future.
    As discussed at the meeting, we plan to finalize the working group case statement by May in order to allow enough time for review before the next plenary. If you are interested in participating in this working group, please take this opportunity to review the case statement and leave comments or edit where appropriate. We need to agree on the scope of the group’s work: what use cases will we target and what will our deliverables be? These are laid out in the case statement, so please pay particular attention to this section and make note of any changes you would like to see.
    Regards,
    David Wilcox and Thomas Jejkal
    Group Co-Chairs

    David Wilcox
    Fedora Product Manager
    DuraSpace
    ***@***.***

Log in to reply.