<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//TaxonX//DTD Taxonomic Treatment Publishing DTD v0 20100105//EN" "https://riojournal.com/nlm/tax-treatment-NS0.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tp="http://www.plazi.org/taxpub" article-type="research-article">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">17</journal-id>
      <journal-id journal-id-type="index">urn:lsid:arphahub.com:pub:8E638694-B4E0-570A-856A-746FF325BF6B</journal-id>
      <journal-id journal-id-type="aggregator">urn:lsid:zoobank.org:pub:FEF66878-15EE-4F8B-B369-7652D735020E</journal-id>
      <journal-title-group>
        <journal-title xml:lang="en">Research Ideas and Outcomes</journal-title>
        <abbrev-journal-title xml:lang="en">RIO</abbrev-journal-title>
      </journal-title-group>
      <issn pub-type="epub">2367-7163</issn>
      <publisher>
        <publisher-name>Pensoft Publishers</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.3897/rio.11.e163817</article-id>
      <article-id pub-id-type="publisher-id">163817</article-id>
      <article-id pub-id-type="manuscript">28436</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Article</subject>
        </subj-group>
        <subj-group subj-group-type="scientific_subject">
          <subject>Computer architecture</subject>
          <subject>Computing systems &amp; Methods</subject>
          <subject>Library &amp; Information Science</subject>
          <subject>Performance &amp; Control</subject>
          <subject>Science policy</subject>
          <subject>Scientometrics</subject>
          <subject>Software ecosystems</subject>
          <subject>Software engineering</subject>
          <subject>Software sustainability</subject>
        </subj-group>
        <subj-group subj-group-type="sdg">
          <subject>Industry</subject>
          <subject> innovation &amp; infrastructure</subject>
          <subject>Peace and justice strong institutions</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Engineering Open by Design into Research Infrastructures</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Haak</surname>
            <given-names>Laurel</given-names>
          </name>
          <email xlink:type="simple">laurelhaak@gmail.com</email>
          <uri content-type="orcid">https://orcid.org/0000-0001-5109-3700</uri>
          <xref ref-type="aff" rid="A1">1</xref>
          <xref ref-type="aff" rid="A2">2</xref>
          <role content-type="http://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</role>
          <role content-type="http://credit.niso.org/contributor-roles/writing-original-draft/">Writing - original draft</role>
          <role content-type="http://credit.niso.org/contributor-roles/writing-review-editing/">Writing - review and editing</role>
          <role content-type="http://credit.niso.org/contributor-roles/investigation/">Investigation</role>
          <role content-type="http://credit.niso.org/contributor-roles/methodology/">Methodology</role>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Skinner</surname>
            <given-names>Katherine</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-0139-7524</uri>
          <xref ref-type="aff" rid="A3">3</xref>
          <role content-type="http://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</role>
          <role content-type="http://credit.niso.org/contributor-roles/writing-original-draft/">Writing - original draft</role>
          <role content-type="http://credit.niso.org/contributor-roles/writing-review-editing/">Writing - review and editing</role>
          <role content-type="http://credit.niso.org/contributor-roles/investigation/">Investigation</role>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Ratan</surname>
            <given-names>Kristen</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0001-9697-0367</uri>
          <xref ref-type="aff" rid="A4">4</xref>
          <role content-type="http://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</role>
          <role content-type="http://credit.niso.org/contributor-roles/writing-original-draft/">Writing - original draft</role>
          <role content-type="http://credit.niso.org/contributor-roles/writing-review-editing/">Writing - review and editing</role>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">Mighty Red Barn, Townsend, United States of America</addr-line>
        <institution>Mighty Red Barn</institution>
        <addr-line content-type="city">Townsend</addr-line>
        <country>United States of America</country>
      </aff>
      <aff id="A2">
        <label>2</label>
        <addr-line content-type="verbatim">University of Wisconsin, Madison, United States of America</addr-line>
        <institution>University of Wisconsin</institution>
        <addr-line content-type="city">Madison</addr-line>
        <country>United States of America</country>
      </aff>
      <aff id="A3">
        <label>3</label>
        <addr-line content-type="verbatim">Invest in Open Infrastructure, Greensboro, United States of America</addr-line>
        <institution>Invest in Open Infrastructure</institution>
        <addr-line content-type="city">Greensboro</addr-line>
        <country>United States of America</country>
      </aff>
      <aff id="A4">
        <label>4</label>
        <addr-line content-type="verbatim">Strategies for Open Science, SANTA CRUZ, United States of America</addr-line>
        <institution>Strategies for Open Science</institution>
        <addr-line content-type="city">SANTA CRUZ</addr-line>
        <country>United States of America</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Laurel Haak (<email xlink:type="simple">laurelhaak@gmail.com</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: Editorial Secretary</p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>18</day>
        <month>09</month>
        <year>2025</year>
      </pub-date>
      <volume>11</volume>
      <elocation-id>e163817</elocation-id>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/9A9684F4-0FD6-5689-A176-89E98C8948F6">9A9684F4-0FD6-5689-A176-89E98C8948F6</uri>
      <history>
        <date date-type="received">
          <day>01</day>
          <month>07</month>
          <year>2025</year>
        </date>
        <date date-type="accepted">
          <day>10</day>
          <month>09</month>
          <year>2025</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Laurel Haak, Katherine Skinner, Kristen Ratan</copyright-statement>
        <license license-type="creative-commons-attribution" xlink:href="http://creativecommons.org/licenses/by/4.0/" xlink:type="simple">
          <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution License (CC BY 4.0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.</license-p>
        </license>
      </permissions>
      <abstract>
        <label>Abstract</label>
        <p>Research activities utilise and depend on interlocking infrastructures – tools, standards, protocols, and other systems and structures at local, national, and international scales that enable researchers to collaborate, analyze and share data and software, and discuss their research findings. Despite growing policy momentum towards open science, a significant challenge persists: a substantial portion of research infrastructure remains inherently closed or restrictive. This lack of openness undermines transparency, integrity, limits reproducibility, and constrains researchers’ ability to fully engage with each other. In this paper, we examine how research infrastructures can be designed to embed open principles throughout their development and operation, borrowing elements from Manufacturing Principles, Systemic Service Design, and Open Science frameworks. We propose an open-by-design reference framework for infrastructure builders and guidance for enabling, making visible, and incentivizing specific elements of “openness” within research infrastructures that are prerequisites for a thriving research and knowledge ecosystem.</p>
      </abstract>
      <kwd-group>
        <label>Keywords</label>
        <kwd>open research infrastructure</kwd>
        <kwd>design thinking principles</kwd>
        <kwd>Manufacturing Principles</kwd>
        <kwd>service design</kwd>
        <kwd>human-centered design</kwd>
        <kwd>systems service design</kwd>
        <kwd>POSI</kwd>
        <kwd>FAIR</kwd>
        <kwd>CARE</kwd>
        <kwd>FOREST</kwd>
        <kwd>research policy</kwd>
        <kwd>open-by-design reference framework</kwd>
        <kwd>open science</kwd>
        <kwd>research integrity</kwd>
        <kwd>persistent identifiers</kwd>
        <kwd>user surveys</kwd>
        <kwd>telemetry</kwd>
        <kwd>research evaluation</kwd>
        <kwd>impact evaluation</kwd>
        <kwd>sustainable development goals</kwd>
      </kwd-group>
      <funding-group>
        <funding-statement>A portion of the work described in this paper was carried out under a contract to LLH with the Australian Research Data Commons, ARDC Contract NDA04.</funding-statement>
      </funding-group>
      <counts>
        <fig-count count="3"/>
        <table-count count="8"/>
        <ref-count count="81"/>
      </counts>
    </article-meta>
  </front>
  <body>
    <sec sec-type="Introduction">
      <title>Introduction</title>
      <p>Over the past two decades, open science has gained significant momentum as a principled framework aimed at enhancing transparency, reproducibility, and innovation within research ecosystems (<xref ref-type="bibr" rid="B13281675">National Academies of Sciences, Engineering, and Medicine 2018b</xref>, <xref ref-type="bibr" rid="B13281751">Hicks et al. 2015</xref>). Driven by an evolving landscape of technology, policies, and practices, open science seeks to facilitate knowledge dissemination through accessible repositories, persistent identifiers, and robust data citation standards. The GO FAIR (Findable, Accessible, Interoperable, and Reusable) framework (<xref ref-type="bibr" rid="B13281693">Wilkinson et al. 2019</xref>, <xref ref-type="bibr" rid="B13281683">Hrynaszkiewicz et al. 2020</xref>, <xref ref-type="bibr" rid="B13281471">GO FAIR 2016</xref>,<xref ref-type="bibr" rid="B13281667">Schultes et al. 2020</xref>) is foundational to this work.</p>
      <p>Balancing this effort to make research products machine readable, open science policies also are directed at processes of research (<xref ref-type="bibr" rid="B13430137">UNESCO 2023</xref>), in recognition that community engagement and relationship-building are fundamental to building trust (<xref ref-type="bibr" rid="B13430145">Leonelli 2023</xref>). A number open science frameworks and initiatives aim to foster normative socio-ethical behavior, centering on the people and communities engaging in and affected by research, including CARE (Collective Benefit, Authority to Control, Responsibility, Ethics) (<xref ref-type="bibr" rid="B13281589">Carroll et al. 2021</xref>), DORA (Declaration on Research Assessment) (<xref ref-type="bibr" rid="B13281572">Gagliardi et al. 2023</xref>, <xref ref-type="bibr" rid="B13281658">Bladek 2014</xref>), and CRediT (Contributor Roles Taxonomy) (<xref ref-type="bibr" rid="B13281563">Allen et al. 2019</xref>).</p>
      <p>Yet, despite these developments, a critical gap persists: research infrastructures themselves. The digital platforms, tools, and underlying standards, protocols, and technical systems that researchers depend upon to build communities of practice often are designed more to extract knowledge than to enrich communities. Research communities experience challenges arising from proprietary systems, unexpected infrastructure failure, lack of governance clarity, little to no interoperability, and the privatization or discontinuation of essential platforms. Such scenarios jeopardize sustainability, limit collaborative potential, and erode community trust in research and scholarship.</p>
      <p>These challenges become even more pressing in the context of emerging technologies, such as Artificial Intelligence (AI), which amplify complexity through intricate dependencies among models, systems and data, each potentially governed by divergent openness standards (<xref ref-type="bibr" rid="B13281650">OECD 2025</xref>). For example, AI-driven research often integrates openly accessible algorithms with proprietary datasets or closed computational infrastructures, and lack of provenance standards complicates assessments of reproducibility and transparency. Without intentional openness embedded within their foundational designs, such emerging technological infrastructures risk enhancing existing issues around reproducibility, equity of access, and accountability (<xref ref-type="bibr" rid="B13281552">Miceli et al. 2022</xref>).</p>
      <p>To address these critical concerns, this paper advocates for a strategic shift towards an “Open by Design” approach in (re-)designing and maintaining research infrastructures. We bring together conceptual frameworks of public goods (<xref ref-type="bibr" rid="B13430153">Ostram 2009</xref>) with manufacturing and systemic services to provide evidence and practical guidance for "Open by Design”. We argue for proactively embedding community engagement and co-design practices into infrastructure development, including consideration of complexity and socio-economic contexts; resource availability; values and policies; and the users and beneficiaries from the earliest stages of infrastructure conception and throughout its operational lifecycle. Our goal is to provide infrastructure builders practical guidance to translate open science principles into infrastructure design components and evaluation frameworks.</p>
    </sec>
    <sec sec-type="Background and Literature Review">
      <title>Background and Literature Review</title>
      <sec sec-type="Historical foundations of “Open by Design” in Manufacturing">
        <title>Historical foundations of “Open by Design” in Manufacturing</title>
        <p>The origins of the “Open by Design” concept can be traced back to manufacturing methodologies developed during the post-World War II industrial expansion. Central among these methodologies is Design for Manufacturing (DFM), a framework introduced to proactively integrate manufacturing constraints, optimize production efficiencies, and systematically enhance product quality at the earliest design stages. DFM addresses manufacturing complexities by anticipating inefficiencies, reducing production costs, minimizing material waste, and ensuring superior reliability and product performance through early stage integrated planning processes (<xref ref-type="bibr" rid="B13281642">Boothroyd et al. 2011</xref>, <xref ref-type="bibr" rid="B13281544">Andreasen et al. 1987</xref>, <xref ref-type="bibr" rid="B13281633">Whitney 1988</xref>).</p>
        <p>Further developments emerged in the form of Design for Assembly (DFA), a complementary approach specifically targeting simplified assembly operations. DFA methodologies prioritize reducing overall product complexity by minimizing the number of components, standardizing interfaces, utilizing modular assemblies, and facilitating straightforward, error-resistant assembly procedures. These design approaches have been instrumental in reducing production timelines, enhancing maintenance efficiency, and promoting the widespread adoption of enduring principles such as modularity, interoperability, and standardization. <xref ref-type="bibr" rid="B13281536">Baldwin and Clark 2014</xref>, through their analysis of modular and platform-based system architectures, further articulated these foundational concepts, emphasizing the benefits of modular designs in fostering technological adaptability and innovation.</p>
        <p>Simultaneously, parallel advancements in manufacturing were realized through the adoption and implementation of Lean Manufacturing and Just-In-Time (JIT) production systems. Originating primarily within Japanese manufacturing practices, notably pioneered by Toyota, these methodologies institutionalized rigorous and disciplined production processes emphasizing workflow transparency, continuous incremental improvement (Kaizen), systematic elimination of waste (Muda), and enhanced inter-organizational collaboration. These principles cultivated an organizational culture characterized by openness, continuous iterative refinement, and collaborative transparency (<xref ref-type="bibr" rid="B13281625">Womack 2007</xref>), elements increasingly relevant in contemporary frameworks of open innovation and research.</p>
        <p>The “Open by Design” concept extends these manufacturing practices by building upon Design Thinking principles. Design Thinking embodies a human-centred, iterative process that prioritizes empathy for users, rapid prototyping, and ongoing iterative testing. This methodological framework actively incorporates continuous feedback mechanisms, systematically refining products to ensure ongoing relevance, adaptability, and user satisfaction (<xref ref-type="bibr" rid="B13281616">Brown 2008</xref>). The iterative, participatory nature of Design Thinking aligns with open innovation frameworks (<xref ref-type="bibr" rid="B13281608">Chesbrough 2003</xref>), which emphasize openness, transparency, and collective stakeholder involvement as essential drivers of innovative capacity and sustained knowledge dissemination. Moreover, the broader influence of these manufacturing philosophies extends beyond mere technical improvements. They foster organizational behaviours conducive to cross-disciplinary collaboration, stakeholder engagement, strategy development and transparency in knowledge sharing (<xref ref-type="bibr" rid="B13281599">Platts and Gregory 1990</xref>).</p>
      </sec>
      <sec sec-type="Evolution of Design Principles in Digital Contexts">
        <title>Evolution of Design Principles in Digital Contexts</title>
        <p>While industrial design emerged from mass manufacturing, service design has emerged from digital transformation of many former in-person transactions, from banking to publishing. Emerging from product design, interaction design and cognitive psychology (<xref ref-type="bibr" rid="B13430164">Rytilahti et al. 2015</xref>), at its best, service design considers all relevant stakeholders and is centered on user needs, not the needs of the business - but also integrates a business case and service sustainability model. Designers engage users in developing narratives and co-designing the service, then prototype and test the service with users, before deploying a minimum viable service, which is then iterated upon and improved based on user feedback (<xref ref-type="bibr" rid="B13430177">Reason et al. 2015</xref>; <xref ref-type="bibr" rid="B13430185">IxDF 2023</xref>). This approach ensures that services are based on evidence and genuine comprehension of the purpose of the service as well as capabilities to deliver value to users.</p>
        <p>More recently, the field of service design has evolved significantly from UI/UX work to become a driver for organizational transformation (<xref ref-type="bibr" rid="B13430206">Souheimo et al. 2025</xref>). Service design can fail when the designers do not have a holistic understanding of the systems in place in and around the product they are developing. The systemic service design approach ensures that broader social, economic, and political environments are considered when developing a service so that the design process incorporates multiple stakeholder perspectives, emphasizes relations and interconnections, and considers the ethical implications of different pathways.</p>
        <p>Systemic service design is a useful construct for considering design and management of public goods. (<xref ref-type="bibr" rid="B13430219">Miettinen and Sarantou 2017</xref>). Services transcend design objects and become a means for supporting the emergence of a more collaborative, sustainable and creative society and economy. At the infrastructure scale, these designs can become commons – community-scale interventions engage staff, organization, and publics and ideally build capacity rather than dependency and can empower knowledge exchange and re-distribution of power (<xref ref-type="bibr" rid="B13430227">Bollier and Helfrich 2015</xref>, <xref ref-type="bibr" rid="B13430235">Sangiorgi 2011</xref>).</p>
        <p>Together, the focus on product from manufacturing design and the engagement of communities in developing that product from service design incorporate the goals of open science: engaging communities in the scientific process and ensuring access to knowledge. The challenge in managing community products, or public goods, has been well-described by <xref ref-type="bibr" rid="B13430153">Ostram (2009)</xref> as a framework of interacting subsystems. Applied to the research, design, and development space (Fig. <xref ref-type="fig" rid="F13430244">1</xref>), this framework helps to articulate the context and high-level components that must be considered when designing research infrastructure. These include the resources (people, facilities, data, funding) that drive scientific processes; the overarching resource system at varying levels of scale from local to international; as well as the values, rules, policies, and ethics that govern how research is carried out; and the communities that use research. Infrastructure designers must endeavor to understand how these subsystems interact with each other to be able to develop effective services.</p>
      </sec>
      <sec sec-type="Application of Design Principles to Open Research Infrastructure">
        <title>Application of Design Principles to Open Research Infrastructure</title>
        <p>The adaptation of design principles into research infrastructures provides a robust, structured framework for embedding openness systematically across conceptual and practical dimensions. Like manufactured products, research infrastructures necessitate comprehensive strategic planning that incorporates sustainability, standardization, interoperability, and lifecycle management from initial design through continuous operational phases. As digital products, research infrastructure requires explicit community partnership from ideation through prototype through launch and subsequent iterative improvement (Fig. <xref ref-type="fig" rid="F13430270">2</xref>). Open source code and software are examples of community goods with a rich history of iteration regarding maintenance and governance (<xref ref-type="bibr" rid="B13430250">Rossi et al. 2012</xref>, <xref ref-type="bibr" rid="B13430259">Lin and Maruping 2021</xref>). These open tools and infrastructures serve the research community, after all, not the other way around.</p>
        <p>Consequently, the “Open by Design” approach explicitly integrates principles of transparency, accessibility, modularity, and interoperability into early-stage decisions. This approach mirrors the proactive methodologies central to DFM and DFA, systematically embedding manufacturability and ease of assembly into product designs from inception. Research infrastructures inherently share characteristics with complex manufactured products, particularly regarding modular architecture and standardized interfaces.</p>
        <p>Such structural considerations facilitate seamless updates, replacements, and integration with complementary systems, substantially enhancing infrastructure adaptability and long-term resilience. This foresight in the initial phases mitigates risks associated with technological obsolescence, vendor lock-in, and operational disruptions, ensuring enhanced sustainability and operational effectiveness (<xref ref-type="bibr" rid="B13281525">Mons et al. 2017</xref>).</p>
        <p>Illustrative examples of successful research infrastructures incorporating these openness principles include platforms such as the WorldWide Protein Data Bank and PubMed. These infrastructures demonstrate tangible advantages gained from embedding systematic openness within their governance frameworks, operational protocols, and technical architectures. Consistent stakeholder engagement, transparent governance practices, and rigorous adherence to open standards substantially contribute to their enduring operational effectiveness and sustained relevance within the research community.</p>
        <p>Additionally, akin to Lean Manufacturing’s commitment to continuous improvement and Systems Service Design’s commitment to ongoing community engagement, open research infrastructures significantly benefit from iterative developmental processes. The importance of iteration is well recognized in design research. <xref ref-type="bibr" rid="B13430272">Wynn and Eckert (2017)</xref> reviewed the efficacy of a variety of iteration methodologies and suggest functional categories to be selected based on design needs, from exploring and refining, to correcting, and also coordinating efforts within and across groups. The goal of iterative methodologies is to integrate robust feedback mechanisms from user communities, leveraging user insights to refine operational processes continuously.</p>
        <p>Transparency in operations, systematic use of persistent identifiers, and clear, comprehensive metadata standards substantially enhance reproducibility, promoting cross-disciplinary interoperability and comprehensive data stewardship (<xref ref-type="bibr" rid="B13281693">Wilkinson et al. 2019</xref>). Furthermore, research infrastructures adopting these principles achieve greater stakeholder confidence through transparency and collaborative engagement, facilitating improved user trust and enhanced community participation. This openness significantly fosters greater innovation potential and adaptive capacity, enabling these infrastructures to evolve dynamically in response to emerging research needs and technological advancements.</p>
        <p>Thus, applying open design principles to research infrastructures provides an integrated and pragmatic framework for embedding openness systematically throughout the infrastructure lifecycle. Outputs generated by open infrastructures are more likely to be ‘born with integrity’ as the originating systems are auditable and the formats more likely to conform to data standards. Consequently, infrastructures developed under this paradigm could potentially demonstrate robustness, enhanced accessibility, superior interoperability, and sustained long-term operational sustainability, aligning closely with contemporary standards of open innovation and built upon relationship and trust building in scholarly communication.</p>
      </sec>
      <sec sec-type="Open Research Infrastructure Frameworks">
        <title>Open Research Infrastructure Frameworks</title>
        <p>The concept of “open” as a scholarly value or principle emerged by the mid-1990s and gained prominence in the early 2000s, when it was invoked widely and variously in open letters, statements, declarations, and manifestos in academic and research communities (see <xref ref-type="bibr" rid="B13281507">FORCE11 Scholarly Commons Working Group 2017</xref>), particularly in the contexts of open access and open science (<xref ref-type="bibr" rid="B13281479">Skinner and Wipperman 2020</xref>). Since that time, it has been used to signal a range of mechanisms and actions that make research available freely online without financial or technical barriers. Openness, in this sense, can be embedded in or enacted by scholars, research objects, and research infrastructures including standards, protocols, and tools.</p>
        <p>Applications of the term “open” extend across open science, open access, open source, and open data; they also extend across many different types of functions, including technical (e.g., interoperability, flexibility) and community engagement (e.g., participation, contribution, governance) (see <xref ref-type="bibr" rid="B13430145">Leonelli 2023</xref>). This highly variable use arguably made claiming and/or evaluating “openness” too subjective, and by 2016, research stakeholders were actively working to build and refine clearer, more consistent standards by which characteristics like “openness” could be measured (see <xref ref-type="bibr" rid="B13430281">CoARA 2025</xref>).</p>
        <p>The resulting promulgation of frameworks between and beyond 2016-2022 (see <xref ref-type="bibr" rid="B13281516">Bilder et al. 2020</xref>, <xref ref-type="bibr" rid="B13281471">GO FAIR 2016</xref>, <xref ref-type="bibr" rid="B13281463">GIDA 2023</xref>, <xref ref-type="bibr" rid="B13281455">COAR 2024</xref>, <xref ref-type="bibr" rid="B13281447">SPARC 2019</xref>, <xref ref-type="bibr" rid="B13281439">DPSC 2018</xref>, <xref ref-type="bibr" rid="B13281431">AmeliCA 2019</xref>, <xref ref-type="bibr" rid="B13281487">Group 2025</xref>, <xref ref-type="bibr" rid="B13281423">UCOLASC 2018</xref>, <xref ref-type="bibr" rid="B13281407">Badolato 2019</xref>, <xref ref-type="bibr" rid="B13281399">OANA 2016</xref>, <xref ref-type="bibr" rid="B13281390">Lippincott and Skinner 2022</xref>,<xref ref-type="bibr" rid="B13281495">Agate et al. 2022</xref>,<xref ref-type="bibr" rid="B13281667">Schultes et al. 2020</xref>) provide those who engage in or manage research outputs, tools, standards, processes and/or protocols with ways of both articulating and evidencing a broad range of values and principles. These frameworks focus on a relatively similar core set of values and principles - including openness, transparency, accessibility, ethics, equity, sustainability, discoverability, reusability, and representation. They have been largely created and issued by associations and working groups with very specific remits, and although there is some level of cross-referencing between them, each stands largely on its own, used by a subset of the landscape. For example, FAIR and CARE are geared towards data collection and sharing (data scientists and analysts); Exemplarity Criteria are geared towards funders and recipients of grant funding; and POSI, It Takes a Village, and FOREST are geared toward those who build and/or offer digital services (e.g., publishing, preservation).</p>
        <p>Focusing on the infrastructure builder use case, among the myriad of open research frameworks we have found the Principles of Open Scholarly Infrastructure (POSI) (<xref ref-type="bibr" rid="B13281516">Bilder et al. 2020</xref>), FAIR (<xref ref-type="bibr" rid="B13281341">Jacobsen et al. 2020</xref>), CARE (<xref ref-type="bibr" rid="B13281589">Carroll et al. 2021</xref>), and FOREST (<xref ref-type="bibr" rid="B13281390">Lippincott and Skinner 2022</xref>) translate well into practice. We describe each briefly in <bold>Table <xref ref-type="table" rid="T13234894">1</xref>.</bold></p>
        <p>While there is ongoing work to develop implementation advice for each of these frameworks (e.g., see <xref ref-type="bibr" rid="B13281341">Jacobsen et al. 2020</xref> and <xref ref-type="bibr" rid="B13281589">Carroll et al. 2021</xref>), our experience as advisors has clearly demonstrated that the people building research infrastructures – entrepreneurs and researchers – are often not able and/or unwilling to invest the time to translate the advice into their design process. As discussed below in <bold><italic>Use Cases</italic></bold>, a challenge with each of these frameworks is that their target audience and evaluation use case is post-hoc community evaluation. From a builder’s perspective, the frameworks are at best directional. From an Open by Design perspective, there are many different and at times apparently contradictory requirements, making it difficult to prioritize and build strategically. Further complicating matters, funders of research infrastructure have not provided clear and specific guidance or incentives to the builders to encourage adoption of these frameworks.</p>
        <p>Given this context, we have developed builder guidance for implementing Open By Design principles from the inception of an infrastructure. With the <italic>technical</italic> goals of modular architecture, standardized interfaces, sustainability, and operational effectiveness, and the <italic>organizational behavior</italic> goals of cross-disciplinary collaboration, stakeholder engagement, strategy development, and transparency in knowledge dissemination, we translate the open research infrastructure frameworks into design questions that make these Open by Design principles immediately applicable (Table <xref ref-type="table" rid="T13234895">2</xref>).</p>
      </sec>
      <sec sec-type="Evaluating Research Infrastructure">
        <title>Evaluating Research Infrastructure</title>
        <p>Part of the Open by Design framework is an evaluative component. One of the benefits of the Open by Design is the prototyping-iteration approach coupled with ongoing community engagement and user feedback. This provides builders with feedback on user experiences for the complement of services offered through the infrastructure, ideas for new features, as well as information on the value of the offering to the user community. What can we learn from existing evaluation frameworks?</p>
        <p>Typically, infrastructure is evaluated based on “classical” technical criteria such as performance and security. While these are crucial metrics, <xref ref-type="bibr" rid="B13430378">Edwards et al. (2003)</xref> argue that we need to distinguish between technical workability and value for end-users. Ideally, infrastructures aim to support ongoing iterated patterns of relationships between human beings (<xref ref-type="bibr" rid="B13430336">Bijl-Brouwer 2017</xref>). <xref ref-type="bibr" rid="B13430227">Bollier and Helfrich (2015)</xref> call for evaluation to be oriented toward the vitality of the system measured through sustainability, resilience, and support of living things, rather than efficiency or profit maximization. This ideal is embedded in the United National Sustainable Development Goals (SDGs) (<xref ref-type="bibr" rid="B13281233">United Nations 2015</xref>), a global partnership that has developed a shared framework for peace and prosperity for people and the planet. SDGs were created through an open consensus process, are openly available, are internationally recognized across many sectors, and are imminently suitable for open evaluation purposes. In particular, SDG 9 calls for building resilient infrastructure, promoting inclusive and sustainable industrialization, and fostering innovation. This is the overarching frame in which all research infrastructure can be assessed.</p>
        <p>The OECD decision support framework for investments in research infrastructures (<xref ref-type="bibr" rid="B13281333">OECD 2019</xref>), while based on large facilities, is well-suited also for assessing digital platforms. Both facilities and platforms are infrastructures purpose-built for research, and are expected to serve multiple community stakeholders over a long time period (decades) through provision of tooling, educational resources, and/or economic impact. The community-developed OECD framework includes 25 Core and additional standard Impact Indicators. The Core indicators are categorized by Scientific impact; Technological impact; Economic impact; Training and education impact; Social and societal impact. Subsequent community work extended these infrastructure indicators to include global-scale interoperability (<xref ref-type="bibr" rid="B13281277">National Academies of Sciences, Engineering, and Medicine 2018a</xref>). However, impact is difficult to assess because many outcomes are indirect and produced by users downstream rather than while using the infrastructure itself.</p>
        <p>Starting in the 2020s, the Australian Research Data Commons (ARDC) has required infrastructures in their national research portfolio to integrate evaluation components, and encouraged the adoption of persistent identifiers as a strategy to “connect the dots” between researchers, data producers, data users, and the data itself and infrastructure(s) that house and deliver the data (<xref ref-type="bibr" rid="B13281325">ARDC 2020</xref>). Similar national-level policy efforts are underway in the UK, Canada, and Netherlands, and are captured in the Research Data Alliance (RDA) National PID Strategies Working Group (WG), which describes benefits of widespread and consistent PID adoption for open research infrastructure implementation frameworks (<xref ref-type="bibr" rid="B13281268">Brown et al. 2023</xref>).</p>
        <p>As with the OECD frameworks, these national infrastructure evaluations have largely focused on downstream bibliometrics – publications and citations. While researchers use infrastructures and eventually write papers, the key value of infrastructure – research process support – as well as its openness is not captured using these metrics. Nor are infrastructures often designed using user experience principles to support generalist use (<xref ref-type="bibr" rid="B13281314">Osagie et al. 2017</xref>) or capture information that can be used for evaluative purposes (<xref ref-type="bibr" rid="B13281259">Seffah et al. 2006</xref>, <xref ref-type="bibr" rid="B13281250">Amorim et al. 2017</xref>, <xref ref-type="bibr" rid="B13281241">Haak et al. 2020</xref>).</p>
        <p>Aligned with Open by Design principles, we propose an evaluation framework that is integrated into the design and build process. One that is based on the concept of research infrastructure as a public good as presented in <bold>Figure 1</bold>. Infrastructures typically operate outside the control of a single stakeholder, so it makes sense to relate the assessment of impact to its role in and fit in the environment it inhabits: Is the infrastructure adopted? Does it evolve? Does it scale? (<xref ref-type="bibr" rid="B13430346">Henfridsson and Bygstad 2013</xref>). <xref ref-type="bibr" rid="B13430355">Vora and Dolan (2022)</xref> suggest a framework that has both supply (design, implementation, and governance) as well as demand (scale, user experience, and outcomes/impacts) components.</p>
        <p>The underlying question, then, is how does the infrastructure enrich the community it serves? <bold>Fig. <xref ref-type="fig" rid="F13430367">3</xref></bold> illustrates an Open by Design evaluation framework, which encompasses adoption, business sustainability, governance, community engagement and support, and relationship and trust building. We will explore how this framework incorporates Open Science principles and review its implementation in Section 4.</p>
      </sec>
    </sec>
    <sec sec-type="Case studies: Real-world applications and lessons learned">
      <title>Case studies: Real-world applications and lessons learned</title>
      <p>We have been exploring the Open by Design concept from a variety of perspectives. One is policy: working with colleagues and community groups to explore open science frameworks for specific contexts (<xref ref-type="bibr" rid="B13281302">Haak et al. 2012</xref>). Another is practice: working with researchers to define open science evaluation strategies (<xref ref-type="bibr" rid="B13281294">IOI 2024</xref>). And finally, implementation: working with entrepreneurs to embed open science design elements and evaluation frameworks into their product offering at launch (<xref ref-type="bibr" rid="B13281285">Flanagan et al. 2021</xref>). Here we provide specific case studies that test the Open by Design concept in real-world infrastructure build environments.</p>
      <sec sec-type="ARDC Impact Reporting Framework">
        <title>ARDC Impact Reporting Framework</title>
        <p>The ARDC has refined OECD impact indicators to create an Impact Reporting framework for Australian national-level data assets (<xref ref-type="bibr" rid="B13281325">ARDC 2020</xref>). The intent was to drive application of FAIR principles and persistent identifier (PID) strategies, and promote openness and transparency in data management. However, even with a funding supplement to promote implementation, the adoption barrier for those building the data assets was substantial. Infrastructure builders were focused on the specific use case they were solving for, and did not have the knowledge or capacity to learn about open principles and how to implement them.</p>
        <p>Working in collaboration with the project teams in the Health Studies Australian National Data Asset portfolio and ten disciplinary National Data Asset projects, one of the authors (Haak) tested an Open by Design approach to translate the evaluation framework into practical implementation plans. These projects included field instrumentation and data processing and pipelines for ocean microbes, biomedical data discovery, geophysics, barley science, ocean wave dynamics, plant trait data, air pollution, species distribution data, electronic medical records, and a cancer registry for companion animals.</p>
        <p>As a first step, teams reviewed webpages and initial funding proposals for each infrastructure project and extracted infrastructure services, beneficiaries, and impact goals for each project. The breadth of disciplines and use cases represented by the projects provided an opportunity to test for shared approaches and features while also identifying unique features and functions. Teams explored the question set described in <bold>Table <xref ref-type="table" rid="T13234895">2</xref></bold> in a series of online workshops with project leaders from April to June 2023. Using whiteboarding, teams mapped out the value proposition and core technical features of each infrastructure. Then, teams focused on the behavioral aspects: stakeholders and primary and secondary beneficiaries; options for user and community engagement; evaluation strategies.</p>
        <p>From findings elicited in these conversations, project feature maps were updated and then and then options were explored for implementing open principles. After highlighting structural congruences between infrastructures, existing modular architecture components were discussed, as well as standard interfaces and workflows, and schemas and persistent identifiers that can engage the intended infrastructure users while also providing information about usage patterns and longer term impacts on the research field or area of practice.</p>
        <p>Based on this work, teams revised their infrastructure outcome statements to incorporate data collection strategies, available telemetry and instrumentation toolsets, and data processing pipelines to support integrated evaluation, as well as explicit alignment with UN Sustainable Development Goals (<xref ref-type="bibr" rid="B13281233">United Nations 2015</xref>).</p>
        <p>Through this iterative consultative process, we found that the Open by Design approach provided a general design process as well as practical and flexible design elements that allowed builders to engage with open infrastructure principle frameworks across research disciplines, target users, and infrastructure types.</p>
      </sec>
      <sec sec-type="Infra Finder">
        <title>Infra Finder</title>
        <p>If asked, many stakeholders involved in building and managing research tools, standards, protocols, and services would readily say they believe in an open ethos. They may openly share (or be willing to share with anyone who asks) the content and software elements that they create and maintain. Some even use open licensing mechanisms (e.g., open source, open access) to indicate to others how their creations can be used. Still, the gap between professing openness and really practicing openness is wide.</p>
        <p>Invest in Open Infrastructure (IOI), has been actively testing ways to improve investment in and adoption of “openness” (and other key scholarly values and principles) and to better understand what barriers stand in the way of its implementation for different stakeholders in the research and knowledge ecosystem. In 2022, IOI began inviting infrastructures to participate in Infra Finder (<xref ref-type="bibr" rid="B13281294">IOI 2024</xref>), an information tool that would showcase “open infrastructures” in research and scholarship, providing up-to-date and verified information about key attributes of these tools, protocols, and standards to help their prospective funders and adopters to quickly see what options are available and to gauge their fitness for purpose across a number of vectors. Infra Finder launched in April 2024 with an initial set of 57 infrastructures, and in its first year, it added more than 50 additional infrastructures through a rolling intake process.</p>
        <p>The attributes Infra Finder focuses on and shares about these infrastructures are deeply informed by IOI’s work with values and principles frameworks, including POSI, FOREST, FAIR, CARE, and CHAOSS (<xref ref-type="bibr" rid="B13281225">CHAOSS 2025</xref>). Each infrastructure’s listing includes technical details (licensing, dependencies, road map) as well as information about its community engagement mechanisms, governance model, business form, and key policies.</p>
        <p>To participate, the represented infrastructures submit information about their entity and its practices, including its launch date, maintenance status, technical documentation, licensing, programming languages, standards used (metadata, PIDs, etc), how and by whom it is hosted, integrations with other tools/standards, community norms and contribution pathways (e.g., code of conduct, contribution guidelines), governance, policies, organizational structure, and engagement with values frameworks (FAIR, POSI, etc). IOI vets the information for each entity at submission and again annually, ensuring clear evidence exists for each claim that is made. IOI also evaluates whether the infrastructure conforms to at least one of its key criteria. Along the way, there is usually some level of dialogue between IOI and the infrastructure to elaborate or clarify particular points about the infrastructure.</p>
        <p>What IOI has learned in the first year of active hosting of this resource is just how much the process of engaging with IOI (and with the formal set of questions they answer in order to be included) has meant to its represented infrastructures. For these infrastructures, being represented publicly in this way has motivated and enabled them to clarify, both internally and externally, how they evidence their values.</p>
        <p>Participating infrastructures have actively increased their values alignment, citing Infra Finder’s intake process as “kind of an x-ray of our operations and way of working” that “certainly revealed some areas where we could improve” (<xref ref-type="bibr" rid="B13281167">Collister 2024</xref>). The intake process has prompted infrastructures to create or make more readily available their policies and documentation. It has also helped some to question and pursue changes in their governance models, and to prioritize work they may not have considered before, including creating a “living will” or sunset plans describing where open assets will (and won’t) go in the case of a shut down or transition and budgeting an operational reserve to fund these activities if/when needed. Infrastructures that are not (yet) featured are also reporting their use of the framework to better understand and strategically build towards more of the mission-aligned characteristics that Infra Finder surfaces.</p>
        <p>Much like the values and principles standards from which it has drawn (POSI, FOREST, etc), Infra Finder as a framework actively helps infrastructures to consider and evaluate their options for better values alignment; it also provides them with a crucial lens into the practices and behaviors modeled by their peers.</p>
        <p>It also helps make others - the funders and adopters - more aware of differences in models deployed by various infrastructures and gives those funders and adopters ample details to help them structure a conversation with the infrastructures that interest them.</p>
        <p>IOI created Infra Finder for a different, though related, purpose - to provide adopters and funders with additional, clear information about open tools, standards, and protocols that they could consider in hopes that it would increase their awareness and engagement with these infrastructures. In a 2025-2026 research study, “Measurement of Community Health Indicators,” funded by the Digital Infrastructure Insights Fund, IOI has been exploring how community health frameworks (CHAOSS, POSI, FOREST) are experienced by three key groups: infrastructures, adopters (institutions that use the software or standard, for example), and funders (e.g., philanthropies providing grant funding). Preliminary findings based on discovery interviews with academic libraries, research institutions, funders, technology creators, vendors, and collectives, include:</p>
        <p><list list-type="bullet">
          <list-item>
            <p>Many adopters/uses are primarily driven by practical needs like cost and fit-for-purpose. For this group, community health attributes are seen as value-added factors rather than decision drivers.</p>
          </list-item>
          <list-item>
            <p>Funders cite their strong desires to see underlying values like openness, transparency, sustainability, and community governance evidenced by the groups they fund, but also demonstrate very low awareness of the tools that could help.</p>
          </list-item>
          <list-item>
            <p>Adopters in well-resourced environments with capacity and desire to contribute (time or funding) to the open infrastructures with whom they work, saw community health as crucial for building and maintaining their trust (particularly elements like governance, community contribution, and financial transparency).</p>
          </list-item>
          <list-item>
            <p>Infrastructures themselves demonstrated low knowledge of community health frameworks, and their initial reaction to the idea was grounded not in “trust” but in “grading.” As one participant put it, “no one likes being judged.”</p>
          </list-item>
        </list></p>
        <p>As reflected also in the ARDC example above, two key barriers to the use of open infrastructure principle frameworks are the time and attention that are required to understand, let alone explore use of them. Embedding the frameworks in a reference environment like Infra Finder incentivizes players to engage with the key values and principles in very practical ways, thinking explicitly about their value to the work they do rather than as a philosophical exercise or other time-consuming, nice-to-have but exhausting-to-undertake requirement.</p>
        <p>In other words, part of what IOI is learning from running the Infra Finder service is that groups that resist spending time and energy on values and principles (either infrastructure providers evidencing them or funders and users finding evidence of them) may be highly motivated to provide clear signals of their open practices in an informational system that helps to spotlight these elements as design features (e.g., open licensing). The Infra Finder environment may help to encourage and incentivize “open by design” work without requiring separate evidence trails created for or provided by individual “principle” frameworks.</p>
      </sec>
      <sec sec-type="Next Generation Library Publishing">
        <title>Next Generation Library Publishing</title>
        <p>Library publishing, an early form of what is now referred to as diamond open access publishing, started in the early 2000s as a low cost way to put a range of content online, including journal and book content, as well as grey literature and digital humanities content. The California Digital Library (CDL), for example, launched the eScholarship Publishing program in 2002, offering free publishing solutions for the University of California (UC) faculty, students, and staff. eScholarship has become an exemplar for large scale diamond open access, providing publishing solutions for now over 90 scholar-led OA journals affiliated with the 10 campuses of the UC System. CDL supports publishing at this scale with a team of publishing professionals and technical staff, a level of dedicated resourcing that is not necessarily available to smaller libraries or other open access providers.</p>
        <p>For smaller library publishing programs, externally hosted publishing platforms, including bepress have historically enabled them to serve their communities with diamond OA publication options. In 2017, when bepress, the main outsourced library publishing solution, was acquired by a commercial publisher, library publishers sought new options aligned with open, non profit, and community-led values. Many library publishers have also been looking for ways to expand their programs to provide a compelling alternative to commercial and society publishers in alignment with these values.</p>
        <p>The Next Generation Library Publishing (NGLP) project launched in 2019, with the goal of knitting together open access components and filling in gaps in order to provide end-to-end infrastructures for submission, production, and distribution of journals at a level that would compete with proprietary commercial publishing options (<xref ref-type="bibr" rid="B13281159">NGLP 2022</xref>). With a grant from the Arcadia Fund, NGLP was formed by CDL, Strategies for Open Science (Stratos), and Educopia, and launched with a year of community engagement to gather requirements. The library publishing community indicated that, along with values-alignment, they wanted to build on existing infrastructures whenever possible and they would need hosting and production services since many could not manage hosting their own open source technologies in house.</p>
        <p>Building on this needs assessment, then-NGLP Product Owner Sarah Lippincott and then co-Principal Investigator Katherine Skinner, created, vetted, and released the FOREST Framework (<xref ref-type="bibr" rid="B13281390">Lippincott and Skinner 2022</xref>), a new methodology and instrument for assessing alignment with community values. This resource codified and made explicit a set of open values that could inform the design process for the NGLP project. It provided guidance on how to embed and enact common values in open infrastructures, including Financial sustainability; Openness; Representative governance; Equity, accessibility, and anti-oppression; Sharing of knowledge, and Transparency (FOREST), at any stage of their development. For the NGLP team, FOREST served as a framework for both the project’s development and business-planning work, from determining what OS components to use and how to build and host the code base, to planning for its future governance and management as an open infrastructure.</p>
        <p>NGLP has been designed to unite systems run by open infrastructures such as Open Journal Systems (OJS), Janeway, and DSpace, with a newly built publishing front end called Meru, built by Cast Iron Coding. Leveraging a modular framework, Meru enables aggregated display of publications managed in multiple back-end systems, supporting the growth of library publishing programs without requiring migration off of the often disparate tools they use. The NGLP project ran several pilots in 2021-2022 and received a lot of positive feedback from partners. The University of North Carolina (UNC) Press and Longleaf Services were able to turn this pilot into a successful business offering for local libraries and other customers, leading the way for a new set of mission-aligned services for diamond journal publishing.</p>
        <p>Then, in 2022, NGLP received a grant from IMLS to explore scaling the Meru effort with partner University of Iowa Libraries, a member of the Big Ten Academic Alliance (BTAA) of libraries. Recently, NGLP announced a partnership with BTAA to bring scale to the effort, working with multiple member libraries to explore a shared solution for the consortium to aggregate and display its combined publishing portfolio. Despite a funding shortage from IMLS, which required recalibrating goals for moving the University of Iowa to a production-ready system, the BTAA pilot is underway, and will be another proof point that the modular, open source solution is flexible and can meet the needs of different diamond open access publishers. With current funding challenges in institutions in the US, it is unclear whether diamond open access will receive enough support, but having choices in open source solutions will reduce costs and enable more cross-institutional collaboration and scale.</p>
        <p>The NGLP example is demonstrating that being intentional at the start of a large-scale infrastructure initiative can lead to alignment with community values and that separate and even competing services can share open infrastructures and assemble novel solutions that meet the needs of their user community.</p>
      </sec>
    </sec>
    <sec sec-type="Toward an “Open by Design” practice ">
      <title>Toward an “Open by Design” practice</title>
      <p>Working with and as entrepreneurs building open infrastructure, we have experienced first-hand the need for specific technical and behavioral design components that can be easily deployed in a modular architecture using standardized interfaces. We also realize that many entrepreneurs prefer to focus on technical requirements rather than socio-behavioral change, believing that it is easier to code than to converse. But, as design thinking teaches us, we must do both to position the infrastructure for adoption and impact.</p>
      <sec sec-type="Establishing the Design Framework">
        <title>Establishing the Design Framework</title>
        <p>We have taken learnings from each use case and here propose a flexible evaluation framework that combines public goods and open infrastructure frameworks (Fig. <xref ref-type="fig" rid="F13430244">1</xref> and Table <xref ref-type="table" rid="T13234894">1</xref>) with Open by Design product and process principles (Fig. <xref ref-type="fig" rid="F13430270">2</xref> and Table <xref ref-type="table" rid="T13234895">2</xref>) and the Open by Design evaluation framework (Fig. <xref ref-type="fig" rid="F13430367">3</xref>) organized by SDG, that can be used by any research infrastructure. Ideally, this framework would be consulted during the design phase, but it can also inform existing infrastructures with goals to align with open science principles.</p>
        <p>The Open by Design framework aligns accountabilities and metrics for research infrastructures designed as research resource technology (SDG 9, Table <xref ref-type="table" rid="T13234896">3</xref>), as training tools (SDG 4, Table <xref ref-type="table" rid="T13234897">4</xref>), and as foundations for research and policy studies (People &amp; Planet SDGs, Table <xref ref-type="table" rid="T13234898">5</xref>).</p>
        <p>Each infrastructure can ensure it meets the facets of open by design while also customizing its framework depending on its functional specifications and features, and also can use the framework to ensure that the product offering includes components of FAIR, CARE, POSI, and FOREST frameworks, as is pertinent to the product offering.</p>
      </sec>
      <sec sec-type="Instrumenting Impact Evaluation">
        <title>Instrumenting Impact Evaluation</title>
        <p>Once the design framework is established, the next step is the evaluation component. Given that each infrastructure has a specific constellation of services, activities, and beneficiaries, it is important that each customizes its community engagement and telemetry strategy. At the same time, there are similarities between infrastructures, and there is good reason to harmonise reporting when possible to enable effective internal and community oversight. To balance these needs, we have created a set of impact metrics for each Impact Area, aligned with the SDG pillars of Infrastructure, Education, and a grouping of SDGs around People-Planet. Within each, we ask a set of questions, and the infrastructure host can select which questions and measures are most relevant. The frameworks are shown below in Table <xref ref-type="table" rid="T13234900">6</xref>, Table <xref ref-type="table" rid="T13234901">7</xref>, and Table <xref ref-type="table" rid="T13234902">8</xref>.</p>
      </sec>
      <sec sec-type="Telemetry Strategies">
        <title>Telemetry Strategies</title>
        <p>Measuring adoption and use of research infrastructures is complex and flexible, but do-able. As shown above, to capture impact we need to use a range of approaches, including user surveys, usage data, and outputs monitoring. A key component of any measurement strategy is a combination of pre-planning and telemetry (<xref ref-type="bibr" rid="B13281212">Gagnon and Swanson 2023</xref>), which can include the integration and use of persistent identifiers (PIDs) in data pipelines and workflows (<xref ref-type="bibr" rid="B13281097">Haendel et al. 2021</xref>, <xref ref-type="bibr" rid="B13281088">Haak et al. 2018</xref>, <xref ref-type="bibr" rid="B13281268">Brown et al. 2023</xref>) as well as in-workflow user surveys, monitoring of help desk inquiries, and community meetings.</p>
        <sec sec-type="User Surveys">
          <title>User Surveys</title>
          <p>Research infrastructures are built by and for research communities. They need to reflect and support the needs of those communities. To do so, infrastructure project teams need to build pathways for connecting with users on an ongoing basis. ORCID single-sign-on (SSO) is one way to both collect user information and also request permission to send survey materials. ORCID SSO can be integrated into the pathways used to access the infrastructure; to process and/or download data; as well as to access webinars, code, and educational materials. Completion of ORCID SSO and permission to contact can be used to trigger a quick turn-around (within 24 hours) 3-question Net Promoter Score survey.</p>
          <p>Contact information collected in this way can also be used to carry out quarterly or annual surveys, and also compare users over time. An additional benefit of using ORCID SSO is the opportunity to collect user ORCID iDs to enable output tracking, as well as request permission to post information into a user’s ORCID record, such as creation of a dataset, contribution to a codebase, or curation of a data asset. In addition to these transactional data, it is important to also understand whether the infrastructure is facilitating relationship and trust building. Building out local community groups, supporting working groups, participating in standards work, and co-developing strategy with the community are all examples</p>
        </sec>
        <sec sec-type="Usage Data">
          <title>Usage Data</title>
          <p>How people are interacting with the infrastructure should also be monitored. This can provide data to improve the user experience as well as improve understanding of which product features, such as workflows or datasets, are being accessed. Data collected can include number of page views, datafile or database accesses and/or downloads, and should encompass the data asset as well as related code and educational materials. The use of PIDs for the component parts (“items”) of the data asset – at the very least, the entire asset (e.g., landing page), but also databases, data file subsets, codebases, and educational materials – will greatly facilitate this process. DataCite’s Fabrica and Usage Tracker toolsets (<xref ref-type="bibr" rid="B13281080">DataCite 2025b</xref>, <xref ref-type="bibr" rid="B13281204">DataCite 2025c</xref>) can be used to create, find, connect, and track DOIs and associated metadata.</p>
          <p>These tools align with COUNTER reporting practices. The COUNTER Project specifies total, unique, search, and session metrics for regular full-content databases (<xref ref-type="bibr" rid="B13281196">COUNTER 2023</xref>).</p>
          <p><list list-type="bullet">
            <list-item>
              <p>Total_Item_Requests. Counts every click where a user downloads the full content of an item from the database.</p>
            </list-item>
            <list-item>
              <p>Total_Item_Investigations. Total_Item_Requests and clicks on other information and clicks on links to other details.</p>
            </list-item>
            <list-item>
              <p>Unique_Item_Requests. Counts first click to download the full content of an item, per item per session (see below).</p>
            </list-item>
            <list-item>
              <p>Unique_Item_Investigations. Counts first click to download and follow-on clicks, one click per item per session.</p>
            </list-item>
            <list-item>
              <p>Search_Regular. Counts the number of user clicks in a search interface; for a resource such as an infrastructure this could count the number of searches kicked off from the infrastructure landing page.</p>
            </list-item>
            <list-item>
              <p>Sessions. COUNTER uses IP addresses to measure the amount of time within one hour in a 24-hour block that a user is logged into a data resource. The metric logs the number of total sessions within each one-hour timeblock.</p>
            </list-item>
          </list></p>
          <p>For some databases, standard Google Analytics reporting may be sufficient. While not open, GA is free for smaller-use websites; a subscription is needed for higher-volume websites. Google Analytics Engagement Reporting (<xref ref-type="bibr" rid="B13281188">Google 2025</xref>) can provide information on sessions, page accesses, user actions and “conversions’’ – such as an action taken on a database or dataset, and usage by country. This type of reporting does not require use of DOIs, but does benefit from their use.</p>
        </sec>
        <sec sec-type="Code Repository Activity">
          <title>Code Repository Activity</title>
          <p>Additional frameworks like Community Health Analytics in Open Source Software (<xref ref-type="bibr" rid="B13281225">CHAOSS 2025</xref>) have been developed to establish ways to gauge and measure aspects of an open source software based on specific topics, each of which includes explicit metrics. For example, CHAOSS can be used to understand the community health of a technical solution (software) developed and managed by an open source community by using metrics gathered through a github repository that relate to things like “Development Responsiveness” (how well a project is responding to issues and comments), “Code Changes Lines” (measuring how many lines of code are touched via additions and removals over a period of time), or “Project Popularity” (measuring visibility and engagement through forks, stars, social media mentions, and downstream dependencies). CHAOSS includes a wide range of both topics and metrics, and users of this assessment model can pick those that are applicable to their industry, software focus, and/or community design in order to surface data that can help them to analyze what is working and what may need attention within an open source project.</p>
        </sec>
        <sec sec-type="Outputs Monitoring">
          <title>Outputs Monitoring</title>
          <p>We also care about what users are doing with the data they have obtained from or processed using an infrastructure. How is the infrastructure being used to support inquiry and problem-solving? Modular architecture, standard triggers and labels, and data mining techniques have been deployed with success in educational games research (<xref ref-type="bibr" rid="B13281175">Zoeller 2013</xref>, <xref ref-type="bibr" rid="B13281072">DataCite 2025a</xref>). In addition, PIDs can help to automate reporting. Infrastructures that integrate ORCID SSO and manage PID assignments for their asset and component items can construct a PID graph. DataCite Commons (<xref ref-type="bibr" rid="B13281063">Costa Kohwalter et al. 2017</xref>) can be used to track DOI citations, as well as connections with PIDs for people, places, and funding.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="Discussion: Navigating openness and sustainability">
      <title>Discussion: Navigating openness and sustainability</title>
      <p>As a unifying concept, “Open by Design” provides a useful construct for designing and assessing research infrastructure openness. Coupled with SDGs, Open by Design provides a community-validated standard that enables a structured conversation about openness and impact while also allowing each infrastructure team the flexibility to discuss and decide which framework components are relevant for their project.</p>
      <p>From a design perspective, open research infrastructures should incorporate all of the Open by Design components. From an impact evaluation perspective, we posit that all open research infrastructures are aligned with SDG 9: Industry, Innovation,and Infrastructure, as they are all creating a new or novel research process resource in a governance framework with delivery tooling. While not always recognized by the infrastructure team, each also is aligned with SDG 4: Quality Education, as they are creating open data models, curation methods, and in some cases, open source code and training resources and workshops. Each of the infrastructures is associated with a constellation of other SDGs, which for the purposes of this project we have combined into “People and Planet”.</p>
      <p>The design framework developed in this project supports generative conversations about community benefit, and enables infrastructure teams to take a broad view of openness and impact. The design framework supports product design decisions, and together with the evaluation templates, informs design and implementation of usage telemetry in the present, near term, and farther into the future with a constellation of relevant impact metrics.</p>
      <p>The Open by Design framework provides clarity for design of open research infrastructure product features. It also can serve as a tool for existing research infrastructures to conduct a gap analysis to determine what might be missing in their functional requirements to be considered a true open science infrastructure. In addition to continuing to test the Open by Design approach with entrepreneurs and established infrastructures, we seek to share this approach to enable broader adoption of open science principles by research infrastructures, clarity in impact reporting, and general community understanding and expectation of the fulfillment of open science principles by the research tools and infrastructures they use.</p>
    </sec>
    <sec sec-type="Conclusion and recommendations ">
      <title>Conclusion and recommendations</title>
      <p>Overall, design thinking is as applicable in the research community as it is in manufacturing and service design. The iterative and interactive processes used are effective for engaging with stakeholders to test the applicability of the Open by Design approach.</p>
      <p>The Open by Design framework is relevant across a broad group of research e-infrastructure projects. There are salient examples of open infrastructures that have integrated these design components with great impact for their user and stakeholder communities, as recognized by the FASEB DataWorks Prize (<xref ref-type="bibr" rid="B13281097">Haendel et al. 2021</xref>, <xref ref-type="bibr" rid="B13280776">Abidi et al. 2020</xref>, <xref ref-type="bibr" rid="B13280762">Suraj et al. 2022</xref>).</p>
      <p>Of course, as with any Open by Design construct, continuous improvement is critical. Ongoing iterative testing should be used to assess the Open by Design framework. The data and means of collection for each of the impact areas should be assessed regularly to capture new survey methods, web usage tools, telemetry modules and implementation of persistent identifier tracking systems such as COUNTER and SCHOLIX. And, it is critical that the community continue to strive for workflow transparency by sharing not just data and code, but also the modules that support organizational behavior improvements, including templates for governance, fundraising and business models, user surveys and telemetry modules.</p>
      <p>Out of this work, we make the following recommendations for encouraging the adoption of Open by Design in the design, development, and evaluation of research infrastructure:</p>
      <sec sec-type="Infrastructure Builders">
        <title>Infrastructure Builders</title>
        <p>For individuals and organizations that design, engineer, build user communities, and maintain research infrastructures:</p>
        <p><list list-type="bullet">
          <list-item>
            <p>Engage on international data standards</p>
          </list-item>
          <list-item>
            <p>Use modular architecture, standardized interfaces, and ongoing user engagement to support sustainability and operational effectiveness.</p>
          </list-item>
          <list-item>
            <p>Use multiple methods to engage with all direct beneficiaries specifically to gather feedback to assess if your infrastructure is meeting their needs.</p>
          </list-item>
          <list-item>
            <p>Expand your training offering, including open source models, sample analysis code, documentation, and workshops.</p>
          </list-item>
          <list-item>
            <p>Proactively determine your impact goals, build your evaluation strategy into your infrastructure, and regulrly report out.</p>
          </list-item>
          <list-item>
            <p>Perform regular self-assessments of infrastructure openness and continue to improve your offering.</p>
          </list-item>
          <list-item>
            <p>Share your work, including software code, governance documents, evaluation criteria, and fundraising and budgeting templates.</p>
          </list-item>
        </list></p>
      </sec>
      <sec sec-type="Infrastructure Funders">
        <title>Infrastructure Funders</title>
        <p>For organizations – including government sector Ministries and Agencies and philanthropic organizations — that develop policies, funding programs, and training related to research infrastructures:</p>
        <p><list list-type="bullet">
          <list-item>
            <p>Work with infrastructure hosts and builders at project initiation and regularly throughout the project to signal the importance of openness and transparency and perform regular assessments.</p>
          </list-item>
          <list-item>
            <p>Work with infrastructure hosts and builders to map Impact Areas and determine reporting options, requirements, and workflows.</p>
          </list-item>
          <list-item>
            <p>Fund the development of standard interfaces and modules: plug-in “applets” for sign-on, permissioning, user surveys, web analytics, impact analytics.</p>
          </list-item>
          <list-item>
            <p>Continue to support international infrastructure standards work, through staff involvement and direct infrastructure participant support</p>
          </list-item>
          <list-item>
            <p>Build Impact reporting communities of practice through hands-on workshops with featured infrastructures</p>
          </list-item>
          <list-item>
            <p>Showcase infrastructure openness and impact in national and international venues, including workshops, articles, and demonstrations</p>
          </list-item>
          <list-item>
            <p>Include openness and transparency criteria in funding calls and funding agreements</p>
          </list-item>
          <list-item>
            <p>Support projects that work to enable ongoing infrastructure user engagement</p>
          </list-item>
        </list></p>
      </sec>
    </sec>
  </body>
  <back>
    <ack>
      <title>Acknowledgements</title>
      <p>Thank you to Leonidas Aristodemou for sharing his expertise on Design for Manufacturing frameworks; Catherine Mitchell, Sarah Lippincott, and Natasha Simons for comments on the paper; and to the ARDC National Data Asset project leads for their participation in workshops, thoughtful comments, and inputs into the evaluation frameworks. Also thank you to our reviewers Jonathan Starr, Zach Chandler, and Cameron Neylon for their insights and very useful suggestions for improving the paper. A portion of the work described in this paper was carried out under a contract to LLH with the Australian Research Data Commons, ARDC Contract NDA04.</p>
    </ack>
    <sec sec-type="Conflicts of interest">
      <title>Conflicts of interest</title>
      <p>No conflict of interest to declare</p>
      <p>Disclaimer: This article is (co-)authored by any of the Editors-in-Chief, Managing Editors or their deputies in this journal.</p>
    </sec>
    <ref-list>
      <title>References</title>
      <ref id="B13280776">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abidi</surname>
              <given-names>Maheen</given-names>
            </name>
            <name name-style="western">
              <surname>Aboulafia</surname>
              <given-names>David M.</given-names>
            </name>
            <name name-style="western">
              <surname>Accordino</surname>
              <given-names>Melissa K.</given-names>
            </name>
            <name name-style="western">
              <surname>Acoba</surname>
              <given-names>Jared D.</given-names>
            </name>
            <name name-style="western">
              <surname>Ahluwalia</surname>
              <given-names>Manmeet S.</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmad</surname>
              <given-names>Syed A.</given-names>
            </name>
            <name name-style="western">
              <surname>Ajmera</surname>
              <given-names>Archana</given-names>
            </name>
            <name name-style="western">
              <surname>Alimohamed</surname>
              <given-names>Saif I.</given-names>
            </name>
            <name name-style="western">
              <surname>Altman</surname>
              <given-names>Jessica</given-names>
            </name>
            <name name-style="western">
              <surname>Angevine</surname>
              <given-names>Anne H.</given-names>
            </name>
            <name name-style="western">
              <surname>Bakouny</surname>
              <given-names>Ziad</given-names>
            </name>
            <name name-style="western">
              <surname>Bar</surname>
              <given-names>Michael H.</given-names>
            </name>
            <name name-style="western">
              <surname>Bardia</surname>
              <given-names>Aditya</given-names>
            </name>
            <name name-style="western">
              <surname>Barnholtz-Sloan</surname>
              <given-names>Jill S.</given-names>
            </name>
            <name name-style="western">
              <surname>Barrow McCollough</surname>
              <given-names>Briana</given-names>
            </name>
            <name name-style="western">
              <surname>Bashir</surname>
              <given-names>Babar</given-names>
            </name>
            <name name-style="western">
              <surname>Batist</surname>
              <given-names>Gerald</given-names>
            </name>
            <name name-style="western">
              <surname>Bekaii-Saab</surname>
              <given-names>Tanios S.</given-names>
            </name>
            <name name-style="western">
              <surname>Berg</surname>
              <given-names>Stephanie</given-names>
            </name>
            <name name-style="western">
              <surname>Bernicker</surname>
              <given-names>Eric H.</given-names>
            </name>
            <name name-style="western">
              <surname>Bhutani</surname>
              <given-names>Divaya</given-names>
            </name>
            <name name-style="western">
              <surname>Bilen</surname>
              <given-names>Mehmet A.</given-names>
            </name>
            <name name-style="western">
              <surname>Bindal</surname>
              <given-names>Poorva</given-names>
            </name>
            <name name-style="western">
              <surname>Bishnoi</surname>
              <given-names>Rohit</given-names>
            </name>
            <name name-style="western">
              <surname>Blau</surname>
              <given-names>Sibel</given-names>
            </name>
            <name name-style="western">
              <surname>Bohachek</surname>
              <given-names>Pamela</given-names>
            </name>
            <name name-style="western">
              <surname>Boland</surname>
              <given-names>Genevieve</given-names>
            </name>
            <name name-style="western">
              <surname>Bonnen</surname>
              <given-names>Mark</given-names>
            </name>
            <name name-style="western">
              <surname>Bouchard</surname>
              <given-names>Gabrielle</given-names>
            </name>
            <name name-style="western">
              <surname>Bouganim</surname>
              <given-names>Nathaniel</given-names>
            </name>
            <name name-style="western">
              <surname>Bowles</surname>
              <given-names>Daniel W.</given-names>
            </name>
            <name name-style="western">
              <surname>Busser</surname>
              <given-names>Fiona J.</given-names>
            </name>
            <name name-style="western">
              <surname>Butt</surname>
              <given-names>Omar</given-names>
            </name>
            <name name-style="western">
              <surname>Cabal</surname>
              <given-names>Angelo</given-names>
            </name>
            <name name-style="western">
              <surname>Cabalona</surname>
              <given-names>Wilhelmina D.</given-names>
            </name>
            <name name-style="western">
              <surname>Cabebe</surname>
              <given-names>Elwyn C.</given-names>
            </name>
            <name name-style="western">
              <surname>Caimi</surname>
              <given-names>Paolo</given-names>
            </name>
            <name name-style="western">
              <surname>Campian</surname>
              <given-names>Jian L.</given-names>
            </name>
            <name name-style="western">
              <surname>Carducci</surname>
              <given-names>Theresa M.</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>James L.</given-names>
            </name>
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>Alex</given-names>
            </name>
            <name name-style="western">
              <surname>Chism</surname>
              <given-names>David D.</given-names>
            </name>
            <name name-style="western">
              <surname>Choueiri</surname>
              <given-names>Toni K.</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>Melanie J.</given-names>
            </name>
            <name name-style="western">
              <surname>Clement</surname>
              <given-names>Jessica M.</given-names>
            </name>
            <name name-style="western">
              <surname>Connors</surname>
              <given-names>Jean M.</given-names>
            </name>
            <name name-style="western">
              <surname>Cook</surname>
              <given-names>Erin</given-names>
            </name>
            <name name-style="western">
              <surname>Curran</surname>
              <given-names>Catherine R.</given-names>
            </name>
            <name name-style="western">
              <surname>Daher</surname>
              <given-names>Ahmad</given-names>
            </name>
            <name name-style="western">
              <surname>Dailey</surname>
              <given-names>Mark E.</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>Elizabeth J.</given-names>
            </name>
            <name name-style="western">
              <surname>Dawsey</surname>
              <given-names>Scott J.</given-names>
            </name>
            <name name-style="western">
              <surname>Deeken</surname>
              <given-names>John F.</given-names>
            </name>
            <name name-style="western">
              <surname>Del Prete</surname>
              <given-names>Salvatore A.</given-names>
            </name>
            <name name-style="western">
              <surname>Demetri</surname>
              <given-names>George D.</given-names>
            </name>
            <name name-style="western">
              <surname>Desai</surname>
              <given-names>Aakash</given-names>
            </name>
            <name name-style="western">
              <surname>Doroshow</surname>
              <given-names>Deborah B.</given-names>
            </name>
            <name name-style="western">
              <surname>Durbin</surname>
              <given-names>Eric B.</given-names>
            </name>
            <name name-style="western">
              <surname>Egan</surname>
              <given-names>Pamela C.</given-names>
            </name>
            <name name-style="western">
              <surname>Elias</surname>
              <given-names>Rawad</given-names>
            </name>
            <name name-style="western">
              <surname>Elkrief</surname>
              <given-names>Arielle</given-names>
            </name>
            <name name-style="western">
              <surname>Elms</surname>
              <given-names>Destry J.</given-names>
            </name>
            <name name-style="western">
              <surname>Elshoury</surname>
              <given-names>Amro</given-names>
            </name>
            <name name-style="western">
              <surname>Faller</surname>
              <given-names>Bryan</given-names>
            </name>
            <name name-style="western">
              <surname>Farmakiotis</surname>
              <given-names>Dimitrios</given-names>
            </name>
            <name name-style="western">
              <surname>Fecher</surname>
              <given-names>Leslie A.</given-names>
            </name>
            <name name-style="western">
              <surname>Feldman</surname>
              <given-names>Lawrence E.</given-names>
            </name>
            <name name-style="western">
              <surname>Ferrario</surname>
              <given-names>Cristiano</given-names>
            </name>
            <name name-style="western">
              <surname>Fiala</surname>
              <given-names>Mark A.</given-names>
            </name>
            <name name-style="western">
              <surname>Flora</surname>
              <given-names>Daniel B.</given-names>
            </name>
            <name name-style="western">
              <surname>French</surname>
              <given-names>Benjamin</given-names>
            </name>
            <name name-style="western">
              <surname>Friese</surname>
              <given-names>Christopher R.</given-names>
            </name>
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>Julie C.</given-names>
            </name>
            <name name-style="western">
              <surname>Gadgeel</surname>
              <given-names>Shirish M.</given-names>
            </name>
            <name name-style="western">
              <surname>Gainor</surname>
              <given-names>Justin</given-names>
            </name>
            <name name-style="western">
              <surname>Galsky</surname>
              <given-names>Matthew D.</given-names>
            </name>
            <name name-style="western">
              <surname>Gantt</surname>
              <given-names>Gerald</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia</surname>
              <given-names>Jorge A.</given-names>
            </name>
            <name name-style="western">
              <surname>Gartrell</surname>
              <given-names>Benjamin A.</given-names>
            </name>
            <name name-style="western">
              <surname>Gatti-Mays</surname>
              <given-names>Margaret E.</given-names>
            </name>
            <name name-style="western">
              <surname>Gill</surname>
              <given-names>David M.</given-names>
            </name>
            <name name-style="western">
              <surname>Gillaspie</surname>
              <given-names>Erin A.</given-names>
            </name>
            <name name-style="western">
              <surname>Giordano</surname>
              <given-names>Antonio</given-names>
            </name>
            <name name-style="western">
              <surname>Glace</surname>
              <given-names>(Mary) Grace</given-names>
            </name>
            <name name-style="western">
              <surname>Glover</surname>
              <given-names>Michael J.</given-names>
            </name>
            <name name-style="western">
              <surname>Goel</surname>
              <given-names>Sanjay</given-names>
            </name>
            <name name-style="western">
              <surname>Graber</surname>
              <given-names>Jerome J.</given-names>
            </name>
            <name name-style="western">
              <surname>Griffiths</surname>
              <given-names>Elizabeth A.</given-names>
            </name>
            <name name-style="western">
              <surname>Grivas</surname>
              <given-names>Petros</given-names>
            </name>
            <name name-style="western">
              <surname>Grover</surname>
              <given-names>Punita</given-names>
            </name>
            <name name-style="western">
              <surname>Gulati</surname>
              <given-names>Anthony P.</given-names>
            </name>
            <name name-style="western">
              <surname>Gulati</surname>
              <given-names>Shuchi</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>Shilpa</given-names>
            </name>
            <name name-style="western">
              <surname>Gurley</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Hafez</surname>
              <given-names>Navid</given-names>
            </name>
            <name name-style="western">
              <surname>Halabi</surname>
              <given-names>Susan</given-names>
            </name>
            <name name-style="western">
              <surname>Halfdanarson</surname>
              <given-names>Thorvardur R.</given-names>
            </name>
            <name name-style="western">
              <surname>Halmos</surname>
              <given-names>Balazs</given-names>
            </name>
            <name name-style="western">
              <surname>Hausrath</surname>
              <given-names>Daniel J.</given-names>
            </name>
            <name name-style="western">
              <surname>Hawley</surname>
              <given-names>Jessica E.</given-names>
            </name>
            <name name-style="western">
              <surname>Hennessy</surname>
              <given-names>Cassandra</given-names>
            </name>
            <name name-style="western">
              <surname>Herbst</surname>
              <given-names>Roy S.</given-names>
            </name>
            <name name-style="western">
              <surname>Hershman</surname>
              <given-names>Dawn L.</given-names>
            </name>
            <name name-style="western">
              <surname>Hoppenot</surname>
              <given-names>Claire</given-names>
            </name>
            <name name-style="western">
              <surname>Hoskins</surname>
              <given-names>Kent F.</given-names>
            </name>
            <name name-style="western">
              <surname>Hoyo-Ulloa</surname>
              <given-names>Irma</given-names>
            </name>
            <name name-style="western">
              <surname>Hsu</surname>
              <given-names>Emily</given-names>
            </name>
            <name name-style="western">
              <surname>Hsu</surname>
              <given-names>Chih-Yuan</given-names>
            </name>
            <name name-style="western">
              <surname>Hwang</surname>
              <given-names>Clara</given-names>
            </name>
            <name name-style="western">
              <surname>Islam</surname>
              <given-names>Jessica Yasmine</given-names>
            </name>
            <name name-style="western">
              <surname>Jabbour</surname>
              <given-names>Salma K.</given-names>
            </name>
            <name name-style="western">
              <surname>Jani</surname>
              <given-names>Chinmay</given-names>
            </name>
            <name name-style="western">
              <surname>Jha</surname>
              <given-names>Alokkumar</given-names>
            </name>
            <name name-style="western">
              <surname>Jhawar</surname>
              <given-names>Sachin R.</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>Douglas B.</given-names>
            </name>
            <name name-style="western">
              <surname>Joshi</surname>
              <given-names>Monika</given-names>
            </name>
            <name name-style="western">
              <surname>Kasi</surname>
              <given-names>Anup</given-names>
            </name>
            <name name-style="western">
              <surname>Kelleher</surname>
              <given-names>Kaitlin</given-names>
            </name>
            <name name-style="western">
              <surname>Kennecke</surname>
              <given-names>Hagen F.</given-names>
            </name>
            <name name-style="western">
              <surname>Khaki</surname>
              <given-names>Ali Raza</given-names>
            </name>
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>Hina</given-names>
            </name>
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>Mahir</given-names>
            </name>
            <name name-style="western">
              <surname>Kharofa</surname>
              <given-names>Jordan</given-names>
            </name>
            <name name-style="western">
              <surname>Kloecker</surname>
              <given-names>Goetz</given-names>
            </name>
            <name name-style="western">
              <surname>Knoble</surname>
              <given-names>Jeanna L.</given-names>
            </name>
            <name name-style="western">
              <surname>Kulkarni</surname>
              <given-names>Amit A.</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>Vaibhav</given-names>
            </name>
            <name name-style="western">
              <surname>Lammers</surname>
              <given-names>Philip E.</given-names>
            </name>
            <name name-style="western">
              <surname>Leighton</surname>
              <given-names>John C.</given-names>
            </name>
            <name name-style="western">
              <surname>Lemmon</surname>
              <given-names>Christopher A.</given-names>
            </name>
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>Mark A.</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Ang</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Xuanyi</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Stephen V.</given-names>
            </name>
            <name name-style="western">
              <surname>Lo</surname>
              <given-names>K. M.</given-names>
            </name>
            <name name-style="western">
              <surname>Loaiza-Bonilla</surname>
              <given-names>Arturo</given-names>
            </name>
            <name name-style="western">
              <surname>Logan</surname>
              <given-names>Barbara B.</given-names>
            </name>
            <name name-style="western">
              <surname>Loggers</surname>
              <given-names>Elizabeth T.</given-names>
            </name>
            <name name-style="western">
              <surname>De Lima Lopes</surname>
              <given-names>Gilberto</given-names>
            </name>
            <name name-style="western">
              <surname>Loree</surname>
              <given-names>Jonathan M.</given-names>
            </name>
            <name name-style="western">
              <surname>LoRusso</surname>
              <given-names>Patricia</given-names>
            </name>
            <name name-style="western">
              <surname>Low</surname>
              <given-names>Clarke A.</given-names>
            </name>
            <name name-style="western">
              <surname>Lustberg</surname>
              <given-names>Maryam B.</given-names>
            </name>
            <name name-style="western">
              <surname>Lyman</surname>
              <given-names>Gary H.</given-names>
            </name>
            <name name-style="western">
              <surname>Lynch</surname>
              <given-names>Ryan C.</given-names>
            </name>
            <name name-style="western">
              <surname>Madhavan</surname>
              <given-names>Subha</given-names>
            </name>
            <name name-style="western">
              <surname>Mahadevan</surname>
              <given-names>Daruka</given-names>
            </name>
            <name name-style="western">
              <surname>Mahmood</surname>
              <given-names>Sana Z.</given-names>
            </name>
            <name name-style="western">
              <surname>Mansoor</surname>
              <given-names>Abdul-Hai</given-names>
            </name>
            <name name-style="western">
              <surname>Marcum</surname>
              <given-names>Michelle</given-names>
            </name>
            <name name-style="western">
              <surname>Markham</surname>
              <given-names>Merry-Jennifer</given-names>
            </name>
            <name name-style="western">
              <surname>Mashru</surname>
              <given-names>Sandeep H.</given-names>
            </name>
            <name name-style="western">
              <surname>Masters</surname>
              <given-names>Tyler</given-names>
            </name>
            <name name-style="western">
              <surname>Mavromatis</surname>
              <given-names>Blanche H.</given-names>
            </name>
            <name name-style="western">
              <surname>McKay</surname>
              <given-names>Rana R.</given-names>
            </name>
            <name name-style="western">
              <surname>McNair</surname>
              <given-names>Christopher</given-names>
            </name>
            <name name-style="western">
              <surname>McWeeney</surname>
              <given-names>Shannon</given-names>
            </name>
            <name name-style="western">
              <surname>Menendez</surname>
              <given-names>Alvaro G.</given-names>
            </name>
            <name name-style="western">
              <surname>Menon</surname>
              <given-names>Harry</given-names>
            </name>
            <name name-style="western">
              <surname>Mesa</surname>
              <given-names>Ruben A.</given-names>
            </name>
            <name name-style="western">
              <surname>Mico</surname>
              <given-names>Vasil</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>Chaim</given-names>
            </name>
            <name name-style="western">
              <surname>Mishra</surname>
              <given-names>Sanjay</given-names>
            </name>
            <name name-style="western">
              <surname>Monahan</surname>
              <given-names>Ryan S.</given-names>
            </name>
            <name name-style="western">
              <surname>Morgans</surname>
              <given-names>Alicia K.</given-names>
            </name>
            <name name-style="western">
              <surname>Mulcahy</surname>
              <given-names>Mary F.</given-names>
            </name>
            <name name-style="western">
              <surname>Mundt</surname>
              <given-names>Daniel</given-names>
            </name>
            <name name-style="western">
              <surname>Mushtaq</surname>
              <given-names>Sarah</given-names>
            </name>
            <name name-style="western">
              <surname>Nagaraj</surname>
              <given-names>Gayathri</given-names>
            </name>
            <name name-style="western">
              <surname>Nagle</surname>
              <given-names>Sarah</given-names>
            </name>
            <name name-style="western">
              <surname>Nakasone</surname>
              <given-names>Elizabeth S.</given-names>
            </name>
            <name name-style="western">
              <surname>Nakayama</surname>
              <given-names>John M.</given-names>
            </name>
            <name name-style="western">
              <surname>Nelson</surname>
              <given-names>Heather H.</given-names>
            </name>
            <name name-style="western">
              <surname>Nemecek</surname>
              <given-names>Eneida R.</given-names>
            </name>
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>Ryan H.</given-names>
            </name>
            <name name-style="western">
              <surname>Nizam</surname>
              <given-names>Amanda</given-names>
            </name>
            <name name-style="western">
              <surname>Nohria</surname>
              <given-names>Anju</given-names>
            </name>
            <name name-style="western">
              <surname>Nuzzo</surname>
              <given-names>Pier Vitale</given-names>
            </name>
            <name name-style="western">
              <surname>Ohri</surname>
              <given-names>Nitin</given-names>
            </name>
            <name name-style="western">
              <surname>Olszewski</surname>
              <given-names>Adam J.</given-names>
            </name>
            <name name-style="western">
              <surname>Owenby</surname>
              <given-names>Susie</given-names>
            </name>
            <name name-style="western">
              <surname>Painter</surname>
              <given-names>Corrie A.</given-names>
            </name>
            <name name-style="western">
              <surname>Palmer</surname>
              <given-names>Joshua D.</given-names>
            </name>
            <name name-style="western">
              <surname>Panagiotou</surname>
              <given-names>Orestis A.</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>Cathleen</given-names>
            </name>
            <name name-style="western">
              <surname>Pasquinelli</surname>
              <given-names>Mary M.</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>Jaymin M.</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>Kanishka G.</given-names>
            </name>
            <name name-style="western">
              <surname>Peddi</surname>
              <given-names>Prakash</given-names>
            </name>
            <name name-style="western">
              <surname>Pennell</surname>
              <given-names>Nathan A.</given-names>
            </name>
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>Solange</given-names>
            </name>
            <name name-style="western">
              <surname>Pilar</surname>
              <given-names>Christine</given-names>
            </name>
            <name name-style="western">
              <surname>Pillainayagam</surname>
              <given-names>Clement</given-names>
            </name>
            <name name-style="western">
              <surname>Puc</surname>
              <given-names>Matthew</given-names>
            </name>
            <name name-style="western">
              <surname>Ramirez</surname>
              <given-names>Amelie G.</given-names>
            </name>
            <name name-style="western">
              <surname>Rathmann</surname>
              <given-names>Joerg</given-names>
            </name>
            <name name-style="western">
              <surname>Ravindranathan</surname>
              <given-names>Deepak</given-names>
            </name>
            <name name-style="western">
              <surname>Reid</surname>
              <given-names>Sonya A.</given-names>
            </name>
            <name name-style="western">
              <surname>Reuben</surname>
              <given-names>Daniel Y.</given-names>
            </name>
            <name name-style="western">
              <surname>Revankar</surname>
              <given-names>Sanjay G.</given-names>
            </name>
            <name name-style="western">
              <surname>Reynolds</surname>
              <given-names>Kerry L.</given-names>
            </name>
            <name name-style="western">
              <surname>Rho</surname>
              <given-names>Young Soo</given-names>
            </name>
            <name name-style="western">
              <surname>Rhodes</surname>
              <given-names>Terence D.</given-names>
            </name>
            <name name-style="western">
              <surname>Rice</surname>
              <given-names>Robert L.</given-names>
            </name>
            <name name-style="western">
              <surname>Riess</surname>
              <given-names>Jonathan</given-names>
            </name>
            <name name-style="western">
              <surname>Rini</surname>
              <given-names>Brian I.</given-names>
            </name>
            <name name-style="western">
              <surname>Rink</surname>
              <given-names>Cameron</given-names>
            </name>
            <name name-style="western">
              <surname>Rosen</surname>
              <given-names>Lane R.</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenstein</surname>
              <given-names>Lori J.</given-names>
            </name>
            <name name-style="western">
              <surname>Rosovsky</surname>
              <given-names>Rachel P.</given-names>
            </name>
            <name name-style="western">
              <surname>Routy</surname>
              <given-names>Bertrand</given-names>
            </name>
            <name name-style="western">
              <surname>Rovito</surname>
              <given-names>Marc A.</given-names>
            </name>
            <name name-style="western">
              <surname>Rubinstein</surname>
              <given-names>Samuel M.</given-names>
            </name>
            <name name-style="western">
              <surname>Saif</surname>
              <given-names>M. Wasif</given-names>
            </name>
            <name name-style="western">
              <surname>Salazar</surname>
              <given-names>Mary</given-names>
            </name>
            <name name-style="western">
              <surname>Santos Dutra</surname>
              <given-names>Miriam</given-names>
            </name>
            <name name-style="western">
              <surname>Schapira</surname>
              <given-names>Lidia</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>Andrew L.</given-names>
            </name>
            <name name-style="western">
              <surname>Schroeder</surname>
              <given-names>Brett A.</given-names>
            </name>
            <name name-style="western">
              <surname>Schwartz</surname>
              <given-names>Gary K.</given-names>
            </name>
            <name name-style="western">
              <surname>Schwartz</surname>
              <given-names>Candice</given-names>
            </name>
            <name name-style="western">
              <surname>Schweizer</surname>
              <given-names>Michael T.</given-names>
            </name>
            <name name-style="western">
              <surname>Serrano</surname>
              <given-names>Oscar K.</given-names>
            </name>
            <name name-style="western">
              <surname>Shafer</surname>
              <given-names>Danielle A.</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>Pankil K.</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>Dimpy</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>Mansi R.</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>Sumit A.</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>Chintan</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>Grace</given-names>
            </name>
            <name name-style="western">
              <surname>Shaya</surname>
              <given-names>Justin A.</given-names>
            </name>
            <name name-style="western">
              <surname>Shyr</surname>
              <given-names>Yu</given-names>
            </name>
            <name name-style="western">
              <surname>Slosky</surname>
              <given-names>David A.</given-names>
            </name>
            <name name-style="western">
              <surname>Smits</surname>
              <given-names>Melissa</given-names>
            </name>
            <name name-style="western">
              <surname>Solorzano</surname>
              <given-names>Carmen C.</given-names>
            </name>
            <name name-style="western">
              <surname>Stauffer</surname>
              <given-names>Karen</given-names>
            </name>
            <name name-style="western">
              <surname>Stockerl-Goldstein</surname>
              <given-names>Keith E.</given-names>
            </name>
            <name name-style="western">
              <surname>Stover</surname>
              <given-names>Daniel G.</given-names>
            </name>
            <name name-style="western">
              <surname>Stratton</surname>
              <given-names>Jamie</given-names>
            </name>
            <name name-style="western">
              <surname>Stratton</surname>
              <given-names>Catherine</given-names>
            </name>
            <name name-style="western">
              <surname>Streckfuss</surname>
              <given-names>Mitrianna</given-names>
            </name>
            <name name-style="western">
              <surname>Subbiah</surname>
              <given-names>Suki</given-names>
            </name>
            <name name-style="western">
              <surname>Tachiki</surname>
              <given-names>Lisa</given-names>
            </name>
            <name name-style="western">
              <surname>Tadesse</surname>
              <given-names>Eyob</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>Michael A.</given-names>
            </name>
            <name name-style="western">
              <surname>Topaloglu</surname>
              <given-names>Umit</given-names>
            </name>
            <name name-style="western">
              <surname>Tucker</surname>
              <given-names>Matthew D.</given-names>
            </name>
            <name name-style="western">
              <surname>Van Allen</surname>
              <given-names>Eliezer M.</given-names>
            </name>
            <name name-style="western">
              <surname>Van Loon</surname>
              <given-names>Susan</given-names>
            </name>
            <name name-style="western">
              <surname>Vega-Luna</surname>
              <given-names>Karen</given-names>
            </name>
            <name name-style="western">
              <surname>Venepalli</surname>
              <given-names>Neeta K.</given-names>
            </name>
            <name name-style="western">
              <surname>Verma</surname>
              <given-names>Amit</given-names>
            </name>
            <name name-style="western">
              <surname>Vikas</surname>
              <given-names>Praveen</given-names>
            </name>
            <name name-style="western">
              <surname>Vinayak</surname>
              <given-names>Shaveta</given-names>
            </name>
            <name name-style="western">
              <surname>Vinh</surname>
              <given-names>Donald C.</given-names>
            </name>
            <name name-style="western">
              <surname>Wagner</surname>
              <given-names>Michael J.</given-names>
            </name>
            <name name-style="western">
              <surname>Wall</surname>
              <given-names>Sarah</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Lucy L.</given-names>
            </name>
            <name name-style="western">
              <surname>Warner</surname>
              <given-names>Jeremy L.</given-names>
            </name>
            <name name-style="western">
              <surname>Wehbe</surname>
              <given-names>Firas H.</given-names>
            </name>
            <name name-style="western">
              <surname>Weinstein</surname>
              <given-names>Paul L.</given-names>
            </name>
            <name name-style="western">
              <surname>Weiss</surname>
              <given-names>Matthias</given-names>
            </name>
            <name name-style="western">
              <surname>Weissmann</surname>
              <given-names>Lisa B.</given-names>
            </name>
            <name name-style="western">
              <surname>Wildes</surname>
              <given-names>Tanya M.</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Wise-Draper</surname>
              <given-names>Trisha M.</given-names>
            </name>
            <name name-style="western">
              <surname>Wood</surname>
              <given-names>William A.</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Julie Tsu-Yu</given-names>
            </name>
            <name name-style="western">
              <surname>Wulff-Burchfield</surname>
              <given-names>Elizabeth M.</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>Zhuoer</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Wenxin</given-names>
            </name>
            <name name-style="western">
              <surname>Yeh</surname>
              <given-names>Albert C.</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>Irene S.</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>Peter Paul</given-names>
            </name>
            <name name-style="western">
              <surname>Zacks</surname>
              <given-names>Rosemary</given-names>
            </name>
            <name name-style="western">
              <surname>Zaman</surname>
              <given-names>Qamar Ul</given-names>
            </name>
            <name name-style="western">
              <surname>Zaren</surname>
              <given-names>Howard</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Tian</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>Alice Y.</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>Huili</given-names>
            </name>
            <name name-style="western">
              <surname>Zon</surname>
              <given-names>Rebecca L.</given-names>
            </name>
            <name name-style="western">
              <surname>Zubiri</surname>
              <given-names>Leyre</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>A Systematic Framework to Rapidly Obtain Data on Patients with Cancer and COVID-19: CCC19 Governance, Protocol, and Quality Assurance</article-title>
          <source>Cancer Cell</source>
          <volume>38</volume>
          <issue>6</issue>
          <fpage>761</fpage>
          <lpage>766</lpage>
          <uri>https://linkinghub.elsevier.com/retrieve/pii/S1535610820305535</uri>
          <pub-id pub-id-type="doi">10.1016/j.ccell.2020.10.022</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281495">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Agate</surname>
              <given-names>Nicky</given-names>
            </name>
            <name name-style="western">
              <surname>Long</surname>
              <given-names>Christopher P.</given-names>
            </name>
            <name name-style="western">
              <surname>Russell</surname>
              <given-names>Bonnie</given-names>
            </name>
            <name name-style="western">
              <surname>Kennison</surname>
              <given-names>Rebecca</given-names>
            </name>
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>Penelope</given-names>
            </name>
            <name name-style="western">
              <surname>Sacchi</surname>
              <given-names>Simone</given-names>
            </name>
            <name name-style="western">
              <surname>Rhody</surname>
              <given-names>Jason</given-names>
            </name>
            <name name-style="western">
              <surname>Thornton Dill</surname>
              <given-names>Bonnie</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Walking the Talk: Toward a Values-Aligned Academy</article-title>
          <publisher-name>Humetrics HSS</publisher-name>
          <comment>DOI: 10.17613/06SF-AD45</comment>
          <uri>https://works.hcommons.org/doi/10.17613/06sf-ad45</uri>
        </element-citation>
      </ref>
      <ref id="B13281563">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Allen</surname>
              <given-names>Liz</given-names>
            </name>
            <name name-style="western">
              <surname>O’Connell</surname>
              <given-names>Alison</given-names>
            </name>
            <name name-style="western">
              <surname>Kiermer</surname>
              <given-names>Veronique</given-names>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>How can we ensure visibility and diversity in research contributions? How the Contributor Role Taxonomy (CRediT) is helping the shift from authorship to contributorship</article-title>
          <source>Learned Publishing</source>
          <volume>32</volume>
          <issue>1</issue>
          <fpage>71</fpage>
          <lpage>74</lpage>
          <uri>https://onlinelibrary.wiley.com/doi/10.1002/leap.1210</uri>
          <pub-id pub-id-type="doi">10.1002/leap.1210</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281431">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>AmeliCA</surname>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>AmeliCA Principes and Values</article-title>
          <uri>http://amelica.org/index.php/en/principles-and-values/</uri>
        </element-citation>
      </ref>
      <ref id="B13281250">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Amorim</surname>
              <given-names>Ricardo Carvalho</given-names>
            </name>
            <name name-style="western">
              <surname>Castro</surname>
              <given-names>João Aguiar</given-names>
            </name>
            <name name-style="western">
              <surname>Rocha Da Silva</surname>
              <given-names>João</given-names>
            </name>
            <name name-style="western">
              <surname>Ribeiro</surname>
              <given-names>Cristina</given-names>
            </name>
          </person-group>
          <year>2017</year>
          <article-title>A comparison of research data management platforms: architecture, flexible metadata and interoperability</article-title>
          <source>Universal Access in the Information Society</source>
          <volume>16</volume>
          <issue>4</issue>
          <fpage>851</fpage>
          <lpage>862</lpage>
          <uri>http://link.springer.com/10.1007/s10209-016-0475-y</uri>
          <pub-id pub-id-type="doi">10.1007/s10209-016-0475-y</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281544">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Andreasen</surname>
              <given-names>Mogens Myrup</given-names>
            </name>
            <name name-style="western">
              <surname>Hein</surname>
              <given-names>Lars</given-names>
            </name>
            <name name-style="western">
              <surname>Andreasen</surname>
              <given-names>Mogens Myrup</given-names>
            </name>
          </person-group>
          <year>1987</year>
          <source>Integrated product development</source>
          <publisher-name>IFS (Publ.)</publisher-name>
          <publisher-loc>Bedford, UK</publisher-loc>
        </element-citation>
      </ref>
      <ref id="B13281325">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>ARDC</surname>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>National Data Assets \textbar ARDC</article-title>
          <publisher-name>Australian Research Data Commons</publisher-name>
          <uri>https://ardc.edu.au/program/national-data-assets/</uri>
        </element-citation>
      </ref>
      <ref id="B13281407">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Badolato</surname>
              <given-names>Anne-Marie</given-names>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>Criteria for the eligibility of projects for funding by the National Fund for Open Science</article-title>
          <uri>https://www.ouvrirlascience.fr/criteria-for-the-eligibility-of-projects-for-funding-by-the-national-fund-for-open-science</uri>
        </element-citation>
      </ref>
      <ref id="B13281536">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Baldwin</surname>
              <given-names>Carliss Y.</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>Kim B.</given-names>
            </name>
          </person-group>
          <year>2014</year>
          <source>Design Rules: Volume 1. The Power of Modularity</source>
          <publisher-name>The MIT Press</publisher-name>
          <publisher-loc>Cambridge, Massachusetts London</publisher-loc>
        </element-citation>
      </ref>
      <ref id="B13430336">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bijl-Brouwer</surname>
              <given-names>Mieke van der</given-names>
            </name>
          </person-group>
          <year>2017</year>
          <article-title>Designing for Social Infrastructures in Complex Service Systems: A Human-Centered and Social Systems Perspective on Service Design</article-title>
          <source>She Ji: The Journal of Design, Economics, and Innovation</source>
          <volume>3</volume>
          <issue>3</issue>
          <fpage>183</fpage>
          <lpage>197</lpage>
          <pub-id pub-id-type="doi">10.1016/j.sheji.2017.11.002</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281516">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bilder</surname>
              <given-names>Geoffrey</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Jennifer</given-names>
            </name>
            <name name-style="western">
              <surname>Neylon</surname>
              <given-names>Cameron</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>The Principles of Open Scholarly Infrastructure</article-title>
          <source>Websit</source>
          <uri>https://openscholarlyinfrastructure.org</uri>
          <pub-id pub-id-type="doi">10.24343/C34W2H</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281658">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bladek</surname>
              <given-names>Marta</given-names>
            </name>
          </person-group>
          <year>2014</year>
          <article-title>DORA: San Francisco Declaration on Research Assessment (May 2013)</article-title>
          <source>College &amp; Research Libraries News</source>
          <volume>75</volume>
          <issue>4</issue>
          <fpage>191</fpage>
          <lpage>196</lpage>
          <uri>http://crln.acrl.org/index.php/crlnews/article/view/9104</uri>
          <pub-id pub-id-type="doi">10.5860/crln.75.4.9104</pub-id>
        </element-citation>
      </ref>
      <ref id="B13430227">
        <element-citation publication-type="book">
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Bollier</surname>
              <given-names>D.</given-names>
            </name>
            <name name-style="western">
              <surname>Helfrich</surname>
              <given-names>S.</given-names>
            </name>
          </person-group>
          <year>2015</year>
          <source>Patterns of Commoning</source>
          <publisher-name>Off the Commons Press</publisher-name>
          <publisher-loc>Amherst</publisher-loc>
          <uri>https://patternsofcommoning.org/</uri>
          <isbn>9781937146832</isbn>
        </element-citation>
      </ref>
      <ref id="B13281642">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Boothroyd</surname>
              <given-names>Geoffrey</given-names>
            </name>
            <name name-style="western">
              <surname>Dewhurst</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Knight</surname>
              <given-names>Winston A.</given-names>
            </name>
          </person-group>
          <year>2011</year>
          <source>Product design for manufacture and assembly</source>
          <edition>3. ed</edition>
          <publisher-name>CRC Press</publisher-name>
          <publisher-loc>Boca Raton, Fla.</publisher-loc>
        </element-citation>
      </ref>
      <ref id="B13281268">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>Christopher</given-names>
            </name>
            <name name-style="western">
              <surname>Simons</surname>
              <given-names>Natasha</given-names>
            </name>
            <name name-style="western">
              <surname>Bangert</surname>
              <given-names>Daniel</given-names>
            </name>
            <name name-style="western">
              <surname>Sadler</surname>
              <given-names>Shawna</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>RDA National PID Strategies Guide and Checklist</article-title>
          <source>Zenodo</source>
          <uri>https://zenodo.org/records/8431975</uri>
          <pub-id pub-id-type="doi">10.15497/RDA/00091</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281616">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>Tim</given-names>
            </name>
          </person-group>
          <year>2008</year>
          <article-title>Design Thinking</article-title>
          <source>Harvard Business Review</source>
          <volume>86</volume>
          <issue>6</issue>
          <fpage>84</fpage>
          <lpage>92</lpage>
          <uri>https://hbr.org/2008/06/design-thinking</uri>
        </element-citation>
      </ref>
      <ref id="B13281589">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carroll</surname>
              <given-names>Stephanie Russo</given-names>
            </name>
            <name name-style="western">
              <surname>Herczog</surname>
              <given-names>Edit</given-names>
            </name>
            <name name-style="western">
              <surname>Hudson</surname>
              <given-names>Maui</given-names>
            </name>
            <name name-style="western">
              <surname>Russell</surname>
              <given-names>Keith</given-names>
            </name>
            <name name-style="western">
              <surname>Stall</surname>
              <given-names>Shelley</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Operationalizing the CARE and FAIR Principles for Indigenous data futures</article-title>
          <source>Scientific Data</source>
          <volume>8</volume>
          <issue>1</issue>
          <uri>https://www.nature.com/articles/s41597-021-00892-0</uri>
          <pub-id pub-id-type="doi">10.1038/s41597-021-00892-0</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281225">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>CHAOSS</surname>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>Community Health Analytics in Open Source Software</article-title>
          <uri>https://chaoss.community/</uri>
        </element-citation>
      </ref>
      <ref id="B13281608">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chesbrough</surname>
              <given-names>Henry</given-names>
            </name>
          </person-group>
          <year>2003</year>
          <source>Open innovation: the new imperative for creating and profiting from technology</source>
          <publisher-name>Harvard Business School Press</publisher-name>
          <publisher-loc>Boston, Mass</publisher-loc>
        </element-citation>
      </ref>
      <ref id="B13281455">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>COAR</surname>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>COAR Next Generation Repositories: Principles</article-title>
          <publisher-name>Coalition of Open Access Repositories</publisher-name>
          <uri>http://ngr.coar-repositories.org/principles/</uri>
        </element-citation>
      </ref>
      <ref id="B13430281">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>CoARA</surname>
            </name>
          </person-group>
          <article-title>WG Towards Open Infrastructures for Responsible Research Assessment (OI4RRA)</article-title>
          <uri>https://coara.eu/working-groups/working-groups/wg-towards-open-infrastructures-for-responsible-research-assessment-oi4rra/</uri>
          <date-in-citation content-type="access-date">2025-08-11T00:38:54+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13281167">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Collister</surname>
              <given-names>Lauren</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Infra Finder Spotlight: OAPEN and DOAB</article-title>
          <uri>https://investinopen.org/blog/infra-finder-spotlight-oapen-doab/</uri>
        </element-citation>
      </ref>
      <ref id="B13281063">
        <element-citation publication-type="conference-preoceeding">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Costa Kohwalter</surname>
              <given-names>Troy</given-names>
            </name>
            <name name-style="western">
              <surname>Gresta Paulino Murta</surname>
              <given-names>Leonardo</given-names>
            </name>
            <name name-style="western">
              <surname>Walter Gonzalez Clua</surname>
              <given-names>Esteban</given-names>
            </name>
          </person-group>
          <year>2017</year>
          <source>Capturing Game Telemetry with Provenance</source>
          <conf-name>2017 16th Brazilian Symposium on Computer Games and Digital Entertainment (SBGames)</conf-name>
          <uri>https://ieeexplore.ieee.org/document/8400319/</uri>
          <isbn>978-1-5386-4846-9</isbn>
          <pub-id pub-id-type="doi">10.1109/SBGames.2017.00016</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281196">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>COUNTER</surname>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>COUNTER Code of Practice Release 5.1 — COUNTER Code of Practice Release 5 5.1 documentation</article-title>
          <uri>https://cop5.countermetrics.org/en/5.1/index.html</uri>
        </element-citation>
      </ref>
      <ref id="B13281072">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>DataCite</surname>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>DataCite Commons</article-title>
          <publisher-name>Dataite</publisher-name>
          <uri>https://commons.datacite.org/about</uri>
        </element-citation>
      </ref>
      <ref id="B13281080">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>DataCite</surname>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>DataCite Usage Tracker</article-title>
          <publisher-name>DataCite</publisher-name>
          <uri>https://support.datacite.org/docs/datacite-usage-tracker</uri>
        </element-citation>
      </ref>
      <ref id="B13281204">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>DataCite</surname>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>DataCite Fabrica</article-title>
          <publisher-name>DataCite</publisher-name>
          <uri>https://doi.datacite.org/</uri>
        </element-citation>
      </ref>
      <ref id="B13281439">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>DPSC</surname>
            </name>
          </person-group>
          <year>2018</year>
          <article-title>Digital Preservation Declaration of Shared Values</article-title>
          <publisher-name>Digital Preservation Services Collaborative</publisher-name>
          <uri>https://dpscollaborative.org/shared-values_en.html</uri>
        </element-citation>
      </ref>
      <ref id="B13430378">
        <element-citation publication-type="conference-paper">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Edwards</surname>
              <given-names>K.</given-names>
            </name>
            <name name-style="western">
              <surname>Bellotti</surname>
              <given-names>V.</given-names>
            </name>
            <name name-style="western">
              <surname>Dey</surname>
              <given-names>A. K.</given-names>
            </name>
            <name name-style="western">
              <surname>Newman</surname>
              <given-names>M.</given-names>
            </name>
          </person-group>
          <year>2003</year>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>CHI</surname>
            </name>
          </person-group>
          <article-title>Stuck in the middle: The challenges of user-centered design and evaluation for middleware.</article-title>
          <source>Stuck in the middle: The challenges of user-centered design and evaluation for middleware.</source>
          <volume>2003</volume>
          <conf-name>CHI 2003</conf-name>
          <conf-loc>Ft. Lauderdale</conf-loc>
          <conf-date>5-10 April 2003</conf-date>
          <publisher-name>ACM</publisher-name>
          <source>Proceedings of CHI</source>
          <size units="page">6425611-642664</size>
          <isbn>1-58113-630-7/03/0004</isbn>
        </element-citation>
      </ref>
      <ref id="B13281285">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Flanagan</surname>
              <given-names>Heather</given-names>
            </name>
            <name name-style="western">
              <surname>Haak</surname>
              <given-names>Laurel L.</given-names>
            </name>
            <name name-style="western">
              <surname>Paglione</surname>
              <given-names>Laura Dorival</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Approaching Trust: Case Studies for Developing Global Research Infrastructures</article-title>
          <source>Frontiers in Research Metrics and Analytics</source>
          <volume>6</volume>
          <uri>https://www.frontiersin.org/articles/10.3389/frma.2021.746514/full</uri>
          <pub-id pub-id-type="doi">10.3389/frma.2021.746514</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281507">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Group</surname>
              <given-names>FORCE11 Scholarly Commons Working</given-names>
            </name>
          </person-group>
          <year>2017</year>
          <article-title>Principles Of The Scholarly Commons, Version 0.1.1</article-title>
          <source>Website</source>
          <uri>https://zenodo.org/record/569952</uri>
          <pub-id pub-id-type="doi">10.5281/ZENODO.569952</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281572">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gagliardi</surname>
              <given-names>Anna R.</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Rob H. C.</given-names>
            </name>
            <name name-style="western">
              <surname>Boury</surname>
              <given-names>Himani</given-names>
            </name>
            <name name-style="western">
              <surname>Albert</surname>
              <given-names>Mathieu</given-names>
            </name>
            <name name-style="western">
              <surname>Chow</surname>
              <given-names>James</given-names>
            </name>
            <name name-style="western">
              <surname>DaCosta</surname>
              <given-names>Ralph S.</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffman</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Keshavarz</surname>
              <given-names>Behrang</given-names>
            </name>
            <name name-style="western">
              <surname>Kontos</surname>
              <given-names>Pia</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Jenny</given-names>
            </name>
            <name name-style="western">
              <surname>McAndrews</surname>
              <given-names>Mary Pat</given-names>
            </name>
            <name name-style="western">
              <surname>Protze</surname>
              <given-names>Stephanie</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>DORA-compliant measures of research quality and impact to assess the performance of researchers in biomedical institutions: Review of published research, international best practice and Delphi survey</article-title>
          <source>PLOS ONE</source>
          <volume>18</volume>
          <issue>5</issue>
          <uri>https://dx.plos.org/10.1371/journal.pone.0270616</uri>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0270616</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281212">
        <element-citation publication-type="chapter">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gagnon</surname>
              <given-names>David J.</given-names>
            </name>
            <name name-style="western">
              <surname>Swanson</surname>
              <given-names>Luke</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <chapter-title>Open Game Data: A Technical Infrastructure for Open Science with Educational Games</chapter-title>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Haahr</surname>
              <given-names>M.</given-names>
            </name>
            <name name-style="western">
              <surname>Rojas-Salazar</surname>
              <given-names>A.</given-names>
            </name>
            <name name-style="western">
              <surname>Göbel</surname>
              <given-names>S.</given-names>
            </name>
          </person-group>
          <source>Serious Games: 9th Joint International Conference, JCSG</source>
          <volume>14309</volume>
          <publisher-name>Springer Nature</publisher-name>
          <uri>https://link.springer.com/10.1007/978-3-031-44751-8_1</uri>
          <isbn>978-3-031-44750-1 978-3-031-44751-8</isbn>
          <pub-id pub-id-type="doi">10.1007/978-3-031-44751-8_1</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281463">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>GIDA</surname>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>CARE Principles</article-title>
          <uri>https://www.gida-global.org/care</uri>
        </element-citation>
      </ref>
      <ref id="B13281471">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>FAIR</surname>
              <given-names>GO</given-names>
            </name>
          </person-group>
          <year>2016</year>
          <article-title>FAIR Principles</article-title>
          <uri>https://www.go-fair.org/fair-principles/</uri>
        </element-citation>
      </ref>
      <ref id="B13281188">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Google</surname>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>Analytics &amp; Data Analysis Features List - Analytics</article-title>
          <publisher-name>Google</publisher-name>
          <uri>https://marketingplatform.google.com/about/analytics/features/</uri>
        </element-citation>
      </ref>
      <ref id="B13281487">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Group</surname>
              <given-names>FORCE 11 Scholarly Communications Working</given-names>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>Charters and principles in scholarly communication</article-title>
          <publisher-name>FORCE 11</publisher-name>
          <uri>https://docs.google.com/spreadsheets/d/1-aRXFiRg-VL9hpLpxoJqX6-OC-A0R2oCogHfIx52Nug/edit?gid=956616118</uri>
        </element-citation>
      </ref>
      <ref id="B13281302">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Haak</surname>
              <given-names>Laurel L.</given-names>
            </name>
            <name name-style="western">
              <surname>Baker</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Ginther</surname>
              <given-names>Donna K.</given-names>
            </name>
            <name name-style="western">
              <surname>Gordon</surname>
              <given-names>Gregg J.</given-names>
            </name>
            <name name-style="western">
              <surname>Probus</surname>
              <given-names>Matthew A.</given-names>
            </name>
            <name name-style="western">
              <surname>Kannankutty</surname>
              <given-names>Nirmala</given-names>
            </name>
            <name name-style="western">
              <surname>Weinberg</surname>
              <given-names>Bruce A.</given-names>
            </name>
          </person-group>
          <year>2012</year>
          <article-title>Standards and Infrastructure for Innovation Data Exchange</article-title>
          <source>Science</source>
          <volume>338</volume>
          <issue>6104</issue>
          <fpage>196</fpage>
          <lpage>197</lpage>
          <uri>https://www.science.org/doi/10.1126/science.1221840</uri>
          <pub-id pub-id-type="doi">10.1126/science.1221840</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281088">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Haak</surname>
              <given-names>Laurel L.</given-names>
            </name>
            <name name-style="western">
              <surname>Meadows</surname>
              <given-names>Alice</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>Josh</given-names>
            </name>
          </person-group>
          <year>2018</year>
          <article-title>Using ORCID, DOI, and Other Open Identifiers in Research Evaluation</article-title>
          <source>Frontiers in Research Metrics and Analytics</source>
          <volume>3</volume>
          <uri>https://www.frontiersin.org/article/10.3389/frma.2018.00028/full</uri>
          <pub-id pub-id-type="doi">10.3389/frma.2018.00028</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281241">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Haak</surname>
              <given-names>Laurel</given-names>
            </name>
            <name name-style="western">
              <surname>Greene</surname>
              <given-names>Sarah</given-names>
            </name>
            <name name-style="western">
              <surname>Ratan</surname>
              <given-names>Kristen</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>A New Research Economy: Socio-technical framework to open up lines of credit in the academic community</article-title>
          <source>Research Ideas and Outcomes</source>
          <volume>6</volume>
          <uri>https://riojournal.com/article/60477/</uri>
          <pub-id pub-id-type="doi">10.3897/rio.6.e60477</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281097">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Haendel</surname>
              <given-names>Melissa A</given-names>
            </name>
            <name name-style="western">
              <surname>Chute</surname>
              <given-names>Christopher G</given-names>
            </name>
            <name name-style="western">
              <surname>Bennett</surname>
              <given-names>Tellen D</given-names>
            </name>
            <name name-style="western">
              <surname>Eichmann</surname>
              <given-names>David A</given-names>
            </name>
            <name name-style="western">
              <surname>Guinney</surname>
              <given-names>Justin</given-names>
            </name>
            <name name-style="western">
              <surname>Kibbe</surname>
              <given-names>Warren A</given-names>
            </name>
            <name name-style="western">
              <surname>Payne</surname>
              <given-names>Philip R O</given-names>
            </name>
            <name name-style="western">
              <surname>Pfaff</surname>
              <given-names>Emily R</given-names>
            </name>
            <name name-style="western">
              <surname>Robinson</surname>
              <given-names>Peter N</given-names>
            </name>
            <name name-style="western">
              <surname>Saltz</surname>
              <given-names>Joel H</given-names>
            </name>
            <name name-style="western">
              <surname>Spratt</surname>
              <given-names>Heidi</given-names>
            </name>
            <name name-style="western">
              <surname>Suver</surname>
              <given-names>Christine</given-names>
            </name>
            <name name-style="western">
              <surname>Wilbanks</surname>
              <given-names>John</given-names>
            </name>
            <name name-style="western">
              <surname>Wilcox</surname>
              <given-names>Adam B</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>Andrew E</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Chunlei</given-names>
            </name>
            <name name-style="western">
              <surname>Blacketer</surname>
              <given-names>Clair</given-names>
            </name>
            <name name-style="western">
              <surname>Bradford</surname>
              <given-names>Robert L</given-names>
            </name>
            <name name-style="western">
              <surname>Cimino</surname>
              <given-names>James J</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>Marshall</given-names>
            </name>
            <name name-style="western">
              <surname>Colmenares</surname>
              <given-names>Evan W</given-names>
            </name>
            <name name-style="western">
              <surname>Francis</surname>
              <given-names>Patricia A</given-names>
            </name>
            <name name-style="western">
              <surname>Gabriel</surname>
              <given-names>Davera</given-names>
            </name>
            <name name-style="western">
              <surname>Graves</surname>
              <given-names>Alexis</given-names>
            </name>
            <name name-style="western">
              <surname>Hemadri</surname>
              <given-names>Raju</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>Stephanie S</given-names>
            </name>
            <name name-style="western">
              <surname>Hripscak</surname>
              <given-names>George</given-names>
            </name>
            <name name-style="western">
              <surname>Jiao</surname>
              <given-names>Dazhi</given-names>
            </name>
            <name name-style="western">
              <surname>Klann</surname>
              <given-names>Jeffrey G</given-names>
            </name>
            <name name-style="western">
              <surname>Kostka</surname>
              <given-names>Kristin</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Adam M</given-names>
            </name>
            <name name-style="western">
              <surname>Lehmann</surname>
              <given-names>Harold P</given-names>
            </name>
            <name name-style="western">
              <surname>Lingrey</surname>
              <given-names>Lora</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>Robert T</given-names>
            </name>
            <name name-style="western">
              <surname>Morris</surname>
              <given-names>Michele</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>Shawn N</given-names>
            </name>
            <name name-style="western">
              <surname>Natarajan</surname>
              <given-names>Karthik</given-names>
            </name>
            <name name-style="western">
              <surname>Palchuk</surname>
              <given-names>Matvey B</given-names>
            </name>
            <name name-style="western">
              <surname>Sheikh</surname>
              <given-names>Usman</given-names>
            </name>
            <name name-style="western">
              <surname>Solbrig</surname>
              <given-names>Harold</given-names>
            </name>
            <name name-style="western">
              <surname>Visweswaran</surname>
              <given-names>Shyam</given-names>
            </name>
            <name name-style="western">
              <surname>Walden</surname>
              <given-names>Anita</given-names>
            </name>
            <name name-style="western">
              <surname>Walters</surname>
              <given-names>Kellie M</given-names>
            </name>
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>Griffin M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Xiaohan Tanner</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>Richard L</given-names>
            </name>
            <name name-style="western">
              <surname>Amor</surname>
              <given-names>Benjamin</given-names>
            </name>
            <name name-style="western">
              <surname>Girvin</surname>
              <given-names>Andrew T</given-names>
            </name>
            <name name-style="western">
              <surname>Manna</surname>
              <given-names>Amin</given-names>
            </name>
            <name name-style="western">
              <surname>Qureshi</surname>
              <given-names>Nabeel</given-names>
            </name>
            <name name-style="western">
              <surname>Kurilla</surname>
              <given-names>Michael G</given-names>
            </name>
            <name name-style="western">
              <surname>Michael</surname>
              <given-names>Sam G</given-names>
            </name>
            <name name-style="western">
              <surname>Portilla</surname>
              <given-names>Lili M</given-names>
            </name>
            <name name-style="western">
              <surname>Rutter</surname>
              <given-names>Joni L</given-names>
            </name>
            <name name-style="western">
              <surname>Austin</surname>
              <given-names>Christopher P</given-names>
            </name>
            <name name-style="western">
              <surname>Gersing</surname>
              <given-names>Ken R</given-names>
            </name>
            <name name-style="western">
              <surname>Consortium</surname>
              <given-names>the N3C</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>The National COVID Cohort Collaborative (N3C): Rationale, design, infrastructure, and deployment</article-title>
          <source>Journal of the American Medical Informatics Association</source>
          <volume>28</volume>
          <issue>3</issue>
          <fpage>427</fpage>
          <lpage>443</lpage>
          <uri>https://academic.oup.com/jamia/article/28/3/427/5893482</uri>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa196</pub-id>
        </element-citation>
      </ref>
      <ref id="B13430346">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Henfridsson</surname>
              <given-names>Ola</given-names>
            </name>
            <name name-style="western">
              <surname>Bygstad</surname>
              <given-names>Bendik</given-names>
            </name>
          </person-group>
          <year>2013</year>
          <article-title>The Generative Mechanisms of Digital Infrastructure Evolution</article-title>
          <source>The MIS Quarterly</source>
          <volume>37</volume>
          <issue>3</issue>
          <fpage>907</fpage>
          <lpage>931</lpage>
          <uri>http://www.jstor.org/stable/43826006</uri>
          <pub-id pub-id-type="doi">10.25300/MISQ/2013/37.3.11</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281751">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hicks</surname>
              <given-names>Diana</given-names>
            </name>
            <name name-style="western">
              <surname>Wouters</surname>
              <given-names>Paul</given-names>
            </name>
            <name name-style="western">
              <surname>Waltman</surname>
              <given-names>Ludo</given-names>
            </name>
            <name name-style="western">
              <surname>De Rijcke</surname>
              <given-names>Sarah</given-names>
            </name>
            <name name-style="western">
              <surname>Rafols</surname>
              <given-names>Ismael</given-names>
            </name>
          </person-group>
          <year>2015</year>
          <article-title>Bibliometrics: The Leiden Manifesto for research metrics</article-title>
          <source>Nature</source>
          <volume>520</volume>
          <issue>7548</issue>
          <fpage>429</fpage>
          <lpage>431</lpage>
          <uri>https://www.nature.com/articles/520429a</uri>
          <pub-id pub-id-type="doi">10.1038/520429a</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281683">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hrynaszkiewicz</surname>
              <given-names>Iain</given-names>
            </name>
            <name name-style="western">
              <surname>Simons</surname>
              <given-names>Natasha</given-names>
            </name>
            <name name-style="western">
              <surname>Hussain</surname>
              <given-names>Azhar</given-names>
            </name>
            <name name-style="western">
              <surname>Grant</surname>
              <given-names>Rebecca</given-names>
            </name>
            <name name-style="western">
              <surname>Goudie</surname>
              <given-names>Simon</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Developing a Research Data Policy Framework for All Journals and Publishers (Correction)</article-title>
          <source>Data Science Journal</source>
          <volume>19</volume>
          <uri>http://datascience.codata.org/articles/10.5334/dsj-2020-017/</uri>
          <pub-id pub-id-type="doi">10.5334/dsj-2020-017</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281294">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>IOI</surname>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>About Infra Finder</article-title>
          <uri>https://investinopen.org/data-room/about-infra-finder/</uri>
        </element-citation>
      </ref>
      <ref id="B13430185">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>IxDF</surname>
            </name>
          </person-group>
          <year>2023</year>
          <source>The Principles of Service Design Thinking - Building Better Services.</source>
          <publisher-name>Interaction Design Foundation</publisher-name>
          <uri>https://www.interaction-design.org/literature/article/the-principles-of-service-design-thinking-building-better-services</uri>
        </element-citation>
      </ref>
      <ref id="B13281341">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jacobsen</surname>
              <given-names>Annika</given-names>
            </name>
            <name name-style="western">
              <surname>De Miranda Azevedo</surname>
              <given-names>Ricardo</given-names>
            </name>
            <name name-style="western">
              <surname>Juty</surname>
              <given-names>Nick</given-names>
            </name>
            <name name-style="western">
              <surname>Batista</surname>
              <given-names>Dominique</given-names>
            </name>
            <name name-style="western">
              <surname>Coles</surname>
              <given-names>Simon</given-names>
            </name>
            <name name-style="western">
              <surname>Cornet</surname>
              <given-names>Ronald</given-names>
            </name>
            <name name-style="western">
              <surname>Courtot</surname>
              <given-names>Mélanie</given-names>
            </name>
            <name name-style="western">
              <surname>Crosas</surname>
              <given-names>Mercè</given-names>
            </name>
            <name name-style="western">
              <surname>Dumontier</surname>
              <given-names>Michel</given-names>
            </name>
            <name name-style="western">
              <surname>Evelo</surname>
              <given-names>Chris T.</given-names>
            </name>
            <name name-style="western">
              <surname>Goble</surname>
              <given-names>Carole</given-names>
            </name>
            <name name-style="western">
              <surname>Guizzardi</surname>
              <given-names>Giancarlo</given-names>
            </name>
            <name name-style="western">
              <surname>Hansen</surname>
              <given-names>Karsten Kryger</given-names>
            </name>
            <name name-style="western">
              <surname>Hasnain</surname>
              <given-names>Ali</given-names>
            </name>
            <name name-style="western">
              <surname>Hettne</surname>
              <given-names>Kristina</given-names>
            </name>
            <name name-style="western">
              <surname>Heringa</surname>
              <given-names>Jaap</given-names>
            </name>
            <name name-style="western">
              <surname>Hooft</surname>
              <given-names>Rob W. W.</given-names>
            </name>
            <name name-style="western">
              <surname>Imming</surname>
              <given-names>Melanie</given-names>
            </name>
            <name name-style="western">
              <surname>Jeffery</surname>
              <given-names>Keith G.</given-names>
            </name>
            <name name-style="western">
              <surname>Kaliyaperumal</surname>
              <given-names>Rajaram</given-names>
            </name>
            <name name-style="western">
              <surname>Kersloot</surname>
              <given-names>Martijn G.</given-names>
            </name>
            <name name-style="western">
              <surname>Kirkpatrick</surname>
              <given-names>Christine R.</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>Tobias</given-names>
            </name>
            <name name-style="western">
              <surname>Labastida</surname>
              <given-names>Ignasi</given-names>
            </name>
            <name name-style="western">
              <surname>Magagna</surname>
              <given-names>Barbara</given-names>
            </name>
            <name name-style="western">
              <surname>McQuilton</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Meyers</surname>
              <given-names>Natalie</given-names>
            </name>
            <name name-style="western">
              <surname>Montesanti</surname>
              <given-names>Annalisa</given-names>
            </name>
            <name name-style="western">
              <surname>Van Reisen</surname>
              <given-names>Mirjam</given-names>
            </name>
            <name name-style="western">
              <surname>Rocca-Serra</surname>
              <given-names>Philippe</given-names>
            </name>
            <name name-style="western">
              <surname>Pergl</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Sansone</surname>
              <given-names>Susanna-Assunta</given-names>
            </name>
            <name name-style="western">
              <surname>Da Silva Santos</surname>
              <given-names>Luiz Olavo Bonino</given-names>
            </name>
            <name name-style="western">
              <surname>Schneider</surname>
              <given-names>Juliane</given-names>
            </name>
            <name name-style="western">
              <surname>Strawn</surname>
              <given-names>George</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>Mark</given-names>
            </name>
            <name name-style="western">
              <surname>Waagmeester</surname>
              <given-names>Andra</given-names>
            </name>
            <name name-style="western">
              <surname>Weigel</surname>
              <given-names>Tobias</given-names>
            </name>
            <name name-style="western">
              <surname>Wilkinson</surname>
              <given-names>Mark D.</given-names>
            </name>
            <name name-style="western">
              <surname>Willighagen</surname>
              <given-names>Egon L.</given-names>
            </name>
            <name name-style="western">
              <surname>Wittenburg</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Roos</surname>
              <given-names>Marco</given-names>
            </name>
            <name name-style="western">
              <surname>Mons</surname>
              <given-names>Barend</given-names>
            </name>
            <name name-style="western">
              <surname>Schultes</surname>
              <given-names>Erik</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>FAIR Principles: Interpretations and Implementation Considerations</article-title>
          <source>Data Intelligence</source>
          <volume>2</volume>
          <issue>1-2</issue>
          <fpage>10</fpage>
          <lpage>29</lpage>
          <uri>https://www.sciengine.com/doi/10.1162/dint_r_00024</uri>
          <pub-id pub-id-type="doi">10.1162/dint_r_00024</pub-id>
        </element-citation>
      </ref>
      <ref id="B13430145">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Leonelli</surname>
              <given-names>S.</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <source>Philosophy of Open Science</source>
          <publisher-name>Cambridge University Press</publisher-name>
          <publisher-loc>Cambridge</publisher-loc>
          <comment content-type="language">English</comment>
          <pub-id pub-id-type="doi">10.1017/9781009416368</pub-id>
        </element-citation>
      </ref>
      <ref id="B13430259">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Yu-Kai</given-names>
            </name>
            <name name-style="western">
              <surname>Maruping</surname>
              <given-names>Likoebe M.</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Open Source Collaboration in Digital Entrepreneurship</article-title>
          <source>Organization Science</source>
          <volume>33</volume>
          <issue>1</issue>
          <fpage>212</fpage>
          <lpage>230</lpage>
          <pub-id pub-id-type="doi">10.1287/orsc.2021.1538</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281390">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lippincott</surname>
              <given-names>Sarah</given-names>
            </name>
            <name name-style="western">
              <surname>Skinner</surname>
              <given-names>Katherine</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>FOREST Framework for Values-Driven Scholarly Communication</article-title>
          <source>Zenodo</source>
          <uri>https://zenodo.org/records/6557302</uri>
        </element-citation>
      </ref>
      <ref id="B13281552">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Miceli</surname>
              <given-names>Milagros</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Tianling</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia</surname>
              <given-names>Adriana Alvarado</given-names>
            </name>
            <name name-style="western">
              <surname>Posada</surname>
              <given-names>Julian</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Sonja Mei</given-names>
            </name>
            <name name-style="western">
              <surname>Pohl</surname>
              <given-names>Marc</given-names>
            </name>
            <name name-style="western">
              <surname>Hanna</surname>
              <given-names>Alex</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Documenting Data Production Processes: A Participatory Approach for Data Work</article-title>
          <publisher-name>arXiv</publisher-name>
          <uri>http://arxiv.org/abs/2207.04958</uri>
          <pub-id pub-id-type="doi">10.1145/3555623</pub-id>
        </element-citation>
      </ref>
      <ref id="B13430219">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Miettinen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sarantou</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <year>2017</year>
          <source>Social design for servcies framework: Capturing service design for development framework.</source>
          <publisher-name>Design Management Association</publisher-name>
        </element-citation>
      </ref>
      <ref id="B13281525">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mons</surname>
              <given-names>Barend</given-names>
            </name>
            <name name-style="western">
              <surname>Neylon</surname>
              <given-names>Cameron</given-names>
            </name>
            <name name-style="western">
              <surname>Velterop</surname>
              <given-names>Jan</given-names>
            </name>
            <name name-style="western">
              <surname>Dumontier</surname>
              <given-names>Michel</given-names>
            </name>
            <name name-style="western">
              <surname>Da Silva Santos</surname>
              <given-names>Luiz Olavo Bonino</given-names>
            </name>
            <name name-style="western">
              <surname>Wilkinson</surname>
              <given-names>Mark D.</given-names>
            </name>
          </person-group>
          <year>2017</year>
          <article-title>Cloudy, increasingly FAIR; revisiting the FAIR Data guiding principles for the European Open Science Cloud</article-title>
          <source>Information Services and Use</source>
          <volume>37</volume>
          <issue>1</issue>
          <fpage>49</fpage>
          <lpage>56</lpage>
          <uri>https://journals.sagepub.com/doi/10.3233/ISU-170824</uri>
          <pub-id pub-id-type="doi">10.3233/ISU-170824</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281277">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>National Academies of Sciences</surname>
              <given-names>Engineering, and Medicine</given-names>
            </name>
          </person-group>
          <year>2018</year>
          <source>International Coordination for Science Data Infrastructure: Proceedings of a Workshop"</source>
          <publisher-name>National Academies Press</publisher-name>
          <publisher-loc>Washington, D.C.</publisher-loc>
          <uri>https://www.nap.edu/catalog/25015</uri>
        </element-citation>
      </ref>
      <ref id="B13281675">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>National Academies of Sciences</surname>
              <given-names>Engineering, and Medicine</given-names>
            </name>
          </person-group>
          <year>2018</year>
          <source>Open Science by Design: Realizing a Vision for 21st Century Research</source>
          <publisher-name>National Academies Press</publisher-name>
          <publisher-loc>Washington, D.C.</publisher-loc>
          <uri>https://www.nap.edu/catalog/25116</uri>
        </element-citation>
      </ref>
      <ref id="B13281159">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>NGLP</surname>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Next Generation Library Publishing Software</article-title>
          <uri>https://www.nextgenlibpub.org/software</uri>
        </element-citation>
      </ref>
      <ref id="B13281399">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>OANA</surname>
            </name>
          </person-group>
          <year>2016</year>
          <article-title>Vienna Principles a vision for scholarly communication</article-title>
          <uri>https://viennaprinciples.org/</uri>
        </element-citation>
      </ref>
      <ref id="B13281333">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>OECD</surname>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>Reference framework for assessing the scientific and socio-economic impact of research infrastructures</article-title>
          <comment>DOI: 10.1787/3ffee43b-en</comment>
          <uri>https://www.oecd.org/en/publications/reference-framework-for-assessing-the-scientific-and-socio-economic-impact-of-research-infrastructures_3ffee43b-en.html</uri>
        </element-citation>
      </ref>
      <ref id="B13281650">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>OECD</surname>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>Steering AI's future: Strategies for anticipatory governance</article-title>
          <comment>DOI: 10.1787/5480ff0a-en</comment>
          <uri>https://www.oecd.org/en/publications/steering-ai-s-future_5480ff0a-en.html</uri>
        </element-citation>
      </ref>
      <ref id="B13281314">
        <element-citation publication-type="conference-preoceeding">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Osagie</surname>
              <given-names>Edobor</given-names>
            </name>
            <name name-style="western">
              <surname>Waqar</surname>
              <given-names>Mohammad</given-names>
            </name>
            <name name-style="western">
              <surname>Adebayo</surname>
              <given-names>Samuel</given-names>
            </name>
            <name name-style="western">
              <surname>Stasiewicz</surname>
              <given-names>Arkadiusz</given-names>
            </name>
            <name name-style="western">
              <surname>Porwol</surname>
              <given-names>Lukasz</given-names>
            </name>
            <name name-style="western">
              <surname>Ojo</surname>
              <given-names>Adegboyega</given-names>
            </name>
          </person-group>
          <year>2017</year>
          <source>Usability Evaluation of an Open Data Platform</source>
          <conf-name>Proceedings of the 18th Annual International Conference on Digital Government Research</conf-name>
          <uri>https://dl.acm.org/doi/10.1145/3085228.3085315</uri>
          <isbn>978-1-4503-5317-5</isbn>
          <pub-id pub-id-type="doi">10.1145/3085228.3085315</pub-id>
        </element-citation>
      </ref>
      <ref id="B13430153">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ostram</surname>
              <given-names>Elinor</given-names>
            </name>
          </person-group>
          <year>2009</year>
          <article-title>A general framework for analyzing sustainability of social-ecological systems</article-title>
          <source>Science</source>
          <volume>325</volume>
          <issue>5939</issue>
          <fpage>419</fpage>
          <lpage>422</lpage>
          <comment content-type="language">English</comment>
          <pub-id pub-id-type="doi">10.1126/science.1172133</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281599">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Platts</surname>
              <given-names>K. W.</given-names>
            </name>
            <name name-style="western">
              <surname>Gregory</surname>
              <given-names>M. J.</given-names>
            </name>
          </person-group>
          <year>1990</year>
          <article-title>Manufacturing Audit in the Process of Strategy Formulation</article-title>
          <source>International Journal of Operations &amp; Production Management</source>
          <volume>10</volume>
          <issue>9</issue>
          <fpage>5</fpage>
          <lpage>26</lpage>
          <uri>https://www.emerald.com/insight/content/doi/10.1108/EUM0000000001264/full/html</uri>
          <pub-id pub-id-type="doi">10.1108/EUM0000000001264</pub-id>
        </element-citation>
      </ref>
      <ref id="B13430177">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Reason</surname>
              <given-names>Ben</given-names>
            </name>
            <name name-style="western">
              <surname>Løvli</surname>
              <given-names>Lavrons</given-names>
            </name>
            <name name-style="western">
              <surname>Brand Flu</surname>
              <given-names>Melvin</given-names>
            </name>
          </person-group>
          <year>2015</year>
          <source>Service design for business: A practical guide to optimizing the customer experience</source>
          <publisher-name>John Wiley &amp; Sons</publisher-name>
          <comment content-type="language">English</comment>
        </element-citation>
      </ref>
      <ref id="B13430250">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rossi</surname>
              <given-names>Bruno</given-names>
            </name>
            <name name-style="western">
              <surname>Russo</surname>
              <given-names>Barbara</given-names>
            </name>
            <name name-style="western">
              <surname>Succi</surname>
              <given-names>Giancarlo</given-names>
            </name>
          </person-group>
          <year>2012</year>
          <article-title>Adoption of free/libre open source software in public organizations: factors of impact.</article-title>
          <source>Information Technology &amp; People</source>
          <volume>25</volume>
          <issue>2</issue>
          <fpage>156</fpage>
          <lpage>187</lpage>
          <pub-id pub-id-type="doi">10.1108/09593841211232677</pub-id>
        </element-citation>
      </ref>
      <ref id="B13430164">
        <element-citation publication-type="chapter">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rytilahti</surname>
              <given-names>P.</given-names>
            </name>
            <name name-style="western">
              <surname>Miettinen</surname>
              <given-names>S.</given-names>
            </name>
            <name name-style="western">
              <surname>Vuontisjärvi</surname>
              <given-names>H. R.</given-names>
            </name>
          </person-group>
          <year>2015</year>
          <chapter-title>The theoretical landscape of service design</chapter-title>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Aaron</surname>
              <given-names>M.</given-names>
            </name>
          </person-group>
          <source>Design, user experience, and usability: Design discourse</source>
          <publisher-name>Springer</publisher-name>
          <publisher-loc>Berlin</publisher-loc>
          <size units="page">86-97</size>
          <comment content-type="language">English</comment>
          <pub-id pub-id-type="doi">10.1007/978-3-319-20886-2_9</pub-id>
        </element-citation>
      </ref>
      <ref id="B13430235">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sangiorgi</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <year>2011</year>
          <article-title>Transformative Services and Transformation Design.</article-title>
          <source>International Journal of Design</source>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>29</fpage>
          <lpage>4</lpage>
        </element-citation>
      </ref>
      <ref id="B13281667">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schultes</surname>
              <given-names>E.</given-names>
            </name>
            <name name-style="western">
              <surname>Magagna</surname>
              <given-names>B.</given-names>
            </name>
            <name name-style="western">
              <surname>Hettne</surname>
              <given-names>K. M.,</given-names>
            </name>
            <name name-style="western">
              <surname>Pergl</surname>
              <given-names>R.</given-names>
            </name>
            <name name-style="western">
              <surname>Suchánek</surname>
              <given-names>M.</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>T.</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Reusable FAIR Implementation Profiles as Accelerators of FAIR Convergence. In: Grossmann, G., Ram, S. (eds) Advances in Conceptual Modeling. ER 2020. Lecture Notes in Computer Science, vol 12584</article-title>
          <publisher-name>Springer</publisher-name>
          <pub-id pub-id-type="doi">10.1007/978-3-030-65847-2_13</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281259">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Seffah</surname>
              <given-names>Ahmed</given-names>
            </name>
            <name name-style="western">
              <surname>Donyaee</surname>
              <given-names>Mohammad</given-names>
            </name>
            <name name-style="western">
              <surname>Kline</surname>
              <given-names>Rex B.</given-names>
            </name>
            <name name-style="western">
              <surname>Padda</surname>
              <given-names>Harkirat K.</given-names>
            </name>
          </person-group>
          <year>2006</year>
          <article-title>Usability measurement and metrics: A consolidated model</article-title>
          <source>Software Quality Journal</source>
          <volume>14</volume>
          <issue>2</issue>
          <fpage>159</fpage>
          <lpage>178</lpage>
          <uri>http://link.springer.com/10.1007/s11219-006-7600-8</uri>
          <pub-id pub-id-type="doi">10.1007/s11219-006-7600-8</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281479">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Skinner</surname>
              <given-names>Katherine</given-names>
            </name>
            <name name-style="western">
              <surname>Wipperman</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Living Our Values and Principles: Exploring Assessment Strategies for the Scholarly Communication Field</article-title>
          <uri>https://educopia.org/wp-content/uploads/2024/09/20201105_NGLP_PrinciplesValues_FinalPublication.pdf</uri>
        </element-citation>
      </ref>
      <ref id="B13430206">
        <element-citation publication-type="chapter">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Souheimo</surname>
              <given-names>Mari</given-names>
            </name>
            <name name-style="western">
              <surname>Fidos</surname>
              <given-names>Michalina</given-names>
            </name>
            <name name-style="western">
              <surname>Kuronen</surname>
              <given-names>Marja</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Sheng-Hung</given-names>
            </name>
          </person-group>
          <year>2025</year>
          <chapter-title>Blending Boundaries: A thorough exploration of systems‑oriented design and service design integration</chapter-title>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Souheimo</surname>
              <given-names>Mari</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Sheng-Hung</given-names>
            </name>
            <name name-style="western">
              <surname>Sevaldson</surname>
              <given-names>Birger</given-names>
            </name>
          </person-group>
          <source>Systemic Service Design</source>
          <publisher-name>Routledge</publisher-name>
          <publisher-loc>New York</publisher-loc>
          <size units="page">17-40</size>
          <isbn>9781032817200</isbn>
          <pub-id pub-id-type="doi">10.4324/9781003501039-3</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281447">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>SPARC</surname>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>Good Practice Principles for Scholarly Communication Services</article-title>
          <uri>https://sparcopen.org/our-work/good-practice-principles-for-scholarly-communication-services/</uri>
        </element-citation>
      </ref>
      <ref id="B13280762">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Suraj</surname>
              <given-names>Varun</given-names>
            </name>
            <name name-style="western">
              <surname>Del Vecchio Fitz</surname>
              <given-names>Catherine</given-names>
            </name>
            <name name-style="western">
              <surname>Kleiman</surname>
              <given-names>Laura B</given-names>
            </name>
            <name name-style="western">
              <surname>Bhavnani</surname>
              <given-names>Suresh K</given-names>
            </name>
            <name name-style="western">
              <surname>Jani</surname>
              <given-names>Chinmay</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>Surbhi</given-names>
            </name>
            <name name-style="western">
              <surname>McKay</surname>
              <given-names>Rana R</given-names>
            </name>
            <name name-style="western">
              <surname>Warner</surname>
              <given-names>Jeremy</given-names>
            </name>
            <name name-style="western">
              <surname>Alterovitz</surname>
              <given-names>Gil</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>SMART COVID Navigator, a Clinical Decision Support Tool for COVID-19 Treatment: Design and Development Study</article-title>
          <source>Journal of Medical Internet Research</source>
          <volume>24</volume>
          <issue>2</issue>
          <uri>https://www.jmir.org/2022/2/e29279</uri>
          <pub-id pub-id-type="doi">10.2196/29279</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281423">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>UCOLASC</surname>
            </name>
          </person-group>
          <year>2018</year>
          <article-title>Declaration of Rights and Principles to Transform Scholarly Communication</article-title>
          <publisher-name>University of California</publisher-name>
          <uri>https://senate.universityofcalifornia.edu/_files/committees/ucolasc/scholcommprinciples-20180425.pdf</uri>
        </element-citation>
      </ref>
      <ref id="B13430137">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>UNESCO</surname>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Recommendation on Open Science</article-title>
          <publisher-name>UNESCO</publisher-name>
          <uri>https://www.unesco.org/en/open-science/about?hub=686</uri>
        </element-citation>
      </ref>
      <ref id="B13281233">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nations</surname>
              <given-names>United</given-names>
            </name>
          </person-group>
          <year>2015</year>
          <article-title>Transforming Our World: 2030 Agenda for Sustainable Development</article-title>
          <publisher-name>United Nations</publisher-name>
          <uri>https://sdgs.un.org/sites/default/files/publications/21252030%20Agenda%20for%20Sustainable%20Development%20web.pdf</uri>
        </element-citation>
      </ref>
      <ref id="B13430355">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vora</surname>
              <given-names>Priya</given-names>
            </name>
            <name name-style="western">
              <surname>Dolan</surname>
              <given-names>Jonathan</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>What is ‘good’ digital infrastructure?</article-title>
          <source>Brookings Global Working Paper</source>
          <volume>167</volume>
          <uri>https://www.brookings.edu/wp-content/uploads/2022/02/Good-Digital-Infrastructure.pdf</uri>
        </element-citation>
      </ref>
      <ref id="B13281633">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Whitney</surname>
              <given-names>Daniel E.</given-names>
            </name>
          </person-group>
          <year>1988</year>
          <article-title>Manufacturing by Design</article-title>
          <source>Harvard Business Review</source>
          <volume>66</volume>
          <issue>4</issue>
          <fpage>83</fpage>
          <lpage>91</lpage>
          <uri>https://hbr.org/1988/07/manufacturing-by-design</uri>
        </element-citation>
      </ref>
      <ref id="B13281693">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wilkinson</surname>
              <given-names>Mark D.</given-names>
            </name>
            <name name-style="western">
              <surname>Dumontier</surname>
              <given-names>Michel</given-names>
            </name>
            <name name-style="western">
              <surname>Jan Aalbersberg</surname>
              <given-names>Ijsbrand</given-names>
            </name>
            <name name-style="western">
              <surname>Appleton</surname>
              <given-names>Gabrielle</given-names>
            </name>
            <name name-style="western">
              <surname>Axton</surname>
              <given-names>Myles</given-names>
            </name>
            <name name-style="western">
              <surname>Baak</surname>
              <given-names>Arie</given-names>
            </name>
            <name name-style="western">
              <surname>Blomberg</surname>
              <given-names>Niklas</given-names>
            </name>
            <name name-style="western">
              <surname>Boiten</surname>
              <given-names>Jan-Willem</given-names>
            </name>
            <name name-style="western">
              <surname>Da Silva Santos</surname>
              <given-names>Luiz Bonino</given-names>
            </name>
            <name name-style="western">
              <surname>Bourne</surname>
              <given-names>Philip E.</given-names>
            </name>
            <name name-style="western">
              <surname>Bouwman</surname>
              <given-names>Jildau</given-names>
            </name>
            <name name-style="western">
              <surname>Brookes</surname>
              <given-names>Anthony J.</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>Tim</given-names>
            </name>
            <name name-style="western">
              <surname>Crosas</surname>
              <given-names>Mercè</given-names>
            </name>
            <name name-style="western">
              <surname>Dillo</surname>
              <given-names>Ingrid</given-names>
            </name>
            <name name-style="western">
              <surname>Dumon</surname>
              <given-names>Olivier</given-names>
            </name>
            <name name-style="western">
              <surname>Edmunds</surname>
              <given-names>Scott</given-names>
            </name>
            <name name-style="western">
              <surname>Evelo</surname>
              <given-names>Chris T.</given-names>
            </name>
            <name name-style="western">
              <surname>Finkers</surname>
              <given-names>Richard</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez-Beltran</surname>
              <given-names>Alejandra</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>Alasdair J. G.</given-names>
            </name>
            <name name-style="western">
              <surname>Groth</surname>
              <given-names>Paul</given-names>
            </name>
            <name name-style="western">
              <surname>Goble</surname>
              <given-names>Carole</given-names>
            </name>
            <name name-style="western">
              <surname>Grethe</surname>
              <given-names>Jeffrey S.</given-names>
            </name>
            <name name-style="western">
              <surname>Heringa</surname>
              <given-names>Jaap</given-names>
            </name>
            <name name-style="western">
              <surname>Hoen</surname>
              <given-names>Peter A. C. ’T</given-names>
            </name>
            <name name-style="western">
              <surname>Hooft</surname>
              <given-names>Rob</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>Tobias</given-names>
            </name>
            <name name-style="western">
              <surname>Kok</surname>
              <given-names>Ruben</given-names>
            </name>
            <name name-style="western">
              <surname>Kok</surname>
              <given-names>Joost</given-names>
            </name>
            <name name-style="western">
              <surname>Lusher</surname>
              <given-names>Scott J.</given-names>
            </name>
            <name name-style="western">
              <surname>Martone</surname>
              <given-names>Maryann E.</given-names>
            </name>
            <name name-style="western">
              <surname>Mons</surname>
              <given-names>Albert</given-names>
            </name>
            <name name-style="western">
              <surname>Packer</surname>
              <given-names>Abel L.</given-names>
            </name>
            <name name-style="western">
              <surname>Persson</surname>
              <given-names>Bengt</given-names>
            </name>
            <name name-style="western">
              <surname>Rocca-Serra</surname>
              <given-names>Philippe</given-names>
            </name>
            <name name-style="western">
              <surname>Roos</surname>
              <given-names>Marco</given-names>
            </name>
            <name name-style="western">
              <surname>Van Schaik</surname>
              <given-names>Rene</given-names>
            </name>
            <name name-style="western">
              <surname>Sansone</surname>
              <given-names>Susanna-Assunta</given-names>
            </name>
            <name name-style="western">
              <surname>Schultes</surname>
              <given-names>Erik</given-names>
            </name>
            <name name-style="western">
              <surname>Sengstag</surname>
              <given-names>Thierry</given-names>
            </name>
            <name name-style="western">
              <surname>Slater</surname>
              <given-names>Ted</given-names>
            </name>
            <name name-style="western">
              <surname>Strawn</surname>
              <given-names>George</given-names>
            </name>
            <name name-style="western">
              <surname>Swertz</surname>
              <given-names>Morris A.</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>Mark</given-names>
            </name>
            <name name-style="western">
              <surname>Van Der Lei</surname>
              <given-names>Johan</given-names>
            </name>
            <name name-style="western">
              <surname>Van Mulligen</surname>
              <given-names>Erik</given-names>
            </name>
            <name name-style="western">
              <surname>Velterop</surname>
              <given-names>Jan</given-names>
            </name>
            <name name-style="western">
              <surname>Waagmeester</surname>
              <given-names>Andra</given-names>
            </name>
            <name name-style="western">
              <surname>Wittenburg</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Wolstencroft</surname>
              <given-names>Katherine</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Jun</given-names>
            </name>
            <name name-style="western">
              <surname>Mons</surname>
              <given-names>Barend</given-names>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>The FAIR Guiding Principles for scientific data management and stewardship (Addendum)</article-title>
          <source>Scientific Data</source>
          <volume>6</volume>
          <issue>1</issue>
          <uri>https://www.nature.com/articles/s41597-019-0009-6</uri>
          <pub-id pub-id-type="doi">10.1038/s41597-019-0009-6</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281625">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Womack</surname>
              <given-names>James P.</given-names>
            </name>
          </person-group>
          <year>2007</year>
          <source>The Machine That Changed the World: The Story of Lean Production</source>
          <publisher-name>Free Press</publisher-name>
          <publisher-loc>New York</publisher-loc>
        </element-citation>
      </ref>
      <ref id="B13430272">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wynn</surname>
              <given-names>D. C.</given-names>
            </name>
            <name name-style="western">
              <surname>Eckert</surname>
              <given-names>C. M.</given-names>
            </name>
          </person-group>
          <year>2017</year>
          <article-title>Perspectives on iteration in design and development</article-title>
          <source>Researh in Engineering Design</source>
          <volume>28</volume>
          <fpage>153</fpage>
          <lpage>184</lpage>
          <pub-id pub-id-type="doi">10.1007/s00163-016-0226-3</pub-id>
        </element-citation>
      </ref>
      <ref id="B13281175">
        <element-citation publication-type="chapter">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zoeller</surname>
              <given-names>Georg</given-names>
            </name>
          </person-group>
          <year>2013</year>
          <chapter-title>Game Development Telemetry in Production</chapter-title>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Seif El-Nasr</surname>
              <given-names>M.</given-names>
            </name>
            <name name-style="western">
              <surname>Drachen</surname>
              <given-names>A.</given-names>
            </name>
            <name name-style="western">
              <surname>Canossa</surname>
              <given-names>A.</given-names>
            </name>
          </person-group>
          <source>Game Analytics</source>
          <publisher-name>Springer</publisher-name>
          <publisher-loc>London</publisher-loc>
          <uri>https://link.springer.com/10.1007/978-1-4471-4769-5_7</uri>
          <isbn>978-1-4471-4768-8 978-1-4471-4769-5</isbn>
          <pub-id pub-id-type="doi">10.1007/978-1-4471-4769-5_7</pub-id>
        </element-citation>
      </ref>
    </ref-list>
  </back>
  <floats-group>
    <fig id="F13430244" position="float" orientation="portrait">
      <object-id content-type="arpha">619B0573-4899-5EF9-A793-0BF0DCAAE845</object-id>
      <object-id content-type="doi">10.3897/rio.11.e163817.figure2</object-id>
      <label>Figure 1.</label>
      <caption>
        <p>The socio-economic framework of open science.</p>
      </caption>
      <graphic xlink:href="rio-11-e163817-g001.jpg" position="float" id="oo_1393562.jpg" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1393562</uri>
      </graphic>
    </fig>
    <fig id="F13430270" position="float" orientation="portrait">
      <object-id content-type="arpha">860E9337-2E89-5358-904D-9FF871143394</object-id>
      <object-id content-type="doi">10.3897/rio.11.e163817.figure2</object-id>
      <label>Figure 2.</label>
      <caption>
        <p>Systems Service Design: Mapping stakeholders and user needs.</p>
      </caption>
      <graphic xlink:href="rio-11-e163817-g002.jpg" position="float" id="oo_1393565.jpg" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1393565</uri>
      </graphic>
    </fig>
    <fig id="F13430367" position="float" orientation="portrait">
      <object-id content-type="arpha">B90D5276-BF92-594F-BC98-77911CD859D3</object-id>
      <object-id content-type="doi">10.3897/rio.11.e163817.figure1</object-id>
      <label>Figure 3.</label>
      <caption>
        <p>Open by Design evaluation framework.</p>
      </caption>
      <graphic xlink:href="rio-11-e163817-g003.jpg" position="float" id="oo_1393573.jpg" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1393573</uri>
      </graphic>
    </fig>
    <table-wrap id="T13234894" position="float" orientation="portrait">
      <label>Table 1.</label>
      <caption>
        <p>Open infrastructure principle frameworks: audiences and assessment features.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Framework</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Target audience</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Assessment</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Content</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">POSI</td>
            <td rowspan="1" colspan="1">Scholarly infrastructure organizations, geared toward leadership</td>
            <td rowspan="1" colspan="1">Self-audit of practices.<break/>Self-reporting. Non-exclusionary, open to different business types</td>
            <td rowspan="1" colspan="1">Governance, Sustainability, and Insurance</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">FAIR</td>
            <td rowspan="1" colspan="1">Data and machine actionability; geared towards researchers and analysts/curators working with data</td>
            <td rowspan="1" colspan="1">Self-audit of machine readability.<break/>Self or community reported; GOFAIR implementation networks</td>
            <td rowspan="1" colspan="1">Findability, Accessibility, Interoperability, Reusability</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">CARE</td>
            <td rowspan="1" colspan="1">Data collectors and curators; geared toward communities, researchers and analysts/curators working with Indigenous data</td>
            <td rowspan="1" colspan="1">Self-audit of data ethics; consultation with Indigenous communities; labels and notices to indicate compliance</td>
            <td rowspan="1" colspan="1">Collective Benefit Authority to Control Responsibility Ethics</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">FOREST</td>
            <td rowspan="1" colspan="1">Scholarly communications organizations, publishers, libraries, archives; geared towards leadership and staff and towards those adopting open tools or open infrastructures</td>
            <td rowspan="1" colspan="1">Self-audit of organizational practices; Adopter community audit of organizational practices</td>
            <td rowspan="1" colspan="1">Financial and Organizational Sustainability Openness Representative Governance Equity, Accessibility, and Anti-Oppression Sharing of Knowledge Transparency</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13234895" position="float" orientation="portrait">
      <label>Table 2.</label>
      <caption>
        <p>Design thinking criteria applied to open research infrastructures.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Technical</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Design Questions</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Behavioral</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Design Questions</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Modular architecture</td>
            <td rowspan="1" colspan="1"><italic>What standard (open) tools are you using</italic>?</td>
            <td rowspan="1" colspan="1">Cross-disciplinary or locational collaboration</td>
            <td rowspan="1" colspan="1"><italic>How does your product support collaboration? Data sharing? Integration</italic>?</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Standardized interfaces</td>
            <td rowspan="1" colspan="1"><italic>What standards, schema, persistent identifiers are you using</italic>?</td>
            <td rowspan="1" colspan="1">Stakeholder engagement</td>
            <td rowspan="1" colspan="1"><italic>What pain or gain does the infrastructure solve or support? Who is/are the direct beneficiaries? What is the strategy for collecting community feedback to ensure the infrastructure is and continues to solve this problem</italic>?</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Sustainability</td>
            <td rowspan="1" colspan="1"><italic>How will your product be supported over time, both in terms of user support and financial support</italic>?</td>
            <td rowspan="1" colspan="1">Strategy development</td>
            <td rowspan="1" colspan="1"><italic>What is your key innovation(s) or differentiator that enables the product to solve the pain/gain? How does the infrastructure enable cooperation with other products and services in research workflows? How are you engaging stakeholders in strategy development and decisions? How do you ensure longevity for your product</italic>?</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Operational effectiveness</td>
            <td rowspan="1" colspan="1"><italic>What are your terms and conditions of use? How are you ensuring reliable service? What policies and practices are in place to ensure ethical data collection, management, and sharing</italic>?</td>
            <td rowspan="1" colspan="1">Transparency in knowledge dissemination</td>
            <td rowspan="1" colspan="1"><italic>Who are your stakeholders? What are your product evaluation criteria? How are you collecting data to support evaluation of infrastrucure effectiveness and impact for your stakeholders? How are you ensuring that core data are accessible over time</italic>?</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13234896" position="float" orientation="portrait">
      <label>Table 3.</label>
      <caption>
        <p>Infrastructure “Open by Design” product features aligned with SDG 9, FAIR, CARE, POSI, and FOREST principles.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="6">Sustainable Development Goal 9: Build resilient infrastructure, promote inclusive and sustainable industrialisation, and foster innovation. Aligns with OECD RI Core Impact Indicators: Technical Impact and Economic Impact.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Open By Design</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Feature/ Function</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>FAIR</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>CARE</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>POSI</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>FOREST</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Modular Architecture (T)</td>
            <td rowspan="1" colspan="1">Extract- Transform- Load Processes</td>
            <td rowspan="1" colspan="1">Interoperable</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Openness (O2)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Modular Architecture (T)</td>
            <td rowspan="1" colspan="1">Data De- Identification</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Responsibility</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Transparency (T4)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Modular Architecture (T)</td>
            <td rowspan="1" colspan="1">Standard Data Aggregation</td>
            <td rowspan="1" colspan="1">Interoperable</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Sharing of Knowledge (S3)<break/>Transparency (T4)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Modular Architecture (T)</td>
            <td rowspan="1" colspan="1">(Secure) Data Warehouse</td>
            <td rowspan="1" colspan="1">Accessible</td>
            <td rowspan="1" colspan="1">Authority to Control</td>
            <td rowspan="1" colspan="1">Insurance</td>
            <td rowspan="1" colspan="1">Transparency (T4)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Standardized interfaces (T)</td>
            <td rowspan="1" colspan="1">API</td>
            <td rowspan="1" colspan="1">Accessible, Interoperable</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Openness (O2)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Standardized interfaces (T)</td>
            <td rowspan="1" colspan="1">Web and Data Access Protocols</td>
            <td rowspan="1" colspan="1">Accessible</td>
            <td rowspan="1" colspan="1">Responsibility</td>
            <td rowspan="1" colspan="1">Insurance</td>
            <td rowspan="1" colspan="1">Openness (O4)<break/>Equity (E4)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Standardized interfaces (T)</td>
            <td rowspan="1" colspan="1">User Interface</td>
            <td rowspan="1" colspan="1">Accessible</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Equity (E4)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Sustainability (T)</td>
            <td rowspan="1" colspan="1">Business Structure, Business Model</td>
            <td rowspan="1" colspan="1">Accessible</td>
            <td rowspan="1" colspan="1">Ethics</td>
            <td rowspan="1" colspan="1">Sustainability</td>
            <td rowspan="1" colspan="1">Financial and Organizational Resilience (F3)<break/>Transparency (T3)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Operational Effectiveness (T)</td>
            <td rowspan="1" colspan="1">Leadership and Ownership Succession Policies, Team Handbook</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Responsibility</td>
            <td rowspan="1" colspan="1">Governance</td>
            <td rowspan="1" colspan="1">Financial and Organizational Resilience (F4)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Operational Effectiveness (T)</td>
            <td rowspan="1" colspan="1">Operational Policies and Practices</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Financial and Organizational Resilience (F2)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Operational Effectiveness (T)</td>
            <td rowspan="1" colspan="1">Personnel Policies (Governance, Team, Participants)</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Equity (E1-E3)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Transparency in Knowledge Sharing (B)</td>
            <td rowspan="1" colspan="1">Open Source Protocols, Code, Tools</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Insurance</td>
            <td rowspan="1" colspan="1">Openness (O1)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Transparency in Knowledge Sharing (B)</td>
            <td rowspan="1" colspan="1">Data Dictionary, Data Model</td>
            <td rowspan="1" colspan="1">Accessible, Interoperable</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Openness (O2)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Transparency in Knowledge Sharing (B)</td>
            <td rowspan="1" colspan="1">Data Governance</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Responsibility</td>
            <td rowspan="1" colspan="1">Governance</td>
            <td rowspan="1" colspan="1">Openness (O4)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Transparency in Knowledge Sharing (B)</td>
            <td rowspan="1" colspan="1">Licensing, Consent, Privacy</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Consent, Authority to Control, Responsibility, Ethics</td>
            <td rowspan="1" colspan="1">Insurance</td>
            <td rowspan="1" colspan="1">Openness (O3)<break/>Transparency (T4)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Transparency in Knowledge Sharing (B)</td>
            <td rowspan="1" colspan="1">Communication Policies and Practices</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Transparency (T2)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Stakeholder Engagement (B)<break/>Strategy Development (B)</td>
            <td rowspan="1" colspan="1">Stakeholder- Engaged Infrastructure Governance</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Responsibility</td>
            <td rowspan="1" colspan="1">Governance</td>
            <td rowspan="1" colspan="1">Financial and Organizational Resilience (F1)<break/>Responsible Governance (R1-4)<break/>Transparency (T1)</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13234897" position="float" orientation="portrait">
      <label>Table 4.</label>
      <caption>
        <p>Infrastructure “Open by Design” product features aligned with SDG 4, FAIR, and CARE, and POSI.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="6">Sustainable Development Goal 4: Ensure inclusive and equitable quality education and promote lifelong learning opportunities for all. Aligns with OECD RI Core Impact Indicators: Training and Education Impact.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Open by Design</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Feature/ Function</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>FAIR</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>CARE</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>POSI</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>FOREST</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Cross- Disciplinary Collaboration (B)</td>
            <td rowspan="1" colspan="1">File Download</td>
            <td rowspan="1" colspan="1">Reusable</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Sharing of Knowledge (S3)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Stakeholder Engagement (B)</td>
            <td rowspan="1" colspan="1">Outreach Events</td>
            <td rowspan="1" colspan="1">Accessible, Reuseable</td>
            <td rowspan="1" colspan="1">Responsibility</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Sharing of Knowledge (S1)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Stakeholder Engagement (B)</td>
            <td rowspan="1" colspan="1">Help Desk, Curation Service</td>
            <td rowspan="1" colspan="1">Accessible</td>
            <td rowspan="1" colspan="1">Responsibility</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Sharing of Knowledge (S2)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Transparency in Knowledge Sharing (B)</td>
            <td rowspan="1" colspan="1">Open Source Data Model</td>
            <td rowspan="1" colspan="1">Interoperable, Reusable</td>
            <td rowspan="1" colspan="1">Responsibility</td>
            <td rowspan="1" colspan="1">Insurance</td>
            <td rowspan="1" colspan="1">Sharing of Knowledge (S3)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Transparency in Knowledge Sharing (B)</td>
            <td rowspan="1" colspan="1">Open Source Tools and Training</td>
            <td rowspan="1" colspan="1">Interoperable, Reusable</td>
            <td rowspan="1" colspan="1">Ethics</td>
            <td rowspan="1" colspan="1">Insurance</td>
            <td rowspan="1" colspan="1">Sharing of Knowledge (S3)</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13234898" position="float" orientation="portrait">
      <label>Table 5.</label>
      <caption>
        <p>Infrastructure “Open by Design” product features aligned with People &amp; Planet, FAIR, CARE, POSI, and FOREST.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="6">People and Planet: Select SDG(s) that aligns with infrastructure purpose and audience. Aligns with OECD RI Core Impact Indicators: Scientific Impact and Social and Societal Impact.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Open by Design</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Feature/ Function</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>FAIR</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>CARE</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>POSI</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>FOREST</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Modular Architecture (T)</td>
            <td rowspan="1" colspan="1">PIDs for datasets, code, workflows, etc.</td>
            <td rowspan="1" colspan="1">Findable, Reusable</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Insurance</td>
            <td rowspan="1" colspan="1">Sharing of Knowledge (S1)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Modular Architecture (T)</td>
            <td rowspan="1" colspan="1">PIDs for people, organizations, communities, funding</td>
            <td rowspan="1" colspan="1">Findable, Reusable</td>
            <td rowspan="1" colspan="1">Authority to Control</td>
            <td rowspan="1" colspan="1">Insurance</td>
            <td rowspan="1" colspan="1">Sharing of Knowledge (S1)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Modular Architecture (T)</td>
            <td rowspan="1" colspan="1">Data Linkages</td>
            <td rowspan="1" colspan="1">Findable, Accessible, Interoperable</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Sharing of Knowledge (S3)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Standardized Interfaces (T)<break/>Cross- Disciplinary Collaboration (B)</td>
            <td rowspan="1" colspan="1">(Secure) Modelling Workspace, Research Layer</td>
            <td rowspan="1" colspan="1">Reuseable</td>
            <td rowspan="1" colspan="1">Responsible</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Equity (E4)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Standardized Interfaces (T)<break/>Cross- Disciplinary Collaboration (B)</td>
            <td rowspan="1" colspan="1">Visualisation Tools</td>
            <td rowspan="1" colspan="1">Reusable</td>
            <td rowspan="1" colspan="1">Responsible</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Equity (E4)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Standardized Interfaces (T)<break/>Cross- Disciplinary Collaboration (B)</td>
            <td rowspan="1" colspan="1">Data Integrated into External Portals</td>
            <td rowspan="1" colspan="1">Findable, Accessible, Interoperable, Reusable</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Insurance</td>
            <td rowspan="1" colspan="1">Sharing of Knowledge (S3)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Standardized Interfaces (T)<break/>Strategy Development (B)</td>
            <td rowspan="1" colspan="1">Indicators and Trends</td>
            <td rowspan="1" colspan="1">Reusable</td>
            <td rowspan="1" colspan="1">Responsible</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Transparency (T1)</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Transparency in Knowledge Sharing (B)</td>
            <td rowspan="1" colspan="1">Discovery Catalogue, Inventory</td>
            <td rowspan="1" colspan="1">Findable</td>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1"/>
            <td rowspan="1" colspan="1">Sharing of Knowledge (S3)</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13234900" position="float" orientation="portrait">
      <label>Table 6.</label>
      <caption>
        <p>Impact drivers, measures, and PID strategies for the Infrastructure Impact Area. Font Key: Narrative, <italic>Quantitative</italic>, <underline>User Engagement</underline>.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="4">
              <bold>SDG 9: Infrastructure</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Are infrastructure data being curated using data models</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Do we see broader adoption of infrastructure data models and/or governance protocols</bold>
            </td>
            <td rowspan="1" colspan="1"><bold>Is the data governance framework maintained</bold>?</td>
            <td rowspan="1" colspan="1"><bold>Are users able to access the data or metadata</bold>?</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"># <italic>new infrastructure datasets curated using infrastructure data model / Total # new infrastructure datasets (Backlog)</italic><break/><italic>Requests to infrastructure team for curation assistance and/or Availability of curation assistance</italic><break/><italic>Workshops for engaging community in discussion on standards</italic><break/>Data sharing standards, principles and documentation available on infrastructure websites and/or Federation service</td>
            <td rowspan="1" colspan="1">Data sources providing data aligned with data model vs. infrastructure creating a layer from non-homogeneous data<break/>Are related e-infrastructures adopting the data model used by the infrastructure (including international standards)<break/>Infrastructure team participation in (inter)national data sharing methodologies and standards<break/>Open data endpoints for sharing infrastructure data between e-infrastructures</td>
            <td rowspan="1" colspan="1"># <italic>endpoint harvest enhancements | endpoint enhancements up-to-date with data model</italic><break/>Infrastructure Webpage with information on governance group members and activities, updated annually<break/>Update processes for data models and metadata in place<break/>Participation/Contribution to international data standards working group (Advisory Committee) for maintaining metadata standards<break/>Active outreach by infrastructure team to encourage adoption and gather feedback</td>
            <td rowspan="1" colspan="1"># <italic>users able to access data / total # requests</italic><break/># <italic>HelpDesk requests / total # data requests</italic><break/># <italic>of data access requests per dataset: change over time, total and median</italic><break/>User survey to determine user type, field / sector<break/># infrastructure team points of contact, turnover</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>Increased understanding of data access needs drives data collection design</italic>
              </bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>(Inter)national guidance on FAIR-CARE sharing enhances data interoperability</italic>
              </bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>Active maintenance of metadata standard supports community trust and adoption</italic>
              </bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>Infrastructure data sharing leads to improvements in data access processes for the infrastructure and adjacent research communities</italic>
              </bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>PID Strategy</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="3">
              <list list-type="order">
                <list-item>
                  <p>Integrate authenticated ORCID collection into account creation / sign-in</p>
                </list-item>
                <list-item>
                  <p>Include PIDs in metadata model</p>
                </list-item>
                <list-item>
                  <p>Use DOIs or ARKs for component datasets and vocabularies when possible</p>
                </list-item>
                <list-item>
                  <p>Citation advice on infrastructure landing page and in user documentation for how to cite infrastructure derived-data using PIDs.</p>
                </list-item>
              </list>
            </td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13234901" position="float" orientation="portrait">
      <label>Table 7.</label>
      <caption>
        <p>Impact drivers and measures for the Education Impact Area. Font Key: Narrative, <italic>Quantitative</italic>, <underline>User Engagement</underline>.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="3">
              <bold>SDG 4: Education</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>Are educational materials provided by the infrastructure or its Federation service</bold>?</td>
            <td rowspan="1" colspan="1"><bold>Is training provided by the infrastructure or its Federation service</bold>?</td>
            <td rowspan="1" colspan="1"><bold>Is open source code available via the infrastructure or its Federation service</bold>?</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">Curation documentation available on infrastructure host and/or Federation service websites<break/>Metadata schema openly available on infrastructure host and/or Federation service websites<break/>Citation guidance available on infrastructure websites and/or Federation service websites<break/>User survey: field / sector info</td>
            <td rowspan="1" colspan="1"><italic>Availability of training (via infrastructure host or Federation service)</italic><break/><italic>Completed training modules / # registered users (via infrastructure host or Federation service)</italic><break/>Workshops/ Number of registered users (via infrastructure host or Federation service)<break/>Participant survey: field / sector info</td>
            <td rowspan="1" colspan="1"><italic>Accesses and/or contributions and/or code forks to the open source code repository</italic>? <break/>Is there an open source repository (data model, API, analysis code, etc.)?<break/>Codefests or hackathons / Participants / Number of accesses to the code base<break/>Participant survey: field / sector info</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>Materials increase understanding and use of infrastructure resources</italic>
              </bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>Training increases data sharing and reuse activities</italic>
              </bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>Training increases data sharing and reuse activities</italic>
              </bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>PID Strategy</italic>
              </bold>
            </td>
            <td rowspan="1" colspan="2">
              <list list-type="order">
                <list-item>
                  <p>Integration of PIDs into project educational activities and resources (training materials, source code, etc.)</p>
                </list-item>
                <list-item>
                  <p>Project documentation includes citation advice (e.g., how to cite using PIDs)</p>
                </list-item>
              </list>
            </td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13234902" position="float" orientation="portrait">
      <label>Table 8.</label>
      <caption>
        <p>Impact drivers and measures for the People &amp; Planet Impact Area. Font Key: Narrative, <italic>Quantitative</italic>, <underline>User Engagement</underline>.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="3">
              <bold>People &amp; Planet</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>Are infrastructure data findable</bold>?</td>
            <td rowspan="1" colspan="1"><bold>Does the infrastructure have users</bold>?</td>
            <td rowspan="1" colspan="1"><bold>Is there new research based on infrastructure resources</bold>?</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"># <italic>of infrastructure DOIs (or accession numbers) cited / infrastructure DOIs accessed.</italic><break/># <italic>of infrastructure datasets with DOI / total infrastructure datasets</italic><break/># <italic>of infrastructure datasets embedding PIDs for data, people, organisation, funding / total number of infrastructure datasets</italic><break/>Are data contributions attributed and acknowledged?<break/>Use of search tools - which keywords, datasets, user sector</td>
            <td rowspan="1" colspan="1"># <italic>infrastructure data PID resolutions / # infrastructure repository accesses</italic><break/>Use of analytics tools - which tools, what questions, which users<break/>Community engagement activities (Number, topics, participation)<break/>User survey to determine user type, field / sector. Do users map onto expected beneficiaries?<break/>Commencement and completion survey for users of platform(s)</td>
            <td rowspan="1" colspan="1"><italic>infrastructure PID citations: total, timeseries, topics</italic><break/><italic>Citation (PID) of an infrastructure or infrastructure dataset in an article, report, grant, patent application or policy guideline</italic><break/>Analysis code citing infrastructure data (PID)<break/><italic>Data Management Plans (DMPs) citing infrastructure (PID) / total machine readable DMPs (PIDs). Interim metric: Letters of Support for grant writers</italic>.<break/>Are users able to use (or create new) indicator tools and summaries?</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>Attribution of infrastructure data drives data sharing</italic>
              </bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>Improved accessibility of infrastructure data drives community interest</italic>
              </bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>Improved accessibility of infrastructure data drives community trust in shared data</italic>
              </bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>
                <italic>PID Strategy</italic>
              </bold>
            </td>
            <td rowspan="1" colspan="2">
              <list list-type="order">
                <list-item>
                  <p>Implementation of <ext-link ext-link-type="uri" xlink:href="https://doi.datacite.org/">Fabrica</ext-link>, DataCite Commons queries, COUNTER, or similar tool to track citation of infrastructure PIDs or hits/downloads of resources</p>
                </list-item>
              </list>
            </td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
  </floats-group>
</article>
