CINXE.COM
How open are repositories in re3data? | re3data COREF - project blog
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <title>How open are repositories in re3data? | re3data COREF - project blog</title> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta name="generator" content="GravCMS" /> <meta name="description" content="re3data COREF - project blog" /> <link rel="icon" type="image/png" href="/user/themes/quark/images/favicon.png" /> <link rel="canonical" href="https://coref.project.re3data.org/blog/how-open-are-repositories-in-re3data" /> <link href="/user/plugins/latest-tweets/assets/css/latest-tweets.css" type="text/css" rel="stylesheet"> <link href="https://use.fontawesome.com/releases/v5.0.13/css/all.css" type="text/css" rel="stylesheet"> <link href="/user/plugins/markdown-notices/assets/notices.css" type="text/css" rel="stylesheet"> <link href="/user/themes/quark/css-compiled/spectre.min.css" type="text/css" rel="stylesheet"> <link href="/user/themes/quark/css-compiled/theme.min.css" type="text/css" rel="stylesheet"> <link href="/user/themes/quark/css/custom.css" type="text/css" rel="stylesheet"> <link href="/user/themes/quark/css/line-awesome.min.css" type="text/css" rel="stylesheet"> <script src="/system/assets/jquery/jquery-3.x.min.js"></script> <script src="https://platform.twitter.com/widgets.js"></script> </head> <body id="top" class=" header-fixed header-animated sticky-footer"> <div id="page-wrapper"> <section id="header" class="section"> <section class="container grid-lg"> <nav class="navbar"> <section class="navbar-section logo"> <a href="/" class="navbar-brand mr-10"> <img src="/user/themes/quark/images/logo/re3data_COREF_Logo_RGB_3.png" alt="re3data COREF - project blog" /> </a> </section> <section class="navbar-section desktop-menu"> <nav class="dropmenu animated"> <ul > <li> <a href="/" class="active"> Blog </a> <ul> <li> <a href="/blog/re3data-call-for-editorial-board" class=""> re3data Call for Editorial Board </a> </li> <li> <a href="/blog/request-for-comments-version-4-0-of-the-re3data-metadata-schema" class=""> Request for Comments: Version 4.0 of the re3data Metadata Schema (closed) </a> </li> <li> <a href="/blog/canadian-research-data-repositories-in-re3data" class=""> Canadian research data repositories in re3data: A collaborative effort to increase visibility and foster community engagement </a> </li> <li> <a href="/blog/workshop_materials" class=""> Materials from the re3data COREF / CoreTrustSeal Workshop on Quality Management at Research Data Repositories </a> </li> <li> <a href="/blog/10th-anniversary" class=""> Happy 10th Anniversary, re3data! </a> </li> <li> <a href="/blog/save-the-date-5-october-2022-re3data-coref-coretrustseal-workshop-on-data-quality-management-at-repositories" class=""> re3data COREF / CoreTrustSeal Workshop on Data Quality Management at Repositories </a> </li> <li> <a href="/blog/mapping-the-global-repository-landscape" class=""> Mapping the global repository landscape </a> </li> <li> <a href="/blog/how-open-are-repositories-in-re3data" class="active"> How open are repositories in re3data? </a> </li> <li> <a href="/blog/reviewing-the-subject-classification-in-re3data" class=""> Reviewing the subject classification in re3data </a> </li> <li> <a href="/blog/from-workshops-to-the-new-model-of-user-stories-for-re3data-a-journey" class=""> From stakeholder survey and workshops to the new Conceptual Model for User Stories – a journey </a> </li> <li> <a href="/blog/releasing-version-3-1-of-the-re3data-metadata-schema" class=""> Releasing version 3.1 of the re3data Metadata Schema </a> </li> <li> <a href="/blog/request-for-comments-version-3-1-of-the-re3data-metadata-schema" class=""> Request for Comments: Version 3.1 of the re3data Metadata Schema (closed) </a> </li> <li> <a href="/blog/using_the_re3data_api" class=""> Using the re3data API </a> </li> <li> <a href="/blog/how-to-ensure-good-data-a-presentation-at-open-repositories-2021" class=""> How to ensure "good" data? A presentation at Open Repositories 2021 </a> </li> <li> <a href="/blog/using-and-referencing-re3data" class=""> Using and referencing re3data </a> </li> <li> <a href="/blog/releasing-version-4-0-of-the-re3data-metadata-schema" class=""> Releasing version 4.0 of the re3data Metadata Schema </a> </li> <li> <a href="/blog/new-re3data-org-editorial-board-members" class=""> New re3data.org Editorial Board Members </a> </li> <li> <a href="/blog/summer-meeting-of-the-editorial-board" class=""> Summer Meeting of the Editorial Board </a> </li> <li> <a href="/blog/re3data-in-central-america" class=""> re3data in Central America </a> </li> </ul> </li> <li> <a href="/project" class=""> Project </a> </li> <li> <a href="/contact" class=""> Contact </a> </li> </ul> </nav> </section> </nav> </section> </section> <div class="mobile-menu"> <div class="button_container" id="toggle"> <span class="top"></span> <span class="middle"></span> <span class="bottom"></span> </div> </div> <section id="start"> <section id="body-wrapper" class="section blog-listing"> <section class="container grid-lg"> <div class="columns"> <div id="item" class="column col-9 col-md-12 extra-spacing"> <div class="content-item h-entry"> <div class="content-title text-center"> <h2 class="p-name mt-1"><a href="/blog/how-open-are-repositories-in-re3data" class="u-url">How open are repositories in re3data?</a></h2> <span class="blog-date"> <time class="dt-published" datetime="2021-12-06T13:48:00+00:00"> <i class="fa fa-calendar"></i> 6th Dec 2021 </time> </span> </div> <div class="e-content"> <p>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).</p> <h4>Open repositories</h4> <p>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".</p> <p>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>).</p> <p>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.</p> <h4>Describing openness for repositories in re3data</h4> <p>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.</p> <p><img src="/blog/how-open-are-repositories-in-re3data/./re3data_icon_system.jpg" alt="" /></p> <p><em>Figure 1: The re3data icon system.</em></p> <p>Generally, access conditions in re3data are covered by three elements (see <a href="https://www.re3data.org/schema">re3data Metadata Schema</a>): <em>databaseAccessType</em>, <em>dataAccessType</em> and <em>dataUploadType</em>. <em>databaseAccessType</em> refers to the access to the research data repository in general, indicating whether the metadata can be found and accessed by users and services. <em>dataAccessType</em> describes the access to datasets in the repository, and <em>dataUploadType</em> indicates whether researchers can upload datasets to the service. The values for these three elements are constricted by controlled vocabularies. The definitions of the values "open", "restricted" and "closed" are identical for all three elements. Restrictions include requiring fees, registration or institutional membership. The value "embargoed" is only used for the element <em>dataAccessType</em>.</p> <ul> <li><strong>open</strong>: There are no access barriers.</li> <li><strong>embargoed</strong>: External users cannot overcome access barriers until the data is released and openly accessible. (only for <em>dataAccessType</em>)</li> <li><strong>restricted</strong>: External users can overcome access barriers.</li> <li><strong>closed</strong>: External users cannot overcome access barriers.</li> </ul> <p>For the re3data icon system, only the elements <em>databaseAccessType</em> and <em>dataAccessType</em> are considered to determine the openness of a repository, as is shown in figure 2.<br> If <em>databaseAccessType</em> is "open" and <em>dataAccessType</em>, which can occur multiple times for a repository, includes the value "open", the repository is considered open, because users are able to access metadata without restrictions and can access at least some of the repository's holdings openly. (see figure 2 A)<br> If <em>databaseAccessType</em> is either "open" or "restricted" and <em>dataAccessType</em> does not include the value "open", the repository is considered restricted, because users are able to access metadata with or without restrictions, but access to all data is restricted. (see Figure 2 B)<br> If <em>databaseAccessType</em> is "closed", the repository is closed, because external users can not overcome access barriers to metadata records. The values for <em>dataAccessType</em> do not change this categorization. (see figure 2 C)</p> <p><img src="/blog/how-open-are-repositories-in-re3data/./new_access_levels.png" alt="" /></p> <p><em>Figure 2: Schematic overview of determining the openness of repositories indexed in re3data.</em></p> <h5>How can users find repositories that offer data upload?</h5> <p>As mentioned before, this evaluation does not include the element <em>dataUploadType</em>. This is because some services indexed in re3data do not offer data upload in general due to the type of infrastructure they represent. For example, some services offer access to data generated in a specific project, but they do not accept data from researchers beyond that specialized scope. Users looking for services that offer data upload in addition to open content can use <em>dataUploadType</em> as an additional filter in the GUI or in API requests.<br> In November 2021, most repositories (66.6 %, in total 1845) indexed in re3data placed restrictions on data upload. Most often, registration is required.</p> <h4>Open repositories in re3data</h4> <p>Based on the method outlined above, the openness of repositories in terms of the accessibility of metadata and data is evaluated and displayed via the icon system in re3data. An analysis of re3data metadata gives an overview of how research data repositories are distributed across the three categories open, restricted and closed.<br> Figure 3 shows that currently, the majority of all repositories is considered open (85.6 %, in total 2366), some are restricted (13.7 %, in total 378), and only a few are closed (0.7 %, in total 20). Almost all (94.5 %, in total 2611) repositories make metadata records openly available (<em>databaseAccessType</em> = open). Only 13.7 % (in total 380) of all repositories do not offer open access to any of the datasets they store.</p> <p><img src="/blog/how-open-are-repositories-in-re3data/./openness_levels.png" alt="" /></p> <p><em>Figure 3: Openness of repositories indexed in re3data.</em></p> <h4>Conclusion</h4> <p>The landscape of "open repositories" is diverse and manifold, as definitions of open repositories differ in the aspects they include. The icon system in re3data is designed to give users an intuitive overview of the accessibility of metadata and data.<br> The analysis of re3data metadata shows that it is very common among repositories to make metadata records available without access barriers. For many repositories, unrestricted access to metadata is important, for example to enable users to search for, retrieve and reuse the stored datasets. The method for determining repository openness in re3data outlined in this blogpost reflects the idea that providing unrestricted access to metadata is the first step on the path to becoming an open repository.<br> Making data publicly available promotes transparency and collaboration in science and is recommended by funding agencies worldwide. However, some repositories restrict access to datasets, because not all datasets can or should be published openly (Levin & Leonelli, 2017). For example, some repositories store research data that are subject to access restrictions for data protection reasons. Therefore, the degree of openness of the data a repository stores is very situational.</p> <p>We are currently in the process of updating the <a href="http://doi.org/10.48440/re3.010">re3data Metadata Schema</a>, and we highly value your input: What do you think about the method for describing openness of repositories based on the access to metadata and data in re3data? Are there any aspects of openness that you would like to see in the next version of the re3data Metadata Schema?</p> <p>Please feel free to contact us via <a href="mailto:info@re3data.org">info@re3data.org</a>, <a href="https://www.re3data.org/contact">contact form</a> or on Twitter <a href="https://twitter.com/re3data">@re3data</a>.</p> <h4>References</h4> <p>Boulton, G., Campbell, P., Collins, B., Elias, P., Hall, W., Laurie, G., O’Neill, O., Rawlins, M., Thornton, J., Vallance, P., & Walport, M. (2012). Science as an open enterprise. Royal Society. <a href="http://royalsociety.org/policy/projects/science-public-enterprise/report/">http://royalsociety.org/policy/projects/science-public-enterprise/report/</a>(accessed 2021-12-01)</p> <p>Draft Recommendation on Open Science (41 C/22). (2021). United Nations Educational, Scientific and Cultural Organization. <a href="https://unesdoc.unesco.org/ark:/48223/pf0000378841">https://unesdoc.unesco.org/ark:/48223/pf0000378841</a> (accessed 2021-12-01)</p> <p>European Commission. (2021). EU Grants Annotated Model Grant Agreement. <a href="https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/common/guidance/aga_en.pdf">https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/common/guidance/aga_en.pdf</a> (accessed 2021-12-01)</p> <p>Levin, N., & Leonelli, S. (2017). How Does One “Open” Science? Questions of Value in Biological Research. Science, Technology, & Human Values, 42(2), 280–305. <a href="https://doi.org/10.1177/0162243916672071">https://doi.org/10.1177/0162243916672071</a></p> <p>Pasquetto, I. V., Sands, A. E., & Borgman, C. L. (2015). Exploring openness in data and science: What is “open,” to whom, when, and why? Proceedings of the Association for Information Science and Technology, 52(1), 1–2. <a href="https://doi.org/10.1002/pra2.2015.1450520100141">https://doi.org/10.1002/pra2.2015.1450520100141</a></p> </div> </div> <p class="prev-next text-center"> <a class="btn" href="/blog/reviewing-the-subject-classification-in-re3data"><i class="fa fa-angle-left"></i> Previous Post</a> <a class="btn" href="/blog/mapping-the-global-repository-landscape">Next Post <i class="fa fa-angle-right"></i></a> </p> </div> <div id="sidebar" class="column col-3 col-md-12"> <div class="sidebar-content syndicate"> <h4>Syndicate</h4> <a class="btn" href="/blog.atom"><i class="fa fa-rss-square"></i> Atom 1.0</a> <a class="btn" href="/blog.rss"><i class="fa fa-rss-square"></i> RSS</a> <a class="btn" href="/blog.json"><i class="fa fa-rss-square"></i> JSON</a></div> </div> </div> </section> </section> </section> </div> <section id="footer" class="section bg-gray"> <section class="container grid-lg"> <p><a href="//www.re3data.org/legalnotice">Impressum / Legal Notice</a></p> <p><a href="//www.re3data.org">www.re3data.org</a></p> </section> <section class="container grid-lg"> <a href="http://www.datacite.org/"> <img style="height: 96px;" src="/user/themes/quark/images/logo/datacite.png" alt="DataCite"> </a> <a href="https://www.ibi.hu-berlin.de/"> <img style="height: 96px;" src="/user/themes/quark/images/logo/hu.png" alt="Humbold-Universität zu Berlin"> </a> <a href="https://os.helmholtz.de"> <img style="height: 96px;" src="/user/themes/quark/images/logo/gfz.png" alt="Helmholtz Open Science Office"> </a> <a href="https://www.kit.edu/"> <img style="height: 96px;" src="/user/themes/quark/images/logo/kit.png" alt="Karlsruhe Institute of Technology"> </a> </section> </section> <div class="mobile-container"> <div class="overlay" id="overlay"> <div class="mobile-logo"> <a href="/" class="navbar-brand mr-10"> <svg xmlns="http://www.w3.org/2000/svg" fill-rule="evenodd" viewBox="0 0 504 140" clip-rule="evenodd"><path d="M235.83 71.56h-7.98c-1.2 0-2.2 1-2.2 2.2V89.1l-.15.13c-4.7 3.96-10.64 6.14-16.72 6.14-14.36 0-26.04-11.68-26.04-26.04s11.68-26.04 26.04-26.04c5.58 0 10.92 1.76 15.44 5.1.87.66 2.1.57 2.86-.2l5.7-5.7c.44-.44.67-1.05.63-1.68-.02-.62-.32-1.2-.82-1.6-6.76-5.35-15.2-8.3-23.8-8.3-21.18 0-38.42 17.23-38.42 38.4 0 21.2 17.24 38.42 38.42 38.42 10.93 0 21.4-4.7 28.7-12.9.35-.4.55-.93.55-1.47v-19.6c0-1.22-.98-2.2-2.2-2.2M502.8 34.44c-.4-.6-1.1-.98-1.84-.98h-8.7c-.87 0-1.66.52-2 1.32l-24.5 56.84-24.9-56.85c-.36-.8-1.15-1.3-2.02-1.3h-8.72c-.74 0-1.44.36-1.84.98-.4.62-.48 1.4-.17 2.1l30.2 68.85c.34.8 1.13 1.32 2 1.32h11c.88 0 1.67-.53 2.02-1.33l29.66-68.87c.3-.68.22-1.47-.2-2.1"/><path d="M388.68 34.77c-.35-.8-1.14-1.32-2-1.32h-11c-.88 0-1.67.53-2.02 1.33L344 103.64c-.3.68-.22 1.47.18 2.08.4.62 1.1 1 1.84 1h8.7c.86 0 1.66-.53 2-1.33l24.5-56.86 24.9 56.86c.36.8 1.15 1.32 2.02 1.32h8.72c.74 0 1.44-.38 1.84-1 .4-.62.47-1.4.17-2.1l-30.2-68.85zM309.2 81.52l.47-.22c8.68-4.2 14.28-13.1 14.28-22.67 0-13.88-11.3-25.18-25.17-25.18H266.9c-1.2 0-2.2 1-2.2 2.2v68.86c0 1.23 1 2.22 2.2 2.22h8c1.2 0 2.2-1 2.2-2.2V45.8h21.68c7.05 0 12.8 5.75 12.8 12.8 0 5.9-4 11-9.73 12.42-1.04.26-2.07.4-3.07.4h-7.98c-.83 0-1.6.46-1.96 1.2-.38.73-.3 1.62.2 2.3l22.6 30.87c.42.58 1.08.92 1.78.92h9.9c.84 0 1.6-.47 1.97-1.2.37-.75.3-1.64-.2-2.3l-15.9-21.7zM107.2 80.97c-7.26-4.8-11.4-8.85-15.02-16.1-2.47 4.97-8.24 12.37-17.96 18.2-4.86 15.1-27.96 44-35.43 39.9-2.22-1.2-2.64-2.8-2.15-4.45.54-4.13 9.08-13.62 9.08-13.62s.18 2 2.92 6.18c-3.6-11.2 5.96-25.03 8.5-29.73 3.98-1.27 4.27-6.4 4.27-6.4.26-7.9-3.28-13.63-6.7-17.05 2.46 3 3.25 7.54 3.37 11.7v.02c0 .47 0 .93 0 1.4-.12 3.43-1.16 8.18-3.38 8.18v.03c-2.28-.1-5.1.4-7.63 1.18l-5.6 1.34s2.98-.13 4.6 1.25c-1.8 2.9-5.78 6.53-10.22 8.58-6.45 3-8.3-2.96-5.03-6.84.8-.94 1.62-1.74 2.38-2.4-.5-.5-.8-1.2-.88-2.06 0 0 0 0 0-.02-.46-1.97-.2-4.54 2.6-8.62.54-.86 1.2-1.75 2-2.65.02-.04.04-.07.07-.1.03-.04.07-.08.1-.12.02-.02.04-.04.06-.06.2-.23.42-.45.64-.67 3.34-3.4 8.6-6.96 16.9-10.15C64.4 43.68 67.94 41 67.94 41c1.07-1.1 2.94-2.45 3.63-2.8-5.05-8.77-6.07-21.15-4.75-24.5-.1.2-.2.38-.3.57.5-1.14.83-1.5 1.34-2.1 1.38-1.64 6.06-2.5 7.74.96.9 1.84 1.06 4.23 1.03 6.02-3.7-.2-7.06 4.04-7.06 4.04s3.07-1.46 6.88-1.5c0 0 1 .9 2.28 2.56-1.7 3.2-4.52 10.02-2.5 17.16.35 1.4.86 2.62 1.5 3.65.02.05.04.1.07.14.05.07.1.13.14.2 3.37 5.06 9.54 5.66 9.54 5.66-2.9-1.45-5.27-3.76-6.8-6.56-.82-1.5-1.3-2.77-1.6-3.77-1.64-6.3.77-10 2.14-12.47 3.17-4.9 8.95-7.9 15.15-7.18 8.72 1 14.97 8.86 13.98 17.57-.6 5.32-3.78 9.72-8.15 12.12 1.05 2.84-.07 6.28-.07 6.28 2.64 3.32 2.76 5.23 2.67 7-3.36-.55-6.62 1.7-6.62 1.7s6.48-1.53 10.24 1.82c2.44 2.64 4.08 5 5.05 6.77 1.4 2.5 7.86 2.68 7.12 7.2-.74 4.5-5.68 4.53-13.4-.57M69.56 0C31.15 0 0 31.15 0 69.57c0 38.42 31.15 69.57 69.57 69.57 38.42 0 69.57-31.15 69.57-69.57C139.14 31.15 108 0 69.57 0M73.8 51.7c.8-.82.8-2.14 0-2.95-.82-.82-2.14-.82-2.95 0-.82.8-.82 2.13 0 2.94.8.8 2.13.8 2.95 0M66.45 53.15c-.82.8-.82 2.13 0 2.95.8.8 2.13.8 2.94 0 .8-.82.8-2.14 0-2.95-.82-.8-2.14-.8-2.95 0"/><path d="M79.23 54.23c-1.27-1.27-3.34-1.27-4.6 0l-2.72 2.7c-1.27 1.3-1.27 3.35 0 4.63l3 2.97c1.26 1.28 3.32 1.28 4.6 0l2.7-2.7c1.28-1.28 1.28-3.35 0-4.62l-2.97-2.97zM95.76 41.44c-2.15-2.57 1.87-7.25 4.4-4.46 4.64 5.15-2.25 7.04-4.4 4.46m9.24 2.7c3.45-6.56-1.42-10.4-4.77-13.53-5.36-5.03-10.7-7.2-16.8-.23-6.1 6.98-2.24 15.07 3.35 19.06 5.58 4 14.78 1.25 18.22-5.3"/></svg></a> </div> <nav class="overlay-menu"> <ul class="tree"> <li> <a href="/" class="active"> Blog </a> <ul> <li> <a href="/blog/re3data-call-for-editorial-board" class=""> re3data Call for Editorial Board </a> </li> <li> <a href="/blog/request-for-comments-version-4-0-of-the-re3data-metadata-schema" class=""> Request for Comments: Version 4.0 of the re3data Metadata Schema (closed) </a> </li> <li> <a href="/blog/canadian-research-data-repositories-in-re3data" class=""> Canadian research data repositories in re3data: A collaborative effort to increase visibility and foster community engagement </a> </li> <li> <a href="/blog/workshop_materials" class=""> Materials from the re3data COREF / CoreTrustSeal Workshop on Quality Management at Research Data Repositories </a> </li> <li> <a href="/blog/10th-anniversary" class=""> Happy 10th Anniversary, re3data! </a> </li> <li> <a href="/blog/save-the-date-5-october-2022-re3data-coref-coretrustseal-workshop-on-data-quality-management-at-repositories" class=""> re3data COREF / CoreTrustSeal Workshop on Data Quality Management at Repositories </a> </li> <li> <a href="/blog/mapping-the-global-repository-landscape" class=""> Mapping the global repository landscape </a> </li> <li> <a href="/blog/how-open-are-repositories-in-re3data" class="active"> How open are repositories in re3data? </a> </li> <li> <a href="/blog/reviewing-the-subject-classification-in-re3data" class=""> Reviewing the subject classification in re3data </a> </li> <li> <a href="/blog/from-workshops-to-the-new-model-of-user-stories-for-re3data-a-journey" class=""> From stakeholder survey and workshops to the new Conceptual Model for User Stories – a journey </a> </li> <li> <a href="/blog/releasing-version-3-1-of-the-re3data-metadata-schema" class=""> Releasing version 3.1 of the re3data Metadata Schema </a> </li> <li> <a href="/blog/request-for-comments-version-3-1-of-the-re3data-metadata-schema" class=""> Request for Comments: Version 3.1 of the re3data Metadata Schema (closed) </a> </li> <li> <a href="/blog/using_the_re3data_api" class=""> Using the re3data API </a> </li> <li> <a href="/blog/how-to-ensure-good-data-a-presentation-at-open-repositories-2021" class=""> How to ensure "good" data? A presentation at Open Repositories 2021 </a> </li> <li> <a href="/blog/using-and-referencing-re3data" class=""> Using and referencing re3data </a> </li> <li> <a href="/blog/releasing-version-4-0-of-the-re3data-metadata-schema" class=""> Releasing version 4.0 of the re3data Metadata Schema </a> </li> <li> <a href="/blog/new-re3data-org-editorial-board-members" class=""> New re3data.org Editorial Board Members </a> </li> <li> <a href="/blog/summer-meeting-of-the-editorial-board" class=""> Summer Meeting of the Editorial Board </a> </li> <li> <a href="/blog/re3data-in-central-america" class=""> re3data in Central America </a> </li> </ul> </li> <li> <a href="/project" class=""> Project </a> </li> <li> <a href="/contact" class=""> Contact </a> </li> </ul> </nav> </div> </div> <script src="/user/themes/quark/js/jquery.treemenu.js"></script> <script src="/user/themes/quark/js/site.js"></script> </body> </html>