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. Visitors may encounter functionality issues pertaining to group pages, navigation, missing content, broken links, etc. As you explore the new site, please provide your feedback using the UserSnap tool found throughout the site. Thank you in advance for your understanding and support as we work through all issues as quickly as possible.

FAIR for Virtual Research Environments (FAIR4VREs) WG Plenary session on 21st June at 02:30 UTC

  • Creator
    Discussion
  • #66848

    Sandra
    Member

    At the upcoming RDA Plenary 19, the FAIR for Virtual Research Environments (FAIR4VREs) WG (under the umbrella of the Virtual Research Environments IG) is undertaking an analysis of gaps in applying existing FAIR principles to VREs, and wishes to gain feedback from VRE users and developers. The session is scheduled on the 21st June at 02:30 UTC.
    The working group has identified commonalities and differences in the application of FAIR to VREs based on a preliminary analysis of existing high-level principles as applied to data and software. The issues that need to be addressed in defining FAIR for VREs have been outlined, and these are the key questions around which we wish to engage the community at the Plenary.  
    The working group also wishes to crowdsource case studies on how VREs contribute to FAIRness of other digital objects and examples of guidance materials.
    Scheduled agenda is:
    0-10 min: Presentation of the draft analysis of gaps in applying existing FAIR principles to VREs
    10-50 min: Panel discussion on the challenges of implementing VREs that enable FAIR digital objects
    50-70 min: Open discussion on the draft gap analysis and call for case studies of FAIR and FAIR-enabling VREs, and examples of guidance materials for VRE developers
    70-90 min: Review the timeline of future work packages
    Join us for the virtual session! We appreciate your input!

Log in to reply.