briri
commented
3 years ago An updated email from re3data about the changes: "1. Release of Metadata Schema Version 3.1
Version 3.1 realizes two major changes in addition to numerous minor adjustments and is now ready for implementation into the technical infrastructure of re3data, which will be realized in the upcoming weeks. In the course of the re3data COREF project, the schema will be continuously revised. The release of version 4.0 is planned towards the end of the project. The updated schema is the result of an extensive review on which re3data received more than 150 comments. re3data thanks the FDM community for their valuable contributions! More: https://coref.project.re3data.org/blog/releasing-version-3-1-of-the-re3data-metadata-schema
2. Publication of the "Conceptual Model for User Stories" and "Stakeholder Survey and Workshop Report"
The COREF project has reached an important milestone with the publication of the "Conceptual Model for User Stories" (https://doi.org/10.48440/re3.012) for re3data - the Registry of Research Data Repositories. The model is based on the results of a stakeholder survey and three workshops. The survey and workshop report is also available online (https://doi.org/10.48440/re3.013). Both documents allow our team to recalibrate re3data according to current and future needs of the community.
3. Thank you for the large feedback on our survey "Data Quality Management in Research Data Repositories"!
Our team conducted a survey for repository staff responsible for data curation to capture measures of data quality management, contribute to conversations regarding data quality, and highlight the contribution of repositories that often remain invisible. We are very grateful for more than 300 completed questionnaires and are currently working on the survey analysis. Results will be shared with the repository community and contribute to improving descriptions of data quality management at research data repositories in re3data. More: https://coref.project.re3data.org/blog/how-to-ensure-good-data-a-presentation-at-open-repositories-2021
4. Support for reuse of metadata via re3data API
As part of the re3data COREF project work, two Jupyter Notebooks have been set up to provide examples of how to use the re3data API. The examples are implemented in R (https://www.r-project.org/). Jupyter Notebooks are web-based interactive work environments that combine executable code and Markdown text (https://jupyter.org/). The provided notebooks outline the use cases and each step in the process of data collection, processing, and visualization. They have been designed to be adaptable to other use cases as well. More: https://coref.project.re3data.org/blog/using_the_re3data_api
5. Talks and Info Material
First results from the survey "Data Quality Management in Research Data Repositories" were presented at the 16th International Conference on Open Repositories. Presentation slides: https://coref.project.re3data.org/blog/how-to-ensure-good-data-a-presentation-at-open-repositories-2021/presentation_OR2021.pdf The COREF project participated in the 109th German Librarians' Day with a presentation about the re3data service and project updates: https://nbn-resolving.org/html/urn:nbn:de:0290-opus4-177132 In collaboration with the FAIRsFAIR project (https://www.fairsfair.eu/) and FAIRsharing (https://fairsharing.org/), the re3data team organized a webinar for repository managers to illustrate how research data repositories can improve the visibility of their services through repository registries. Slides and recording are available online: https://www.fairsfair.eu/repository-support-webinars UPCOMING: Lightning talk "re3data COREF – Developing a Conceptual Model for User Stories for the Registry of Research Data Repositories" at the Open Science Fair 2021, which will take place from 20 to 23 September (https://www.opensciencefair.eu/)."
re3data.org Schema 3.1 DOI: http://doi.org/10.48440/re3.010
Blog post: https://coref.project.re3data.org/blog/releasing-version-3-1-of-the-re3data-metadata-schema
re3data just announced a new metadata scheme that includes expanded descriptions of repository certification and the opportunity to identify a subset of repositories indexed in re3data pre-defined by a third party based on community-developed criteria. It sounds like the community will regularly update this data.
We're currently pulling down the data via the API and stuffing it into a database table. The system then interacts with the table, not their API. It may make sense to stop using the table and just query their API directly with this new version.