CINXE.COM

<?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> <title>COREF Blog</title> <link href="https://coref.project.re3data.org/blog.atom" rel="self" /> <subtitle>COREF Blog</subtitle> <updated>2024-10-22T15:11:00+01:00</updated> <author> <name>re3data</name> </author> <id>https://coref.project.re3data.org/</id> <entry> <title>re3data in Central America</title> <id>https://coref.project.re3data.org/blog/re3data-in-central-america</id> <updated>2024-10-22T14:24:49+01:00</updated> <published>2024-10-22T15:11:00+01:00</published> <link href="https://coref.project.re3data.org/blog/re3data-in-central-america"/> <content type="html"> <![CDATA[ <img alt="" src="/images/f/b/3/f/7/fb3f7fab0796b4b22049783eeb7398cd11ae27d4-costarica.jpg" /> Dr. Sandra Gisela Martín from the re3data Editorial Board delivered a featured lecture, “re3data: Global Registry of Research Data Repositories”, at the Second Meeting of Colombian Institutional Repository Managers and Open Science (II Encuentro de Gestores de Repositorios Institucionales de Colombia y Ciencia Abierta, <a href="https://www.politecnicojic.edu.co/comunicados-y-boletines/5737-ii-encuentro-de-gestores-de-repositorios-institucionales-y-ciencia-abierta-ericca-2024">ERICCA 2024</a>), which was held in Cartagena, Colombia, September 25-27. Convened by the Colombian Ministry of Science, Technology and Innovation, ERICCA brings together the managers of institutional and data repositories and Current Research Information Systems (CRIS) to democratize science through access to results derived from research funded with public resources. They advocate that products should be available on open and interoperable infrastructures so that they are available to the scientific community, citizens, and national and international knowledge networks. Dr. Martín gave an overview of re3data and guided those in attendance in person and online through the process of adding and editing the records for their data repositories. Outreach activities such as her lecture are important contributions to broaden the coverage of data repositories that are indexed in the registry, in particular in regions and languages that are under-represented. Dr. Martín is a professor and director of the library at the Universidad Católica de Córdoba in Argentina. <iframe width="100%" height="360" src="https://www.youtube.com/embed/16brPk-vjfo?start=3009" title="Día 2 - ERICCA 2024" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> In other news, we are looking forward to continuing to promote re3data and data-sharing through repositories in the region at the <a href="https://www.rd-alliance.org/event/rda-23rd-plenary-meeting-san-jose-costa-rica/">23rd Plenary Meeting of the Research Data Alliance</a> with participation in person in San José, Costa Rica, and online November 12-14. <img title="costarica" alt="costarica" src="/images/a/7/c/7/c/a7c7c2bb120abe1a792164a86512672568d85d65-costarica.jpg" /> La Dra. Sandra Gisela Martín, del Consejo Editorial de re3data, pronunció la conferencia «re3data: Global Registry of Research Data Repositories», en el II Encuentro de Gestores de Repositorios Institucionales de Colombia y Ciencia Abierta (ERICCA 2024), que se celebró en Cartagena, Colombia, del 25 al 27 de septiembre. Convocado por el Ministerio de Ciencia, Tecnología e Innovación de Colombia, ERICCA reúne a los gestores de repositorios institucionales y de datos y Sistemas de Información para la Investigación (CRIS) para democratizar la ciencia mediante el acceso a los resultados derivados de la investigación financiada con recursos públicos. Defienden que los productos estén disponibles en infraestructuras abiertas e interoperables para que estén a disposición de la comunidad científica, los ciudadanos y las redes de conocimiento nacionales e internacionales. La Dra. Martín ofreció una visión general de re3data y guió a los asistentes en persona y en línea a través del proceso de añadir y editar los registros para sus repositorios de datos. Las actividades de divulgación como su conferencia son contribuciones importantes para ampliar la cobertura de los repositorios de datos indexados en el registro, en particular en regiones y lenguas poco representadas. La Dra. Martín es profesora y directora del Sistema de Bibliotecas de la Universidad Católica de Córdoba (Argentina). ]]> </content> </entry> <entry> <title>Summer Meeting of the Editorial Board</title> <id>https://coref.project.re3data.org/blog/summer-meeting-of-the-editorial-board</id> <updated>2024-09-04T14:02:55+01:00</updated> <published>2024-09-04T14:02:55+01:00</published> <link href="https://coref.project.re3data.org/blog/summer-meeting-of-the-editorial-board"/> <content type="html"> <![CDATA[ <img alt="" src="/images/7/b/6/1/b/7b61bcef98211c200b6c508c172e8833ae50caaa-working.jpg" /> Summer Meeting of the Editorial Board The re3data.org editorial board was able to get together in person over the summer, meeting for two days in June at the library of the Karlsruhe Institute of Technology (KIT). It was a great opportunity to on-board our new editors and to reconnect with colleagues to focus on updates and improvements to the registry. In addition to the work, the group enjoyed good food and fellowship in the evening. Some were not able to travel to Germany but were able to join remotely for introductions and an icebreaker to get to know each other better. The KIT staff led a tutorial and demonstrated the registry’s backend editorial workflow, following a submission through each step in the process as it moved through the system. We also had a focussed discussion on new ways to engage with the broader research data community, first by sharing general strategies and then brainstorming specific approaches for each of our regions and networks. Each editor left with 2-3 action items of things they could do to raise awareness of re3data.org and to identify new repositories to index, in particular, from under-represented parts of the world. The board will revisit these on its next quarterly call to update each other on progress. Four additional working sessions addressed important topics. A hands-on activity explored inconsistencies over the years in how editors have identified different types of repositories, and they discussed potential changes to their approach to repository typology. The board mapped and investigated the alignment between Version 4 of re3data’s <a href="https://doi.org/10.48440/re3.014">Metadata Schema for the Description of Research Data Repositories</a> and the <a href="https://doi.org/10.15497/rda00103">RDA Common Descriptive Attributes of Research Data Repositories recommendation</a> that was endorsed earlier this year by the Research Data Alliance. They explored how users from specific disciplines may experience the registry differently. For example, how would a humanities scholar interact with re3data.org in ways that would be different from a geoscientist? Each of the editors has individual expertise in different disciplines and presented their views in the context of their subject area. Last but not least, the group experimented and explored how artificial intelligence (AI) tools consume information about repositories that we present in the registry as well as how we may utilize AI to improve our work. The meeting concluded with a session of lightning talks on topics of relevance that were brought by our editors, which spanned a wide spectrum of initiatives and interests. This was the third in a series of three meetings that were sponsored by the <a href="https://www.dfg.de/">Deutsche Forschungsgemeinschaft (DFG)</a> in support of the <a href="https://coref.project.re3data.org/project">COREF project</a>. The meetings helped reshape the editorial process, brought in missing language and subject expertise, and extended global networks to better cover regions that are currently underrepresented in re3data. <img title="working" alt="working" src="/images/7/1/7/5/b/7175be771978de37dc8a61f11f0bb246905a6169-working.jpg" /> <img title="re3data_editorial_board_2024_s" alt="re3data_editorial_board_2024_s" src="/user/pages/02.blog/18.summer-meeting-of-the-editorial-board/re3data_editorial_board_2024_s.jpg" /> <img title="super_pretzel" alt="super_pretzel" src="/user/pages/02.blog/18.summer-meeting-of-the-editorial-board/super_pretzel.jpg" /> ]]> </content> </entry> <entry> <title>New re3data.org Editorial Board Members</title> <id>https://coref.project.re3data.org/blog/new-re3data-org-editorial-board-members</id> <updated>2024-05-17T13:12:37+01:00</updated> <published>2024-05-17T13:12:37+01:00</published> <link href="https://coref.project.re3data.org/blog/new-re3data-org-editorial-board-members"/> <content type="html"> <![CDATA[ <img alt="" src="/images/c/8/1/5/8/c8158ebb45d1c5197c28f0554e8876a8fa2ad858-karlsruhe-unsplash.jpg" /> The <a href="https://www.re3data.org/editorialboard">re3data Editorial Board</a> is pleased to welcome seven new members: <ul> <li>Dalal Hakim Rahme, Coordinator of Content Curation, United Nations</li> <li>Rene Faustino Gabriel Junior, Professor, Universidade Federal do Rio Grando do Sul</li> <li>Sandra Gisela Martín, Library Director, Universidad Católica de Córdoba</li> <li>Tekleweyni Geday, Lecturer, Mekelle University</li> <li>Theodora Bloom, Executive Editor, BMJ</li> <li>Vaidas Morkevičius, Professor, Lithuanian Data Archive for Social Sciences and Humanities, Kaunas University of Technology</li> <li>Ziyi (Neko) He, Researcher, China National GeneBank</li> </ul> The purpose of the editorial board is to advance re3data’s mission by providing stewardship and curating registry records; identifying and cataloging new data repositories; establishing and maintaining editorial strategies and policies, and promoting the registry across disciplines and geographies. The editorial board will be meeting in a few weeks at the Karlsruhe Institute of Technology to discuss issues related to repository typologies, artificial intelligence, domain repositories, trusted research environments, and potential updates to the <a href="https://doi.org/10.48440/re3.014">Metadata Schema for the Description of Research Data Repositories</a> in consideration and implementation of the <a href="https://doi.org/10.15497/rda00103">RDA Common Descriptive Attributes of Research Data Repositories</a>. <img title="karlsruhe-unsplash" alt="karlsruhe-unsplash" src="/images/5/9/4/e/d/594edce3be4d6d7cc60426665966833e39c23696-karlsruhe-unsplash.jpg" /> ]]> </content> </entry> <entry> <title>re3data Call for Editorial Board</title> <id>https://coref.project.re3data.org/blog/re3data-call-for-editorial-board</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2024-02-28T14:26:31+00:00</published> <link href="https://coref.project.re3data.org/blog/re3data-call-for-editorial-board"/> <content type="html"> <![CDATA[ <img alt="" src="/images/4/1/0/2/a/4102a5a7a3cc157a5116478a6ede288609f6337a-schloss.jpeg" /> <h3>re3data Call for Editorial Board</h3> The <a href="http://re3data.org/">re3data.org</a> registry has been in operation for over 10 years and provides a curated index of over 3,000 research data repositories around the world from all disciplines. New repositories are identified and reviewed by an <a href="https://www.re3data.org/editorialboard">international editorial board</a> who bring different subject, language, and cultural backgrounds to catalog and represent a diverse and ever-growing data repository landscape. The editorial board also maintains re3data’s <a href="http://doi.org/10.48440/re3.014">Metadata Schema for the Description of Research Data Repositories</a>. The editorial board is seeking to expand, in particular, to include editors from countries and disciplines where we have gaps in language, subject expertise, and representation. Editors serve 4-year terms and meet virtually 2-3 times a year with most of our work conducted via email. A travel stipend will be provided for a meeting planned in person for June 2024 in Karlsruhe, Germany. If you are interested in serving, please consult the editorial board’s <a href="https://drive.google.com/file/d/1x-b7kouaTNtdO4P6ngqDh2SAXMSALZIf/view?usp=sharing">terms of reference</a> and <a href="https://forms.gle/ktg8c5tpj6MPQXiW9">apply</a> before March 31. Apply here: <a href="https://forms.gle/ktg8c5tpj6MPQXiW9">https://forms.gle/ktg8c5tpj6MPQXiW9</a> Michael Witt (<a href="mailto:mwitt@purdue.edu">mwitt@purdue.edu</a>) and Charlotte Neidiger (<a href="mailto:charlotte.neidiger@kit.edu">charlotte.neidiger@kit.edu</a>) on behalf of the re3data Editorial Board <img title="schloss" alt="schloss" src="/images/c/6/a/0/9/c6a09245acfe20d434619ca0aefcff97360b98f9-schloss.jpeg" /> ]]> </content> </entry> <entry> <title>Releasing version 4.0 of the re3data Metadata Schema</title> <id>https://coref.project.re3data.org/blog/releasing-version-4-0-of-the-re3data-metadata-schema</id> <updated>2024-02-28T14:35:26+00:00</updated> <published>2023-08-07T13:37:00+01:00</published> <link href="https://coref.project.re3data.org/blog/releasing-version-4-0-of-the-re3data-metadata-schema"/> <content type="html"> <![CDATA[ <img alt="" src="/images/c/7/6/7/a/c767a815778b1c0af22ac30feb943885aece11af-schema4-0.jpg" /> re3data caters to a range of needs for diverse stakeholders (<a href="https://doi.org/10.48440/RE3.012">Vierkant et al., 2021</a>). Detailed and precise repository descriptions are at the heart of the majority of these use cases, and repository metadata are given special attention at the re3data registry. Repository descriptions in re3data are based on a <a href="https://www.re3data.org/schema">metadata schema</a> that describes various aspects of research data repositories, including general scope, content, policies as well as compliance with technical and metadata standards. As the repository landscape evolves, the schema has been expanded and adapted regularly. By now, more than ten years of work have been put into the re3data Metadata Schema - Version 1.0 of the schema was published in 2012. Over the years, more than 40 authors have contributed to the various schema versions, and many more members of the repository community have shared their expertise, needs and feedback with the service. As in previous releases, many have contributed to an open <a href="https://coref.project.re3data.org/blog/request-for-comments-version-4-0-of-the-re3data-metadata-schema">request for comments</a>. We are happy to announce the release of <a href="https://doi.org/10.48440/re3.014">version 4.0 of the re3data Metadata Schema</a> as of August 2023, which is now ready to be implemented in the re3data service. We thank the repository community for their valuable feedback on the schema development. All suggestions from the public request for comments were discussed and considered for implementation. Some suggestions were adopted in version 4.0 of the re3data Metadata Schema, while the remaining feedback was documented for future reference. <h3>In addition to other changes, version 4.0 introduces the following major changes:</h3> relatedRepository The new property relatedRepository offers the option to describe relationships between repositories, such as between predecessors and successors. fundingInformation With the new property fundingInformation, information on repository funding can be expressed, including funder names and identifiers. contentType The controlled vocabulary for indexing contentType will be switched to a subset of the <a href="https://vocabularies.coar-repositories.org/resource_types/">COAR Resource Types 3.1</a> vocabulary (<a href="https://vocabularies.coar-repositories.org/resource_types/c_ddb1/">dataset</a> with subtypes ; <a href="https://vocabularies.coar-repositories.org/resource_types/c_c513/">image</a> with subtypes ; <a href="https://vocabularies.coar-repositories.org/resource_types/c_5ce6/">software</a> with subtypes ; <a href="https://vocabularies.coar-repositories.org/resource_types/c_18cf/">text</a> without subtypes). <img alt="" src="/images/0/c/5/a/2/0c5a2a27cbebac01343caf6efb32e3cad1e0a9ce-schema4-0.jpg" /> ]]> </content> </entry> <entry> <title>Request for Comments: Version 4.0 of the re3data Metadata Schema (closed)</title> <id>https://coref.project.re3data.org/blog/request-for-comments-version-4-0-of-the-re3data-metadata-schema</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2023-05-09T13:37:00+01:00</published> <link href="https://coref.project.re3data.org/blog/request-for-comments-version-4-0-of-the-re3data-metadata-schema"/> <content type="html"> <![CDATA[ <img alt="" src="/images/4/0/b/0/9/40b09a08fb422aa4ea0a856ff9a311e5a57c27cf-rfc4-0.jpg" /> Currently, re3data offers unrestricted access to comprehensive descriptions of more than 3100 research data repositories from all disciplines and all regions. The repository descriptions are based on the re3data Metadata Schema. More than 10 years of conceptual work have gone into this schema, which has been continually adapted as the repository landscape and the requirements and expectations for a registry of research data repositories have shifted. The current <a href="https://www.re3data.org/schema">version 3.1</a> of the re3data Metadata Schema was released in 2021. Within the ongoing project <a href="https://coref.project.re3data.org/">re3data COREF</a>, we will again revise the re3data Metadata Schema to release version 4.0. We invite you to participate in the Request for Comments for version 4.0 of the re3data Metadata Schema by <a href="https://docs.google.com/document/d/1z03lOc4OwiJOCZhWcPpKDPBTpRnISe4Rh8HYoom1JXc/edit?usp=sharing">commenting on our draft</a> until May 31st, 2023. Properties that have been changed or were added with this draft are highlighted in the document, we particularly welcome comments on these properties. Your comments are highly appreciated, as we are committed to finding a way to describe research data repositories that fits the needs of our diverse stakeholders. All comments will be discussed and considered for version 4.0 of the re3data Metadata Schema. <h3>Version 4.0 introduces four major changes:</h3> <ul> <li>relatedRepository: The new property relatedRepository offers the option to describe relationships between repositories. Currently, these relationships are restricted to referencing the repository that took over custody of (parts of) the collection after the repository described by the entry was closed.</li> <li>fundingInformation: With the new property fundingInformation, information on repository funding can be expressed, including funder names and funder identifiers.</li> <li>qualityManagementMeasure: The new property qualityManagementMeasure introduces the opportunity to index specific quality assurance measures the repository implemented.</li> <li>contentType: The controlled vocabulary for indexing content types will be switched to the COAR Resource Types 3.1 (<a href="https://vocabularies.coar-repositories.org/resource_types/c_ddb1/">dataset</a> with subtypes, <a href="https://vocabularies.coar-repositories.org/resource_types/c_c513/">image</a> with subtypes, <a href="https://vocabularies.coar-repositories.org/resource_types/c_5ce6/">software</a> with subtypes, <a href="https://vocabularies.coar-repositories.org/resource_types/c_18cf/">text</a> without subtypes). This will make it easier to identify whether a repository only stores data, or also text and software.</li> </ul> <img alt="" src="/images/2/9/2/1/f/2921f26d968cc9892ad25c71dde7c8747bf7381b-rfc4-0.jpg" /> ]]> </content> </entry> <entry> <title>Canadian research data repositories in re3data: A collaborative effort to increase visibility and foster community engagement</title> <id>https://coref.project.re3data.org/blog/canadian-research-data-repositories-in-re3data</id> <updated>2024-02-28T14:35:26+00:00</updated> <published>2023-03-15T15:20:00+00:00</published> <link href="https://coref.project.re3data.org/blog/canadian-research-data-repositories-in-re3data"/> <content type="html"> <![CDATA[ <img alt="" src="/images/a/6/a/8/5/a6a85557236a9cd28f8dca94e727f4bec1070689-knots.jpg" /> Collaboration has always been a central principle for re3data. This is reflected in the fact that research communities, repository providers, and other relevant stakeholders contribute significantly to the completeness and accuracy of the re3data metadata as well as its further technical and conceptual development. As the world's largest directory of research data repository, re3data currently describes over 3000 infrastructures on the basis of a comprehensive metadata schema. The service was launched in 2012 and therefore has recorded information on the repository landscape for over 10 years. Within the international research data community, the <a href="https://alliancecan.ca/en/services/research-data-management/network-experts">Discovery and Metadata Expert Group</a> (DMEG), part of the Digital Research Alliance of Canada, has led by example to improve the visibility and discoverability of research data repositories. DMEG assists data creators, curators, and other professionals in the planning, creation, management, and dissemination of descriptive metadata to enable effective discovery and reuse of research data across a broad range of disciplines. <h3>The Canadian Data Repositories Landscape Working Group</h3> Among other activities, DMEG established the short-term Canadian Data Repositories Landscape Working Group in April 2021. The group reviewed and updated existing Canadian repository records in re3data, and identified new repository candidates to be added into the registry. This work built on previous fruitful collaborations to index and map the Canadian repository landscape in re3data. The re3data registry was selected as the preferred central reference point for information on Canadian data repositories because of its strong editorial practices, broad coverage, and integrations with global digital research infrastructures. The project group established inclusion criteria for indexing Canadian research data repositories in the light of re3data’s <a href="https://www.re3data.org/suggest">registration policy</a>. Based on these criteria, new repository candidates were identified and communicated to re3data so that they could be added to the registry. According to the recently published <a href="https://doi.org/10.5281/zenodo.7709062">project report of the working group</a>, 153 potential repositories were submitted for review to the re3data editorial team. The repository suggestions were pre-structured in similar batches (e.g. by institutional repositories in case of university repositories or by region in case of governmental repositories) for more effective processing. The pre-filled fields were examined and extended piece by piece by re3data’s <a href="https://www.re3data.org/editorialboard">editorial board</a>. In addition to new suggestions, all existing entries of Canadian repositories were checked for consistency, whereby re3data provided support on the best possible application of its <a href="https://www.re3data.org/schema">schema</a>. The re3data team benefitted from insights into the diversity of the Canadian repository landscape and its networks. Especially for areas that the International Editorial Board cannot cover comprehensively, this information is esential for achieving high-quality metadata. <h3>Recommendations for repository operators</h3> The project also aimed to highlight the value of re3data for different stakeholders within the Canadian research data management community. Recommendations have been developed on how to improve the discoverability and accuracy of Canadian data repositories via re3data: <ul> <li>Operators of Canadian repositories not yet indexed in re3data should consider submitting a <a href="https://www.re3data.org/suggest">registration request</a> in order to help researchers discover and use the unique research data sets they disseminate.</li> <li>Operators of Canadian repositories should notify...</li></ul> ]]> </content> </entry> <entry> <title>Materials from the re3data COREF / CoreTrustSeal Workshop on Quality Management at Research Data Repositories</title> <id>https://coref.project.re3data.org/blog/workshop_materials</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2022-11-17T08:54:00+00:00</published> <link href="https://coref.project.re3data.org/blog/workshop_materials"/> <content type="html"> <![CDATA[ <img alt="" src="/images/d/8/4/5/e/d845e7a49bd80865aeaf638fed4386e522de34ad-image.jpg" /> The objective of the workshop was to approach the pervasive, yet elusive topic of data quality management from several angles. To ensure a common frame of reference for the workshop, contributions were guided by the Framework for Quality Assurance of Data Publications at Research Data Repositories that was developed as part of a PhD project. In the first part of the workshop, results from a comprehensive survey on data quality assurance at research data repositories that was conducted in the project re3data COREF were presented, followed by reflections on quality management from the perspective of the certification organization CoreTrustSeal. In the second part, repositories from earth and environmental sciences (PANGAEA), humanities (ARCHE) and social sciences (UK Data Archive) shared their approaches on data quality assurance. After these presentations, the participants joined breakout discussions, where they further discussed the quality assurance measures they perform and the challenges they face. The workshop was attended by more than 70 participants, most reported working at a repository or a similar service. 10 participants stated that their repository had obtained a certificate, for example CoreTrustSeal. Recordings and presentation slides of the first two parts of the workshop are published and linked below. A workshop report is planned and will be shared once published. <h2>Workshop materials</h2> <h3>Documentation</h3> Kindling, M., Strecker, d., Ferguson, L. M., L'Hours, H., Magder, C., Schabinger, R., Vierkant, P., Weisweiler, N. (2023). Report on re3data COREF / CoreTrustSeal Workshop on Quality Management at Research Data Repositories. Informationspraxis. <a href="https://doi.org/10.11588/ip.2022.1.93173">https://doi.org/10.11588/ip.2022.1.93173</a> <h3>Part 1: Data quality assurance from the perspective of a repository registry and certification organization</h3> re3data COREF - Quality Management at Research Data Repositories. Results from a survey and Framework of Quality Assurance for Data Publications at Research Data Repositories (Maxi Kindling) <ul> <li>Recording: <a href="https://doi.org/10.5446/59609">https://doi.org/10.5446/59609</a></li> <li>Presentation slides: <a href="https://doi.org/10.5281/zenodo.7142736">https://doi.org/10.5281/zenodo.7142736</a></li> </ul> CoreTrustSeal - Data Quality Assurance from the Perspective of CoreTrustSeal (Hervé L’Hours) <ul> <li>Recording: <a href="https://doi.org/10.5446/59610">https://doi.org/10.5446/59610</a></li> <li>Presentation slides: <a href="https://doi.org/10.5281/zenodo.7228059">https://doi.org/10.5281/zenodo.7228059</a></li> </ul> <h3>Part 2: Repositories sharing their approach to quality management</h3> ARCHE - Quality Assurance at ARCHE (Seta Štuhec) <ul> <li>Recording: <a href="https://doi.org/10.5446/59611">https://doi.org/10.5446/59611</a></li> <li>Presentation slides: <a href="https://doi.org/10.5281/zenodo.7228083">https://doi.org/10.5281/zenodo.7228083</a></li> </ul> UK Data Service - Data Quality Assurance at UK Data Service (Cristina Magder) <ul> <li>Recording: <a href="https://doi.org/10.5446/59763">https://doi.org/10.5446/59763</a></li> <li>Presentation slides: <a href="https://doi.org/10.5281/zenodo.7228029">https://doi.org/10.5281/zenodo.7228029</a></li> </ul> <img title="image" alt="image" src="/images/8/3/0/f/f/830ffdc65c0baeddb3b9d8e119ab75328bbe7bc7-image.jpg" /> ]]> </content> </entry> <entry> <title>Happy 10th Anniversary, re3data!</title> <id>https://coref.project.re3data.org/blog/10th-anniversary</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2022-09-05T12:16:00+01:00</published> <link href="https://coref.project.re3data.org/blog/10th-anniversary"/> <content type="html"> <![CDATA[ <img alt="" src="/images/3/d/5/4/4/3d544512b3ddbb7590a08611b6888a76e305cd40-re3datameetingkarlsruhe1.jpg" /> In this post, the authors celebrate the 10th anniversary of re3data, sharing insights about the history, the service itself, and how it has developed over the last decade. The post was published simultaneously on the DataCite Blog. The <a href="https://www.re3data.org/">re3data</a> registry went online in 2012 and is celebrating a decade of curation and making information about data repositories available to the research community. About ten years ago, two projects – one in the United States and another in Germany – began indexing data repositories and laid the groundwork for what would become the service that we know today. The <a href="https://www.ibi.hu-berlin.de/en">Berlin School of Library and Information Science</a> at the Humboldt-Universität zu Berlin, the <a href="https://os.helmholtz.de/en/">Helmholtz Open Science Office</a>, and the <a href="http://www.bibliothek.kit.edu/">Karlsruhe Institute of Technology (KIT) Library</a> collaborated to develop re3data in Germany, funded by the German Research Foundation (DFG). A similar effort, Databib, was initiated at the <a href="https://www.lib.purdue.edu">Purdue University Libraries</a> in the United States, sponsored by the Institute of Museum and Library Services (IMLS) in the United States. Rather than compete with each other, the two registries joined forces in 2013 and combined their efforts to create an international service that has since been hosted by the KIT. A comprehensive <a href="https://www.re3data.org/schema">metadata schema</a> was created and nearly 3,000 research data repositories have been indexed by our dedicated team of editors. For many years, the registry operated as a service of DataCite and supported by the re3data Working Group, a collaboration that continues as the registry has evolved to become a DataCite <a href="https://datacite.org/partnerservices.html">partner service</a> with an <a href="https://www.re3data.org/editorialboard">international editorial board</a> that spans the globe and covers every research domain. Many members of the re3data team had the joyful opportunity to meet in person in July in Karlsruhe to celebrate, share memories, and to look ahead to the future. Of course, there was a great dinner, beer, fellowship, and a birthday cake! <img title="re3data_Meeting_Karlsruhe1" alt="re3data_Meeting_Karlsruhe1" src="/images/7/5/7/0/b/7570bf1affd32ebc65b11184b89e0a7c232b1080-re3datameetingkarlsruhe1.jpg"> We also engaged in important discussions about future developments for re3data, guided by the principles that we share: collaboration, diversity, utility, trust, and openness. We will continue to strive for inclusivity, representation, and participation across disciplines, languages, geographies, and cultures. In the development of new functionality, we prioritize accessibility and usability for researchers and other users of the registry. re3data should be a trusted, reliable service that maximizes availability and accuracy. Last but not least, we strive to practice and advance open science. To this end, we have always made all records in re3data available for reuse under a <a href="https://creativecommons.org/publicdomain/zero/1.0/">CC0</a> license through an <a href="https://www.re3data.org/api/doc">open API</a> with <a href="https://github.com/re3data/using_the_re3data_API">some examples</a>. Services and organizations that <a href="https://www.re3data.org/publications">reference re3data</a> or use metadata from the registry include funder recommendations such as from the <a href="https://ec.europa.eu/research/participants/docs/h2020-funding-guide/cross-cutting-issues/open-access-data-management/open-access_en.htm">European Commission</a> and <a href="https://www.nsf.gov/pubs/2022/nsf22055/nsf22055.jsp">National Science Foundation</a>, guidelines from publishers, resource guides by libraries, and other stakeholders, service providers, and scholars in the research community. Reaching ten years of service would not have been possible without the sustained contributions and collaboration of all stakeholders involved in re3data – our working group, the international editorial board, our project partners, funders, all of the past and current members... ]]> </content> </entry> <entry> <title>re3data COREF / CoreTrustSeal Workshop on Data Quality Management at Repositories</title> <id>https://coref.project.re3data.org/blog/save-the-date-5-october-2022-re3data-coref-coretrustseal-workshop-on-data-quality-management-at-repositories</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2022-08-22T17:38:00+01:00</published> <link href="https://coref.project.re3data.org/blog/save-the-date-5-october-2022-re3data-coref-coretrustseal-workshop-on-data-quality-management-at-repositories"/> <content type="html"> <![CDATA[ <img alt="" src="/images/0/d/6/e/1/0d6e1fc269d5b11def6c0fee6b0692a628167ce3-frameworkeng-2.png" /> Data quality assurance is a fundamental issue for repositories that seek to ensure trust in their services. This workshop focused on measures research data repositories undertake to ensure data quality. The objective of this workshop was to raise awareness and make the various activities repositories perform to assure, assess, and improve data quality visible. The workshop was organized by Humboldt-Universität zu Berlin in collaboration with CoreTrustSeal and the Helmholtz Open Science Office and took place on October 5, 2022, 12:00-15:30 UTC. The workshop consisted of three parts. It started with presentations of a survey on research data quality assurance at repositories conducted in 2021 as part of the re3data COREF project as well as lessons from the CoreTrustSeal consultation processes. Operators of repositories with different scopes presented their approaches to quality assurance. Based on this input, we discussed options for making information on data quality assurance visible at the level of repositories. Results of the discussion are documented and shared with the public to be reused by repository services such as re3data, CoreTrustSeal, as well as other community initiatives. <h3>Documentation</h3> Kindling, M., Strecker, d., Ferguson, L. M., L'Hours, H., Magder, C., Schabinger, R., Vierkant, P., Weisweiler, N. (2023). Report on re3data COREF / CoreTrustSeal Workshop on Quality Management at Research Data Repositories. Informationspraxis. <a href="https://doi.org/10.11588/ip.2022.1.93173">https://doi.org/10.11588/ip.2022.1.93173</a> <h3>Details</h3> <ul> <li>Format: Online workshop (3,5h)</li> <li>Date: 2022-10-05, 12:00-15:30 UTC</li> <li>Audience: The workshop addresses repository managers, data managers, data curators, and all stakeholders interested in quality management at repositories. </li> </ul> Contact: Maxi Kindling (maxi.kindling@hu-berlin.de) <img title="Framework_eng-2" alt="Framework_eng-2" src="/images/5/e/6/7/c/5e67c6fbcad0a798c85ff1fcc139ec4d952f39d2-frameworkeng-2.png" /> ]]> </content> </entry> <entry> <title>Mapping the global repository landscape</title> <id>https://coref.project.re3data.org/blog/mapping-the-global-repository-landscape</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2022-03-15T10:00:00+00:00</published> <link href="https://coref.project.re3data.org/blog/mapping-the-global-repository-landscape"/> <content type="html"> <![CDATA[ <img alt="" src="/images/4/5/f/1/c/45f1cd534b2ba15cf5b4ebc31f1f55bb2346f50e-chordchart.png" /> International collaboration has become very common in the production of scientific knowledge (Coccia and Wang, 2016; Monastersky & Van Noorden, 2019) and contributes substantially to the research output of several countries (Adams, 2013). Moreover, international collaboration can also support the operation and maintenance of pervasive research infrastructures, for example research data repositories (Kindling et al., 2017). Even though science operates in this international context, in some cases it can still be desirable to opt for a national, regional or local perspective on aspects of scholarly communication, for example for the purposes of developing and monitoring resources. This need for a location based perspective can also apply to research data repositories, even though it might be difficult to achieve for several reasons. For example, repositories offer services to both data providers and data users. These groups might differ in terms of their geographical distribution – particularly data users might access and reuse datasets from all over the world, even if the repositories cater mainly to data providers from specific countries. Repositories are also complex infrastructures. Several institutions can be involved in the operation of a repository; and sometimes partners from multiple countries take on various roles. Despite these difficulties, some authors have successfully used the metadata provided by re3data to study research data repositories from a specific region. For example, re3data metadata contributed to analyze usage and costs associated with research data management (e.g., von der Heyde, 2019) or was used for studying the repository landscape in a specific country (e.g., Li et al., 2022). In this blog post, we want to illustrate the characteristics of location information in re3data on a map, analyze international collaborations that run research data repositories, and describe what to watch out for when using re3data metadata. <h4>Location information in re3data</h4> Location information in re3data is not directly associated with a repository, but instead refers to the legal address of the institutions responsible for a repository. This approach to modeling location information was chosen because repositories are virtual services, meaning that the data might not be stored on-site. As a result, data is often not stored where it is curated, making it difficult to determine “where a repository is”. In the <a href="https://doi.org/10.48440/re3.010">re3data Metadata Schema</a>, this information is stored in the element institutionCountry, based on the ISO 3166-1 standard for country names. The controlled vocabulary also includes values for international and EU institutions. The filter “Countries” in the graphical user interface of the <a href="https://www.re3data.org/search">re3data search</a> is built on this element. It is important to note that institutional responsibilities for repositories are very complex and dynamic. Multiple institutions can be responsible for a repository, and responsibilities often change over time. Therefore, if a large number of institutions is listed as partners for a repository, the re3data Editorial Team might not list all of them, but adds a URL to a website listing all institutions to the remarks. For all 2792 repositories listed in re3data currently, there is an average of 2.9 institutions being responsible for the repository.... ]]> </content> </entry> <entry> <title>How open are repositories in re3data?</title> <id>https://coref.project.re3data.org/blog/how-open-are-repositories-in-re3data</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2021-12-06T13:48:00+00:00</published> <link href="https://coref.project.re3data.org/blog/how-open-are-repositories-in-re3data"/> <content type="html"> <![CDATA[ <img alt="" src="/images/4/f/9/c/f/4f9cf5df9354444b839c266f71ca3ae4bf3ce395-newaccesslevels.png" /> Openness may sound self-evident, but in fact it can mean different things, even within the Open Science community (Pasquetto, Sands & Borgman, 2015). To align understanding and to ensure common goals in the transition to Open Science, clear definitions are needed. The Open Knowledge Foundation defines knowledge as open "if anyone is free to access, use, modify, and share it – subject, at most, to measures that preserve provenance and openness." (<a href="https://opendefinition.org/od/2.1/en/">Open Definition 2.1</a>) To account for disciplinary and procedural affordances in different research endeavours, the term “intelligent openness” has been coined by Boulten et al. (2012), denoting an openness that is “as open as possible and as closed as necessary”. Overall, a key effect of (intelligent) openness pertains to making “scientific knowledge openly available, accessible and reusable for everyone“ (United Nations Educational, Scientific and Cultural Organization, 2021, Annex p. 4). <h4>Open repositories</h4> Repositories are central infrastructures for opening data, enabling "broad, equitable and ideally open access to content" (European Commission, 2021, p. 155). In this capacity, repositories that provide open access to research output can also be considered "open". However, openness is more complex for repositories, because several characteristics of a repository influence its openness overall. For example, in its terms of use, a research data repository can provide free access to its metadata, or to datasets, or it can offer its services to any researcher without or with minimal restrictions. In the context of the openness of repositories, some sources mention only aspects related to discovering and retrieving data (e.g., <a href="https://casrai-test.evision.ca/glossary-term/repository-access/">CASRAI Research Data Management Terms</a>). Other sources suggest a much broader understanding of accessible repositories, such as avoiding proprietary data formats or making documentation and metadata accessible to persons with disabilities (e.g., <a href="https://www.coar-repositories.org/coar-community-framework-for-good-practices-in-repositories/">COAR Community Framework for Good Practices in Repositories</a>). This blog post is not intended to present a new definition of open repositories, but an approach to making certain aspects of openness visible in re3data, with the intention to help researchers find repositories that are suitable for publishing their data. <h4>Describing openness for repositories in re3data</h4> re3data provides information on openness for indexed repositories via its icon system (see figure 1). The icon system is displayed for all repositories and gives re3data users an overview of key characteristics. For example, the lock symbol tells re3data users whether a repository is considered open, restricted or closed. The lock symbol in the re3data icon system is derived from metadata that describe the access conditions of research data repositories. To be indexed in re3data, a repository must provide information about access to the metadata and data stored as well as the terms of use. <img src="/blog/how-open-are-repositories-in-re3data/./re3data_icon_system.jpg" alt=""> Figure 1: The re3data icon system. Generally, access conditions in re3data are covered by three elements (see <a href="https://www.re3data.org/schema">re3data Metadata Schema</a>): databaseAccessType, dataAccessType and dataUploadType. databaseAccessType refers to the access to the research data repository in general, indicating whether the metadata can be found and accessed by users and services. dataAccessType describes the access to datasets in the repository, and... ]]> </content> </entry> <entry> <title>Reviewing the subject classification in re3data</title> <id>https://coref.project.re3data.org/blog/reviewing-the-subject-classification-in-re3data</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2021-10-18T10:00:00+01:00</published> <link href="https://coref.project.re3data.org/blog/reviewing-the-subject-classification-in-re3data"/> <content type="html"> <![CDATA[ <img alt="" src="/images/4/9/0/8/5/4908524725971b929fdf2dcc46167162b8abe1fe-dfgre3data.png" /> When looking for a suitable repository, the discipline(s) a repository caters to is one of the most important pieces of information. The <a href="http://doi.org/10.48440/re3.010">re3data Metadata Schema</a> reflects this priority by requiring the element subject for all indexed repositories. However, describing the disciplinary focus of research data repositories is not an easy task. In this blog post, we therefore analyze the status quo of subject classification in re3data, and outline some options for going forward. <h4>The DFG Subject Areas</h4> Currently, re3data uses an older version of the <a href="https://web.archive.org/web/20140901204254/http://dfg.de/en/dfg_profile/statutory_bodies/review_boards/subject_areas/index.jsp">DFG Subject Areas</a>. This classification comprises four levels. At the top level, there are four disciplines: Humanities and Social Sciences, Life Sciences, Natural Sciences and Engineering Sciences. The granularity increases with each level. Across all levels, there are 275 categories (see Figure 1). <img alt="Figure 1: Structure of the re3data subject classification" src="/images/a/3/6/8/d/a368d340f07bb173025b34a8410c095faf3436fd-dfgre3data.png"> Figure 1: Structure of the re3data subject classification <h4>Subject information in re3data</h4> re3data has used the DFG Subject Areas for subject information for nine years. Subject information in re3data serves two main purposes: describing repositories in adequate depth, enabling re3data users to find a repository that suits their specific needs; and creating separation between repositories, enabling re3data users to distinguish repositories based on their disciplinary focus. <h4>Depth</h4> When describing a repository, re3data editors generally select the most specific categories that are applicable. Generalist or multidisciplinary repositories, for example <a href="https://www.re3data.org/repository/r3d100010468">Zenodo</a>, are assigned abstract categories from the top level to indicate their broad disciplinary focus (see Figure 2A). In contrast, specialized disciplinary repositories such as the <a href="https://www.re3data.org/repository/r3d100010791">National Center for Atmospheric Research</a> are described in more depth (see Figure 2B). <img alt="Figure 2: subjects assigned to Zenodo (A) and National Center for Atmospheric Research (B)" src="/user/pages/02.blog/09.reviewing-the-subject-classification-in-re3data/repository_comparison.png"> Figure 2: subjects assigned to Zenodo (A) and National Center for Atmospheric Research (B) This approach ensures a solid description of the disciplinary affiliation of repositories in re3data, which is reflected in the fact that a notation at the third level of the DFG Subject Areas was assigned to approximately 86% of all repositories indexed in re3data (see Figure 3). If necessary, re3data users can gradually narrow down the results of a search query by selecting increasingly specific notations. Thus, in terms of depth, the DFG Subject Areas is well suited for re3data. <img alt="Figure 3: depth of notations by repository; each level is counted once" src="/user/pages/02.blog/09.reviewing-the-subject-classification-in-re3data/depth_repositories.png"> Figure 3: depth of notations by repository; each level is counted once <h4>Separation</h4> Using the DFG Subject Areas for describing research data repositories also creates sufficient separation. About two thirds of all repositories indexed in re3data are assigned notations from just one discipline (the four broadest categories of the classification; see Figure 4). In most cases, users therefore get a good idea of which discipline a repository belongs to. For example, the National Center for Atmospheric Research is only assigned notations from Natural Sciences (see Figure 2B). This assessment might, however, be less relevant for generalist multidisciplinary repositories. <img alt="Figure 4: number of disciplines from which a repository is assigned notations; each discipline is counted once" src="/user/pages/02.blog/09.reviewing-the-subject-classification-in-re3data/overlap_l1.png"> Figure 4: number of disciplines from which a repository is assigned notations; each discipline is counted once <h4>Friction</h4> In terms of depth and separation, the DFG Subject Areas works well for re3data. However, this subject classification was not developed with the description of repositories in mind - its main purpose is the... ]]> </content> </entry> <entry> <title>From stakeholder survey and workshops to the new Conceptual Model for User Stories – a journey</title> <id>https://coref.project.re3data.org/blog/from-workshops-to-the-new-model-of-user-stories-for-re3data-a-journey</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2021-09-30T15:52:00+01:00</published> <link href="https://coref.project.re3data.org/blog/from-workshops-to-the-new-model-of-user-stories-for-re3data-a-journey"/> <content type="html"> <![CDATA[ <img alt="" src="/images/7/7/d/7/f/77d7f343a79f2890bda8e516fd02591e1183d2e9-explore-45855211280.jpg" /> To keep track of where you are going, you need to check your compass from time to time. For this purpose, the re3data COREF project undertook a series of workshops in 2020 and have now come up with a new Conceptual Model for User Stories for the Registry of Research Data Repositories – re3data. We are grateful to welcome you along this journey and share our results with you. Since 2012, re3data has been a relevant part of the open science service landscape. The registry provides substantial information about research data repositories (RDR) directly for researchers. In addition to this, several other services reuse re3data metadata about RDR to provide additional services for their target audiences (be it individuals or institutions). To adapt re3data and its metadata to the current needs of involved stakeholders the re3data COREF project conducted a stakeholder survey and held a series of workshops at the end of 2020. Participants were asked about the ways they already use re3data and how they would like to use re3data in the future. The results and findings of the survey, presentations, and discussions are documented and have been published in the <a href="https://doi.org/10.48440/re3.013">re3data Stakeholder Survey and Workshop Report</a>. This report represents the basis of the <a href="https://doi.org/10.48440/re3.012">Conceptual Model for User Stories</a>, published in August 2021. The publication of both the report and the model are important milestones within the re3data COREF project. The model describes the history, governance, and current technical infrastructure of re3data. The results of the report were consulted in restructuring the model’s main section concerning target groups and user stories. Both documents allow the project and service teams to recalibrate re3data according to current and future needs of the community. If you have any feedback regarding the report or Conceptual Model for User Stories, please get in touch with the re3data COREF team via <a href="mailto:info@re3data.org">info@re3data.org</a>. We would like to thank all participants for their contributions to the workshops and will continue to work to maintain and expand re3data as a vital resource for the scientific community and its infrastructures! <img alt="" src="/images/3/5/9/9/5/35995d9ca15fe50d3032874d9b230660cb3cb4ba-explore-45855211280.jpg" /> ]]> </content> </entry> <entry> <title>Releasing version 3.1 of the re3data Metadata Schema</title> <id>https://coref.project.re3data.org/blog/releasing-version-3-1-of-the-re3data-metadata-schema</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2021-08-10T15:54:00+01:00</published> <link href="https://coref.project.re3data.org/blog/releasing-version-3-1-of-the-re3data-metadata-schema"/> <content type="html"> <![CDATA[ <img alt="" src="/images/5/4/5/3/9/54539e65774d382081f6a61607827f5028f6ed39-elementcount.png" /> Detailed descriptions of research data repositories are at the core of re3data. They increase a repository's visibility by enabling re3data users to find a suitable service for storing their data. Repository descriptions are based on the re3data Metadata Schema, which covers various aspects of research data repositories, including general scope, content, policies as well as compliance with technical and metadata standards. Version 1.0 of the schema was published in 2012. As repositories evolved, the schema was expanded and adapted regularly across versions 2.0, 2.1, 2.2, and 3.0 (see Figure 1). <img src="/blog/releasing-version-3-1-of-the-re3data-metadata-schema/./element_count.png" alt="" /> We are happy to announce the release of <a href="https://www.re3data.org/schema">version 3.1</a> of the re3data Metadata Schema as of August 2021, which is now ready to be implemented in re3data’s technical infrastructure. <h4>Version 3.1 introduces two major changes on top of manifold minor changes</h4> certificate: Version 3.1 expands descriptions of repository certification. References to a document outlining details of the certificate as well as certification start and end date will describe the certification status in greater detail. profile: The new property profile provides the opportunity to identify a subset of repositories indexed in re3data pre-defined by a third party based on community-developed criteria. Each profile has to provide a URL outlining the selection criteria. Feedback provided by the repository community via workshops, interviews, poster presentations, conference papers, and personal communication has accompanied every step of the schema development. In a public request for comments preceding the release of version 3.1, we received more than 150 comments. We thank the repository community for their valuable contributions; some suggestions could already be implemented in version 3.1. All remaining suggestions will be discussed and considered for following revisions. ]]> </content> </entry> <entry> <title>Using the re3data API</title> <id>https://coref.project.re3data.org/blog/using_the_re3data_api</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2021-06-15T11:25:00+01:00</published> <link href="https://coref.project.re3data.org/blog/using_the_re3data_api"/> <content type="html"> <![CDATA[ <img alt="" src="/images/9/c/c/2/5/9cc25f28d5e7f98fe22a57e42e933b57de1f380d-re3dataapi.png" /> re3data offers detailed descriptions of more than 2600 repositories. These descriptions are based on the <a href="https://www.re3data.org/schema/2-2">re3data Metadata Schema</a> and can be accessed via the<a href="https://www.re3data.org/api/doc"> re3data API</a>. There are many conceivable use cases for re3data metadata. We set up a <a href="https://github.com/re3data/using_the_re3data_API">GitHub repository</a> where we provide some examples for using the re3data API. The examples are implemented in <a href="https://www.r-project.org/">R</a> using Jupyter Notebooks. <a href="https://jupyter.org/">Jupyter Notebooks</a> are interactive computational environments combining executable code and markdown text. The notebooks we provide outline the use case as well as each step in the process of data collection, processing and visualization (if applicable). Currently, the GitHub repository covers two use cases: <h4>Identifying and collecting information about repositories catering to the medical research community</h4> As a research data manager in medical science, you might be looking for a suitable repository for researchers at your institution to deposit their data. Suitable repositories might be catering to medical research, offering data upload and assigning DOIs to datasets. Repositories meeting these specifications can be identified via the re3data API. The API also provides the option to retrieve further information about these repositories, such as the name of the repository or a description. <h4>Analyzing the distribution of certificates across repository types</h4> As an observer of the repository landscape, you might be interested in conducting multivariate analysis of repository characteristics, for example the distribution of certification status across repository types. Research data repositories are diverse. The re3data Metadata Schema tries to account for that, resulting in rich and detailed metadata that can be accessed via the re3data API. The notebooks were designed to be reused and adapted to fit other use cases. If your specific use case is not covered here, feel free to contact us: <a href="mailto:info@re3data.org">info@re3data.org</a>. Visit the <a href="https://github.com/re3data/using_the_re3data_API">GitHub repository...</a> <img src="/blog/using_the_re3data_api/./re3data_API.png" alt="" /> This work "re3data_API" is a detrivative of <a href="http://www.pngall.com/cat-png/download/119">Cat PNG 2 </a> by <a href="http://www.pngall.com/author/rojal">Rojal</a>, used under <a href="https://creativecommons.org/licenses/by-nc/4.0/" style="margin-right: 5px;">CC BY-NC 4.0</a>, and is licensed under <a href="https://creativecommons.org/licenses/by-nc/4.0/" style="margin-right: 5px;">CC BY-NC 4.0</a>by the re3data team. ]]> </content> </entry> <entry> <title>How to ensure "good" data? A presentation at Open Repositories 2021</title> <id>https://coref.project.re3data.org/blog/how-to-ensure-good-data-a-presentation-at-open-repositories-2021</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2021-06-10T15:51:00+01:00</published> <link href="https://coref.project.re3data.org/blog/how-to-ensure-good-data-a-presentation-at-open-repositories-2021"/> <content type="html"> <![CDATA[ <img alt="" src="/images/6/d/a/0/c/6da0c633e98941fca334832a4e2791a2034a5b06-wp4.png" /> <h4>Data quality as a research topic in re3data COREF</h4> Among other activities, re3data COREF is conducting multi-method empirical research into data quality and data quality assurance practices at data repositories. Based on qualitative content analysis of data journal guidelines and CoreTrustSeal self assessment documents, we developed a survey that was distributed among operators of repositories indexed in re3data. Results of the survey will contribute to revising the metadata element r3d:qualityManagement (see <a href="http://doi.org/10.2312/re3.008">re3data metadata schema 3.0</a>), with the goal of increasing the visibility of efforts to ensure data quality at data repositories. <h4>Presentation at Open Repositories 2021</h4> Today, we presented an overview on the project, our research and preliminary results of the survey at the Open Repositories 2021 conference. If you missed our presentation, you can find the presentation slides <a href="/blog/how-to-ensure-good-data-a-presentation-at-open-repositories-2021/./presentation_OR2021.pdf">here</a>. Please note that the survey is still running (until 14 June 2021), so results might change. <img src="/blog/how-to-ensure-good-data-a-presentation-at-open-repositories-2021/./WP4.png" alt="" /> ]]> </content> </entry> <entry> <title>Using and referencing re3data</title> <id>https://coref.project.re3data.org/blog/using-and-referencing-re3data</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2021-05-31T11:17:00+01:00</published> <link href="https://coref.project.re3data.org/blog/using-and-referencing-re3data"/> <content type="html"> <![CDATA[ <img alt="" src="/images/5/b/0/5/c/5b05c1e391787d1fa9aa3b4380bfb9fac5550f18-bibtexcategories.png" /> The German version of this article has been published on the <a href="https://blogs.tib.eu/wp/dini-ag-blog/2021/05/27/re3data-literaturanalyse/">DINI AG-FIS and AG-E-Pub blog</a>. As a global directory, <a href="https://www.re3data.org/">re3data</a> describes research data repositories from all scientific disciplines. It lists repositories that enable researchers, funding organizations, publishers and scientific institutions to permanently store research data and ensure access to datasets. The registry has been online since fall 2012 and has received multiple grants from the German Research Foundation (DFG). In March 2013, the two registries re3data and Databib were merged into one service, which has been managed under the auspices of DataCite since late 2015. Since then, the international team of <a href="https://www.re3data.org/editorialboard">experienced editors</a> has indexed more than 2600 research data repositories based on a <a href="https://doi.org/10.2312/re3.008">comprehensive metadata schema</a>, which is currently being further developed and improved. The German Research Foundation (DFG) has been funding the project "re3data COREF (Community Driven Open Reference for Research Data Repositories)" for a period of 36 months since January 2020. The aim of the project is to further expand re3data and to network it even more closely with other services and infrastructures as a reference for research data repositories. re3data is designed as a tool for researchers who are looking for a suitable repository to publish their data. The metadata stored for each repository can also be used for other purposes, such as a data source for monitoring and analyzing the landscape of research data repositories. In this blog post, we explore how re3data is currently referenced in the scientific literature and highlight various uses of the service. <h3>How is re3data being used?</h3> <h4>Data collection and processing</h4> The following analysis examines documents that mention and refer to re3data. These documents have been identified by monitoring several sources continuously, including the bibliographic databases Scopus, Web of Science, and Google Scholar. These references were managed and annotated in Zotero. As of March 5, 2021, the Zotero library comprised 1571 documents in total (available <a href="https://www.zotero.org/groups/2856942/using_and_referencing_re3data/library">here</a>). <h4>Results</h4> Based on our current findings, re3data is mentioned in documents using at least 25 languages. This shows that the service not only lists repositories worldwide, but is also referenced and used globally. Information on the language used is available for 913 documents in the collection. The collection includes various types of documents, which are based on BibTex document types. In total, 9 document types are present in the collection. Figure 1 shows the number of documents mentioning re3data per publication year (cumulative), split by document type (1524 documents, excluding documents added in 2021). As the plot shows, the number of publications increased continually. On the one hand, this observation coincides with growing publication rates in general, but it also indicates increasing interest in and continued use of re3data. Article (567) and other (551; including, for example, guidelines from journals or other entities, posters and presentation slides) are the most common document types. The publication year 2021 is not included in this plot. This year, however, various new documents that mention re3data and refer to its use have already been... ]]> </content> </entry> <entry> <title>Request for Comments: Version 3.1 of the re3data Metadata Schema (closed)</title> <id>https://coref.project.re3data.org/blog/request-for-comments-version-3-1-of-the-re3data-metadata-schema</id> <updated>2024-02-28T14:26:31+00:00</updated> <published>2021-05-06T11:19:00+01:00</published> <link href="https://coref.project.re3data.org/blog/request-for-comments-version-3-1-of-the-re3data-metadata-schema"/> <content type="html"> <![CDATA[ <img alt="" src="/images/d/9/b/4/4/d9b4466f148f64f66ce9309371135ec26e72282c-feedbackm.jpg" /> UPDATE: The revised version 3.1 of the re3data Metadata Schema was published in August 2021 and can be accessed via the <a href="https://www.re3data.org/schema">re3data website</a>. re3data currently describes more than 2600 research data repositories from all disciplines based on the re3data Metadata Schema. The current <a href="https://doi.org/10.2312/re3.008">version 3.0</a> of the re3data Metadata Schema was released in 2015. Since then, the repository landscape and the requirements and expectations for a registry of research data repositories have shifted. Within the project re3data COREF, we address these changes and will progressively revise the re3data Metadata Schema. We therefore invite you to participate in the Request for Comments for our first planned revision of the re3data Metadata Schema within the re3data COREF project (version 3.1) by commenting on <a href="https://docs.google.com/document/d/1_FIQ25YjNeimQByeQxbJ8qdrmKq89qvKj-0XWiGAc-0/edit?usp=sharing">this document</a> until May 28th, 2021. Properties that have been significantly changed or were added with this draft are highlighted in the document, we particularly welcome comments on these properties. Note that the re3data Metadata Schema will be further revised as the project progresses. Your comments are highly appreciated and will be discussed and considered for the final version 3.1 of the re3data Metadata Schema. <h4>Version 3.1 introduces two major changes:</h4> certificate: Version 3.1 will expand descriptions of repository certification. References to a document outlining details of the certificate as well as certification start and end date will describe the certification status in greater detail. profile: The new property profile provides the opportunity to identify a subset of repositories indexed in re3data pre-defined by a third party based on community-developed criteria. Each profile has to provide a URL outlining the selection criteria. <img alt="" src="/images/0/a/5/5/0/0a550f18eaf766e391d6ef73cd4004381d89a447-feedbackm.jpg" /> <a href="https://www.flickr.com/photos/59217476@N00/10173857405">"Feedback"</a> by <a href="https://www.flickr.com/photos/59217476@N00">giulia.forsythe</a> is licensed under <a href="https://creativecommons.org/licenses/by-nc-sa/2.0/?ref=ccsearch&atype=html" style="margin-right: 5px;">CC BY-NC-SA 2.0</a> ]]> </content> </entry> </feed>