<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//TaxonX//DTD Taxonomic Treatment Publishing DTD v0 20100105//EN" "../../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.e177037</article-id>
      <article-id pub-id-type="publisher-id">177037</article-id>
      <article-id pub-id-type="manuscript">29067</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Grant Proposal</subject>
        </subj-group>
        <subj-group subj-group-type="scientific_subject">
          <subject>Biochemistry</subject>
          <subject>Chemistry</subject>
          <subject>Computer architecture</subject>
          <subject>Databases</subject>
          <subject>Materials science</subject>
          <subject>Open access publishing</subject>
          <subject>Software sustainability</subject>
        </subj-group>
        <subj-group subj-group-type="sdg">
          <subject>Industry</subject>
          <subject> innovation &amp; infrastructure</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Proposal NFDI4Chem 2025-2030 In the National Research Data Infrastructure (NFDI) — Our Vision: All Chemists Publish FAIR Data</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Steinbeck</surname>
            <given-names>Christoph</given-names>
          </name>
          <email xlink:type="simple">christoph.steinbeck@uni-jena.de</email>
          <uri content-type="orcid">https://orcid.org/0000-0001-6966-0814</uri>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Jung</surname>
            <given-names>Nicole</given-names>
          </name>
          <email xlink:type="simple">nicole.jung@kit.edu</email>
          <uri content-type="orcid">https://orcid.org/0000-0001-9513-2468</uri>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Bach</surname>
            <given-names>Felix</given-names>
          </name>
          <email xlink:type="simple">Felix.Bach@fiz-karlsruhe.de</email>
          <uri content-type="orcid">https://orcid.org/0000-0002-5035-7978</uri>
          <xref ref-type="aff" rid="A3">3</xref>
        </contrib>
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Neumann</surname>
            <given-names>Steffen</given-names>
          </name>
          <email xlink:type="simple">sneumann@ipb-halle.de</email>
          <uri content-type="orcid">https://orcid.org/0000-0002-7899-7192</uri>
          <xref ref-type="aff" rid="A4">4</xref>
        </contrib>
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Herres-Pawlis</surname>
            <given-names>Sonja</given-names>
          </name>
          <email xlink:type="simple">sonja.herres-pawlis@ac.rwth-aachen.de</email>
          <uri content-type="orcid">https://orcid.org/0000-0002-4354-4353</uri>
          <xref ref-type="aff" rid="A5">5</xref>
        </contrib>
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Liermann</surname>
            <given-names>Johannes C.</given-names>
          </name>
          <email xlink:type="simple">liermann@uni-mainz.de</email>
          <uri content-type="orcid">https://orcid.org/0000-0003-2060-842X</uri>
          <xref ref-type="aff" rid="A6">6</xref>
        </contrib>
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Koepler</surname>
            <given-names>Oliver</given-names>
          </name>
          <email xlink:type="simple">oliver.koepler@tib.eu</email>
          <uri content-type="orcid">https://orcid.org/0000-0003-3385-4232</uri>
          <xref ref-type="aff" rid="A7">7</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Bannwarth</surname>
            <given-names>Christoph</given-names>
          </name>
          <xref ref-type="aff" rid="A5">5</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Bender</surname>
            <given-names>Theo</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0009-0004-4064-6065</uri>
          <xref ref-type="aff" rid="A6">6</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Bocklitz</surname>
            <given-names>Thomas W.</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-2778-6624</uri>
          <xref ref-type="aff" rid="A8">8</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Boehm</surname>
            <given-names>Franziska</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-3785-7828</uri>
          <xref ref-type="aff" rid="A3">3</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Bonatto Minella</surname>
            <given-names>Christian</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0001-7696-7662</uri>
          <xref ref-type="aff" rid="A3">3</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Biedermann</surname>
            <given-names>Frank</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-1077-6529</uri>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Brack</surname>
            <given-names>Werner</given-names>
          </name>
          <xref ref-type="aff" rid="A9">9</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Cunha</surname>
            <given-names>Ricardo</given-names>
          </name>
          <xref ref-type="aff" rid="A10">10</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Czodrowski</surname>
            <given-names>Paul</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-9468-3687</uri>
          <xref ref-type="aff" rid="A6">6</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Eberl</surname>
            <given-names>Franziska</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Engel</surname>
            <given-names>Thomas</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-9468-3687</uri>
          <xref ref-type="aff" rid="A11">11</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Engstfeld</surname>
            <given-names>Albert K.</given-names>
          </name>
          <xref ref-type="aff" rid="A12">12</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Fischer</surname>
            <given-names>Tillmann G.</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-4480-8661</uri>
          <xref ref-type="aff" rid="A13">13</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Friedrich</surname>
            <given-names>Pascal</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Glorious</surname>
            <given-names>Frank</given-names>
          </name>
          <xref ref-type="aff" rid="A14">14</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Golub</surname>
            <given-names>Benjamin</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-4374-909X</uri>
          <xref ref-type="aff" rid="A15">15</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Grathwol</surname>
            <given-names>Christoph</given-names>
          </name>
          <xref ref-type="aff" rid="A16">16</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Haag</surname>
            <given-names>Rainer</given-names>
          </name>
          <xref ref-type="aff" rid="A17">17</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Hunold</surname>
            <given-names>Johannes</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-4378-6061</uri>
          <xref ref-type="aff" rid="A7">7</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Jacob</surname>
            <given-names>Christoph R.</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-6227-8476</uri>
          <xref ref-type="aff" rid="A15">15</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Johannsen</surname>
            <given-names>Jochen</given-names>
          </name>
          <xref ref-type="aff" rid="A5">5</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Jollife</surname>
            <given-names>John D.</given-names>
          </name>
          <xref ref-type="aff" rid="A6">6</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Kast</surname>
            <given-names>Stefan M.</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0001-7346-7064</uri>
          <xref ref-type="aff" rid="A18">18</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Kettner</surname>
            <given-names>Carsten</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-8697-6842</uri>
          <xref ref-type="aff" rid="A19">19</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Kuhn</surname>
            <given-names>Stefan</given-names>
          </name>
          <xref ref-type="aff" rid="A20">20</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Lanza</surname>
            <given-names>Giacomo</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-2239-3955</uri>
          <xref ref-type="aff" rid="A21">21</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Lisec</surname>
            <given-names>Jan</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-1220-2286</uri>
          <xref ref-type="aff" rid="A22">22</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Manolikakes</surname>
            <given-names>Georg</given-names>
          </name>
          <xref ref-type="aff" rid="A23">23</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Mata</surname>
            <given-names>Ricardo A.</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-2720-3364</uri>
          <xref ref-type="aff" rid="A24">24</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Meiler</surname>
            <given-names>Jens</given-names>
          </name>
          <xref ref-type="aff" rid="A13">13</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Müller</surname>
            <given-names>Matthias</given-names>
          </name>
          <xref ref-type="aff" rid="A5">5</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Müller-Pfefferkorn</surname>
            <given-names>Ralph</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0001-8719-5741</uri>
          <xref ref-type="aff" rid="A25">25</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Ortmeyer</surname>
            <given-names>Jochen</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-2074-8027</uri>
          <xref ref-type="aff" rid="A5">5</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Patterson</surname>
            <given-names>Wendy</given-names>
          </name>
          <xref ref-type="aff" rid="A19">19</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Pleiss</surname>
            <given-names>Jürgen</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-1045-8202</uri>
          <xref ref-type="aff" rid="A26">26</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Riedel</surname>
            <given-names>Annalisa</given-names>
          </name>
          <xref ref-type="aff" rid="A6">6</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Riedel</surname>
            <given-names>Jens</given-names>
          </name>
          <xref ref-type="aff" rid="A22">22</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Schatzschneider</surname>
            <given-names>Ulrich</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-1960-1880</uri>
          <xref ref-type="aff" rid="A27">27</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Schuster</surname>
            <given-names>Leonie</given-names>
          </name>
          <xref ref-type="aff" rid="A7">7</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Seeberger</surname>
            <given-names>Peter</given-names>
          </name>
          <xref ref-type="aff" rid="A28">28</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Seibert</surname>
            <given-names>Johann-Nikolaus</given-names>
          </name>
          <xref ref-type="aff" rid="A23">23</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Stadler</surname>
            <given-names>Peter F.</given-names>
          </name>
          <xref ref-type="aff" rid="A13">13</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Strömert</surname>
            <given-names>Philip</given-names>
          </name>
          <xref ref-type="aff" rid="A7">7</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Strötgen</surname>
            <given-names>Robert</given-names>
          </name>
          <xref ref-type="aff" rid="A15">15</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Théato</surname>
            <given-names>Patrick</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-4562-9254</uri>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Tielker</surname>
            <given-names>Nicolas</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-0974-8739</uri>
          <xref ref-type="aff" rid="A18">18</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Tremouilhac</surname>
            <given-names>Pierre</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Weinig</surname>
            <given-names>Hans-Georg</given-names>
          </name>
          <xref ref-type="aff" rid="A29">29</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Wenzel</surname>
            <given-names>Wolfgang</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0001-9487-4689</uri>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Zeitler</surname>
            <given-names>Kirsten</given-names>
          </name>
          <xref ref-type="aff" rid="A13">13</xref>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">Friedrich Schiller University, Jena, Germany</addr-line>
        <institution>Friedrich Schiller University</institution>
        <addr-line content-type="city">Jena</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A2">
        <label>2</label>
        <addr-line content-type="verbatim">Karlsruhe Institute of Technology, Karlsruhe, Germany</addr-line>
        <institution>Karlsruhe Institute of Technology</institution>
        <addr-line content-type="city">Karlsruhe</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A3">
        <label>3</label>
        <addr-line content-type="verbatim">FIZ Karlsruhe – Leibniz Institute for Information Infrastructure, Eggenstein-Leopoldshafen, Germany</addr-line>
        <institution>FIZ Karlsruhe – Leibniz Institute for Information Infrastructure</institution>
        <addr-line content-type="city">Eggenstein-Leopoldshafen</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A4">
        <label>4</label>
        <addr-line content-type="verbatim">Leibniz Institute of Plant Biochemistry, Halle (Saale), Germany</addr-line>
        <institution>Leibniz Institute of Plant Biochemistry</institution>
        <addr-line content-type="city">Halle (Saale)</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A5">
        <label>5</label>
        <addr-line content-type="verbatim">RWTH Aachen University, Aachen, Germany</addr-line>
        <institution>RWTH Aachen University</institution>
        <addr-line content-type="city">Aachen</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A6">
        <label>6</label>
        <addr-line content-type="verbatim">Johannes Gutenberg University Mainz, Mainz, Germany</addr-line>
        <institution>Johannes Gutenberg University Mainz</institution>
        <addr-line content-type="city">Mainz</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A7">
        <label>7</label>
        <addr-line content-type="verbatim">TIB Leibniz Information Centre for Science and Technology, Hannover, Germany</addr-line>
        <institution>TIB Leibniz Information Centre for Science and Technology</institution>
        <addr-line content-type="city">Hannover</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A8">
        <label>8</label>
        <addr-line content-type="verbatim">Leibniz Institute of Photonic Technology e.V., Jena, Germany</addr-line>
        <institution>Leibniz Institute of Photonic Technology e.V.</institution>
        <addr-line content-type="city">Jena</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A9">
        <label>9</label>
        <addr-line content-type="verbatim">Helmholtz Centre for Environmental Research - UFZ, Leipzig, Germany</addr-line>
        <institution>Helmholtz Centre for Environmental Research - UFZ</institution>
        <addr-line content-type="city">Leipzig</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A10">
        <label>10</label>
        <addr-line content-type="verbatim">Institut für Umwelt &amp; Energie, Technik &amp; Analytik e.V. (IUTA), Duisburg, Germany</addr-line>
        <institution>Institut für Umwelt &amp; Energie, Technik &amp; Analytik e.V. (IUTA)</institution>
        <addr-line content-type="city">Duisburg</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A11">
        <label>11</label>
        <addr-line content-type="verbatim">Ludwig-Maximilians-Universität München, Munich, Germany</addr-line>
        <institution>Ludwig-Maximilians-Universität München</institution>
        <addr-line content-type="city">Munich</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A12">
        <label>12</label>
        <addr-line content-type="verbatim">Ulm University, Ulm, Germany</addr-line>
        <institution>Ulm University</institution>
        <addr-line content-type="city">Ulm</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A13">
        <label>13</label>
        <addr-line content-type="verbatim">Leipzig University, Leipzig, Germany</addr-line>
        <institution>Leipzig University</institution>
        <addr-line content-type="city">Leipzig</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A14">
        <label>14</label>
        <addr-line content-type="verbatim">University of Münster, Münster, Germany</addr-line>
        <institution>University of Münster</institution>
        <addr-line content-type="city">Münster</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A15">
        <label>15</label>
        <addr-line content-type="verbatim">Technische Universität Braunschweig, Braunschweig, Germany</addr-line>
        <institution>Technische Universität Braunschweig</institution>
        <addr-line content-type="city">Braunschweig</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A16">
        <label>16</label>
        <addr-line content-type="verbatim">Deutsche Pharmazeutische Gesellschaft e.V., Frankfurt am Main, Germany</addr-line>
        <institution>Deutsche Pharmazeutische Gesellschaft e.V.</institution>
        <addr-line content-type="city">Frankfurt am Main</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A17">
        <label>17</label>
        <addr-line content-type="verbatim">Freie Universität Berlin, Berlin, Germany</addr-line>
        <institution>Freie Universität Berlin</institution>
        <addr-line content-type="city">Berlin</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A18">
        <label>18</label>
        <addr-line content-type="verbatim">Dortmund University, Dortmund, Germany</addr-line>
        <institution>Dortmund University</institution>
        <addr-line content-type="city">Dortmund</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A19">
        <label>19</label>
        <addr-line content-type="verbatim">Beilstein-Institut, Frankfurt am Main, Germany</addr-line>
        <institution>Beilstein-Institut</institution>
        <addr-line content-type="city">Frankfurt am Main</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A20">
        <label>20</label>
        <addr-line content-type="verbatim">Tartu University, Tartu, Estonia</addr-line>
        <institution>Tartu University</institution>
        <addr-line content-type="city">Tartu</addr-line>
        <country>Estonia</country>
      </aff>
      <aff id="A21">
        <label>21</label>
        <addr-line content-type="verbatim">Physikalisch-Technische Bundesanstalt, Braunschweig, Germany</addr-line>
        <institution>Physikalisch-Technische Bundesanstalt</institution>
        <addr-line content-type="city">Braunschweig</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A22">
        <label>22</label>
        <addr-line content-type="verbatim">Bundesanstalt für Materialforschung und -prüfung, Berlin, Germany</addr-line>
        <institution>Bundesanstalt für Materialforschung und -prüfung</institution>
        <addr-line content-type="city">Berlin</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A23">
        <label>23</label>
        <addr-line content-type="verbatim">RPTU University Kaiserslautern-Landau, Kaiserslautern, Germany</addr-line>
        <institution>RPTU University Kaiserslautern-Landau</institution>
        <addr-line content-type="city">Kaiserslautern</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A24">
        <label>24</label>
        <addr-line content-type="verbatim">University of Göttingen, Göttingen, Germany</addr-line>
        <institution>University of Göttingen</institution>
        <addr-line content-type="city">Göttingen</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A25">
        <label>25</label>
        <addr-line content-type="verbatim">Dresden University of Technology, Dresden, Germany</addr-line>
        <institution>Dresden University of Technology</institution>
        <addr-line content-type="city">Dresden</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A26">
        <label>26</label>
        <addr-line content-type="verbatim">University of Stuttgart, Stuttgart, Germany</addr-line>
        <institution>University of Stuttgart</institution>
        <addr-line content-type="city">Stuttgart</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A27">
        <label>27</label>
        <addr-line content-type="verbatim">Julius-Maximilians-Universität Würzburg, Würzburg, Germany</addr-line>
        <institution>Julius-Maximilians-Universität Würzburg</institution>
        <addr-line content-type="city">Würzburg</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A28">
        <label>28</label>
        <addr-line content-type="verbatim">Center for the Transformation of Chemistry, Delitzsch, Germany</addr-line>
        <institution>Center for the Transformation of Chemistry</institution>
        <addr-line content-type="city">Delitzsch</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="A29">
        <label>29</label>
        <addr-line content-type="verbatim">Gesellschaft Deutscher Chemiker e.V., Frankfurt am Main, Germany</addr-line>
        <institution>Gesellschaft Deutscher Chemiker e.V.</institution>
        <addr-line content-type="city">Frankfurt am Main</addr-line>
        <country>Germany</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding authors: Christoph Steinbeck (<email xlink:type="simple">christoph.steinbeck@uni-jena.de</email>), Nicole Jung (<email xlink:type="simple">nicole.jung@kit.edu</email>), Felix Bach (<email xlink:type="simple">Felix.Bach@fiz-karlsruhe.de</email>), Steffen Neumann (<email xlink:type="simple">sneumann@ipb-halle.de</email>), Sonja Herres-Pawlis (<email xlink:type="simple">sonja.herres-pawlis@ac.rwth-aachen.de</email>), Johannes C. Liermann (<email xlink:type="simple">liermann@uni-mainz.de</email>), Oliver Koepler (<email xlink:type="simple">oliver.koepler@tib.eu</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: </p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>26</day>
        <month>11</month>
        <year>2025</year>
      </pub-date>
      <volume>11</volume>
      <elocation-id>e177037</elocation-id>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/86F1C888-60EE-59A5-B7E2-1721E5AD516B">86F1C888-60EE-59A5-B7E2-1721E5AD516B</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/17747150">17747150</uri>
      <permissions>
        <copyright-statement>Christoph Steinbeck, Nicole Jung, Felix Bach, Steffen Neumann, Sonja Herres-Pawlis, Johannes C. Liermann, Oliver Koepler, Christoph Bannwarth, Theo Bender, Thomas W. Bocklitz, Franziska Boehm, Christian Bonatto Minella, Frank Biedermann, Werner Brack, Ricardo Cunha, Paul Czodrowski, Franziska Eberl, Thomas Engel, Albert K. Engstfeld, Tillmann G. Fischer, Pascal Friedrich, Frank Glorious, Benjamin Golub, Christoph Grathwol, Rainer Haag, Johannes Hunold, Christoph R. Jacob, Jochen Johannsen, John D. Jollife, Stefan M. Kast, Carsten Kettner, Stefan Kuhn, Giacomo Lanza, Jan Lisec, Georg Manolikakes, Ricardo A. Mata, Jens Meiler, Matthias Müller, Ralph Müller-Pfefferkorn, Jochen Ortmeyer, Wendy Patterson, Jürgen Pleiss, Annalisa Riedel, Jens Riedel, Ulrich Schatzschneider, Leonie Schuster, Peter Seeberger, Johann-Nikolaus Seibert, Peter F. Stadler, Philip Strömert, Robert Strötgen, Patrick Théato, Nicolas Tielker, Pierre Tremouilhac, Hans-Georg Weinig, Wolfgang Wenzel, Kirsten Zeitler</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>The first funding period of NFDI4Chem established a robust foundation for research data management (RDM) in chemistry by promoting FAIR data principles and creating a cohesive infrastructure to capture well-annotated data early in the lab through electronic lab notebooks (ELNs) and making this data available in public repositories. Key achievements include standardised data formats and metadata, a federated repository environment, and improved data visibility and accessibility. Training programs and outreach have significantly increased awareness and adoption of best RDM practices. In the second funding period, the consortium aims to advance these achievements by consolidating this infrastructure, developing a model for its sustainable maintenance and operation, and fostering cultural change for its widespread adoption. Goals include ensuring seamless data workflows from laboratories to open repositories, enhancing interoperability, and supporting innovative research through AI-ready data. The work plan is organised into six task areas (TAs). TA1 (Management) provides leadership and supports all other TAs in achieving their objectives. TA2 (Smart Lab) aims to develop a fully digital research environment, including an ELN as a modular platform. This environment will support data collection, management, storage, analysis, and sharing. Integrating devices and external resources will enable seamless data transfer to repositories. TA3 (Repositories) will consolidate the repository ecosystem. The goal is to integrate repositories into a federated system for better accessibility and interoperability, ensuring long-term data availability and sustainability. TA4 (Metadata, Data Standards, and Publication Standards) focuses on developing and promoting new data and metadata standards in an international community process. This includes applying ontologies to create a semantic foundation for linking research data, making it machine-readable and enabling knowledge graphs. TA5 (Community and Training) is dedicated to fostering a cultural shift towards digital chemistry through continuous engagement, collecting requirements, and providing extensive training and support through workshops and open education resources. It will promote FAIR-compliant machine learning applications, embedding RDM into academic curricula to ensure future scientists are well-versed in these practices. TA6 (Synergies and Cross-Cutting Topics) aims to enhance collaboration across NFDI consortia and beyond. This includes developing ontologies, terminology services, the search service, and other cross-cutting solutions, integrating these developments into existing infrastructure, enabling interdisciplinary data harmonisation and fostering machine learning applications.</p>
      </abstract>
      <kwd-group>
        <label>Keywords</label>
        <kwd>data</kwd>
        <kwd>infrastructure</kwd>
        <kwd>FAIR</kwd>
        <kwd>chemistry</kwd>
      </kwd-group>
      <counts>
        <fig-count count="8"/>
        <table-count count="7"/>
        <ref-count count="127"/>
      </counts>
    </article-meta>
  </front>
  <body>
    <sec sec-type="List of Abbreviations">
      <title>List of Abbreviations</title>
      <p>
        <bold>AAI</bold>
      </p>
      <p>Authentication and Authorization Infrastructure</p>
      <p>
        <bold>AB</bold>
      </p>
      <p>Advisory Board</p>
      <p>
        <bold>API</bold>
      </p>
      <p>Application Programming Interface</p>
      <p>
        <bold>CD</bold>
      </p>
      <p>Circular Dichroism</p>
      <p>
        <bold>ChEMBL</bold>
      </p>
      <p>Chemical database of the European Molecular Biology Laboratory</p>
      <p>
        <bold>CI/CD</bold>
      </p>
      <p>Continuous Integration / Continuous Deployment</p>
      <p>
        <bold>CRC</bold>
      </p>
      <p>Collaborative Research Centre</p>
      <p>
        <bold>CTS</bold>
      </p>
      <p>CoreTrustSeal</p>
      <p>
        <bold>CV</bold>
      </p>
      <p>Cyclic Voltammetry</p>
      <p>
        <bold>DB</bold>
      </p>
      <p>Database</p>
      <p>
        <bold>DBG</bold>
      </p>
      <p>Deutsche Bunsen-Gesellschaft für Physikalische Chemie</p>
      <p>
        <bold>(D)LS</bold>
      </p>
      <p>(Dynamic) Light Scattering</p>
      <p>
        <bold>DPhG</bold>
      </p>
      <p>Deutsche Pharmazeutische Gesellschaft</p>
      <p>
        <bold>DSC</bold>
      </p>
      <p>Differential Scanning Calorimetry</p>
      <p>
        <bold>ELN</bold>
      </p>
      <p>Electronic Laboratory Notebook</p>
      <p>
        <bold>EOSC</bold>
      </p>
      <p>European Open Science Cloud</p>
      <p>
        <bold>EPR</bold>
      </p>
      <p>Electron Paramagnetic Resonance</p>
      <p>
        <bold>FID</bold>
      </p>
      <p>Specialised Information Services (Fachinformationsdienst)</p>
      <p>
        <bold>FP1</bold>
      </p>
      <p>Funding Phase 1</p>
      <p>
        <bold>FP2</bold>
      </p>
      <p>Funding Phase 2</p>
      <p>
        <bold>GPC</bold>
      </p>
      <p>Gel Permeation Chromatography</p>
      <p>
        <bold>GUI</bold>
      </p>
      <p>Graphical User Interface</p>
      <p>
        <bold>HPC</bold>
      </p>
      <p>High-Performance Computing</p>
      <p>
        <bold>HPLC</bold>
      </p>
      <p>High-Performance liquid Chromatography</p>
      <p>
        <bold>InChI</bold>
      </p>
      <p>IUPAC International Chemical Identifier</p>
      <p>
        <bold>IR</bold>
      </p>
      <p>Infrared (vibrational spectroscopy)</p>
      <p>
        <bold>IUPAC</bold>
      </p>
      <p>International Union of Pure and Applied Chemistry</p>
      <p>
        <bold>KO</bold>
      </p>
      <p>Key objective</p>
      <p>
        <bold>LADS</bold>
      </p>
      <p>Laboratory and Analytical Device Standard</p>
      <p>
        <bold>LTA</bold>
      </p>
      <p>Long Term Archiving</p>
      <p>
        <bold>LIMS</bold>
      </p>
      <p>Laboratory Information and Management System</p>
      <p>
        <bold>MI</bold>
      </p>
      <p>Minimum Information</p>
      <p>
        <bold>MIChI</bold>
      </p>
      <p>Minimum Information about a Chemical Investigation</p>
      <p>
        <bold>MS</bold>
      </p>
      <p>Mass Spectrometry</p>
      <p>
        <bold>NMR</bold>
      </p>
      <p>Nuclear Magnetic Resonance (spectroscopy)</p>
      <p>
        <bold>OA</bold>
      </p>
      <p>Open Access</p>
      <p>
        <bold>OAI-PMH</bold>
      </p>
      <p>Open Archives Initiative Protocol for Metadata Harvesting</p>
      <p>
        <bold>OC</bold>
      </p>
      <p>Organic Chemistry</p>
      <p>
        <bold>OER</bold>
      </p>
      <p>Open Educational Resource</p>
      <p>
        <bold>OS</bold>
      </p>
      <p>Open Source</p>
      <p>
        <bold>PAINS</bold>
      </p>
      <p>Pan Assay Interference Compounds</p>
      <p>
        <bold>PC</bold>
      </p>
      <p>Physical Chemistry</p>
      <p>
        <bold>PMC</bold>
      </p>
      <p>Pharmaceutical and Medicinal Chemistry</p>
      <p>
        <bold>PSDI</bold>
      </p>
      <p>Physical Sciences Data Infrastructure</p>
      <p>
        <bold>RDA</bold>
      </p>
      <p>Research Data Alliance</p>
      <p>
        <bold>RDM</bold>
      </p>
      <p>Research Data Management</p>
      <p>
        <bold>RM</bold>
      </p>
      <p>Risk and Mitigation</p>
      <p>
        <bold>SBOM</bold>
      </p>
      <p>Software Bill Of Materials</p>
      <p>
        <bold>SC</bold>
      </p>
      <p>Steering Committee</p>
      <p>
        <bold>SDH</bold>
      </p>
      <p>Semantic Data Hub</p>
      <p>
        <bold>SMILES</bold>
      </p>
      <p>Simplified Molecular-Input Line-Entry System</p>
      <p>
        <bold>TA</bold>
      </p>
      <p>Task Area</p>
      <p>
        <bold>TF</bold>
      </p>
      <p>Task Force</p>
      <p>
        <bold>TGA</bold>
      </p>
      <p>Thermogravimetric Analysis</p>
      <p>
        <bold>UI</bold>
      </p>
      <p>User Interface</p>
      <p>
        <bold>UV</bold>
      </p>
      <p>Absorption spectroscopy in the UltraViolet wavelength range</p>
      <p>
        <bold>UX</bold>
      </p>
      <p>User Experience</p>
    </sec>
    <sec sec-type="1 Preface">
      <title>1 Preface</title>
      <p>This proposal was written and submitted to the funding agency in August 2024. The text published here is a slightly shortened version of the submitted proposal and is structured along the guidelines specified by the funding agency. It outlines a working program for 5 years and assumes the full funding of the requested budget. Upon the decision by the German Research Council (Gemeinsame Wissenschaftskonferenz) in July 2025, NFDI4Chem is facing a shorter period of funding (2025/10 - 2028/12) and a yearly budget 30% lower than originally requested. These shorter resources will certainly influence our work program. Nevertheless, we are grateful for the funding and look forward to further building and supporting the National Research Data Infrastructure for chemists.</p>
    </sec>
    <sec sec-type="2 Scope and Objectives">
      <title>2 Scope and Objectives</title>
      <sec sec-type="2.1 Research domains addressed by the consortium, specific aim(s)">
        <title>2.1 Research domains addressed by the consortium, specific aim(s)</title>
        <p>NFDI4Chem is building a research data infrastructure for all chemical fields dealing with the synthesis, analysis and characterisation of molecules (<xref ref-type="bibr" rid="B13519287">Steinbeck et al. 2020</xref>). We are making this distinction to define clear-cut boundaries to those NFDI consortia dealing with materials science. To spend the inevitably limited funding responsibly and effectively, our working principle is to establish infrastructure components for those fields in chemistry with the highest number of users, as defined by the size of the respective divisions in the German Chemical Society.</p>
        <p>In the next funding period, NFDI4Chem aims to expand and enhance its scope by addressing several future needs: We will consolidate our repository ecosystem and extend existing ones to cover more subdisciplines and data types and pursue the integration of repositories into a federated system for better accessibility and interoperability. We will develop further standards for data and metadata and promote and establish open data standards in cooperation with international bodies. Additionally, we develop and apply ontologies to create a semantic foundation for linking research data, enabling machine-readable data and creating knowledge graphs. All this enables us to continue the digital transformation of chemistry by using Electronic Lab Notebooks (ELNs) and tools in Smart Lab environments for early digital data and metadata capture, linking these with data repositories and a downstream search service to seamlessly digitise the entire research process. Ultimately, we provide access to semantically annotated, high-quality research data for chemistry research and future AI methods.</p>
        <p>Since its inception, NFDI4Chem has impacted the research landscape in several ways: We promoted standardised data formats and metadata, facilitating better data sharing and reuse (<xref ref-type="bibr" rid="B13519322">Herres‐Pawlis et al. 2022</xref>). NFDI4Chem established a virtual environment of federated repositories, improving the visibility and accessibility of research data and integrating existing repositories with national and international systems, thus improving the overall data infrastructure for chemical research (<xref ref-type="bibr" rid="B13553459">Neumann et al. 2023</xref>).</p>
        <p>Towards a cultural change to digital chemistry, we boosted interest and engagement for the FAIR data principles within the chemistry community through training programmes and outreach activities to promote best practices in research data management (RDM) (<xref ref-type="bibr" rid="B13547994">Herres-Pawlis 2023</xref>, <xref ref-type="bibr" rid="B13520029">Herres-Pawlis et al. 2023</xref>, <xref ref-type="bibr" rid="B13520622">Pearman-Kanza et al. 2024</xref>, <xref ref-type="bibr" rid="B13553491">Koepler et al. 2020</xref>). We established a solid ontological ground for machine-actionable data with well-curated chemistry ontologies provided by the terminology services (<xref ref-type="bibr" rid="B13568831">Strömert et al. 2022</xref>, <xref ref-type="bibr" rid="B13568869">Strömert et al. 2023</xref>).</p>
      </sec>
      <sec sec-type="2.2 Objectives and measuring success">
        <title>2.2 Objectives and measuring success</title>
        <p>NFDI4Chem’s efforts and decisions are guided by our vision that <italic>all chemists publish FAIR data.</italic> Our mission is to <italic>support scientists in their efforts to collect, store, process, analyse, publish, and reuse research data in chemistry.</italic> We develop and maintain a national research data infrastructure for the research domain of chemistry in Germany, and we enable innovative services and science based on research data.</p>
        <p>To translate our vision and mission into reality, we have identified several key objectives:</p>
        <p><bold>Key Objective 1</bold>: Evolve the federation of services and repositories for storing, disclosing, searching and reusing research data. Integrate community standards for the seamless integration of distributed data sources and uniform access to data for innovative data reuse.</p>
        <p><bold>Key Objective 2</bold>: Lead international community processes to establish minimum information (MI) standards for data and machine-readable metadata to create semantically rich linked chemistry data.</p>
        <p><bold>Key Objective 3</bold>: Develop and foster the application of Smart Laboratory Environments by promoting the use of digital tools in all stages of research and creating seamless digital data workflows.</p>
        <p><bold>Key Objective 4</bold>: Foster cultural and digital change within the chemistry community in Germany to create awareness for and foster a community-agreed technically reliable RDM infrastructure for all levels of academia, beginning in undergraduate studies curricula.</p>
        <p><bold>Key Objective 5</bold>: Collaborate with other consortia and promote cross-cutting developments to extend synergies within OneNFDI and enable interdisciplinary data harmonisation and integration.</p>
        <p><bold>Key Objective 6</bold>: Facilitate data reuse and enable AI in chemistry by providing AI-ready data, data infrastructures, and high-quality data and metadata through all services.</p>
        <p>These key objectives align with the overarching goals of the NFDI, described in the federal-state agreement (Bund-Länder-Vereinbarung) (<xref ref-type="bibr" rid="B13579118">Gemeinsame Wissenschaftskonferenz 2018</xref>). For long-term commitment and the trust of the chemistry community, statements on the long-term availability of the NFDI4Chem infrastructure are imperative. Key players of the consortium are, in alignment with their strategic vision, willing to commit to the long-term provision of repositories and services, which nonetheless require reliable, additional funding. NFDI4Chem recognises its role in the consolidation of the NFDI. The entanglement of our own services with basic services, exemplified by the terminology service, demonstrates our commitment to the consolidation process. We continue to contribute to the cross-cutting topics of the NFDI and metadata standardisation efforts. Our services are tailored to meet the needs of our community. We will continue our strategy and conduct in-depth community surveys regularly. We have adapted the DFG datasheet and the defined key performance indicators (KPI) to monitor our services and community impact in FP2. We will identify further KPIs relevant to NFDI4Chem and embed these in the organisational structure and operations in FP2 to evaluate our success (T1.3.3). A critical assessment of the KPIs will be conducted as part of the annual consortium meeting. We will participate in the NFDI TF Evaluation &amp; Reporting for the overarching development of NFDI-wide KPIs and utilise recommendations from the NFDI.</p>
      </sec>
    </sec>
    <sec sec-type="3 Consortium">
      <title>3 Consortium</title>
      <sec sec-type="3.1 Composition of the consortium and its embedding in the community of interest">
        <title>3.1 Composition of the consortium and its embedding in the community of interest</title>
        <p>NFDI4Chem started in October 2020 with 7 (co-)applicant institutions, many of which contributed with several institutes or departments, and 13 participating institutions. From 2022 to 2024, we gained 4 additional partners for the consortium who had already supported the work in various areas in FP1, specifically in enzymology, material and analytical sciences, didactics, photo- and electrochemistry.</p>
        <p>For FP2, we will expand the consortium to include more representatives in physical, theoretical, and computational chemistry, scientific infrastructure, data processing, and AI development With these new partners, the consortium in FP2 will have 7 applicant institutions (many of them including several contributing institutes), 20 participating institutions and 2 participating individuals.</p>
        <p>Embedding in the community</p>
        <p>From the outset, NFDI4Chem identified the needs of the community with a survey in 2019 (<xref ref-type="bibr" rid="B13551429">Herres‐Pawlis et al. 2020</xref>). In spring 2023, a second survey with more than 800 responses (680 from Germany) included professors (22%), senior researchers (24%) and PhD students (33%) from different areas of chemistry. Digital data analysis improved, with 45% using seamless methods and 65% still using some non-digital steps. Metadata description increased to 56% (42% in 2019). ELN use increased to 30% (18% in 2019), particularly in organic chemistry (34%) and materials chemistry (33%). Common ELNs included Chemotion (26%), ELabFTW (20%) and Sciformation / Open Enventory (9%), as well as Word and Excel, which some also classified as ELNs. The use of data repositories increased by 20% (from 13%). 86% felt that research data management in the curriculum would benefit future students and groups. This feedback demonstrates the impact of NFDI4Chem, and further surveys will continue in FP2. (see M5.1).</p>
        <p>NFDI4Chem has strong links with the major subdisciplines of chemistry (organic, inorganic, polymer, biochemical, pharmaceutical, physical, computational and analytical chemistry) through learned societies as consortium members (GDCh, DPhG, Bunsen Society, FID Pharmazie) and outreach activities. Collaborative development with specialised communities such as chemical ontologies, NMR, EPR standards, electrochemistry, coordination chemistry, macromolecules, and enzymes is achieved through regular meetings and workshops. Users can provide feedback via the helpdesk and GitHub repositories. Interaction with the ontology community is particularly strong, as evidenced by the annual Ontologies4Chem workshops with ~50 participants from major chemistry ontology projects (<xref ref-type="bibr" rid="B13551688">Koepler et al. 2023</xref>) and joint activities with IUPAC and international projects such as the Physical Sciences Data Infrastructure (PSDI). NFDI4Chem actively participates in working groups on standards for analytical chemistry methods.</p>
        <p>The NFDI4Chem training programme is essential to promote RDM awareness. We have developed a two-day interactive course for chemists covering RDM basics and specific scenarios based on the FD Mentor concept (<xref ref-type="bibr" rid="B13551839">Biernacka et al. 2020</xref>) and materials from the research data teams at FSU, RWTH and JGU. Launched in January 2022, the workshop is open to all chemists in Germany, with growing international participation. It was held every two months in 2022 and was consistently well booked. In 2023, we moved to institution-specific workshops in collaboration with local RDM teams. The Chemotion workshop series introduces the electronic lab notebook through a "learning by doing" approach, adaptable to the needs of the participants. A similar format is offered for the generic LabIMotion modules in Chemotion. By July 2024, we have organised 73 workshops (see Fig. <xref ref-type="fig" rid="F13519912">1</xref> for an overview of on-site workshops in Germany), reaching over 800 participants. To meet demand and support the <ext-link ext-link-type="uri" xlink:href="https://www.nfdi.de/section-edutrain/"><underline>NFDI section EduTrain</underline></ext-link>, we are expanding to include workshops for data stewards and a 1-day Lead-by-example workshop. In addition, we are providing materials for integrating chemistry-specific RDM content into curricula to facilitate teaching culture change.</p>
        <p>To promote RDM awareness among young scientists, we presented the FAIR4Chem award at the GDCh JungChemikerForum (JCF) in 2022, 2023, and 2024. In 2023, we organised the first Chemistry Data Days, a two-day conference on data management for non-RDM experts, with around 100 participants. We engage with the community through monthly 'Stammtisch' discussions on RDM, ELNs, repositories, and ontologies, along with Chemotion Q&amp;A sessions and various RDM and Chemotion workshops. Finally, NFDI4Chem is active on several social media channels: LinkedIn (753 followers, &gt;170 articles), Instagram (168 followers, 148 posts), BlueSky (247 followers, 109 posts), and X (formerly Twitter, 1184 followers, 562 tweets), the latter no longer actively promoted (all figures as of 30/07/2024).</p>
      </sec>
      <sec sec-type="3.2 The consortium within the NFDI and the national academic research system">
        <title>3.2 The consortium within the NFDI and the national academic research system</title>
        <p>NFDI4Chem members have actively shaped the NFDI, with our spokesperson leading the Consortium Assembly in 2021/22. NFDI4Chem spokespersons and co-spokespersons played key roles in NFDI strategy workshops (<xref ref-type="bibr" rid="B13521128">Glöckner et al. 2019</xref>, <xref ref-type="bibr" rid="B13520868">Bierwirth et al. 2020</xref>, <xref ref-type="bibr" rid="B13520557">Ebert et al. 2021</xref>, <xref ref-type="bibr" rid="B13552896">Konsortialversammlung des Vereins Nationale Forschungsdateninfrastruktur (NFDI) e.V. 2022</xref>), helping to establish its foundational bodies. Recognising that the success of NFDI hinges on effective collaboration across consortia, NFDI4Chem is deeply committed to addressing cross-cutting topics and creating overarching solutions to common challenges. In NFDI, the sections serve as crucial forums for addressing cross-cutting issues with the goal of creating overarching solutions. NFDI4Chem's commitment to this collaborative approach is evidenced by the election of three consortium members as spokespersons for NFDI e.V. sections (<xref ref-type="bibr" rid="B13521115">Boehm et al. 2021</xref>, <xref ref-type="bibr" rid="B13520126">Koepler et al. 2021</xref>, <xref ref-type="bibr" rid="B13520506">Herres-Pawlis et al. 2021</xref>), i.e. Section “Education and Training”, “(Meta)data, Terminologies and Provenance”, and “Ethical, Legal and Social Aspects. Two of them are heading the sections in their second term of office from April 2024. NFDI4Chem members actively contributed to task forces and working groups within the various sections during the first funding phase. Our contributions include developing standardised methodologies for ontology curation and development processes, using terminology services in research data management tools and services, and establishing NFDI-wide identity and access management services. We also contribute to developing research data management plans, open educational resources for RDM training, support and recommendations for ELN implementations in consortia, legal aspects of RMD, or an NFDI metadata standard in the Task Force Metadata (<xref ref-type="bibr" rid="B13520148">Hunold et al. 2023</xref>). A significant outcome of our collaborative efforts is the close cooperation with NFDI4Cat, FAIRMat, NFDI4Ing, DataPlant, NFDI4Health, NFDI4Culture, and NFDI4Objects (<xref ref-type="bibr" rid="B13552916">Dolcet et al. 2003</xref>). Cooperations cover developing and curating ontologies while enhancing tools and services for ontology curation (<xref ref-type="bibr" rid="B13552954">NFDI4Chem 2023</xref>, <xref ref-type="bibr" rid="B13552928">Bender 2024</xref>, <xref ref-type="bibr" rid="B13552970">NFDI4Chem 2024e</xref>). Furthermore, we are collaborating with FAIRMat and NFDI4Cat to develop and apply electronic lab notebooks (ELN). In FP2, we will closely monitor developments and stay involved in strengthening the sections, contributing to joint solutions for common challenges, and achieving tangible cross-consortia results.</p>
        <p>The work of the sections highlights the need for collaborative solutions across NFDI consortia. We, therefore, welcome the Base4NFDI objective to create common services to support RDM in chemistry. NFDI4Chem is committed to fostering the emerging Base4NFDI services and, where relevant for our consortium, to engage with and use future Base4NFDI services. NFDI4Chem has actively participated in the Base4NFDI workshops held on 16 February 2024 and 22 April 2024 to identify and agree on viable contributions of the consortia for the successful integration of Base4NFDI services. In alignment with ongoing developments for the chemistry community, NFDI4Chem is actively contributing to the basic service for Terminology Services TS4NFDI during the initialisation phase, integrating the NFDI4Chem TS into the TS4NFDI backend architecture. We will continue our engagement in the integration phase of TS4NFDI as described in M6.2. During the initialisation phase, we actively contributed to the requirements collection for IAM4NFDI, TS4NFDI, KG4NFDI, and PID4NFDI by completing surveys and attending workshops. NFDI4Chem has engaged with IAM4NFDI in incubator pilots (<xref ref-type="bibr" rid="B13577493">IAM4NFDI 2024</xref>), prototyping the access control to our Terminology Services and Chemotion ELN via Community AAI. In FP2, NFDI4Chem will continue to support structured ongoing communication with Base4NFDI. We will closely monitor and connect to activities in Base4NFDI and provide a dedicated communication channel to Base4NFDI technical and community updates in M6.4.</p>
        <p>NFDI4Chem and community members have also contributed to the NFDI infra-talk series and co-organise the Physical Sciences Consortia Joint Colloquium with five other consortia. In addition, NFDI4Chem is strengthening links with universities, RDM service units, and IT centres, having (co-)organised six local networking events in the past (<xref ref-type="bibr" rid="B13553161">Neumann et al. 2024</xref>). NFDI4Chem continues to present its work and services at national RDM events. Targeting FDM initiatives of the federated states, we strive to sustain the integration of NFDI4Chem training measures into academic RDM services (see T5.3.5). Hereby, we empower the next generation of scientists with urgently needed digital skills (<xref ref-type="bibr" rid="B13553257">Bertelmann et al. 2024</xref>). This goes hand in hand with integrating RDM content into curricular teaching (see M5.4).</p>
        <p>More details on our continuous involvement in the NFDI are described in M6.4, and in <xref ref-type="bibr" rid="B13553375">Eberl et al. (2024)</xref> concerning collaborations.</p>
      </sec>
      <sec sec-type="3.3 International networking">
        <title>3.3 International networking</title>
        <p>NFDI4Chem emphasises that developing standards and best practices for research data management requires a global perspective. Thus, NFDI4Chem actively engages with the worldwide community of chemists and research data infrastructure experts. Strengthening collaboration with the International Union of Pure and Applied Chemistry (IUPAC), NFDI4Chem aligns its measures with several IUPAC projects. TA4 and TA6 work with the <ext-link ext-link-type="uri" xlink:href="https://iupac.org/project/2019-031-1-024/">FairSpec project</ext-link>. In the WorldFAIR: Global cooperation on FAIR data policy and practice project, NFDI4Chem contributed to IUPAC WorldFAIR Chemistry deliverable 3.2 "Chemistry Training Package" (<xref ref-type="bibr" rid="B13520630">Chalk et al. 2024</xref>). TA6 and IUPAC are jointly developing recommendations for using the Compendium of Chemical Terminology ("Gold Book") to define new ontology terms in chemistry-specific ontologies (<xref ref-type="bibr" rid="B13553613">Strömert et al. 2024</xref>). NFDI4Chem representatives participate in various Research Data Alliance (RDA) working and interest groups, i.e., regularly contributing to the Chemistry Research Data Interest Group (CRDIG) sessions at RDA plenary meetings. The interoperable federation of repositories was showcased and discussed with RDM experts at international conferences like <ext-link ext-link-type="uri" xlink:href="https://www.fdo2022.org/programme">FDO2022</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://www.rd-alliance.org/plenaries/rda-20th-plenary-meeting-gothenburg-hybrid/describing-diverse-chemistry-datasets-across">RDA plenary 20</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://www.rda-deutschland.de/news/save-the-date-rda-de-tagung-2023">RDA-DE2023</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://internationaldataweek.org/idw2023/">IDW2023</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://codata.org/scidatacon-2023-deadline-for-submitting-sessions-and-presentations-extended/">SciDataCon</ext-link>, and <ext-link ext-link-type="uri" xlink:href="https://www.pidfest.org/">PIDfest2024</ext-link>. S. Herres-Pawlis is a Board Member of the <ext-link ext-link-type="uri" xlink:href="https://www.inchi-trust.org/inchi-board/">InChI Trust</ext-link>, guiding inorganic chemistry implementation into the InChI. P. Théato chairs the <ext-link ext-link-type="uri" xlink:href="https://iupac.org/body/401/">Sub-Committee on Polymer Terminology</ext-link>, and the NFDI4Chem spokesperson C. Steinbeck serves on the IUPAC <ext-link ext-link-type="uri" xlink:href="https://iupac.org/body/024/">Committee on Publications and Cheminformatics Data Standards</ext-link>. Additionally, NFDI4Chem organised three <ext-link ext-link-type="uri" xlink:href="https://iupac.org/gwb/">IUPAC Global women’s breakfasts</ext-link>, highlighting women's achievements in NFDI4Chem. We recently joined a panel on critical reflections on RDM at the <ext-link ext-link-type="uri" xlink:href="https://www.zef.de/fileadmin/downloads/2023_06_-_DSSP_SDGs_summary.pdf">SDG Graduate Schools Alliance midterm conference</ext-link>, emphasising equal opportunities for researchers in the global south. NFDI4Chem has established collaborations with international learned societies such as the American Chemical Society (ACS) with its division of Chemical Information (CINF). NFDI4Chem co-organized two sessions on "Helping Chemists manage their Data" and "Metadata to Knowledge Graphs" at the ACS Fall Meeting 2023. S. Herres-Pawlis is on the advisory board of the UK's Physical Sciences Data Infrastructure (PSDI), and a joint session with PSDI was held during EuChemS 2024 in Dublin. NFDI4Chem regularly collaborates with the European Chemical Society (EuChemS). At the EuChemS congress 2022 in Lisbon and 2024 in Dublin, Chemotion ELN garnered significant interest. We also collaborate with the International and the European Younger Chemists Networks (IYCN and EYCN), key stakeholders for RDM implementation in universities, while GDCh-JCF acts as a multiplier for NFDI4Chem in the German community. For instance, we organised an international RDM workshop at the IUPAC Conference in Den Hague in 2023. NFDI4Chem works with the Royal Society for Chemistry (RSC) on developing and curating ontologies. NFDI4Chem partners are active in the <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org">European Life Sciences Infrastructure ELIXIR</ext-link>, contributing to Bioschemas developments and organising projects at the 2022 and 2023 ELIXIR Hackathons. Embedded in the NFDI activities, NFDI4Chem has presented its work at European Open Science Cloud (EOSC) events, such as the presentation of the Terminology Service at the EOSC Symposium 2021 in the session "Metadata and Data Quality." Co-spokesperson Oliver Koepler actively contributes to the <ext-link ext-link-type="uri" xlink:href="https://eosc.eu/advisory-groups/technical-and-semantic-interoperability-task-force/">EOSC Technical and Semantic Interoperability Task Force</ext-link>.</p>
      </sec>
      <sec sec-type="3.4 Organisational structure and viability">
        <title>3.4 Organisational structure and viability</title>
        <p>We have designed the organisational structure of NFDI4Chem to ensure that the work programme can be pursued in an efficient and agile manner, that the decision-making process within NFDI4Chem is legally sound and transparent, and that the community and our stakeholders are closely attached to our operation. The organisational structure described below has been established during the FP1 and has served the consortium well. In the following, we describe the various components of our <bold>organisational structure</bold>, as shown in Fig. <xref ref-type="fig" rid="F13519927">2</xref>.</p>
        <p><bold>The General Assembly (GA)</bold> is the central decision-making body of the project. The GA comprises all co-applicants and participants (represented by one delegate from each partner).</p>
        <p>The GA will decide on all issues of fundamental importance for the whole project. The GA will be held at the annual NFDI4Chem project meetings or online if urgent matters require it. The annual NFDI4Chem meetings will be used for strategic planning, presentation of scientific results, and discussion of significant management issues. The GA decides when an overall agreement is required in budget and consortium management matters.</p>
        <p>The <bold>Steering Committee (SC)</bold> is the central body responsible for monitoring and evaluating project progress and supervising project objectives, and it makes the necessary decisions in scientific coordination and administration of the project. Based on the contributions from task areas (TAs), the SC prepares periodic and final reports. The SC consists of the two speakers, the NFDI4Chem project manager, the TA leads and their project managers. Project speaker Christoph Steinbeck heads the SC.</p>
        <p>NFDI4Chem has established a focused set of <bold>Advisory Boards</bold>, which are consulted regularly to ensure that the consortium is on track and develops and delivers services that are</p>
        <p>a) aligned with the mission of the NFDI in general and</p>
        <p>b) address the needs of the chemistry community.</p>
        <p>The ABs and their advice proved invaluable during our first funding period.</p>
        <p><bold>Advisory Board <italic>Industry</italic></bold> comprises companies developing data-producing equipment, data management systems, and data analysis solutions. They provide insights on data formats and software and aim to incorporate the NFDI4Chem recommendations and processes into their software developments.</p>
        <p><bold>Advisory Board <italic>Publishers</italic></bold> provides insights on research data associated with scientific publications. They aim to include the NFDI4Chem recommendations and processes into their guidelines for authors, editors, and reviewers. The manuscript submission systems should support compliance with the guidelines.</p>
        <p><bold>Advisory Board <italic>National Research Community</italic></bold> represents researchers and organisations performing research in Germany. We aim to cover the subject areas reflected in the list of DFG review boards (DFG Fachkollegien) mentioned in the section General Information above.</p>
        <p><bold><italic>International</italic> Advisory Board</bold> complements the advisory boards described above, focusing on international organisations and individuals. These are lighthouses of collaboration and alignment of efforts to collect, store, process, analyse, disclose, and re-use research data.</p>
        <p><bold>Decision Making</bold>: The distributed nature of the NFDI4Chem project necessitates a decentralised administration of execution control for effective decision-making. The operational level comprises all the project partners who are responsible for the execution of the strategic work plan detailed in the TAs. The TA leaders will be responsible for keeping track of the measures with the listed deliverables. Any deviations will be brought to the attention of the project office (PO) and discussed at the next steering committee (SC) meeting. The TA leaders oversee the budget and technical aspects, including quality checks and communications with the project office when required. This process is supported by the detailed project management plan maintained at the FSU. The main scientific controlling and decision-making body in the project is the steering committee (SC). The SC is responsible for all decisions regarding project management, distribution, monitoring, and re-organisation of specific tasks if necessary and for all cases that do not require the voting of the GA. The SC convenes by electronic communication regularly and on-demand, as organised by the project office. The GA will be the highest decision-making body in the project and will be consulted for strategic planning, major management topics and other fundamental issues. The GA will make particular decisions if overall consensus is required in the matters of inclusion of a new partner, exclusion of an existing partner, major budget or project strategy changes, and other unforeseen situations that need discussion or decision-making. Decisions of the GA that need voting require a simple majority of the project partners based on the principle “one partner – one vote”. To have a quorum, 75% of the partners have to be physically present at the GA or through teleconference facilities during decision-making and voting. In a stalemate situation, the Project Coordinator will have the deciding vote.</p>
        <p><bold>Internal Distribution of Funds</bold>: According to our consortium agreement, FSU, as the lead organisation for NFDI4Chem, will conclude forwarding contracts with all co-applicants and participants as part of a normal consortium agreement following well-established models.</p>
      </sec>
      <sec sec-type="3.5 Operating model">
        <title>3.5 Operating model</title>
        <p>NFDI4Chem is committed to building a robust and sustainable open data research infrastructure that is accessible and beneficial to users and providers. Our operating model is based on the following pillars: <bold>User-centric approach</bold>: We prioritise the needs of researchers, educators and other stakeholders by providing easy access to high-quality research data. Our services include data storage, management, sharing, and analysis tools that are user-friendly and reliable. <bold>Collaborative Framework</bold>: Data providers, including academic institutions, research organisations and data centres, work together within the consortium to offer their resources and expertise. This collaborative approach ensures a diverse and comprehensive federation of data repositories serving various research areas. <bold>Open access and interoperability</bold>: We are committed to the principles of open access, ensuring that all data within our infrastructure is freely available to users. In addition, we emphasise interoperability to facilitate seamless integration with other data infrastructures and research tools worldwide. Our operational and financial model has proven effective, benefiting both users and providers. By relying on funding from research funding agencies, we have avoided the pitfalls of commercial interests that could compromise the open-access ethos of our consortium. The current funding spares data providers and users from costs, preventing a drop in scientific engagement and avoiding the overhead of collecting user fees across multiple services. The critical components of our funding model are as follows. <bold>Infrastructure funding</bold>: Primary funding comes from national infrastructure funding. Funding agencies recognise the importance of open research data for scientific progress and innovation and provide grants and subsidies to support our activities. This infrastructure funding allows for the sustainable operation and maintenance of NFDI4Chem after the first two funding periods. <bold>In-kind Contributions</bold>: Consortium members contribute in-kind resources such as computing power, data storage facilities and personnel. This model leverages existing capabilities within member institutions, reducing overall costs and fostering a sense of ownership and commitment among members. <bold>Project-based grants</bold>: We actively seek project-based grants to fund specific orthogonal initiatives related to the consortium. These grants allow us to develop new tools that could not be integrated into the main development plan, expand our data repositories and curation capacities, allow the integration of further community members, and improve user support services. We do not currently charge user fees and have no plans to do so in the future. Our mission is to ensure that financial barriers do not impede access to valuable research data. By securing sufficient funding from research organisations and leveraging in-kind contributions, we maintain a sustainable model that supports free access for all users.</p>
        <p>We are implementing the following strategies to ensure the continuity of services and the sustainability of NFDI-wide activities. <bold>Diversified funding sources</bold>: We diversify our funding to include multiple research agencies and project-based grants to reduce reliance on any single funding source. <bold>Regular evaluation and adjustment</bold>: We assess our services and financial health and adapt our strategies to meet evolving needs and the financial landscape. This proactive approach helps us to stay ahead of potential challenges. <bold>Community engagement and advocacy</bold>: We actively engage with the research community to understand its needs and advocate for continued support from funding agencies. Building strong relationships with stakeholders ensures continued relevance and support for our infrastructure. <bold>Collaboration with NFDI</bold>: We collaborate with other NFDI consortia, including Base4NFDI, joining forces and generating synergies to provide a suitable service portfolio, including all required services, without duplicating them.</p>
        <p>In summary, our operational and financial model is designed to support an open, collaborative and sustainable research data infrastructure that meets the needs of both users and providers. Through diversified funding, in-kind contributions and a commitment to open access, we ensure our services' long-term viability and relevance.</p>
      </sec>
    </sec>
    <sec sec-type="4 Research Data Management Strategy">
      <title>4 Research Data Management Strategy</title>
      <sec sec-type="4.1 Scientific relevance and quality of the measures">
        <title>4.1 Scientific relevance and quality of the measures</title>
        <p>NFDI4Chem aims to provide all scientists with an infrastructure for collecting, managing and publishing FAIR data. At the same time, awareness of this infrastructure and services and the willingness and ability to use them must be established. Therefore, we have drafted a comprehensive strategy to develop and provide infrastructure and services for research data management and training in the chemistry community. Since 2020, we have been pursuing our goals through close cooperation in 6 task areas (TAs) allowing us to work successfully on the measures that we aimed for: TA1 deals with the management of NFDI4Chem, TA2 develops software for digital labs, TA3 establishes and hosts repositories, TA4 develops standards and metadata schemes, TA5 ensures communication with and education of the community, and TA6 provides overarching services for terminologies, (meta)data search and harmonisation.</p>
        <p><bold>Visible success of the consortium’s work</bold>: The achievements of NFDI4Chem are tangible in different forms and contexts. For the researching laboratory chemist, the digitalisation of chemistry is becoming imminent through the expanding use of electronic laboratory journals and software tools supporting data capture and analysis. Within FP1, we provided generally applicable, extendable, and freely available software and tools covering the whole research data lifecycle, demonstrated for several use cases (recent application: workflow for cyclic voltammetry) (<xref ref-type="bibr" rid="B13553625">Herrmann et al. 2023</xref>). Meanwhile, 70 local instances (at 68 different locations) of the Chemotion ELN are known, spanning academia (instances in German universities and other countries: DE: 41, NL: 5, CH: 4, FR: 2, other EU: 6, UK: 1, India: 2, US: 1, Singapore: 1) and first industrial users (5 companies known).</p>
        <p>Chemists face the next challenge with integrating FAIR data publication into the publication process of research results in a research article. NFDI4Chem has successfully tackled this challenge on two fronts. Firstly, from the data producer perspective, the smart lab supports users in the downstream publication of data in repositories through a user-friendly and seamless transfer of metadata from ELN to repositories of the NFDI4Chem federation such as Chemotion repository, RADAR4Chem and nmrXiv, with no additional burden for the user. In the evolving landscape of chemical research, a suite of repositories has been established to cover all major data types, subdisciplines, and functions in chemistry. The chemistry community trusts and accepts these repositories, with endorsements from leading journals and funding agencies. RADAR4Chem stands out for optimising FAIRness scores of datasets through the FAIRimpact implementation action (<xref ref-type="bibr" rid="B13578549">Soltau et al. 2024</xref>), integrated archiving for more than 25 years, and allowing complex and big datasets. Chemotion has made significant strides with over thirteen frequent releases, continually integrating new features to meet researchers' and reviewers’ needs. Even in its pre-release phase in early 2023, nmrXiv already hosted 81 compounds and 490 spectra, demonstrating its value for the community.</p>
        <p>Secondly, NFDI4Chem has initiated a broad-based discourse with all relevant chemistry publishers to integrate data publications into the article submission processes. The central aim is to ease the data publishing processes so that researchers can lower the barrier to publishing data. Our two Editors4Chem Workshops were attended by 25 editors, including many editors-in-chief, covering main publishers in chemistry, such as Wiley-VCH, RSC, Springer Nature, ACS Publications, Thieme, Beilstein, PLoS, and MDPI. Projects included the adoption of data availability statements and the recommendation of trusted chemistry-friendly repositories, highlighted in the <ext-link ext-link-type="uri" xlink:href="https://knowledgebase.nfdi4chem.de/knowledge_base/docs/choose_repository/">NFDI4Chem Knowledge Base</ext-link> and implemented e.g. by <ext-link ext-link-type="uri" xlink:href="https://onlinelibrary.wiley.com/page/journal/15213773/homepage/notice-to-authors#sectGDataDeposition">Angewandte Chemie</ext-link>. Moreover, TA4 brought the idea of Minimum Information Standards into the Community (<xref ref-type="bibr" rid="B13519322">Herres‐Pawlis et al. 2022</xref>) and elaborated on standards for NMR, among others. As a molecular standard, the InChI stagnated over many years until NFDI4Chem joined many InChI subgroups, pushing it forward towards opening the core development to GitHub and implementing inorganic chemistry (<xref ref-type="bibr" rid="B13574014">Herres-Pawlis et al. 2024</xref>).</p>
        <p>With a perspective on machine-readable data and in preparation for AI applications, TA6 has established a further cornerstone with chemistry ontologies for the semantic annotation of data. The NFDI4Chem Terminology Service (TS) provides 40 high-quality ontologies for both human and service-to-service use, the last one impressively demonstrated by over 400,000 API calls to the TS backend by now. The services and offers of NFDI4Chem quickly find their way into the community through the engaged work of TA5. A dedicated team of trainers delivered 73 workshops on research data management to more than 800 chemists. A newly established knowledge base with now 62 individual articles in English and German was created by 24 contributors and attracts 400-500 visitors per month. Moreover, NFDI4Chem could present the first examples of embedding RDM content into chemistry curricula (<xref ref-type="bibr" rid="B13569079">Fink et al. 2023</xref>).</p>
        <p><bold>Review of measures in FP1 and adjustments in FP2</bold>: Overall, our general strategy for the organisation of TAs and measures was well-balanced and efficient, so we are proposing the same structure for FP2. Nevertheless, we adapted some organisational aspects of our work in comparison to previous plans: In addition to the individual focus topics in the TAs, we have recognised an increasing need for regular dialogue on the collaboration between all TAs on a joint strategy for the development and implementation of standards to cover the perspectives from data producers to data re-users and the intermediary services over the course of FP1. We, therefore, introduced cross-TA meetings on a biweekly basis, supported by regular workshops. This formerly not planned meeting routine allows us to discuss dependencies of tasks across the TAs, adjust priorities, and accelerate decisions required to plan and conduct the measures.</p>
        <p>We have to recognise that standardisation work is complex and is becoming more so. This concerns standards for metadata, data, and ontologies through coordination in our international network with IUPAC, RDA, or EOSC, as well as the standardisation of devices with formats and interfaces. Standardisation will, therefore, continue to be an integral part of FP2 work. With the establishment of NFDI consortia in the second and third rounds, NFDI4Chem consolidated activities with consortia close to its scientific scope. Consequently, the integration of NOMAD, now funded by FAIRmat, shifted within NFDI4Chem. NOMAD is now associated with NFDI4Chem, enabling collaboration and support for the theoretical and computational chemistry community. Similarly, NFDI4Chem will consolidate Suprabank into the Chemotion repository (see M3.4). We will review current and new services for their potential integration to avoid duplication and to ensure compatibility with existing NFDI4Chem infrastructure. We will expand our perspective for the review of potential consolidation candidates to NFDI basic services and the ongoing work on the overarching NFDI service architecture drafted by the NFDI and its sections in FP2. The first steps of our approach are outlined in Chapter 3.2, which includes the NFDI4Chem terminology service and the NFDI basic terminology service. With the establishment of the ELSA section, we will continue the discussion of the legal aspects of RDM at the NFDI level.</p>
        <p>In FP1, the consortium gained strong support from previously less-involved chemistry sub-disciplines, including electrochemistry, photochemistry, environmental chemistry, and theoretical and computational chemistry. This support allowed systematic inclusion in all NFDI4Chem areas, formalised by adding new partners and adjusting measures in TA2-TA6 to meet community needs in FP2.</p>
        <p>NFDI4Chem emphasises the importance of quality assurance for generating high-quality data and maintaining a trustworthy infrastructure. While initial efforts in FP1 focused on establishing and expanding services and data available, FP2 will prioritise quality assurance measures to raise the maturity and quality of the infrastructure and provide (meta)data. Quality measures will cover data and metadata validation in software services (T2.3.5, T3.3.1, and T3.3.4.), but also underlying standardisation processes for Minimum Information about Chemical Investigations MIChI and derived metadata schemas (T4.1.1., T4.3.2), the integration of terminologies (T6.1.1, T6.2.2) and the schema validations and crosswalks (T6.3.3).</p>
        <p>In the course of FP1, the wealth and granularity of chemical information obtained from all areas of chemistry, particularly through the smart lab, has increased significantly as a result of the systematic digitisation of processes. This information needs to be expressed in rich chemistry metadata to be available in downstream services and data reuse scenarios. We, therefore, adjusted our metadata strategy to support the development of interoperable metadata schemas based on discipline-specific MIChIs (see Chapter 4.2) The newly defined Metadata Schema Service (MSS) will provide the necessary tools to support the creation and application of these schemas ensuring interoperability and mapping to more generic schemas (M6.3).</p>
        <p>In summary, the planned measures and adjustments allow NFDI4Chem to provide FAIR data on a large scale and take actions to ensure data reuse in all areas, collectively extending the infrastructure towards machine-actionable and AI-ready data. Building upon standardisation and semantically rich chemistry metadata, the Chemistry Knowledge Graph allows us to harness the potential of machine-actionable data. The expansion of ML-focused expertise in FP2 enables NFDI4Chem to demonstrate data reuse in chemistry-specific use cases and make it accessible for other future partners and models. Furthermore, the integration of AI models can directly create benefits for users of the NFDI4Chem infrastructure (e.g., in ELN or repositories). These incentives for our users will help gain additional supporters in FP2. In the following sections we describe the individual measures and outcomes of TAs in more detail, especially with respect to results that are achieved to prepare our work plan for FP2.</p>
        <p><bold>TA1 (Management)</bold>: based at the applicant institution, manages the technical, financial and administrative processes with the support of the partner institutions. The cooperation agreement of November 2020 serves as the legal basis for the cooperation and the transfer of funds. OpenProject (an enterprise licence that has been purchased together with other consortia) is being used to monitor the progress of work at the consortium level, in addition to a meeting and reporting system that ensures project control. TA1 organises two consortium meetings per year. Additionally, smaller retreats within and between TAs have been effective in driving developments. Four <ext-link ext-link-type="uri" xlink:href="https://www.nfdi4chem.de/the-advisory-boards/">Advisory Boards</ext-link> (National, International, Industry, and Publishers) have been established to provide advice and feedback at the consortium meetings. Communication within the consortium is based on regular meetings, mailing lists, and the chat tool Rocket.Chat. A strategic communication concept was initiated early on, including a corporate design and the <ext-link ext-link-type="uri" xlink:href="https://www.nfdi4chem.de/">website</ext-link>, which was launched in Q4 2021 and is frequently updated and expanded. It serves as a single point of information for the community and provides an overview of the consortium and all its services.</p>
        <p><bold>TA2 (Smart Lab)</bold>: Chemotion ELN and other tools in NFDI4Chem underwent substantial improvements in functionality and development approaches, facilitating the distribution and fostering their acceptance. Key achievements were reached with the establishment of a feasible Docker container approach for all institutions using the ELN (<xref ref-type="bibr" rid="B13577501">KIT Karlsruhe Institute of Technology 2024</xref>) and the adaptation of the ELN to the needs of different sub-disciplines. Highlights consist of new entities (<xref ref-type="bibr" rid="B13569096">Chemotion ELN contributors 2022</xref>), modules for inorganic and <ext-link ext-link-type="uri" xlink:href="https://github.com/ComPlat/Chemotion-Templates">polymer chemists</ext-link>, and flexible modules (<ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5281/zenodo.8305411">LabIMotion</ext-link>) (<xref ref-type="bibr" rid="B13553728">Huang and Lin 2024</xref>). TA2’s software development follows a defined workflow: planning, community consultation, coding, testing, and frequent releases (Chemotion core: 13 releases, NMRium wrapper and further tools: 28 releases in 2020-2024). Feedback via helpdesk and <ext-link ext-link-type="uri" xlink:href="https://github.com/ComPlat/chemotion_ELN">GitHub</ext-link> (582 resolved GitHub issues in 2020-2024) allows transparent activity tracking, requirement discussions and task allocation. TA2 improved and extended <ext-link ext-link-type="uri" xlink:href="https://www.chemotion.net/docs/eln/devices">device integration into the ELN</ext-link> (<xref ref-type="bibr" rid="B13569104">Starman 2023</xref>), improved data conversion from device-generated files to open, standardised formats with the <ext-link ext-link-type="uri" xlink:href="https://github.com/ComPlat/chemotion-converter-client">Converter software</ext-link>, and developed and harmonised software for reading, processing, visualising, and analysing multiple data types (<xref ref-type="bibr" rid="B13569112">Huang et al. 2021</xref>, <xref ref-type="bibr" rid="B13569122">Patiny et al. 2023</xref>). A comprehensive <ext-link ext-link-type="uri" xlink:href="https://www.chemotion.net/docs">online documentation</ext-link> describes features, methods, and videos for easy reuse of components. The data transfer and publication from the ELN to the repositories Chemotion and RADAR (<xref ref-type="bibr" rid="B13569154">Chemotion ELN contributors 2021</xref>, <xref ref-type="bibr" rid="B13569162">Tremouilhac et al. 2020</xref>) was established, and similar processes for other NFDI4Chem repositories are partly implemented (<xref ref-type="bibr" rid="B13577509">ComPlat 2024</xref>) and will be continued in FP2. The ELN developments are or will also be used by scientists in the consortia NFDI4Cat, DAPHNE4NFDI (<xref ref-type="bibr" rid="B13552916">Dolcet et al. 2003</xref>), and FAIRmat. Additionally, the work on ELN interoperability and data exchange will be continued to enable interdisciplinary work. In FP2, TA2 will add additional focus on enabling the re-use of the data in a machine-readable and actionable way, e.g. for AI projects. This investment will be returned to the ELN users who will benefit from ELN-enabled AI tools, creating incentives through advanced tools that support the scientists’ work.</p>
        <p><bold>TA3 (Repositories)</bold> successfully established a virtual environment of federated repositories that covers all subdisciplines and data types in chemistry with a focus on molecule-related data. The services are feature-rich, interoperable, trusted by the community, and recommended by journals and funding agencies. TA3 integrated important existing repositories that were selected based on quality criteria like functionality for users, suitability, open source accessibility, adherence to standards, and funding requirements. The repositories currently part of the NFDI4Chem federation are listed in TA3. Detailed information is summarised <ext-link ext-link-type="uri" xlink:href="https://www.nfdi4chem.de/repos/">on our website</ext-link> and in <xref ref-type="bibr" rid="B13520248">Bach et al. (2023)</xref>. Our knowledge base article <ext-link ext-link-type="uri" xlink:href="https://knowledgebase.nfdi4chem.de/knowledge_base/docs/choose_repository/">How to Choose the Right Repository</ext-link> guides researchers in choosing the right repository for their data type and needs. In addition, we evaluated other international repositories through <ext-link ext-link-type="uri" xlink:href="https://www.re3data.org/">re3data</ext-link> using criteria (<xref ref-type="bibr" rid="B13520269">Bonatto Minella et al. 2023</xref>) selected by TA3 in collaboration with other TAs. For FP2, we aim to grow the federation, and we have signed LoIs with CSD, ICSD, and CCDC Access Structures Service for crystallography for their integration with NFDI4Chem. All NFDI4Chem repositories were optimised for operational fitness, interoperability, metadata standards (developed by TA4) and harvesting, dataset landing pages and interfaces to services (e.g. NFDI4Chem Search Service). Concepts were developed to connect repositories with scientists' workspaces, enabling data transfer from the Chemotion ELN to the repositories. The <ext-link ext-link-type="uri" xlink:href="https://github.com/ComPlat/Repository-Tracker">repotracker</ext-link> software was developed to record and monitor data transfer processes. In collaboration with TA4, we decided on minimum information standards (<xref ref-type="bibr" rid="B13519322">Herres‐Pawlis et al. 2022</xref>) for the metadata of datasets in the repositories of our federation, based on DataCite. The <ext-link ext-link-type="uri" xlink:href="https://github.com/ER-FIZKarlsruhe/fiz-oai-provider">FIZ OAI-PMH provider</ext-link> and <ext-link ext-link-type="uri" xlink:href="https://github.com/ER-FIZKarlsruhe/fiz-oai-backend">backend</ext-link> software were published open source on GitHub and <ext-link ext-link-type="uri" xlink:href="https://github.com/ER-FIZKarlsruhe/fiz-oai-docker">integration help</ext-link> was made available to repositories. The relevance of TA3’s work can be seen in rising data publication numbers and recommendations by journals and funders, e.g., <ext-link ext-link-type="uri" xlink:href="https://onlinelibrary.wiley.com/journal/15213773">Angewandte Chemie</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://chemistry-europe.onlinelibrary.wiley.com/journal/14397633">ChemBioChem</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://pubs.acs.org/doi/10.1021/acs.jnatprod.3c00281">Journal of Natural Products</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://wissenschaftliche-integritaet.de/kommentare/elektronisches-laborjournal-und-repositorium-in-der-chemie/">DFG GSP</ext-link> (in German) (<xref ref-type="bibr" rid="B13579215">Wiley-VCH 2024</xref>, <xref ref-type="bibr" rid="B13569179">Proteau 2023</xref>).</p>
        <p><bold>TA4 (Metadata, Data Standards and Publication Standards)</bold> focuses on the development and harmonisation of minimum information (MI) standards and metadata for chemical research data, as well as data standards for molecules and reactions, including experimental and theoretical characterisation. We reviewed data standards and file formats (<xref ref-type="bibr" rid="B13574034">Rauh et al. 2022</xref>), and contributed relevant standards and formats to the EDAM ontology and to the FAIRsharing catalogue. In FP2, these can be the basis of chemistry software content in the Base4NFDI project nfdi.software. The development of MIChI guidelines is an ongoing process involving discipline-specific workshops, consensus on journal reporting standards and technical interoperability. In workshops, we have developed MIChIs for polymers and NMR, reports of which are available on the <ext-link ext-link-type="uri" xlink:href="https://www.nfdi4chem.de/index.php/reports-from-minimum-information-standards-workshops/">NFDI4Chem website</ext-link>. Based on these, TA2's LabIMotion extension allows the implementation of corresponding documentation templates, which are hosted on a <ext-link ext-link-type="uri" xlink:href="https://www.chemotion-repository.net/home/genericHub">template hub</ext-link> (<xref ref-type="bibr" rid="B13579223">Karlsruhe Institute of Technology (KIT) 2024</xref>) and may become documentation standards. Internationally, we work with IUPAC, the InChI Trust, and TA5 on the <ext-link ext-link-type="uri" xlink:href="https://iupac.org/worldfair-global-cooperation-on-fair-data-policy-and-practice">WorldFAIR initiative</ext-link> on a FAIR chemistry cookbook. Our involvement in the InChI Trust Organometallics Working Group has led to important developments in the international open molecular representation standard, including a non-disconnection approach. S. Herres-Pawlis currently serves as the leader of the unified InChI organometallics/inorganics working group and is a member of the InChI Trust Board. In FP2, we need to incorporate these improvements on the InChI for inorganics into our services. NFDI4Chem assisted the chemistry community and partners in preparing standards-compliant data publications in the Lead-by-Example measure. They are described in our <ext-link ext-link-type="uri" xlink:href="https://knowledgebase.nfdi4chem.de/knowledge_base/docs/datasets">knowledge base</ext-link> and serve as test data for service development (<xref ref-type="bibr" rid="B13520706">Fischer et al. 2023</xref>). These activities were successful and will be ramped down since self-service training material reduced the need for individual support. The <ext-link ext-link-type="uri" xlink:href="https://www.nfdi4chem.de/index.php/2021/11/23/1st-editors4chem-workshop/">Editors4Chem</ext-link> workshops with IUPAC in 2021 and 2023 involved publishers to integrate FAIR data recommendations into journal author guidelines. Our survey results on author guidelines in chemistry journals show (<xref ref-type="bibr" rid="B13574047">Parks et al. 2023</xref>, <xref ref-type="bibr" rid="B13521359">Parks et al. 2024</xref>) increased focus on research data guidelines. Feedback encourages us to continue with the Editors4Chem activities.</p>
        <p>In <bold>TA5 (Community and Training)</bold> we made significant efforts to facilitate a cultural shift towards FAIR RDM within the scientific community. We conducted two major surveys, the second with over 800 participants in 2023, which showed a gradual increase in the use of ELNs and strong support for the inclusion of RDM in curricula (for details, see 3.1 and <xref ref-type="bibr" rid="B13551429">Herres‐Pawlis et al. (2020)</xref>). We also gathered community requirements through conference booths and presentations on national and international conferences and workshops. A comprehensive communication strategy was implemented, including a regularly updated website, newsletters, social media outreach, and monthly digital “Stammtisch” (regulars’ table) meetings for discussion of RDM topics. Extensive training and support initiatives were launched, including the development of the NFDI4Chem Knowledge Base (400-500 visitors per month from all over the world, s. 4.4), bespoke RDM training modules, OER RDM materials and a helpdesk. Those measures with multiplicative effects will remain important in FP2, and the materials flow directly into the section EduTrain and the knowledge-graph-based DALIA platform for OER RDM materials. Curricular integration of RDM content was promoted through practical exercises in labs and lectures, and best practices were highlighted through use cases and flagship labs. The annually presented FAIR4Chem award highlights excellent FAIR data practices from the community for the community. We also initiated blind prediction challenges to improve reproducibility in experimental and computational workflows.</p>
        <p><bold>TA6 (Synergies and Cross-Cutting Topics)</bold> aims at a holistic use of the NFDI4Chem infrastructure and services with a special focus on data integration and semantics. During FP1, significant progress was made in cooperation with TA2, TA3 and TA4 in developing a joint strategy for ontologies and metadata standards to ensure seamless data integration within the NFDI4Chem service federation. The implementation of the metadata standards is closely related to the search service (<xref ref-type="bibr" rid="B13577183">TIB-Leibniz Information Centre for Science and Technology 2024a</xref>), which harvests and indexes metadata from currently 140,000 datasets in the NFDI4Chem repository federation. Initial harvesting included utilisation of the DataCite and Bioschemas JSON-LD formats. For the NFDI4Chem ontology collection, we conducted a thorough evaluation of ontologies in the chemistry domain and defined selection criteria (<xref ref-type="bibr" rid="B13568831">Strömert et al. 2022</xref>). We are continuously curating ontologies such as CHMO, MOP, RXNO, CHEMINF or the IUPAC Goldbook in collaboration with RSC, IUPAC and the OBO Foundry, and created the new Vibrational Spectroscopy Ontology (VIBSO <xref ref-type="bibr" rid="B13577477">Strömert et al. 2024c</xref>). We organised Ontologies4Chem workshops (<xref ref-type="bibr" rid="B13596187">Strömert et al. 2022a</xref>) in 2022 and 2023, with an average of 50 international participants. TA6 further developed the Terminology Service (TS <xref ref-type="bibr" rid="B13574190">Jupp et al. 2015</xref> During FP1, the TS was extended to become a central ontology management platform for chemistry ontologies (<xref ref-type="bibr" rid="B13568869">Strömert et al. 2023</xref>). TA6 further ensured NFDI4Chem’s participation and contributions to NFDI measures, NFDI basic services, and international networking, as described in chapters 3.2 and 3.3. TA6 evaluates its measures through KPIs like visits, API calls, and indexed repositories and datasets. The NFDI4Chem ontology collection is assessed against self-defined criteria, and its impact is measured by curation issues and pull requests. We also evaluate Ontologies4Chem output by participants and represented ontology projects. Additionally, published recommendations, best practices, and policies are assessed. In FP2, TA6 will integrate terminologies, the metadata schema service and chemistry knowledge graphs into the Semantic Data Hub as logical steps towards machine-actionable AI-ready chemistry data.</p>
      </sec>
      <sec sec-type="4.2 Metadata standards">
        <title>4.2 Metadata standards</title>
        <p>NFDI4Chem adopts and develops metadata standards associated with chemical research data, including information about molecules, reactions and processes, as well as data for their experimental and theoretical characterisation. As a fundamental molecular standard, IUPAC’s InChI is used to link data across repositories and as identifiers in molecular metadata. Moreover, the InChI key makes molecules searchable through generic search engines. NFDI4Chem has been intensively involved during FP1 in the development of the next version of the InChI by making the InChI FAIR and opening development via a public GitHub repository. The InChI code is guarded by the InChI Trust, of which S. Herres-Pawlis is a board member. For FP2, we will contribute to the implementation of inorganic stereochemistry into the InChI and the PolymerInChI (see T4.2.1). We are active in the European <ext-link ext-link-type="uri" xlink:href="https://bioschemas.org/">ELIXIR Bioschemas</ext-link> community, where S. Neumann has become co-leader of the chemicals working group. New Bioschemas profiles, such as for reactions, are under discussion to be specified and submitted to become an accepted standard. F. Bach is a member of the Technical Specification &amp; Implementation Group of the international <ext-link ext-link-type="uri" xlink:href="https://fairdo.org/">FAIR Digital Objects Forum</ext-link>. We contribute to curating the ELIXIR Toxicology Community collection on <ext-link ext-link-type="uri" xlink:href="https://fairsharing.org/3496">FAIRsharing</ext-link>.</p>
        <p>Looking at FAIR metadata with a special focus on Findability and Interoperability, NFDI4Chem utilises metadata standards in two ways: The integration of metadata into landing web pages of repositories or other services to ensure findability by data or general search engines utilising common schema.org or Bioschemas standards and the availability of structured, machine-readable metadata using various metadata content and serialisation schemes like DataCite, Dublin Core, DCAT accessible through a standard API like Open Archives Initiative Protocol for Metadata Harvest (OAI-PMH).</p>
        <p>At the beginning of FP1, RADAR4Chem and Chemotion Repository provided agnostic DataCite and Dublin Core metadata with limited chemical information implemented via an <ext-link ext-link-type="uri" xlink:href="https://www.openarchives.org/pmh/">OAI-PMH</ext-link> endpoint for metadata harvesting. Later on, we extended the XML-based OAI-PMH architecture (using the <ext-link ext-link-type="uri" xlink:href="https://github.com/ER-FIZKarlsruhe/fiz-oai-docker">FIZ-OAI provider</ext-link>) to provide JSON-LD format via OAI-PMH service, where it can be queried both as JSON-LD and via a crosswalk as OAI Dublin Core (<xref ref-type="bibr" rid="B13574209">Castro et al. 2023</xref>). MassBank embeds Bioschemas into the landing pages of the datasets, enabling web crawlers to access them. NmrXiv, the latest addition to the NFDI4Chem repository federation, provides experimental, extended Bioschemas to provide the chemistry-specific metadata. The search service applies different harvesting agents to gather metadata from these repositories and integrate it into the central search index. Additionally, the Search Service API provides all metadata of the federation in DCAT.</p>
        <p>Proceeding from this situation, further metadata integration and harmonisation strategy was drafted in collaboration between TA2, TA3, TA4 and TA6. Aspects covered were data structures and data export capabilities of ELN systems and data repositories, as well as the downstream data integration and indexing of the search service. For the various data types in the scope of NFDI4Chem, we facilitate the creation of Minimal Information of Chemical Information of Chemical Investigations (MIChI), integrating elements of general-purpose schemas followed by domain-specific additions.</p>
        <p>In the course of the MIChI development across the subdisciplines of chemistry, we identified and described various data structures with detailed information and the chemical context of the research data. With more and more MIChI evolving, we recognised chemistry core elements across the individual MIChI profiles. This led to the idea of defining a base profile for general chemical information that can be extended with discipline-specific modules. This modular design will enable NFDI4Chem to develop more tailored and adaptable metadata schemas, better serving the needs of various chemistry subdisciplines. With the goal to transform MIChI profiles, including ontological concepts from our NFDI4Chem ontology collection, into commonly used schemas like Bioschemas, we recognised that a significant amount of the newly defined detailed chemistry information could not be mapped adequately or at all. Both schema.org and the extended Bioschemas are, in the end, general schemas or a set of vocabularies with types and properties. In order to be able to meaningfully use the Bioschemas for our needs, it would therefore be necessary to extend it with new types and properties within the limits of its own semantic framework. To avoid these limitations (i.e., losing the expressivity of MIChI) during the integration, we have adjusted our general metadata strategy to harness the full potential of semantically rich chemistry-specific metadata schemas within the scope of chemistry and related disciplines and map to common metadata schemas like Bioschemas for broader dissemination of metadata across further communities to promote data discoverability. To adequately support discipline-specific metadata schemas for the community and metadata interoperability, we will introduce the Metadata Schema Service (MSS) in FP2. The service will fulfil several purposes: it will enable the MIChI teams to transform MIChI profiles into actionable metadata schemas, utilising semantic concepts from the terminology service into the schemas. Acting as a registry, the MSS stores MIChI-based schemas and makes them searchable. At a later stage, the MSS enables crosswalks between schemas, supported by the mapping services that use mappings between concepts.</p>
        <p>This strategy enables us to create and apply discipline-specific metadata schemas for chemistry research data. We utilise the full potential of semantically rich data to build chemistry knowledge graphs and apply reasoning on chemistry ontologies with extended logical axioms and still map these schemas to cross-domain ones like DataCite or Bioschemas. On the other hand, the strategy enables us to easily support common metadata standards like DataCite, Bioschemas or schema.org and broader dissemination across disciplines taking into account the recommendations on the Cross-Domain Interoperability Framework (CDIF) (<xref ref-type="bibr" rid="B13520070">Gregory et al. 2024</xref>).</p>
        <p>In FP2, we will further focus on machine actionability of data and metadata and follow national (e.g. SMART principles described in the <italic>German Standardization Roadmap on Artificial Intelligence</italic> (<xref ref-type="bibr" rid="B13574238">Wahlster and Winterhalter 2022</xref>), developed jointly by the German Institute for Standardization (DIN), German Commission for Electrical, Electronic &amp; Information Technologies of DIN and VDE (DKE) and Federal Ministry of Economic Affairs and Climate Action (BMWK).</p>
      </sec>
      <sec sec-type="4.3 Implementation of the FAIR principles and data quality assurance">
        <title>4.3 Implementation of the FAIR principles and data quality assurance</title>
        <p>NFDI4Chem endorses FAIR (meta)data across all task areas and services, ensuring consistent implementation through standards, policies and recommendations. Additionally, education and training (TA5) support community acceptance and understanding of the concept of FAIR data.</p>
        <p>To ensure <bold>Findability</bold>, all our services aim to provide rich, machine-readable (meta)data linked to domain-specific and cross-domain vocabularies. Our ELN and instrument integration strategy in TA2 promotes early metadata collection during data generation. Most NFDI4Chem repositories register their datasets with DataCite and assign globally unique and persistent DOIs. Most dataset landing pages of NFDI4Chem repositories already provide HTML-embedded metadata following <ext-link ext-link-type="uri" xlink:href="https://bioschemas.org/">Bioschemas</ext-link> (<xref ref-type="bibr" rid="B13553459">Neumann et al. 2023</xref>) and FAIR signposting (<xref ref-type="bibr" rid="B13574273">Van de Sompel et al. 2023</xref>) to increase findability via search engines such as Google Dataset Search.</p>
        <p>To ensure <bold>Accessibility</bold>, NFDI4Chem data are retrievable via persistent identifiers using HTTPS. All components are available under open-access models. For functions requiring login, established authentication protocols like OpenID and Shibboleth are used, with a planned migration to NFDI-AAI. NFDI4Chem repositories support OAI-PMH for programmatic access, and standardised APIs are provided or will be implemented (see TA3).</p>
        <p>To ensure <bold>Interoperability</bold>, our metadata and data adhere to existing standards. We address gaps by developing solutions discussed with the chemistry community, such as MIChI-based metadata standards for experiments, simulations, and molecule characterisation. NFDI4Chem promotes and extends open data formats (<xref ref-type="bibr" rid="B13574034">Rauh et al. 2022</xref>), implementing them systematically in our services. All components, from ELN to repositories, automate the collection of standardised data and metadata, ensuring interoperability. We use community-accepted toolkits like RDKit, CDK, and OpenBabel, as well as terms from established ontologies such as CHMO and RXNO. Automated conversion processes store data in standardised formats like JCAMP-DX. Integrated data editors ensure even proprietary inputs are stored in standardised, readable formats, producing interoperable information reusable in other systems, including repositories.</p>
        <p>To ensure <bold>Reusability</bold>, our (meta)data have accurate, relevant attributes conforming to domain-specific standards. We use established ontologies and develop our own, such as VIBSO, ensuring data is machine-readable. We prioritise openly licensed, well-maintained ontologies and integrate standards like ROR and GND into NFDI4Chem services. Data are released with clear, accessible usage licences supported by legal policies. NFDI4Chem repositories curate data and metadata to ensure reusability, with curation levels varying. For example, the Chemotion Repository is highly curated, while RADAR4Chem is mainly automatically checked. We also provide targeted datasets for machine learning and other support, facilitating data reuse.</p>
        <p>NFDI4Chem ensures data and metadata quality by different <bold>quality assurance</bold> measures.</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>The <bold>Minimum Information for Chemical Investigations (MIChI)</bold> define requirements on how to fully describe the various data types and serve as a reference.</p>
            </list-item>
            <list-item>
              <p>NFDI4Chem services capture or process data according to schemas derived from MIChI profiles. All data are <bold>captured in a structured manner</bold>, so both the presence of the data elements and their values can be verified. Wherever possible, data is collected applying subject-specific standards (e.g., MolFile and InChI for structures), allowing inputs to be assessed at least formally and often also in terms of their values. Additional tools (e.g., structure editors) are often required for data entry according to these standards; these tools are integrated into NFDI4Chem services, and their use within the services is harmonised.</p>
            </list-item>
            <list-item>
              <p>NFDI's services include automated data audit protocols. This allows the structured and standardised data to be tested for readability and reusability through processing and validation. By incorporating cheminformatics tools such as CDK or RDKit, the data captured or provided in the services (e.g., ELN or repositories) can be verified through simple plausibility checks using various inputs. Special checks can be carried out in, for example, Chemotion or nmrXiv, where developed tools compare the obtained experimental data to, e.g., simulated data. These and other verification procedures are particularly accelerated and improved in FP2 due to the rapid development of AI and the involvement of relevant experts in NFDI4Chem.</p>
            </list-item>
            <list-item>
              <p>NFDI4Chem services <bold>support multi-level data curation</bold>. Curation in NFDI4Chem repositories is partly organised by subject-specific and organisational responsibility (RADARChem) or by manual curation of the complete dataset by a fixed team of curators in Chemotion. All repositories already support or will support curation and commenting by the community, allowing for the control and correction of published data. This is accompanied by systematic versioning of datasets and metadata, either in whole or in parts.</p>
            </list-item>
            <list-item>
              <p>Users of NFDI4Chem services are supported by extensive training, primarily through TA5, preventing misuse, incorrect data input or annotation, and thus improving data quality. The knowledge base offers general data preparation guidance, while individual services provide specific instructions according to chemical community standards.</p>
            </list-item>
          </list>
        </p>
      </sec>
      <sec sec-type="4.4 Services provided by the consortium">
        <title>4.4 Services provided by the consortium</title>
        <p>Following the definitions in <xref ref-type="bibr" rid="B13521250">Amelung et al. (2023)</xref>, these services are developed and provided by NFDI4Chem:</p>
        <p>The <bold>NFDI4Chem Knowledge Base</bold> (N4C-KB) (<xref ref-type="bibr" rid="B13574321">NFDI4Chem 2024d</xref>), launched in late 2021, involves 21 contributors and offers various entry points based on the viewer's discipline, role, or specific interests. It covers a wide range of topics, from basic RDM concepts to more in-depth articles. The N4C-KB assists users in selecting the right data repository for their research data needs. Hosted at JGU and built using the open-source framework <ext-link ext-link-type="uri" xlink:href="https://docusaurus.io/">Docusaurus</ext-link>, the platform allows all content to be stored in a <ext-link ext-link-type="uri" xlink:href="https://github.com/NFDI4Chem/knowledge_base">GitHub repository</ext-link> using simple Markdown syntax. This approach makes it easy for authors to contribute without requiring web programming skills. The website is automatically updated with every change to the repository. The N4C-KB team actively supports contributors and accepts content in a variety of formats. Since 2023, N4C-KB has employed Matomo for privacy-friendly web analytics, showing that it is accessed by 400-500 persons per month.</p>
        <p>The <bold>Terminology Service</bold> (TS) (<xref ref-type="bibr" rid="B13574337">TIB-Leibniz Information Centre for Science and Technology 2024b</xref>), hosted by the TIB, is a comprehensive repository and curation platform for ontologies, terminologies and vocabularies in chemistry and related disciplines. As of August 2024, it contains 40 terminologies, selected based on criteria established by our Ontologies4Chem overview (<xref ref-type="bibr" rid="B13568831">Strömert et al. 2022b</xref>) and community approval (<xref ref-type="bibr" rid="B13596187">Strömert et al. 2022a</xref>). The TS provides advanced search, browse and access capabilities within these terminologies, providing rich metadata and information. Users can explore terminologies through graph or tree visualisations and access development and curation features. It facilitates connections to original terminology repositories, enabling term requests and comments as a step towards a comprehensive terminology curation platform. The TS plays a pivotal role in generating semantically annotated, machine-actionable data and provides a comprehensive API (<xref ref-type="bibr" rid="B13574361">TIB-Leibniz Information Centre for Science and Technology 2024d</xref>) for other NFDI4Chem services to integrate terminologies into their data annotation workflows, such as ELNs or data repositories. In addition, NFDI4Chem's Ontology Elements web components <xref ref-type="bibr" rid="B13574369">Venkata et al. (2023)</xref> provide an easy way to implement semantic annotation widgets using these terminologies. The TS is part of the basic service TS4NFDI backend architecture.</p>
        <p>NFDI4Chem drives the development and establishment of <bold>ELNs</bold> (<xref ref-type="bibr" rid="B13574379">NFDI4Chem 2024c</xref>) as a key requirement to achieve systematic digitalisation. While the developed ELN software is offered to users as source code to be hosted locally, there are three additional ELN-based services within NFDI4Chem:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>For IT staff and admins, a <ext-link ext-link-type="uri" xlink:href="https://github.com/ComPlat/chemotion-builder">Docker container</ext-link> service is provided to easily install the ELN with all required dependencies (<xref ref-type="bibr" rid="B13577501">KIT Karlsruhe Institute of Technology 2024</xref>). Management of single instances or multiple instances is supported by providing a <ext-link ext-link-type="uri" xlink:href="https://github.com/Chemotion/ChemOrc">command line interface</ext-link> (<xref ref-type="bibr" rid="B13574411">Chemotion ELN contributors n.d.</xref>).</p>
            </list-item>
            <list-item>
              <p>NFDI4Chem offers the hosting of four (five until the end of 2023) ELNs as <ext-link ext-link-type="uri" xlink:href="https://demo.chemotion.scc.kit.edu/">test instances</ext-link> that can be easily used by scientists looking for the right ELN solution. From more than 60 available ELN software tools, the four (five) most important OS solutions for chemists have been selected and are hosted for testing, comparison and educational purposes (<xref ref-type="bibr" rid="B13574419">NFDI4Chem 2024f</xref>).</p>
            </list-item>
            <list-item>
              <p>Chemotion ELN will be hosted as a service for individual researchers and small groups. The service is currently being set up. Initial pilot use cases with individual users and small groups are already underway in preparation for the full service. The service includes the migration of content to a local instance when a sustainable user group size is reached - which could be successfully completed with a first pilot user group in 2023.</p>
            </list-item>
          </list>
        </p>
        <p>The <bold>federation of core repositories</bold> (<xref ref-type="bibr" rid="B13574427">NFDI4Chem 2024b</xref>) comprises seven German-hosted repositories, each covering essential content in key subdisciplines of the chemical community. These repositories are developed and provided as individual services tailored to specific discipline-specific processes and functionalities driven by their respective communities. Within the NFDI4Chem federation, existing repositories adapt, and emerging repositories develop workflows, standards and functionalities to create a harmonised data infrastructure. This infrastructure aims not only at data interoperability but also at collaborative interaction between repositories and other NFDI4Chem services. The selected core repositories can handle different data types, chemical processes, analytical data and specialised methods, thus supporting the entire data landscape. The roles and requirements of these core repositories vary, with the first funding period focusing on strengthening existing repositories through strategic source code improvements for efficient development and stable hosting.</p>
        <p>To date, five NFDI4Chem repositories are in operational use. Of these, we describe RADAR4Chem, Chemotion repository, nmrXiv, and MassBank EU in more detail, as they are currently relevant to the widest user community, and major changes have been released.</p>
        <p><bold>RADAR4Chem</bold> (<xref ref-type="bibr" rid="B13578275">FIZ Karlsruhe – Leibniz-Institut für Informationsinfrastruktur GmbH 2024</xref>) is a feature-rich repository covering complex datasets from all domains of chemistry. Launched in March 2022, it offers free, versatile publication and storage options for any kind of chemistry-related data type. It has been developed by adapting the existing <ext-link ext-link-type="uri" xlink:href="https://www.radar-service.eu/radar/">RADAR</ext-link> service (DFG project 2013-2016). RADAR4Chem is crucial to filling gaps in discipline-specific repositories, allowing the publication of complex, heterogeneous, and large datasets, as well as long-term data preservation. A seamless data transfer from the Chemotion ELN to RADAR4Chem allows the publication of data collected in the ELN with just a few clicks.</p>
        <p>The <bold>Chemotion Repository</bold> (<xref ref-type="bibr" rid="B13579329">Karlsruhe Institute of Technology (KIT) 2024b</xref>) deals with data related to chemical reactions and chemical substances and was established at KIT in 2015, initially serving a narrow range of scientific data. Since then, it has evolved within NFDI4Chem to meet different scientific needs. It serves as a pilot for data transfer from ELN to repositories and will be adapted to manage data transfer to other suitable repositories for interoperability. Key milestones have been achieved in 2022 and 2023, including the development of tools such as the <ext-link ext-link-type="uri" xlink:href="https://github.com/ComPlat/Repository-Tracker">repo-tracker</ext-link> and <ext-link ext-link-type="uri" xlink:href="https://github.com/ComPlat/Repository-Downloader">repo-downloader</ext-link> software. It provides enhanced reporting capabilities and supports the publication of different data types with discipline-specific templates. NFDI4Chem funds its development, and the content of the repository is curated by in-kind contributions.</p>
        <p>The <bold>nmrXiv</bold> repository (<xref ref-type="bibr" rid="B13578408">nmrXiv Project Group 2024</xref>), hosted at FSU, is a new NMR spectroscopy data repository and analysis platform built from the ground up. It builds on the experience of its predecessor, nmrshiftdb2. nmrXiv is open, FAIR and consensus-driven, preserving both raw and processed NMR data. In July 2024, shortly after its release, it already contained 459 compounds with 2704 spectra organised in 45 projects. It provides DOIs, web UI and REST APIs (Open API, DataCite, Bioschemas, NMRium). nmrXiv follows the DataCite metadata schema, enhanced with InChI and SMILES. It uses two-factor authorisation and single sign-on with popular social network logins, including ORCID. Storage capacity is provided in-kind by FSU. nmrXiv is recommended for the deposition of NMR data associated with publications by a growing number of journals, including Angewandte Chemie and the Journal of Natural Products of the ACS.</p>
        <p><bold>MassBank EU</bold> (<xref ref-type="bibr" rid="B13579337">MassBank consortium 2024</xref>), hosted at the UFZ, is the first public repository of mass spectrometry data, facilitating its sharing with the scientific community. Since 2021, its compound dataset has grown to 15,075 (from 14,788) and its spectra to 90,190 (from 86,576) in 2023. MassBank uses GitHub for AAI (open read access, limited write access) and uses <ext-link ext-link-type="uri" xlink:href="https://github.com/MassBank/MassBank-web/issues">GitHub issues</ext-link> for curation tracking, which are managed by the <ext-link ext-link-type="uri" xlink:href="https://github.com/MassBank/validator-cli">MassBank record validator</ext-link>. Spectral data and metadata are stored in a human-readable record format within a revision control system, and continuous integration ensures record integrity with each change. NFDI4Chem funding has enabled a modern software overhaul, with a first development release using a JS-based front-end and a REST-based back-end.</p>
        <p><bold>Suprabank</bold> (<xref ref-type="bibr" rid="B13579345">Biedermann Labs 2024</xref>) is a specialised database, hosted at KIT since 2019, offering unique data on intermolecular and supramolecular interactions. It primarily addresses supramolecular and physical chemists as well as biologists in organic chemistry, focusing on binding, assembly and interaction phenomena not found in other repositories.</p>
        <p><bold>STRENDA DB</bold> (<xref ref-type="bibr" rid="B13579381">Beilstein-Institut zur Förderung der Chemischen Wissenschaften 2024</xref>), established in 2016 and operated by BI, is a well-established repository for enzymology data. It collaborates with over <ext-link ext-link-type="uri" xlink:href="https://www.beilstein-institut.de/en/projects/strenda/journals/">55 international biochemistry journals</ext-link> and has integrated the STRENDA guidelines into its author instructions. The database ensures the completeness and validity of enzymology data prior to submission for publication. It primarily contains functional enzymology data, including kinetic and experimental data. STRENDA DB is an in-kind contribution.</p>
        <p>In addition to the services available in production mode, the <bold>VibSpecDB</bold> repository, focusing on Raman and IR spectra, is under development and will publish the first prototype in FP1.</p>
        <p><bold>NOMAD</bold> (<xref ref-type="bibr" rid="B13579431">Scheidgen et al. 2023</xref>) plays a pivotal role in theoretical and computational chemistry, bridging the gap to material sciences. Although they are no longer represented by an institutional partner in NFDI4Chem, we continue to collaborate closely to evaluate data exchange interfaces and co-design functionalities (see LOS NOMAD). This cooperation will significantly benefit both communities, facilitating interdisciplinary use cases and advancing scientific research.</p>
        <p>The <bold>Search Service</bold> by TIB (<xref ref-type="bibr" rid="B13574444">TIB-Leibniz Information Centre for Science and Technology 2024c</xref>), which was released in the summer of 2022, acts as a central hub for searching the federated repositories of NFDI4Chem. It currently includes ~140.000 datasets from the Chemotion Repository, MassBank, nmrXiv and RADAR4Chem. The integration of the chemistry sub-collection of DaRUS marks the first integration of datasets from a generic data repository. The service regularly harvests and indexes metadata, handling different metadata models and protocols It enhances them with chemical metadata, enabling searches by chemical structure codes like InChI, molecules and analytical methods. The metadata and search capabilities are continuously adapted to the latest MIChi and metadata schema releases to increase the granularity of discipline-specific metadata.</p>
        <p>The <bold>NFDI4Chem Helpdesk</bold> (<xref ref-type="bibr" rid="B13574452">NFDI4Chem 2024a</xref>) serves as a central hub for community requests. It provides efficient support for all NFDI4Chem services and RDM topics. Basic issues and common questions are handled by first-level support, while specialised second-level teams of the corresponding services handle complex cases. The Helpdesk streamlines communication with our user community, collects common queries in the N4C-KB for proactive solutions and is hosted by TIB, supported by teams from JGU, FSU, TuBr, KIT and RWTH.</p>
        <p>NFDI4Chem offers <bold>workshop series on general chemistry RDM and Chemotion ELN / LabIMotion</bold> (<xref ref-type="bibr" rid="B13578424">NFDI4Chem 2024h</xref>, <xref ref-type="bibr" rid="B13578432">NFDI4Chem 2024i</xref>, <xref ref-type="bibr" rid="B13578440">NFDI4Chem 2024j</xref>), which can be tailored to the needs of working groups and institutions. During FP1, 73 workshops were conducted with over 800 active participants (for details, see 3.1).</p>
        <p>The <bold>Metadata Schema Service</bold> will be newly developed in FP2, acting as a repository for MIChI-based metadata schemas. The service will enable users to create, store, browse and re-use schemas. A corresponding API allows services to perform metadata validation and schema crosswalks.</p>
        <p>The <bold>Chemistry Knowledge Graph</bold> will be a new service developed in FP2. The knowledge graph will be fed by the search service providing harmonised, semantic rich data streams from the NFDI4Chem service federation. Besides SPARQL endpoints the service will provide an easy-to-use visual interface to query Chemistry Knowledge Graph.</p>
      </sec>
    </sec>
    <sec sec-type="5. Work Programme ">
      <title>5. Work Programme</title>
      <p>The consortium’s work is divided into six primary task areas (TAs) with several measures each (see Table <xref ref-type="table" rid="T13519834">1</xref>), focusing on specific aspects of the infrastructure development and implementation (see Fig. <xref ref-type="fig" rid="F13519929">3</xref> below).</p>
      <p><bold>TA1 Management</bold> oversees the administrative, financial, and technical management of the consortium. It coordinates consortium activities, manages funds, ensures compliance with legal and ethical standards, and facilitates communication among partners.</p>
      <p><bold>TA2 Smart Lab</bold> develops and implements digital tools and environments for efficient data capture and management in laboratories necessary to capture data early in the life cycle. It creates and enhances electronic lab notebooks (ELNs), integrates laboratory instruments, and develops workflows that facilitate seamless data transfer and interoperability within the infrastructure.</p>
      <p><bold>TA3 Repositories</bold> develops and evolves a federated system of repositories to store, share, and preserve chemical data. This includes raw data in diverse formats as well as curated datasets. It develops and maintains core repositories like RADAR4Chem, Chemotion, and nmrXiv, ensuring they meet the needs of various subdisciplines in chemistry. It facilitates data deposition, retrieval through standardised protocols, and re-using research data across distributed data services.</p>
      <p><bold>TA4 Metadata, Data Standards, and Publication Standards</bold> defines and implements standards for metadata and data formats to ensure consistency and interoperability, together with reference implementations and data validation. Ontologies are used where possible, and missing terminological artefacts are added. It develops minimum information standards, harmonises metadata practices, and collaborates with international organisations like IUPAC to adopt and foster global standards.</p>
      <p><bold>TA5 Community and Training</bold> fosters a culture of effective data management practices within the chemical research community. It conducts training workshops, develops educational materials, and engages with researchers to promote the adoption of RDM practices and offers incentives for innovations. It is present at chemical conferences with booths and talks and maintains multiple active communication channels to disseminate information and collect the community’s requirements, needs and feedback.</p>
      <p><bold>TA6 Synergies and Cross-Cutting Topics</bold> develops and provides the Terminology Service, Metadata Schema Service, Search Service and Chemistry Knowledge Graph. It develops, curates ontologies and promotes their use in conjunction with semantic technologies to enhance data interoperability, machine-actionability and AI-readiness. Through these means, TA6 ensures the harmonisation of various components of the NFDI4Chem infrastructure. It further coordinates with other NFDI consortia, sections, and working groups on cross-domain metadata standards, cross-domain development, ontologies mapping, and terminology services development. TA6 ensures collaboration with international bodies such as the Research Data Alliance (RDA) or the International Union of Pure and Applied Chemistry (IUPAC) and relevant projects like the Physical Sciences Data Infrastructure (PSDI) in the UK.</p>
      <p>The NFDI4Chem consortium is making significant progress in building a national research data management infrastructure for chemistry in Germany. These efforts are already advancing chemical research and ensuring that data are managed efficiently, shared openly, and utilised to their full potential.</p>
      <sec sec-type="5.1 TA1 Management">
        <title>5.1 TA1 Management</title>
        <p><bold>TA1</bold> provides adequate and lean leadership and support to all task areas in achieving their objectives. The highly collaborative and distributed nature of NFDI4Chem calls for an effective management structure and a sound decision-making process to be in place to ensure efficient planning and controlling of project activities, seamless communication across partners, balance multiple responsibilities and competing priorities of consortium partners, prompt reporting and finally, successful project delivery. The overall management structure is illustrated in Fig. <xref ref-type="fig" rid="F13519929">3</xref>. The details of the distinct levels and responsibilities of the management are discussed below.</p>
        <p>The Project Office (PO) is located at the Friedrich-Schiller-University (FSU) in Jena, where space and facilities are available for administrative purposes. The PO supports the Project Speaker as well as the steering committee in the day-to-day operational management of the project and handles administrative management, compliance with contractual obligations of the Consortium Agreement, and the correct dissemination and exploitation of the project results. The PO is also responsible for the appropriate communication with the consortium and the DFG and will handle the financial administration and safeguard the adequate execution of the project budget. The PO will manage and monitor the project's progress to meet the project objectives and handle time and resource constraints appropriately.</p>
        <p>Prof. Steinbeck heads the PO and consists of the project management team with a project manager exclusively hired for this project, experienced staff from the FSU administrative and financial team, the FSU funding coordinator, Dr Margull and the FSU press office as required during the course of the project. The PO guarantees adequate administrative project control, coordination of reporting, and care of financial and budgetary matters.</p>
        <p>In the consolidation phase of the project, TA1 will focus on integrating the progress and achievements of the past years into a cohesive framework that ensures sustainability and long-term impact. This involves harmonising the work of various TAs, streamlining processes, and reinforcing the collaborative infrastructure established during the initial phase. By consolidating our efforts, we aim to enhance the efficiency and effectiveness of project activities. Additionally, consolidation will facilitate the transfer of knowledge and best practices across the consortium, enabling continuous improvement and innovation. This phase is crucial for maintaining momentum and preparing for future project extensions, allowing us to address new challenges and opportunities with a robust, unified approach.</p>
        <p>To summarise, the <bold>objectives</bold> of TA1 are:</p>
        <p><bold>O1.1</bold>: Efficiently manage the consortium activities to maximise NFDI4Chem's impact and ensure future sustainability. If necessary, handling time and resource adjustments appropriately.</p>
        <p><bold>O1.2</bold>: Organise and document all NFDI4Chem services, consortium, advisory board, stakeholder meetings and decision-making processes, and regular staff exchanges between the NFDI4Chem partners in collaboration with our consortium partners.</p>
        <p><bold>O1.3</bold>: Safeguard compliance with the contractual obligations of the Governance Model and correct dissemination, exploitation and monitoring of the project results.</p>
        <p>These objectives will be pursued through the following <bold>measures</bold>:</p>
        <p>
          <bold>M1.1: Overall legal, contractual, ethical, financial and administrative management of the consortium</bold>
        </p>
        <p><bold>Goals</bold>: Ensure the legal and financial operation of the consortium</p>
        <p><bold>Description</bold>: This measure will deal with the management of the project funding and the monitoring of the decision-making procedures, always in compliance with contractual obligations under the consortium agreement and the DFG regulations.</p>
        <p>
          <italic>T1.1.1 Negotiate and conclude a consortium agreement with all partners</italic>
        </p>
        <p>A consortium agreement will be negotiated with all partners to ensure a legally sound distribution of funding from the funder via the FSU to all co-applicants and participants. The consortium agreement will further set the framework for the successful project implementation and set out the rights and obligations between the partners.</p>
        <p>
          <italic>T1.1.2 Transfer of annual budget to partners. Retrieve and collate reports on the use of financial resources by partners</italic>
        </p>
        <p>Based on the transfer agreement negotiated above, the FSU administration will ensure the timely and correct transfer of funds to all partners. We will also collect all information for the reporting required by the DFG.</p>
        <p>
          <italic>T1.1.3 Maintain communications with the NFDI headquarters and the DFG</italic>
        </p>
        <p>This task comprises regular reporting to and communication with the DFG and the NFDI headquarters. Reporting to the DFG will adhere to their rules of resource usage.</p>
        <p>
          <bold>M1.2: Coordination at consortium level of the technical, outreach, training activities and their future sustainability</bold>
        </p>
        <p><bold>Goals</bold>: Ensure the timely and precise execution of the work plan through effective and agile management of a highly distributed project.</p>
        <p><bold>Description</bold>: The NFDI4Chem speaker, assisted by the project manager for day-to-day management of the project, will be closely monitoring and coordinating the activities of the consortium based on the work plan laid out in this proposal and harmonise the work of the TAs.</p>
        <p>
          <italic>T1.2.1 Organise consortium and TA meetings and harmonise work among TAs</italic>
        </p>
        <p>As part of this task, the PO will organise weekly tele-meetings of the NFDI4Chem steering committee. Discussions and decisions will be minuted and, if applicable, communicated to the consortium or other partners involved. We will invite national and international collaborating PI’s to participate if needed. Technical teleconferences of the TA participants and leads will be held separately and likewise individually documented. Those meetings will be organised by the respective project manager of the TA. Joint meetings of two or more TAs will increase in number and intensity in order to harmonise the work of the TAs and ensure effective long-lasting cooperation efforts in overarching topics. For day-to-day communication among NFDI4Chem participants, a chat platform is used, which is self-hosted at FSU to ensure cost-effective and sustainable use of this communication platform.</p>
        <p>
          <italic>T1.2.2 Organise and document advisory board meetings for NFDI4Chem</italic>
        </p>
        <p>The composition of the Advisory Boards (ABs) as formed during the first funding period will be critically reviewed and, if necessary, adapted. We will maintain communication with the Advisory Boards through meetings which will be held at least annually. ABs will be invited to join the annual consortium meetings organised in this TA. AB’s will be consulted for advice on questions of strategic importance for NFDI4Chem and their advice will be evaluated within the consortia and with neighbouring consortia as well as used to steer the future directions of NFDI4Chem.</p>
        <p>
          <italic>T1.2.3 Day-to-day management of the NFDI4Chem project</italic>
        </p>
        <p>This task will be dedicated to the execution of the work <bold>plan</bold> as laid out in this proposal. At the beginning of the project we will produce a <bold>detailed project plan</bold> which will include a list of success indicators to monitor during the whole project, as well as the data we will gather that will help in assessing its impact. These indicators and metrics will be reported at least in the quarterly flash reports and in the annual meetings, and will be fed into the reporting system described in Task 1.3.3. The project plan will <bold>organise</bold>, focus, continually motivate, and empower the project staff to do their work. It will perform <bold>controlling</bold> of the project, by tracking the work and comparing it and results against the work plan. It will use information from these tracking efforts to make changes to plans when the information suggests that a change is called for. It will continuously monitor project risks and mitigate them if necessary.</p>
        <p>
          <bold>M1.3: Coordination of long-term knowledge management, internet publishing system and other innovation-related activities</bold>
        </p>
        <p><bold>Goal</bold>: The chemistry community, the consortium, the NFDI as a whole, and other stakeholders will be holistically informed about the work of NFDI4Chem</p>
        <p><bold>Description</bold>: Efficient, complete and accessible information about NFDI4Chem’s work, progress and results will be maintained and disseminated via our NFDI4Chem central web portal, service portals, and social media. This will allow our users and stakeholders, the consortium, the NFDI as a whole as well as the wider public to evaluate our progress and best use our services in the long term.</p>
        <p>
          <italic>T1.3.1 Maintain and host an informative portal</italic>
        </p>
        <p>The NFDI4Chem portal at https://www.nfdi4chem.de/ will be maintained in close coordination with the project’s community and training activities (e.g., M5.2 and M5.3). <bold>The NFDI4Chem portal is the single point of access for user services and information</bold>. Most prominently, it will provide access to the catalogue of services provided by NFDI4Chem. Secondly, the Knowledge Base (see T5.3.1), which contains documentation, resolutions, workarounds, and best practices for the NFDI4Chem services and tools, which support both helpdesk staff and users, will constantly be expanded. Each tool will be well documented and accompanied by didactically structured online manuals and multimedia web tutorials that allow our users to learn how to use our tools themselves. This ensures the long-term usability of our tools when the expected increase in the number of users can no longer be fully instructed through in-person training.</p>
        <p>Thirdly, users will find help through a ticketing system by the RDM helpdesk unit (see T5.3.4)</p>
        <p>For the consortium, the portal allows for content management by the partners and employs additional components e.g. calendar, portal searches, as well as advanced analytics, functional testing, and communication via mailing lists.</p>
        <p>
          <italic>T1.3.2 Maintain full documentation of all NFDI4Chem activities</italic>
        </p>
        <p>The policies, standards and workflows developed in this endeavour will be formally documented and published in the form of manuals, white papers and recommendations. Any document created under this umbrella will be released under a Creative Commons License to allow for barrier-free dissemination and long-term availability for our target communities.</p>
        <p>
          <italic>T1.3.3. Develop and maintain a sustainable reporting system</italic>
        </p>
        <p>A sustainable reporting system will be established to continuously improve the consortium’s services, monitor our own governance structure and work progress, and meet the increasing quantitative evaluation requirements from external stakeholders. To this end, automated read-out of indicators will be established for all NFDI4Chem services. The data will be aggregated into a database set up in close collaboration with the NFDI e.V. and all other consortia. A central publicly available library with all written publications, media and software items of NFDI4Chem will allow consortium members and our target audience to view the consortium’s output at a glance.</p>
        <p>
          <bold>M1.4: Overseeing the promotion of equal opportunity in the project</bold>
        </p>
        <p><bold>Goals</bold>: Ensure that minorities, e.g. female researchers, are provided with equal opportunities in the project.</p>
        <p><bold>Description</bold>: Equal opportunities are a central part of the staff development strategy in modern institutions. This comprises the support of recognised minorities in general and female researchers in particular. Data Science, Cheminformatics, and even more so computer science experience an underrepresentation of female developers and researchers. The promotion of equal opportunity for minorities in science is, therefore, an important component of NFDI4Chem management.</p>
        <p>
          <italic>T1.4.1 Promote and optimise equal opportunity measures across NFDI4Chem</italic>
        </p>
        <p>We will collect and report information about efforts to improve the provision of equal opportunity across the project. Based on this information, we will constantly aim to improve our way of working and advertising towards better provision of equal opportunity.</p>
        <p>Table <xref ref-type="table" rid="T13519835">2</xref></p>
      </sec>
      <sec sec-type="5.2 TA2: Enabling digitalisation for chemists: Smart Lab">
        <title>5.2 TA2: Enabling digitalisation for chemists: Smart Lab</title>
        <p>The overarching aim of <bold>TA2</bold> is to develop and provide a modular lab environment composed of concepts, services, and software to fully digitalise research data management. The key aspect of work in TA2 is a modular approach to the software design with open, well-described interfaces, enabling a flexible combination of all developments with different NFDI4Chem or external services. In FP1, most of the basic features for the envisaged Smart Lab concept have been identified, designed, developed and deployed. In FP2, we will improve, adapt, extend, and add to the bundle of these developments to complete and optimise the Smart Lab functionalities. We will continue to establish a robust infrastructure, including state-of-the-art scientific tools, and will implement concepts for continued updates with less dependence on NFDI4Chem and institutional funding. TA2 includes all software developments and solutions that are close to the community in the sense that they form the work instruments that are used for the scientists’ daily work. To this end, work packages from the other TAs are implemented within TA2 and its work spans the full range of solutions: data acquisition from different devices, collection of experimental and computational data, capture of metadata, management and analysis of data, and finally, its storage in repositories. With this, TA2 aims to solve the technological challenges that currently hinder digital availability, storage, and seamless data transfer in chemistry laboratories. Further, enabling the transfer of FAIR data to repositories and databases through standardised interfaces, a prerequisite for automated data processing applications, promotes innovative applications such as developing machine learning (ML) approaches. Smart Lab with full device integration requires decentralised architecture and institutional hosting, though it can also take the form of a centrally hosted virtual lab environment i.e. ELN-as-a-service usage model, if institutional hosting is not viable.</p>
        <p>TA2 was and will be deeply embedded into the work of NFDI4Chem: TA2 strongly collaborates with the services in TA3 to provide the data in a FAIR way, adapted to the specific needs of the repositories. It provides fundamental concepts and information for TA4 to accelerate MIChI development and modelling of metadata (see M4.1), and it implements the results of TA4 in the form of standardisation processes. TA2 feeds its new developments and solutions into TA5, providing input for teaching and training materials (see M5.3). Finally, TA2 implements the work of TA6, e.g., by translating ontologies into ELN workflows. All these measures are and will be elaborated in close collaboration among participating scientists, developers, and institutions. At present, TA2 gets its requirements from and designs the suggested concepts with the support of scientists from the subdisciplines of</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>organic,</p>
            </list-item>
            <list-item>
              <p>inorganic,</p>
            </list-item>
            <list-item>
              <p>polymer,</p>
            </list-item>
            <list-item>
              <p>physical,</p>
            </list-item>
            <list-item>
              <p>medicinal and pharmaceutical,</p>
            </list-item>
            <list-item>
              <p>biological, and</p>
            </list-item>
            <list-item>
              <p>analytical chemistry. The subdisciplines</p>
            </list-item>
            <list-item>
              <p>photo- and electrochemistry,</p>
            </list-item>
            <list-item>
              <p>environmental chemistry, and</p>
            </list-item>
            <list-item>
              <p>theoretical chemistry became strongly engaged during FP1 and will be especially strengthened through tasks in FP2.</p>
            </list-item>
          </list>
        </p>
        <p>TA2 will contribute to the key objectives KO1, KO2, KO3, and KO6. More specifically, the <bold>objectives</bold> of TA2 are:</p>
        <p><bold>O2.1</bold>: Development of a digital research environment (Smart Lab) that provides all functions to collect, manage, store, analyse, and share data. The Smart lab includes an ELN as a modular platform for all subdisciplines in chemistry that allows for the integration of devices, use of external resources, and transfer of data to repositories.</p>
        <p><bold>O2.2</bold>: Creating feedback-driven, easy-to-use software solutions that accelerate scientific work and foster the use of the NFDI4Chem infrastructure by scientists.</p>
        <p><bold>O2.3</bold>: Support the provisioning of high-quality FAIR data to enable reuse cases that scientists can benefit from and which generate incentives such as data comparison, systematic analysis, and aiding AI initiatives.</p>
        <p><bold>O2.4</bold>: Making the components of the Smart Lab available to all scientists in Germany and beyond who currently lack suitable means to make their data FAIR.</p>
        <p>Fig. <xref ref-type="fig" rid="F13519931">4</xref></p>
        <p>
          <bold>M2.1: Device integration and management</bold>
        </p>
        <p><bold>Goals</bold>:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>Extend the applicability of our existing concepts to integrate scientific devices into a digital workflow using modular, open-source solutions available to all research institutions.</p>
            </list-item>
            <list-item>
              <p>Inclusion of standards for data management, such as LADS to reduce customisation.</p>
            </list-item>
          </list>
        </p>
        <p><bold>Description</bold>: Devices play a pivotal role in the experimental work environment of a chemistry laboratory by conducting experiments, recording data, and analysing results. In the FP1, many device types, including legacy devices, have been made accessible, such as those for HPLC, NMR, UV, or IR, MS, and many others (<xref ref-type="bibr" rid="B13521065">Jung et al. 2024</xref>). The developed solutions were made available by provisioning software at different universities and documenting the processes (<xref ref-type="bibr" rid="B13553625">Herrmann et al. 2023</xref>). In FP2, we will extend the available methods to meet the requirements of techniques in different fields of chemistry. We will refactor and extend the established mechanisms, simplifying integration, improving stability and increasing the performance of these mechanisms to transfer data (T2.1.1). New methods allowing the transfer and inclusion of information from large datasets need to be designed and developed (T2.1.2). With regard to user applications, we will allow LIMS-like data management and remote control of devices by a comprehensive interface (T2.1.3).</p>
        <p>
          <italic>T 2.1.1 Data availability and data transfer</italic>
        </p>
        <p>A suitable data transfer strategy to access and transfer data to an institutional server in a flexible and extendable manner was developed in FP1. In FP2, the approach will be improved to implement a less resource-intensive process that extends the capabilities of data transfer while augmenting the functionality of the current system. The middleware, which is used to collect data before assigning it to an ELN, will be enhanced so that it makes use of the ELN’s API to transfer the data directly. We will continue to develop data transfer solutions for all required devices in chemistry, describing the individual process and the generic approach that allows the reuse of developed protocols, strategies, code, and documentation. The efforts will be prioritised based on the evaluation of user requests. In parallel, we will support data transfer standards (<xref ref-type="bibr" rid="B13578448">OPC Foundation 2024</xref>) recommended by diverse stakeholders in academia and industry - allowing for simplified solutions for an increasing number of devices in the long run.</p>
        <p>
          <italic>T2.1.2 Metadata strategies for large data</italic>
        </p>
        <p>Current strategies for the work with data and metadata in TA2 of NFDI4Chem are based on data which is of small to medium size (up to 1GB per data file), but increasingly, scientists need a systematic strategy to also manage large data (several GBs to TBs per dataset) in a suitable way. Currently, this is problematic in terms of resource intensity and performance. A solution is to link large data to the original source and a parallel approach to capture the relevant metadata. Such an approach needs concepts that enable the extraction of metadata (in close interaction with M4.2) and the provision of selected metadata (files) depending on data type, instrument, and its software. In FP2, the OS software ChemConverter (work of FP1) will be systematically extended to support the required routines for large data either on local institutional instruments or external clusters in FP2.</p>
        <p>
          <italic>T2.1.3 D ata management</italic>
        </p>
        <p>Within FP1, routines to monitor new incoming data on the registered data server(s) and its subsequent assignment to responsible scientists and the semi-automatic assignment to experiments in a lab were implemented. As a result of user feedback in FP1, options to transfer data collected using mobile devices were developed. In FP2, we will</p>
        <p>
          <list list-type="bullet">
            <list-item>
              <p>generalise and consolidate our current strategies to extend the capability from our first use case (i.e. scale recording) to different techniques (e.g. elemental analysis date),</p>
            </list-item>
            <list-item>
              <p>build a data manager directly in the ELN, and</p>
            </list-item>
            <list-item>
              <p>introduce a sophisticated UI that can be used to plan, record, and visualise data analysis workflows for samples.</p>
            </list-item>
          </list>
        </p>
        <p>
          <bold>M2.2: Establishment and maintenance of the electronic lab notebook</bold>
        </p>
        <p><bold>Goals</bold>:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>Extension and improvement of the functionality of the Chemotion ELN as a component of the open, modular virtual lab environment.</p>
            </list-item>
            <list-item>
              <p>Efficient coordination and management of the ELN development team and the code contributions.</p>
            </list-item>
          </list>
        </p>
        <p><bold>Description</bold>: Within M2.2, the core software of the ELN Chemotion will be improved, extended, and continuously upgraded. This measure was the basis of further work on the ELN in FP1 and will remain an important aspect of the work in TA2 in FP2 as a prerequisite for an up-to-date secure codebase. Additionally, continued maintenance of the core system greatly enhances its stability, flexibility and performance in the long run. The work within M2.2 will include the tasks that need to be developed and supported in a general manner to ensure the success of all ELN modules. The results will be parts of the main software i.e. components that are adaptable and usable in different scenarios. The seven tasks are designed to achieve sustainable software, especially T2.2.1 and T2.2.2, which is necessary for a code of the size and importance of Chemotion ELN. We also aim to deliver present and future (during FP2) user feedback, with features already in the design stage.</p>
        <p>
          <italic>T 2.2.1 Basic ELN structure, coordination of functions and final code</italic>
        </p>
        <p>In T2.2.1, the basic ELN structure will be maintained by planning and incorporating changes and adaptations, and the work of all tasks related to Smart Lab topics will be managed. The key aspects of T2.2.1 are the coordination and harmonisation of the activities of all developers at different sites in Germany, the planning of resources, the assignment of coding tasks, the organisation of code review and the supervision of the quality of the code. During FP1, a systematic approach of accepting code into the main codebase after review and then following its impact on a subset of users (alpha/beta testing) was put in place. In FP2, we will improve this process by using the industry standards of continuous integration and continuous delivery (CI/CD). Code is managed publicly via GitHub, including not only communication and planning between developers but also the collection of feedback from users and tracking of bugs &amp; issues. T2.2.1 ensures the onboarding and training of programmers within the group as well as maintaining ELN’s user-facing documentation reflecting the changes and new features.</p>
        <p>
          <italic>T2.2.2 Maintenance, upgrades and updates</italic>
        </p>
        <p>The ELN codebase has dependencies in the form of other OS software and libraries, such as the backend framework called <italic>Ruby on Rails</italic> and various frontend JavaScript libraries, which are used to buttress the usefulness of the ELN. These need to be maintained, routinely upgraded and updated to ensure the software's functionality, security, longevity and performance. The steps for the required upgrades (at least two per year) include automated monitoring and, when possible, fixing of security issues as well as a manual intervention to ensure proper integration and functionality, integration of major changes to the codebase, e.g. those brought in by the addition of new features, thorough testing, as well as additional maintenance tasks to ensure the stability and security of the ELN. Additionally, the ELN relies on the database software PostgreSQL, for which updates should be applied promptly, including reviewing and potentially modifying queries and schemas. Those changes need to be transcribed into the ELN’s codebase, and the related automation scripts need to be provided to the ELN user/administrator community.</p>
        <p>
          <italic>T2.2.3 Coding of extensions for basic functions</italic>
        </p>
        <p>The basic functions for the ELN have been continuously improved and extended during FP1, e.g., with single sign-on options (v1.6.0 <xref ref-type="bibr" rid="B13569096">Chemotion ELN contributors 2022</xref>), a simple Python API client (<xref ref-type="bibr" rid="B13578456">Starman et al. 2024</xref>), seamless integration of the LabIMotion extension (v1.8.0 <xref ref-type="bibr" rid="B13569096">Chemotion ELN contributors 2022</xref>), and an advanced search interface for users (v1.9.0 <xref ref-type="bibr" rid="B13569096">Chemotion ELN contributors 2022</xref>). In FP2, the work plan includes</p>
        <p>
          <list list-type="bullet">
            <list-item>
              <p>extending the admin interface into a more fine-grained roles-based model to support diverse AAI functions,</p>
            </list-item>
            <list-item>
              <p>adaptation of the ELN according to the needs of practical courses and other special environments,</p>
            </list-item>
            <list-item>
              <p>implementing a comprehensive tracking system,</p>
            </list-item>
            <list-item>
              <p>designing, developing, and implementing an additional ELN-embedded database for measurement values enabling enhanced searchability of analytical results and better provisioning of data for AI models.</p>
            </list-item>
          </list>
        </p>
        <p>These subtasks are dictated by users’ requirements which we continuously continue to monitor in FP2 to include newer requirements into the development strategy with the support of TA4 and TA5.</p>
        <p>
          <italic>T2.2.4 Rework of UI and UX</italic>
        </p>
        <p>An intuitive user interface (UI) and a well-designed user experience (UX) are the keys to successful software. During the FP1, the functions and representations within Chemotion ELN increased in almost all aspects, bringing complexity and new UI constraints that need to be resolved to improve UX. Due to the already visible limitations of the current UI framework and, again, driven by user feedback, we started to upgrade the existing libraries and designed a new UX concept with the support of external UX experts for the most relevant aspects of the ELN. The implementation of the resulting design and extending its scope to all areas of the ELN, alongside continuous fixing of UI and UX issues, will be part of FP2.</p>
        <p>
          <italic>T2.2.5 Interfaces</italic>
        </p>
        <p>APIs allow the ELN to communicate with other internal and external services using a well-documented versioned schema. Chemotion ELN already uses different APIs to exchange data with additional toolkits (Biostats, PhysStats, TLC-App), databases (PubChem, SciFinderN, CAS Common Chemical API), and services (TIB’s terminology service, RADAR4Chem repository, Chemotion repository, CrossRef). We will have four main subtasks in T2.2.5 during FP2:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>Consolidation of all existing and new interfaces to a strategic subtask within T2.2.5,</p>
            </list-item>
            <list-item>
              <p>inclusion of new APIs to provide functionalities and information in the ELN by the access to third-party applications (e.g. Jupyter notebooks and Shiny apps), the interaction with theoretical chemistry workflows (e.g. DFT calculations), the interaction with databases (examples include PDB and CSD), and the connection to AI-based tools and services.</p>
            </list-item>
            <list-item>
              <p>provision of a comprehensive Python API Client for Chemotion ELN so that the ELN’s content and data can be accessed for AI projects (in close interaction with M4.4), and</p>
            </list-item>
            <list-item>
              <p>further support APIs from ELN to repositories e.g. by repository to repository transfer (see T3.2.1).</p>
            </list-item>
          </list>
        </p>
        <p>
          <bold>M2.3: Viewers, processors, and editors for structures and data</bold>
        </p>
        <p><bold>Goal</bold>: Improve OS data viewers, processors, and structure editors to embed them into NFDI4Chem infrastructure or use them as standalone tools.</p>
        <p><bold>Description</bold>: Viewers and editors for data and chemical structures are a fundamental part of the Smart Lab concept and chemistry repositories (among other systems such as databases, inventories, and chemistry services), as the creation of FAIR machine-readable data depends on them in a digital research environment. This also means that the limitations of viewers and editors, in terms of their functionality, applicability, accessibility, or performance, have a direct impact on the availability of FAIR data in chemistry. Improving OS viewers and editors also serves as a valuable contribution to the wider NFDI4Chem community, which can use them in their standalone versions. All components improved in this measure will be of equal importance for all infrastructure services, in particular for the repositories and databases described in TA3, which have similar requirements for searching, visualising and analysing the research data they store.</p>
        <p>
          <italic>T2.3.1 ChemConverter</italic>
        </p>
        <p>During FP1, we developed ChemConverter, which allows us to convert data from myriad formats into a few standardised file formats, which is important for using data in digital systems such as ELNs and guaranteeing sustainable storage and access to the data. We designed and built a standardised way to</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>read (meta)data from various file formats,</p>
            </list-item>
            <list-item>
              <p>map metadata to community-defined metadata schemas, and</p>
            </list-item>
            <list-item>
              <p>convert data into the standard ‘JCAMP-DX’ format with support for single files as well as file collections in the form of ‘BagIT’ containers.</p>
            </list-item>
          </list>
        </p>
        <p>In FP2, the concepts will be extended to more complicated data, such as multidimensional data and the usage of additional readers designed by external communities. ChemConverter aims to support a wider range of possible input formats, also including proprietary formats. To comply with other systems and strategies for RDM, ChemConverter will be extended (also see M4.3) to export additional standards such as HDF5, RO-crate, frictionless data, and JSON-LD.</p>
        <p>
          <italic>T2.3.2 NMRium</italic>
        </p>
        <p>NMRium is an open-source React component developed by Zakodium for processing, viewing, and analysing NMR spectra (<xref ref-type="bibr" rid="B13578466">Davies and Patiny 2021</xref>, <xref ref-type="bibr" rid="B13578475">Patiny et al. 2024</xref>). NMRium has already been successfully integrated into Chemotion ELN and nmrXiv (s. T3.1.3). During FP2, the integration will be enhanced by improving the interoperability of the component. Specifically, the file format will be fundamentally refactored to separate spectral data, annotations and metadata. This will streamline callbacks between NMRium and its environment and greatly improve performance, as only small JSON chunks will be passed instead of the entire dataset. In addition, the internal filter handling will be refactored to allow modular extensions. The most important planned extensions will be a 2D NMR Fourier transformation, a non-uniform sampling (NUS) reconstruction, and improved usability with respect to touch device support.</p>
        <p>
          <italic>T2.3.3 ChemSpectra</italic>
        </p>
        <p>ChemSpectra (<xref ref-type="bibr" rid="B13569112">Huang et al. 2021</xref>) is the default data visualisation tool of the ELN, being able to process and visualise the standard file format ‘JCAMP-DX’ or ‘BagIt’ containers. ChemSpectra can be embedded into the ELN functions or used as a standalone version. In FP2, the currently supported workflows, layouts and functions, e.g., NMR, MS, IR, UV-Vis, CV, SEC, and TGA, will be continuously extended in accordance with T2.3.1 to support all techniques required by the users and to improve and extend the existing technologies. The functions will include the requirements of all applicable chemistry subdisciplines. Examples from our user feedback to be implemented are EPR, LSS, DLS, CD, porosimetry, rheometry, two- and multidimensional- HPLC and GC with fluorescence matrix as well as combined techniques such as GC-MS and HPLC-MS. ChemSpectra is a flexible tool with the ability to analyse a variety of measurements, offering a broad use case that is indispensable for sustainable, standardised, and affordable FAIR RDM.</p>
        <p>
          <italic>T 2.3.4 Implementation and rework of Structure Editor Ketcher (KIT)</italic>
        </p>
        <p>A structure editor called Ketcher is of growing importance for NFDI4Chem, as there are only a few other structural editors available that allow professional work with chemical structures (ChemDraw or Marvin). In the last few years, commercial software vendors have increased their licence fees in a way that many institutions cannot afford anymore. At the same time, the providers restrict the use of the licensed products in digital tools and thus prevent the use of the licensed software in software other than their own. Ketcher is the only sophisticated OS structure editor, and its further development should be supported to cover the needs of NFDI4Chem. In FP2, the additional necessary functions for advanced inorganic chemistry, catalysis, and materials sciences will be developed with experts from the different subdisciplines and in collaboration with experts from EPAM Systems’ development team.</p>
        <p>
          <italic>T 2.3.5 Enhancing data and metadata quality control</italic>
        </p>
        <p>Measures to control data and metadata quality are important to increase the acceptance of digital systems and to make use of their benefits for data producers and data reusers. In FP1, quality control features of ELN content were achieved, referring to the completeness of (meta)data, its readability and re-usability, as well as its consistency and scientific plausibility (<xref ref-type="bibr" rid="B13578489">Huang et al. 2024</xref>). The developed functions were implemented based on OS components described in T2.3.2 - T.2.3.4 and additional AI tools - showing the past and future importance and scope of those developments. In FP2, the work on automated curation and quality control features will continue to provide robust and trustworthy data control methods and tools.</p>
        <p>
          <bold>M2.4: Development and extension of topic-related ELN functions</bold>
        </p>
        <p><bold>Goals</bold>: Further development, adaptation, and extension of the ELN Chemotion (reference implementation for NFDI4Chem) to meet the requirements of the scientific community in all subdisciplines of chemistry.</p>
        <p><bold>Description</bold>: In FP1, the requests referring to the further development of the ELN were included according to different subdisciplines. In FP2, we will consolidate the work on the requirements of different subdisciplines (see description of TA2 above) by discussing and designing new functions with broad applicability, suitable for different areas of the ELN, independent of the user community. Adaptation of the ELN with such functions that combine the efforts of several needs and use cases will be designed in the form of working groups bridging different subdisciplines and technology experts. The working groups’ measures for quality control will be closely coordinated with all software developers in NFDI4Chem and advised by colleagues in Research Software Engineering (RSE) [see LOS RSEde].</p>
        <p>
          <italic>T2.4.1 Ontologies, semantic enrichment, and standards implementation, InChI</italic>
        </p>
        <p>In FP1, the use of ontology terms from the NFDI4Chem’s Terminology Service was enabled in different modules of the ELN e.g. hard-coded elements (cell lines, enzymes by the end of 2024) or extensions (see T2.6.1). In FP2, we will include a general approach to flexibly integrate ontologies and/or their terms in all areas of the ELN, supporting the standardisation of terms and the export of well-defined schemas (see also T2.6.2). As a prerequisite to systematically enrich the data with semantics, to support linked data, and to provide machine actionable FAIR data, we will implement MIChI-derived metadata schemas (see M4.1 and M6.3), and make ontologies assignable to generic forms to support interdisciplinary work (see M6.1, M6.2). Further chemistry standards, such as different InChI types (see T.4.2.1) and EnzymeML, will be included and continuously updated (see T2.4.2) in collaboration with TA4 and TA6.</p>
        <p>
          <italic>T2.4.2 Coding of new entities and ELN wide entity embedding</italic>
        </p>
        <p>During FP1, TA2 implemented several new main entities within the ELN according to the requests from users in different domains: Altogether four hard-coded entities (devices, sample types, cell lines, and enzymes (planned until end of 2024) and 11 generic elements providing versioned templates for new entities were provided (using LabIMotion, see T2.6.1). In FP2, the new entities proteins, samples for materials applications, environmental chemistry, and electrochemistry workflows (support by the Cluster ETOS, see LOS) are scheduled, including the definition of community-relevant identifiers, the inclusion of information queried from external community-relevant databases and the implementation of common reporting standards for these entities. Further entities will be designed and developed based on the community’s feedback in FP2 and prioritised according to the user group, depending on the new entities.</p>
        <p>
          <italic>T2.4.3 High throughput and parallel experimentation</italic>
        </p>
        <p>In FP2, TA2 will include workflows and representations to allow the documentation of high throughput experimentation, which has special importance in experimental areas such as but not only (in)organic chemistry (screening and catalysis) and biochemistry (assay conduction and analysis). While the basic requirements were already planned and partly implemented in FP1 (e.g. adaptation of well-plate format options; reaction variations tab), the coding of user input options for the structured planning, e.g., as a result of the design of experiment approach, design of experiments (DOE), the representation of multiple information based on matrix-like setups and the input, processing and representation of analytical data needs to be continued in FP2.</p>
        <p>
          <italic>T2.4.4 Data analysis and representation - data overview</italic>
        </p>
        <p>In FP1, the focus of data analysis and representation functions in the ELN lay on the implementation of routines for single datasets. In the next step, the ELN needs options to analyse and represent data on a higher level of the software, enabling</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>overarching analysis of analytical data,</p>
            </list-item>
            <list-item>
              <p>a combination of calculated and experimentally obtained data, and</p>
            </list-item>
            <list-item>
              <p>graphical visualisation of calculated properties in ELN-spanning 2D and 3D visualisation plots.</p>
            </list-item>
          </list>
        </p>
        <p>The analysis and representation tools need the implementation of different options such as filters and a flexible adaptation of the plotting actions. The newly gained data collections need to be organised and managed in parallel to the originally stored source data.</p>
        <p>
          <italic>T2.4.5 Beyond experimental investigation</italic>
        </p>
        <p>The focus of the work of TA2 in FP1 lies in solving challenges in laboratory environments. FP2 will include the systematic inclusion of workflows and features needed for chemists who work in theoretical chemistry, computational chemistry, and the cheminformatics community (see also M4.4). The first requirements were assessed by existing partners in computational chemistry and by a working group consisting of representatives of five theoretical chemistry groups (<xref ref-type="bibr" rid="B13579482">Jacob et al. 2024</xref>) and include, amongst others,</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>a JSON import and export for entities and subentities,</p>
            </list-item>
            <list-item>
              <p>an API to the content of the ELN on different levels e.g. for Jupyter Notebooks,</p>
            </list-item>
            <list-item>
              <p>the implementation of methods for quantum chemistry calculation,</p>
            </list-item>
            <list-item>
              <p>the representation of spectra from the theoretical output,</p>
            </list-item>
            <list-item>
              <p>and the implementation of simple analysis routines for theoretical chemistry such as calculation of energy differences.</p>
            </list-item>
          </list>
        </p>
        <p>
          <italic>T2.4.6 Extensions referring to reported issues</italic>
        </p>
        <p>The ELN team needs to work on additional requirements and bug fixes that are encountered during the project's runtime. Addressing unforeseen issues, upcoming new topics, or reported challenges is an important instrument for enabling community-driven code development. In FP1, we received a total of 393 issues via GitHub (in addition to many requests via helpdesk and email). 209 issues were solved until 07/2024, while more protracted tasks were included as suggested changes in the FP2 program. In FP2, we will continue this approach of continuous support of requests in combination with a strategic alignment and integration of major themes.</p>
        <p>
          <bold>M2.5: Services provided to the community</bold>
        </p>
        <p><bold>Goals</bold>:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>Ensure the availability of the Chemotion ELN for all scientists in Germany.</p>
            </list-item>
            <list-item>
              <p>Provide access to other OS ELNs, ensuring the best support and advice for the scientists.</p>
            </list-item>
          </list>
        </p>
        <p><bold>Description</bold>: For institutions or user groups of NFDI4Chem that want to host the ELN Chemotion under their own responsibility using their own resources to have full control over data and access options, TA2 provides a Docker image and a command line interface (CLI) for an easy installation, update, and maintenance of the ELN (T2.5.1). For single users or small groups that need an out-of-the-box solution with minimal cost and maintenance effort enabling low barriers to entry, we will continue to offer an ELN as a service (T2.5.2). A technical helpdesk supports users and system admins with information and hands-on support for all TA2 relevant systems (T2.5.4) and an openly accessible server for OS ELNs allows the comparison of available ELN systems in the domain of chemistry for testing and teaching purposes.</p>
        <p>
          <italic>T 2.5.1 Distribution of updates, Docker, CLI/GUI tool</italic>
        </p>
        <p>The source code and its documentation will be available on code repositories such as GitHub for interested developers. T2.5.1 will manage the Docker image generation for each main, minor and most important patch releases. The availability of updates and upgrades for self-hosted instances of the ELN (at different German universities) will be managed and communicated via different channels, e.g. admin and user mailing lists. Driven by user feedback, the CLI will be further extended by a GUI to simplify the management and configuration of the ELN instance(s). The versions, dependencies and changes have to be disseminated based on a CI model via GitHub and via additional documentation on the Knowledge Base (see T5.3.1).</p>
        <p>
          <italic>T 2.5.2 ELN as a service/ hosting</italic>
        </p>
        <p>A centrally hosted ELN Chemotion as a service was prepared and run in a test period with selected users within FP1. A generally applicable procedure for an access model by different users implemented with the AAI infrastructure (see cross-cutting topic M6.3.2) was defined and implemented. TA2 will care for the recent updates and upgrades of the software and will assign the needed resources. FIZ will manage the implementation of features like searching in external databases whenever allowed according to available licences. The constant access to the ELN as a service is overseen by a support team, which provides its best effort to solve user problems and mediate bug fixes. High availability of the ELN service is ensured by fail-safe hosting using a professional redundant server architecture and virtualisation.</p>
        <p>
          <italic>T 2.5.3 Service for open source ELNs</italic>
        </p>
        <p>KIT will install demo instances for OS ELNs other than the NFDI4Chem-supported one. In FP1, five (+1) ELNs (OpenEnventory, openBIS, eLabFTW, Herbie, SciNote, Chemotion, planned: RSpace) were supported in the form of an up-to-date test environment, allowing scientists to test different systems for the suitability to their requirements without the obstacle to set up these ELN on their own. A new survey on additional systems is currently ongoing (examples are: sample.de, AI4green), giving the requirements to include further systems in FP2.</p>
        <p>
          <italic>T2.5.4 Technical helpdesk (second-level support)</italic>
        </p>
        <p>In FP1, 53% of the users’ requests (2022-2024: 730 tickets in total) were assigned to topics related to TA2 and especially the use, installation and configuration of the ELN. The second-level support of TA2 handled and answered those requests in FP1 (passed by the general helpdesk installed in TA5; see T5.3.4) and will continue its activities and support for the requests in FP2. The technical helpdesk will solve all technical issues (installation, setup, maintenance and use) of the admins or users with respect to the ELN device integration modules and will answer questions with respect to software requirements and issues.</p>
        <p>
          <bold>M2.6: ELN as part of a digital ecosystem</bold>
        </p>
        <p><bold>Goal(s)</bold>: Enable the sustainable handling of data, independent of the used software</p>
        <p><bold>Description</bold>: Measure 2.4 will adapt the applicability of Chemotion ELN to a broader scientific scope to fill the current gaps between the work of chemists and other disciplines that require either an application-related focus and/or the inclusion of chemistry aspects for analytical and interdisciplinary work with 3rd party funding (T2.6.1). Further, we will enable the interoperability of the ELN Chemotion with other systems that are not part of the NFDI4Chem federation yet via different means, such as the support and implementation of standards that are developed within the most important open source ELNs (T2.6.2).</p>
        <p>
          <italic>T2.6.1 LabIMotion extension</italic>
        </p>
        <p>During FP1, the ELN team received an increasing number of requirements, each of which would have necessitated field-specific ELN functions and forms at different levels of information within the ELN’s structure. To offer solutions to the user community of NFDI4Chem, which often overlaps with communities from other NFDI consortia and their work, we designed and implemented LabIMotion, enabling the design of new ELN entities at different structural levels assigned to well-defined metadata without the need for hard-coded changes. These activities will be maintained and are planned to be extended by applying for further 3rd party funding.</p>
        <p>
          <italic>T2.6.2 ELN interoperability</italic>
        </p>
        <p>The interoperability of ELN content will be gained by the support of the initiative ‘ELN consortium’, which started the development of common standards for ELN-interoperability based on RO-crate and the file format *.eln. The team of TA2 will support this approach by implementing and the design of JSON-LD schemas for reuse in RO-crates, enabling the specific, detailed inclusion of scientific information into the interdisciplinary community. The work will be well-negotiated and supported by working groups in the Helmholtz community (coordinated by KIT and strengthened in TA6, T6.4.1).</p>
        <p>Table <xref ref-type="table" rid="T13519836">3</xref></p>
      </sec>
      <sec sec-type="5.3 TA3: Repositories">
        <title>5.3 TA3: Repositories</title>
        <p>TA3 focuses on maintaining and enhancing the federated research data repository system in chemistry, established in FP1, to ensure trust and cooperation for seamless data exchange and interoperability. This federation includes high-quality repositories trusted by the chemical community and recommended by journals and funding agencies, e.g., <ext-link ext-link-type="uri" xlink:href="https://www.angewandte.org">Angewandte Chemie Int. Ed.</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://chemistry-europe.onlinelibrary.wiley.com/journal/14397633">ChemBioChem</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://pubs.acs.org/doi/10.1021/acs.jnatprod.3c00281">Journal of Natural Products</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://wissenschaftliche-integritaet.de/kommentare/elektronisches-laborjournal-und-repositorium-in-der-chemie/">DFG GSP</ext-link> (in German), which covers all relevant subdisciplines and data types in chemistry. We foster the publication of high-quality, open-access FAIR chemistry data to guarantee access and easy reuse. TA3 operates and maintains reliable services with interfaces that connect various systems, including data ingestion (directly or via an ELN), terminology services, and external tools. Adhering to NFDI4Chem’s high standards and FAIR principles is crucial. Key repositories were connected to our central search. We will expand this to the entire federation to enhance disciplinary findability.In FP2, we aim to sustain, optimise, and consolidate all federated repositories, enhancing user interfaces, disciplinary metadata and MIChI support in cooperation with TA4 and TA6, interoperability, and machine-actionability for AI applications as shown in Fig. <xref ref-type="fig" rid="F13519933">5</xref>. Key workflows for publication, curation, review, and versioning will be streamlined to improve data quality and service usability. Sustainable operating models will be developed, and new repositories meeting our criteria will be onboarded. We will track data reuse and citations to evaluate our goal of promoting high-quality FAIR data publication and reuse by the whole chemistry community.</p>
        <p>TA3 will contribute to NFDI4Chem’s <bold>key objectives 1, 2, 3, 5, and 6</bold>, which are also reflected and differentiated in the <bold>objectives of TA3</bold>, which are:<bold>O3.1</bold> Expanding and consolidating a sustainable and trusted federation of standards-based and quality assured data repositories covering the needs of the chemistry community.</p>
        <p><bold>O3.2</bold> Enabling researchers to easily ingest, search, annotate, exchange, publish, archive and reuse chemistry research data and metadata across internationally distributed data services.</p>
        <p><bold>O3.3</bold> Enhance seamless interoperability of services using state-of-the-art technologies and providing FAIR, high quality chemistry data for interdisciplinary research, data science and AI.</p>
        <p><bold>O3.4</bold> Ensuring long-term operation and accessibility of repositories and chemistry data.To reach our goals, we defined <bold>five measures</bold> covering key elements for the enhancement and sustainable operation of the federation of interconnected repositories, including:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>trust and cooperation, exchanging metadata and data,</p>
            </list-item>
            <list-item>
              <p>compliance with our standards for data and metadata (including MIChI), data quality, interoperability, reliable operation, and long-term availability,</p>
            </list-item>
            <list-item>
              <p>covering essential needs of major chemistry subdisciplines,</p>
            </list-item>
            <list-item>
              <p>onnectivity between repositories, ELN, processing systems, terminology and ontology services, and tools,</p>
            </list-item>
            <list-item>
              <p>metadata harvesting allowing disciplinary findability in NFDI4Chem’s search and other systems,</p>
            </list-item>
            <list-item>
              <p>integrating functions and tools needed by chemists (converters, viewers, editors),</p>
            </list-item>
            <list-item>
              <p>tracking data reuse and citations,</p>
            </list-item>
            <list-item>
              <p>providing user guidelines (e.g., <ext-link ext-link-type="uri" xlink:href="https://www.nfdi4chem.de">how to choose the right repository</ext-link>), and</p>
            </list-item>
            <list-item>
              <p>seamless journal publication workflows identified in Editors4Chem.</p>
            </list-item>
          </list>
        </p>
        <p>
          <bold>M3.1 Sustainable operation, enhancement and maintenance of chemistry repositories</bold>
        </p>
        <p><bold>Goal(s)</bold>:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>Ensure sustainable operation of each core repository</p>
            </list-item>
            <list-item>
              <p>Ensure secure and up-to-date research software maintenance by patches and minor and major operating system updates</p>
            </list-item>
            <list-item>
              <p>Guarantee fully operational and reliable services and technical infrastructure</p>
            </list-item>
          </list>
        </p>
        <p><bold>Description</bold>: We describe</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>functionalities developed in FP1 that require</p>
            </list-item>
            <list-item>
              <p>maintenance and operational tasks for each repository in the form of seven levels: (A) Required security updates by continuous delivery of patches; (B) Major updates and upgrades of the main backend and frontend components and/or framework(s); (C) Update and upgrade of the database; (D) Update, upgrade, and replacement (if needed) of included software libraries, supported by software bills of materials (SBOM); (E) Adaptation of code required by changed dependencies; (F) Operating system updates and patches; (G) Resilient technical operation and backup strategies.</p>
            </list-item>
          </list>
        </p>
        <p>
          <italic>T3.1.1 Chemotion repository</italic>
        </p>
        <p>In FP1, the Chemotion repository was extended referring to strategic requirements such as:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>the integration of NFDI4Chem recommended AAI options and ROR,</p>
            </list-item>
            <list-item>
              <p>the improvement and fine-granular definition of the authors’ and reviewers’ rights and the connected available functions for different user roles,</p>
            </list-item>
            <list-item>
              <p>the versioning of reactions, samples and their analytical data,</p>
            </list-item>
            <list-item>
              <p>the support of JSON-LD the most relevant content of the repository, and the integration of embargo options for data collections and their support with collection DOIs. The repository was</p>
            </list-item>
            <list-item>
              <p>systematically extended with all requirements and updates available from the developments of Chemotion ELN, which were integrated successively respecting the repository’s specific dependencies. The greatest advance was gained with</p>
            </list-item>
            <list-item>
              <p>the integration of modules that come with the functionality of LabIMotion (see T2.6.1), allowing not only the adaptation of the content of the repository at different levels to diverse subdisciplines of chemistry but also the standardisation of the content in ELN and repository across different instances with an</p>
            </list-item>
            <list-item>
              <p>integrated, version-including template hub of which the content is aligned with the developments of TA4.</p>
            </list-item>
          </list>
        </p>
        <p>Maintenance and Operation (applicable to levels A-G) will cover the above-described improvements of FP1 and further developments aimed for in FP2 (see M3.2-M3.5), as well as the curation of the submitted datasets.</p>
        <p>
          <italic>T3.1.2 RADAR4Chem</italic>
        </p>
        <p>In FP1, the <ext-link ext-link-type="uri" xlink:href="https://radar.products.fiz-karlsruhe.de/de/radarabout/radar4chem">RADAR4Chem Repository</ext-link> was launched, based on the RADAR repository operated by FIZ Karlsruhe since 2017. RADAR4Chem is a reliable, user-friendly catch-all repository with a low entry threshold (currently free). It allows the publication of large, complex datasets of all chemistry subdisciplines and data types. Access to published data is guaranteed for at least 25 years, with a DOI and comprehensive landing page for each dataset.Developments focused on ensuring FAIRness and increasing interoperability through software releases:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>Metadata schema update: Integration of <ext-link ext-link-type="uri" xlink:href="https://ror.org">Research Organization Registry (ROR)</ext-link> and Integrated Authority File (GND),</p>
            </list-item>
            <list-item>
              <p>Optimisation of <ext-link ext-link-type="uri" xlink:href="http://schema.org">Schema.org</ext-link> conformity: Improved mapping, markup, embedding JSON-LD and Turtle format serialisations on landing pages,</p>
            </list-item>
            <list-item>
              <p>Enhanced Linked Open Data (LOD) framework and extension of the RADAR Knowledge Graph (KG) based on the Schema.org ontology,</p>
            </list-item>
            <list-item>
              <p>Optimisation of landing pages according to the FAIR signposting approach, improving machine readability and actionability,</p>
            </list-item>
            <list-item>
              <p>Daily creation of a RADAR4Chem knowledge graph based on Schema.org ontology,</p>
            </list-item>
            <list-item>
              <p>Support of a <ext-link ext-link-type="uri" xlink:href="https://www.w3.org/TR/sparql11-query">SPARQL endpoint</ext-link> for querying the knowledge graph in a standardised and machine-accessible way,</p>
            </list-item>
            <list-item>
              <p>Participation in the “FAIRness assessment challenge” organised by the EU project <ext-link ext-link-type="uri" xlink:href="https://www.fair-impact.eu">FAIR-IMPACT</ext-link>, increasing the FUJI-score of RADAR4Chem to 87%,</p>
            </list-item>
            <list-item>
              <p>Introduction of support for WebDAV for flexible dataset transfer and larger data volumes,</p>
            </list-item>
            <list-item>
              <p>Dockerisation of the software application for efficient deployment and maintenance.</p>
            </list-item>
          </list>
        </p>
        <p>Maintenance and operation (tasks A-G) will continue in FP2, guiding further developments (see M3.2 - M3.5). We will also continue to operate RADAR4Chem free of charge, expand dataset curation, enhance subject-specific metadata annotation (and MIChI), and improve functionality.</p>
        <p>
          <italic>T3.1.3 nmrXiv</italic>
        </p>
        <p>NmrXiv´s ultimate goal is accelerating broader coordination and data sharing among researchers by creating a platform for managing, sharing, and analysing raw and processed NMR spectral data. The milestones achieved by the repository during FP1 are:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>advanced search,</p>
            </list-item>
            <list-item>
              <p>API for data searching and retrieving,</p>
            </list-item>
            <list-item>
              <p>faceted search capabilities,</p>
            </list-item>
            <list-item>
              <p>management of access permission levels,</p>
            </list-item>
            <list-item>
              <p>restricted data access mode via roles,</p>
            </list-item>
            <list-item>
              <p>multiple download options in various formats and metadata export as JSON,</p>
            </list-item>
            <list-item>
              <p>DOI assignment to datasets,</p>
            </list-item>
            <list-item>
              <p>integration of NMRium for data format conversion,</p>
            </list-item>
            <list-item>
              <p>mapping of NMR data associated with compounds to third-party databases through identifiers,</p>
            </list-item>
            <list-item>
              <p>standardised protocols (e.g., RESTful APIs, OAI-PMH) for data exchange,</p>
            </list-item>
            <list-item>
              <p>citation export,</p>
            </list-item>
            <list-item>
              <p>data versioning,</p>
            </list-item>
            <list-item>
              <p>recommendations covering Liquid-State NMR Experiments of Small Molecules to extend MIChI.</p>
            </list-item>
          </list>
        </p>
        <p>Maintenance and operation (tasks A-G) will continue in FP2, guiding further developments (see M3.2 - M3.5). Additionally, we implement RO-Crate support to create self-describing data packages and (4) support the ISA data model.</p>
        <p>
          <italic>T3.1.4 MassBank</italic>
        </p>
        <p>During FP1, several achievements were made for MassBank:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>multiple data releases were deployed, adding spectra from MSSJ, Eawag, "Shin-MassBank", the Federal Institute of Hydrology, Agilent, the University of Antwerp, UFZ, the University of Birmingham, the US EPA, and Stockholm University.</p>
            </list-item>
            <list-item>
              <p>Introduction of tombstone pages for deprecated records and metadata improvements through Bioschemas updates and mapping to PSI MS ontology</p>
            </list-item>
            <list-item>
              <p>System updates included server versions 2.2.3 and 2.2.4 in 2023 and the new MassBank Accession schema in August 2022.</p>
            </list-item>
            <list-item>
              <p>Community engagement was enhanced by participation in key meetings such as the Metabolomics Society meeting in Osaka (June 2024).</p>
            </list-item>
          </list>
        </p>
        <p>Maintenance and operation (tasks A-G) will continue in FP2, with the primary site at UFZ and the backup site at IPB. Further developments (see M3.2 - M3.5 and PID optimisations) will follow.</p>
        <p>
          <italic>T3.1.5 VibSpec DB</italic>
        </p>
        <p>In FP1, the first pre-release version of the VibSpecDB, which specialised in vibrational spectroscopy data, was deployed as a test instance on a Kubernetes cluster. It provides basic functionality, such as:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>file upload,</p>
            </list-item>
            <list-item>
              <p>user’s profile pages,</p>
            </list-item>
            <list-item>
              <p>single sign-on and registration,</p>
            </list-item>
            <list-item>
              <p>admin console,</p>
            </list-item>
            <list-item>
              <p>spectral and file tree viewer,</p>
            </list-item>
            <list-item>
              <p>export functionality.</p>
            </list-item>
          </list>
        </p>
        <p>Users can set up minimal required or custom metadata and tags and create search queries. A separate python microservice was created to parse input data and metadata of some common file formats. A workflow and infrastructure to deploy the software (servers, file storage, database) were developed. By the end of FP1, the data publishing functionality needs to be created, and the first public version will be released. In FP2, the Vibrational Spectroscopy Ontology (see TA4) will be integrated, and standards and minimal requirements for spectra and metadata will be developed and implemented. Additional user interfaces are planned: VibSpecDB CLI and a collection of documented APIs, which will be used in a UI-free repository. Maintenance and operation of the public instance (tasks A-G) will continue in FP2, guiding further developments (see M3.2 - M3.5).</p>
        <p>
          <italic>T3.1.6 Suprabank</italic>
        </p>
        <p>In FP1, SupraBank was enhanced with features such as</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>ROR integration,</p>
            </list-item>
            <list-item>
              <p>user rights and roles management,</p>
            </list-item>
            <list-item>
              <p>DataCite integration for DOI-based references,</p>
            </list-item>
            <list-item>
              <p>embargo options for pre-publication datasets,</p>
            </list-item>
            <list-item>
              <p>peer-review process for dataset curation,</p>
            </list-item>
            <list-item>
              <p>CrossRef integration for linking datasets with publications,</p>
            </list-item>
            <list-item>
              <p>enhanced metadata for better machine readability and sharing, and</p>
            </list-item>
            <list-item>
              <p>new compounds like nanoparticles and materials, including external API integration.</p>
            </list-item>
          </list>
        </p>
        <p>In FP2, SupraBank will enter a consolidation phase to merge with Chemotion, preventing parallel development and double maintenance. The integration concept will be completed by the end of FP1, allowing the design and implementation phase to start in FP2. The planned functions</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>raw data upload and processing,</p>
            </list-item>
            <list-item>
              <p>dataset versioning,</p>
            </list-item>
            <list-item>
              <p>collections for user search and curation, and</p>
            </list-item>
            <list-item>
              <p>API expansion will be covered by Chemotion after the consolidation.</p>
            </list-item>
          </list>
        </p>
        <p>
          <bold>M3.2 Advanced FAIRification: optimise interoperability, data reuse, AI-readiness and user experience</bold>
        </p>
        <p><bold>Goal(s)</bold>:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>Unfolding the full potential of the federation of repositories by optimising interoperability and interfaces, connecting additional services</p>
            </list-item>
            <list-item>
              <p>enabling NFDI4Chem services to track data transfer, -citation and re-use scenarios</p>
            </list-item>
            <list-item>
              <p>FAIR-compliant provision of data collections and metadata for machine agents (machine-actionability)</p>
            </list-item>
            <list-item>
              <p>provide optimised user interfaces</p>
            </list-item>
            <list-item>
              <p>exchange with international FAIR implementation experts, enhance FAIR principles implementation in chemistry and consult repositories.</p>
            </list-item>
          </list>
        </p>
        <p><bold>Description</bold>: The federation of repositories benefits from a common strategy that includes data exchange, storage, and provision. Distinct interfaces enable interaction within the federation and with overarching services (e.g., the Search Service). In FP1, NFDI4Chem developed a sharing policy and concept for implementing the federation. Repositories are gradually integrated into the data exchange and interoperability concept (T3.2.1, T3.2.3), which began in FP1 and continues in FP2. Information exchange and reuse are tracked by systems identifying data flow in various scenarios, including unpublished (repotracker, T3.2.2) and published data (search service, T3.2.4 and citation tracker, T3.2.2). APIs ensure seamless background exchange, while user interfaces provide standardised access via LLMs and SPARQL queries. The federation concept is managed and controlled by collaborative (T3.2.5) and central means (T3.2.6).</p>
        <p>
          <italic>T3.2.1 Data and service interoperability</italic>
        </p>
        <p>T3.2.1 will optimise the following aspects for each repository:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>Interfaces for data transfers (a) between ELN and repositories and (b) between repositories. As shown in Fig. <xref ref-type="fig" rid="F13519933">5</xref>, repositories within NFDI4Chem are fed with data by manual upload or transfer from services used earlier in the research data life cycle, such as ELN Chemotion (see T2.2.5, TA2) or Repository Chemotion (T3.2.2). Data transfer from the repository Chemotion to the specialised repository nmrXiv is going to be realised until the end of FP1. In FP2, this reference implementation will be extended stepwise to other repositories within the federation.</p>
            </list-item>
            <list-item>
              <p>Support for widely accepted data formats in the chemistry community, such as <ext-link ext-link-type="uri" xlink:href="https://nmredata.org/">NMReData</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://iupac.org/what-we-do/digital-standards/jcamp-dx/">JCAMP-DX</ext-link>, and <ext-link ext-link-type="uri" xlink:href="https://iupac.org/project/2019-002-2-024/">SMILES</ext-link>. This includes implementing community-recognized metadata standards based on the MIChI developments in M4.1 for comprehensive dataset descriptions and transformation via the MSS to schemas like <ext-link ext-link-type="uri" xlink:href="https://datacite.org/">DataCite</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://schema.org/">schema.org</ext-link>, and <ext-link ext-link-type="uri" xlink:href="https://bioschemas.org/">Bioschemas</ext-link> for interoperability and findability through external search services,</p>
            </list-item>
            <list-item>
              <p>assignment of persistent identifiers, such as <ext-link ext-link-type="uri" xlink:href="https://www.doi.org/">DOIs</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://www.handle.net/">Handles</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://ror.org/">ROR</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://metadata.raid.org/">RAiD</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://ev.igsn.org/">ISGN</ext-link>, and <ext-link ext-link-type="uri" xlink:href="https://www.inchi-trust.org/">InChI</ext-link>, to metadata and digital objects as needed,</p>
            </list-item>
            <list-item>
              <p>integration of <ext-link ext-link-type="uri" xlink:href="https://docs.google.com/document/d/1OL40i9-PdzmKt-PRRSF9iUMXxu1s4ktYxI_MgB2yIII/edit#heading=h.wgc8xusolm5j">TA6 services</ext-link> to ensure consistent use of controlled vocabularies, ontologies, and taxonomies specific to chemistry,</p>
            </list-item>
            <list-item>
              <p>machine-actionable metadata: Ensure digital objects are accompanied by machine-readable metadata and detailed contextual documentation, in conjunction with <ext-link ext-link-type="uri" xlink:href="https://docs.google.com/document/d/1OL40i9-PdzmKt-PRRSF9iUMXxu1s4ktYxI_MgB2yIII/edit#heading=h.a2t9dkgqryjo">T2.3.3 techniques</ext-link>,</p>
            </list-item>
            <list-item>
              <p>optimisation of APIs and data exchange protocols, such as <ext-link ext-link-type="uri" xlink:href="https://www.openapis.org/">OpenAPI</ext-link> for RESTful APIs and <ext-link ext-link-type="uri" xlink:href="https://www.openarchives.org/pmh/">OAI-PMH</ext-link> for metadata harvesting, to enable seamless data integration and retrieval across different systems.</p>
            </list-item>
          </list>
        </p>
        <p>
          <italic>T3.2.2 Data reuse tracking</italic>
        </p>
        <p>Data reuse tracking will be implemented for different scenarios: data transfer from ELNs to repositories and between repositories will be tracked by the ‘<ext-link ext-link-type="uri" xlink:href="https://github.com/ComPlat/Repository-Tracker">Repotracker</ext-link>’ (developed in FP1). The Repotracker, currently used as monitoring for the same dataset in different repositories, will be extended to track detailed interactions with individual repositories in FP2. Further, the reuse of data sets of the federated repositories will be tracked using the <ext-link ext-link-type="uri" xlink:href="https://support.datacite.org/docs/data-citation-corpus-first-release">DataCite Citation Corpus</ext-link> and similar approaches. We will develop the CitationTracker-SW capable of identifying and counting data citations and how data is re-used to be fed e.g. into the NFDI4Chem knowledge graph (T6.3.3).</p>
        <p>
          <italic>T3.2.3 Enhanced machine-actionability and user-friendly database queries</italic>
        </p>
        <p>To streamline data retrieval from large or nested datasets, the federated repositories will implement:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>machine-actionable landing pages (e.g., using the <ext-link ext-link-type="uri" xlink:href="https://fairsharing.org/4476">FAIR signposting approach</ext-link>),</p>
            </list-item>
            <list-item>
              <p>SPARQL endpoints, and</p>
            </list-item>
            <list-item>
              <p>LLM support (or equivalent technologies). We will simplify SPARQL query generation with AI tools like LLMs, enabling user-friendly query results (see also T6.3.2).</p>
            </list-item>
            <list-item>
              <p>Data and metadata can be stored in an <ext-link ext-link-type="uri" xlink:href="https://www.researchobject.org/ro-crate/">RO-Crate</ext-link>.</p>
            </list-item>
          </list>
        </p>
        <p>Each file and dataset will have a persistent identifier, integrating the <ext-link ext-link-type="uri" xlink:href="https://fairdo.org">FAIR Digital Objects (FDO) approach</ext-link> for robust interaction with digital objects. RO-Crates will be validated and indexed, with APIs and web interfaces provided for accessing FDOs. Implementations will vary by service and user needs, with consultation by the TA3 core team. We will also support repositories with the integration into the Semantic Data Hub (M6.3).</p>
        <p>
          <italic>T3.2.4 Connections of the federation of repositories to other services</italic>
        </p>
        <p>The federation of repositories aims to connect repositories with several other services:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>to the NFDI4Chem and other data search services and the Semantic Data Hub (M6.3) to enable seamless discovery of chemical data and related scientific information</p>
            </list-item>
            <list-item>
              <p>to the massively scalable <ext-link ext-link-type="uri" xlink:href="https://github.com/ER-FIZKarlsruhe/fiz-oai-provider">(OAI-PMH) provider</ext-link> <ext-link ext-link-type="uri" xlink:href="http://radar.products.fiz-karlsruhe.de/de/radarfeatures/radar-oai-provider">offered by FIZ</ext-link> to collect and harmonise metadata from federated repositories, ensuring consistent and up-to-date information across the federation,</p>
            </list-item>
            <list-item>
              <p>to service overviews and marketplaces like <ext-link ext-link-type="uri" xlink:href="https://www.re3data.org/">re3data</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://fairsharing.org/">FAIRsharing</ext-link>, or the <ext-link ext-link-type="uri" xlink:href="https://marketplace.eosc-portal.eu/">EOSC marketplace</ext-link>.</p>
            </list-item>
          </list>
        </p>
        <p>
          <italic>T3.2.5 Continuous design and adaptation of the main common work principles (“TA15”)</italic>
        </p>
        <p>T3.2.5 facilitates ongoing, long-term collaboration among the PIs of main services (TA 2+3+4+6, “TA15”) to optimise the core infrastructure. This involves elaborating, investigating, and negotiating new tasks for NFDI4Chem services. For FP2, key aspects include:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>designing interoperability concepts for unaddressed repository entities,</p>
            </list-item>
            <list-item>
              <p>exploring innovative concepts like FAIR signposting and FDOs,</p>
            </list-item>
            <list-item>
              <p>developing a work program for fully implementing the “I” in FAIR (knowledge representation, vocabularies, and metadata references),</p>
            </list-item>
            <list-item>
              <p>connecting with external services, and</p>
            </list-item>
            <list-item>
              <p>evaluating licensing options for research data and collections. Many of these tasks require cross-task area discussions within NFDI4Chem.</p>
            </list-item>
          </list>
        </p>
        <p>
          <italic>T3.2.6 International FAIR technology assessment and consulting for NFDI4Chem repositories</italic>
        </p>
        <p>By engaging with international experts (e.g., Research Data Alliance (RDA), European Open Science Cloud (EOSC)), TA3 will shape FAIR principles and implementation standards, transferring knowledge to the federation's repositories. We aim to ensure our services comply with FAIR principles, set benchmarks and provide recommendations for improvement. We will present and discuss our approaches at international conferences, showcasing our impact and gathering feedback. This will strengthen international collaboration, enhance visibility and credibility globally, and ensure optimal FAIR implementation in our services.</p>
        <p>
          <bold>M3.3 Consolidation, harmonisation and standardisation of the federation of repositories</bold>
        </p>
        <p><bold>Goal(s)</bold>:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>raise data quality and adapt existing descriptions and schemes according to the already developed and forthcoming standards (TA4 and beyond);</p>
            </list-item>
            <list-item>
              <p>harmonise dataset versioning;</p>
            </list-item>
            <list-item>
              <p>connect to NFDI base services;</p>
            </list-item>
            <list-item>
              <p>increased operational fitness;</p>
            </list-item>
            <list-item>
              <p>optimal embedding into journal publishing processes.</p>
            </list-item>
          </list>
        </p>
        <p><bold>Description</bold>: M3.3 emphasises thorough quality assurance and adaptation to NFDI4Chem standards, ensuring careful management of versioning, data history, and reuse tracking (e.g., data citations). We are committed to seamlessly integrating the repositories into NFDI core services and other overarching infrastructures to enhance collaboration and operational synergies. This comprehensive approach optimises efficiency while maintaining robust data management practices throughout our projects.</p>
        <p>
          <italic>T3.3.1 Data quality assurance and adaptation to our standards</italic>
        </p>
        <p>In FP2, all repositories, especially Chemotion and RADAR4Chem, will</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>adapt descriptions and schemes to MIChI standards to cover profiles by at least one service. This includes</p>
            </list-item>
            <list-item>
              <p>various levels of standardisation, such as (a) relations between investigations, (b) reactions, (c) other chemical processes, (d) entities like samples and devices, and (e) measurement types.</p>
            </list-item>
            <list-item>
              <p>Implementation will provide metadata based on MIChI-derived schemas for the NFDI4Chem search and the Semantic Data Hub (M6.3) and optionally support schema.org or DataCite-compliant schemas to facilitate reuse and harvesting (T3.2.1).</p>
            </list-item>
            <list-item>
              <p>Templates for user input forms to describe data types will be harmonised or developed, connected to controlled vocabulary and ontologies (M6.2). FP2 will also focus on</p>
            </list-item>
            <list-item>
              <p>data quality assurance and</p>
            </list-item>
            <list-item>
              <p>data curation mechanisms, depending on data types and available or planned functions for manual or automated processes.</p>
            </list-item>
          </list>
        </p>
        <p>Scientific teams will support manual curation for peer review and diverse data types, while automated curation will be supported by tools developed in TA2, using specialised software like AI.</p>
        <p>
          <italic>T3.3.2 Dataset versioning - a harmonised implementation and adaptation</italic>
        </p>
        <p>Data versioning means tracking and managing changes to datasets over time. Modifications have to be uniquely identifiable and retrievable, much like version control in software development and allow citing dedicated versions. Existing data versioning frameworks have the drawback of depending on journal paper citations to make new data versions discoverable (<xref ref-type="bibr" rid="B13579491">González–Cebrián et al. 2024</xref>). Versioning is a <ext-link ext-link-type="uri" xlink:href="https://zenodo.org/records/7051012">key requirement</ext-link> for the <ext-link ext-link-type="uri" xlink:href="https://www.coretrustseal.org/">CoreTrustSeal</ext-link> (CTS) certification, which establishes to report any changes to data and metadata. Thus, we will improve and harmonise it on different levels, promoting transparency of data provenance and reproducibility, enhancing the recognition of data curation efforts (T3.3.1) and allowing citing datasets as well as their individual versions.</p>
        <p>
          <italic>T3.3.3 Integrating repositories with NFDI base services</italic>
        </p>
        <p>The NFDI4Chem repositories will integrate NFDI base services, starting with <ext-link ext-link-type="uri" xlink:href="https://base4nfdi.de/projects/iam4nfdi">IAM4NFDI</ext-link> (AAI infrastructure, SSO) through a phased approach:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>initial repository integration,</p>
            </list-item>
            <list-item>
              <p>handling complex integrations in projects supported by <ext-link ext-link-type="uri" xlink:href="https://www.base4nfdi.de/">Base4NFDI</ext-link>, including advanced IAM for group membership management across services (ELN, repositories), harmonisation of user representation, roles and rights.</p>
            </list-item>
          </list>
        </p>
        <p>We will evaluate and adapt the virtual organisation concept, and repository operators will receive support for implementation. Other services to be connected include the NFDI Knowledge Graph (<ext-link ext-link-type="uri" xlink:href="https://base4nfdi.de/projects/kgi4nfdi">KGI4NFDI</ext-link>) and DMP tools like <ext-link ext-link-type="uri" xlink:href="https://rdmorganiser.github.io/">RDMO</ext-link> (DMP4NFDI).</p>
        <p>
          <italic>T3.3.4 Operational quality, policies and licences for research data</italic>
        </p>
        <p>Operational fitness is crucial for a sustainable and reliable service. Certification, such as <ext-link ext-link-type="uri" xlink:href="https://www.coretrustseal.org/">CTS</ext-link>, strengthens repositories and builds trust. In FP1, only a few repositories applied for certification due to challenges like the need to be fully operational, application effort, and restrictions to specialised repositories. In FP2, we will enable our repositories to achieve CTS certification or equivalent, first assessed in FP1. We will establish quality measures that meet certification requirements, ensuring repositories operate with a commitment to transparency, reliability, and trust, documented by accessible policies. We will harmonise commitments to meet general standards, including data protection, ethical principles, and adopting specialised licences for research data (e.g., <ext-link ext-link-type="uri" xlink:href="https://opendatacommons.org/licenses/odbl/">ODbL</ext-link>,<ext-link ext-link-type="uri" xlink:href="https://cdla.dev/"> CDLA</ext-link>).</p>
        <p>
          <italic>T3.3.5 Peer-review process harmonisation for data publications</italic>
        </p>
        <p>NFDI4Chem promotes publishing research data alongside traditional papers and established a <ext-link ext-link-type="uri" xlink:href="https://www.nfdi4chem.de/2nd-editors4chem-workshop/">dialogue with publishers</ext-link> in FP1, leading to a mutual understanding of data publishing. However, aligning peer review workflows for journal and data publications is challenging due to varied submission processes, fear of releasing data before manuscript acceptance, cultural biases, and maintaining reviewer anonymity. To integrate the publication process for both papers and data, repositories must support a transparent, anonymous, and efficient peer review process involving</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>creating/reserving a PID before data publication for referencing in manuscripts,</p>
            </list-item>
            <list-item>
              <p>enabling anonymous access to data and metadata for publishers and reviewers, and</p>
            </list-item>
            <list-item>
              <p>making data temporarily immutable during review.</p>
            </list-item>
          </list>
        </p>
        <p>Task T3.3.5 will address these needs in coordination with TA4 (M4.5) and <ext-link ext-link-type="uri" xlink:href="https://www.nfdi4chem.de/2nd-editors4chem-workshop/">Editors4Chem</ext-link> (<xref ref-type="bibr" rid="B13574047">Parks et al. 2023</xref>, <xref ref-type="bibr" rid="B13521359">Parks et al. 2024</xref>), extending publisher recommendations (e.g. <ext-link ext-link-type="uri" xlink:href="https://onlinelibrary.wiley.com/page/journal/15213773/homepage/notice-to-authors">Wiley</ext-link>).</p>
        <p>
          <bold>M3.4 Developing and implementing sustainable service operating models</bold>
        </p>
        <p><bold>Goal(s)</bold>: Ensuring</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>reliable long-term archiving (LTA),</p>
            </list-item>
            <list-item>
              <p>a functional exit strategy,</p>
            </list-item>
            <list-item>
              <p>data migration paths,</p>
            </list-item>
            <list-item>
              <p>reliable hosting of central software tools as services,</p>
            </list-item>
            <list-item>
              <p>sustainable operating models for the federated repositories.</p>
            </list-item>
          </list>
        </p>
        <p><bold>Description</bold>: M3.4 aims to establish a comprehensive LTA solution for federated repositories. This includes designing a robust LTA blueprint (based on RADAR's model), implementing it in repositories, and developing exit strategies for discontinued repositories with support for data migration. It offers centralised hosting of key software tools to improve efficiency and promotes sustainable operating models to ensure the long-term reliability and scalability of data services.</p>
        <p>
          <italic>T3.4.1 Design of a blueprint for Long-Term Archiving (LTA)</italic>
        </p>
        <p>In T3.4.1, we will design an LTA solution as a blueprint for repositories without LTA. We propose using RADAR's well-established design, which can serve directly or as a blueprint for a more specific solution. Data transfer uses standardised protocols and is maintained on tape storage libraries with redundant copies in three locations. The storage architecture is technology-independent. Data is ingested for temporary, then permanent storage. Initially, data is transferred via HTTPS to RADAR's temporary memory, checked for integrity, packaged (<ext-link ext-link-type="uri" xlink:href="https://datatracker.ietf.org/doc/html/rfc8493">BagIt</ext-link>) and transferred via SFTP (TAR file) to three permanent archive tape storage systems. During retention, data packages are immutable and preserved physically. FIZ Karlsruhe (TA3) manages operations, including data distribution, virtual machine maintenance, software development, updates, and patching.</p>
        <p>
          <italic>T3.4.2 Long-Term archiving implementation plan</italic>
        </p>
        <p>We will follow a structured process to implement the LTA solution proposed in T3.4.1. Hardware and software components will be procured, and the virtual environment will be prepared. Data will be assessed and inventoried for archiving. The archiving solution will be installed and configured for seamless integration, and storage solutions will be established. Testing and validation will be performed. Documentation and policies for data archiving, retention, and access control will be established. Continuous monitoring and maintenance will be ensured.</p>
        <p>
          <italic>T3.4.3 Defining an exit strategy for each core repository</italic>
        </p>
        <p>TA3 will develop an exit strategy for repositories that can no longer manage their data sustainably. Relevant data collections or repositories should be migrated to a suitable repository or transferred to LTA storage (T3.4.4). Operations like metadata and format preservation, PID transfer, and ensuring long-term accessibility and usability of data need to be organised, independent of the repository software stack.</p>
        <p>
          <italic>T3.4.4 Data migration to other repositories</italic>
        </p>
        <p>TA3 supports data migration when relevant repositories are discontinued or require integration into the NFDI4Chem infrastructure. Data will be transferred to the most suitable repository to ensure long-term availability for the chemistry community. This includes mapping database contents, converting data for the target repository, and adapting metadata and licences. Original service functions will be maintained whenever possible. In FP2, the first use case for such a migration will be the consolidation of the Suprabank and Chemotion repositories.</p>
        <p>
          <italic>T3.4.5 Hosting sustainable software on central infrastructure</italic>
        </p>
        <p>To streamline software tools for chemists, we aim to centralise hosting for minimal costs and efficient maintenance. Identified candidates include the FIZ-OAI provider, viewers, editors, converters for various file types, and ELN instances (T2.5.2). Centralising these tools enhances interoperability and resource efficiency. A flexible deployment infrastructure using container technology (e.g., Docker) will allow updates from multiple sources. Continuous DevOps support will ensure seamless integration and connectivity, providing up-to-date, optimised software across services.</p>
        <p>
          <italic>T3.4.6 Sustainable operating-, funding- or business-models</italic>
        </p>
        <p>TA3 will advise core services on sustainable operations for long-term reliability, focusing on optimising processes, scalability, and continuity. While services are currently free, securing sustainable funding is essential. RADAR's business model could be used by other repositories to ensure longevity. We prioritise reliable service providers and propose transition solutions to ensure minimal disruption if sustainable models are not feasible (T3.4.3 - T3.4.5).</p>
        <p>
          <bold>M3.5 Extension of the federation of repositories</bold>
        </p>
        <p><bold>Goal(s)</bold>:</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>Continuously monitor the global landscape of chemistry repositories.</p>
            </list-item>
            <list-item>
              <p>Identify and catalogue candidate repositories for onboarding based on functionality, governance, and user engagement.</p>
            </list-item>
            <list-item>
              <p>Integrate new chemistry repositories into the federation, ensuring compatibility and interoperability.</p>
            </list-item>
            <list-item>
              <p>Support repositories during the integration phase.</p>
            </list-item>
          </list>
        </p>
        <p><bold>Description</bold>: M3.5 monitors global chemistry repositories, assessing their functionality, governance, and user engagement while staying updated on technological and policy changes. Selected repositories are onboarded, meeting technical benchmarks and integrating with consortium services like ELN and central search. Regular forums ensure knowledge exchange on FAIR technologies, adherence to standards, and smooth integration.</p>
        <p>
          <italic>T3.5.1 Ongoing analysis of the international repositories landscape</italic>
        </p>
        <p>In T3.5.1, TA3 will continuously monitor global chemistry repositories. Initially focused on national repositories, we began internationalisation with FAIRsharing in FP1.In T3.5.1, TA3 will continuously monitor global chemistry repositories. Since NFDI was initiated as a national call, in FP1, we focused on national chemistry repositories (<xref ref-type="bibr" rid="B13579500">Bonatto Minella et al. 2023a</xref>). In FP1 the internationalisation process was initiated by collaborating with <ext-link ext-link-type="uri" xlink:href="https://fairsharing.org/">FAIRsharing</ext-link>: a <ext-link ext-link-type="uri" xlink:href="https://fairsharing.org/5027">collection</ext-link> of standards and repositories (called NFDI4Chem) was created. The goal is to assess the current technological state, trends, and emerging patterns in repositories, covering additional subdisciplines or needs in chemistry. This ongoing task involves identifying and cataloguing repositories that fit our federation, considering subdiscipline coverage, data, functionalities, governance, technology, and user engagement, while monitoring new developments, policy changes, and technological advances.</p>
        <p>
          <italic>T3.5.2 Onboarding of additional chemistry data repositories</italic>
        </p>
        <p>We will</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>select international repositories that</p>
            </list-item>
            <list-item>
              <p>meet our technical standards and can be interoperable within our federation. Based on (a) M3.1 specifications for technical interoperability and standard compliance and (b) benefits for the chemistry community, our goal is to</p>
            </list-item>
            <list-item>
              <p>embed these resources in<ext-link ext-link-type="uri" xlink:href="https://www.nfdi4chem.de"/>NFDI4Chem and enhance their accessibility and interoperability. New repositories will be</p>
            </list-item>
            <list-item>
              <p>connected to our services, such as our (a) knowledge base, (b) <ext-link ext-link-type="uri" xlink:href="https://github.com/ER-FIZKarlsruhe/fiz-oai-provider">OS</ext-link> <ext-link ext-link-type="uri" xlink:href="http://radar.products.fiz-karlsruhe.de/de/radarfeatures/radar-oai-provider">FIZ-OAI</ext-link>, (c) Terminology and Vocabulary Services and (d) ELN-interface, as well as to new services of NFDI4Chem. Candidates that were already identified in FP1 include <ext-link ext-link-type="uri" xlink:href="https://www.ccdc.cam.ac.uk/">CSD</ext-link> and <ext-link ext-link-type="uri" xlink:href="https://icsd.products.fiz-karlsruhe.de/">ICSD</ext-link>. Bilateral meetings led to the plan to integrate them into our search service. We will further</p>
            </list-item>
            <list-item>
              <p>develop (a) a formal onboarding process, (b) classes of embedding degree, (c) assessment of infrastructure readiness, (d) onboarding documentation and (e) integration testing, risk management and reviews.</p>
            </list-item>
          </list>
        </p>
        <p>
          <italic>T3.5.3 Knowledge transfer to onboarded repositories with integration and FAIRification support</italic>
        </p>
        <p>In FP2, we will</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>initiate a regular exchange forum for onboarded and federated repositories. These engagements will centre around (a) FAIR technologies and (b) adherence to our established standards, as well as (c) connection to our services (T3.5.2). We will offer</p>
            </list-item>
            <list-item>
              <p>comprehensive technical support throughout the integration phase.</p>
            </list-item>
          </list>
        </p>
        <p>Table <xref ref-type="table" rid="T13519839">4</xref></p>
      </sec>
      <sec sec-type="5.4 TA4 Metadata, Data Standards, and Publication Standards">
        <title>5.4 TA4 Metadata, Data Standards, and Publication Standards</title>
        <p><bold>TA4</bold> defines and implements standards for metadata and data formats to ensure FAIRness, together with reference implementations and data validation, as well as standards for publishing workflows relevant to authors, academic publishers and developers of data and metadata infrastructures. Ontologies are used in metadata standards where possible, and missing terminological artefacts are added (in collaboration with M6.1). TA4 develops minimum information standards, harmonises metadata practices, and collaborates with international standardisation bodies like IUPAC to adopt and foster global standards. Moreover, TA4 cooperates with academic publishers to streamline the publishing processes of datasets along with corresponding scientific articles.</p>
        <p>The development and maintenance of standards for both data and metadata are important to ensure the FAIRness (<xref ref-type="bibr" rid="B13579509">Wilkinson et al. 2016</xref>) and RIPEness (Reliable, Interpretable, Processable and Exchangeable, (<xref ref-type="bibr" rid="B13520311">McEwen and Bruno 2023</xref>)) of research data. With these goals, TA4 contributes to key objectives 2 and 5. Specifically, the objectives of TA4, designed to support FAIRness in NFDI4Chem, are:</p>
        <p><bold>O4.1</bold>: Create a set of <bold>modular</bold>, <bold>machine-actionable</bold> and <bold>interoperable metadata</bold> and <bold>data standards</bold> in key areas of chemistry through national and international processes</p>
        <p><bold>O4.2</bold>: Ubiquitous use of (<bold>persistent</bold>) <bold>identifiers</bold> for <bold>data</bold>, <bold>instrumentation</bold>, <bold>protocols</bold> and <bold>terminology</bold>, all with <bold>informative metadata</bold> ready for integration into semantically rich <bold>linked open data</bold></p>
        <p><bold>O4.3</bold>: Increased <bold>adoption</bold> and <bold>integration</bold> of standards through generic <bold>reference software</bold> implementations</p>
        <p><bold>O4.4</bold>: Integration with the <bold>scientific publishing processes</bold></p>
        <p><bold>O4.5: Contribution of</bold> standards and identifiers on (bio-)chemical entities <bold>to the entire NFDI</bold></p>
        <p>These objectives will be pursued through the following measures:</p>
        <p>
          <bold>M4.1 Development and harmonisation of Minimum Information Metadata Standards</bold>
        </p>
        <p><bold>Goals</bold>: M4.1 contributes to the objectives O4.1, O4.2, and O4.4.</p>
        <p><bold>Description</bold>: Rich and harmonised metadata are required to make entities and datasets in chemistry FAIR. We will develop and maintain a set of modular, machine-actionable and interoperable metadata standards in key areas of chemistry. To be modular, we will develop requirements for Minimum Information about a Chemical Investigation (MIChIs) standards, which form the basis for chemistry-specific metadata schemas and mappings with and for the Metadata Schema Service (MSS, see M6.3). By including marginality in the MIChIs, we will achieve the key goal of identifying minimal common denominators. We will use a combination of semantically rich information following the linked open data principles (<xref ref-type="bibr" rid="B13579611">Bizer et al. 2009</xref>), using persistent identifiers and concepts obtained from terminology services.</p>
        <p>There is still a real need for a thorough description of research objects, methods, tools and variables, which at present are partially covered by authoritative bodies like the IUPAC, e.g. via the Gold or Purple Book (<xref ref-type="bibr" rid="B13579620">Chalk and McEwen 2017</xref>, <xref ref-type="bibr" rid="B13579638">Jones et al. 2009</xref>), or the Joint Committee for Guides in Metrology (<xref ref-type="bibr" rid="B13579658">Joint Committee for Guides in Metrology 2012</xref>, <xref ref-type="bibr" rid="B13579675">Joint Committee for Guides in Metrology, Working Group 1 2008</xref>) though our partner PTB, or grassroots activities also in NFDI consortia (e.g. Metadata4Ing).</p>
        <p>Our international network (IUPAC, RDA, PSDI), community engagement (in collaboration with M5.1), and interaction with neighbouring NFDI consortia will be used to discuss the MIChIs from the subdisciplines for all relevant chemical methods, e.g. through workshops. The harmonisation will be achieved through iterative refinement and feedback when implemented by researchers, infrastructures, journals, and participants from TA2, TA3, TA5, and TA6.</p>
        <p>
          <italic>T4.1.1 Development and harmonisation of Minimum Information standards about Chemical Investigations (MIChI)</italic>
        </p>
        <p>During FP1, several international workshops were conducted to bring domain experts together, to develop MIChIs for diverse methods and subdisciplines of chemistry. These typically result in guidelines and checklists, identification of (existing or missing) controlled vocabulary-derived term definitions and providing human and machine-readable examples.</p>
        <p>In FP2, we will continue the discussion with domain experts in additional subdisciplines and for further methods used in chemical sciences to extend and broaden the coverage of MIChIs, including, but not limited to, organic chemistry, inorganic chemistry, polymer chemistry, physical chemistry, medicinal and pharmaceutical chemistry, biochemistry, analytical chemistry, photo- and electrochemistry, environmental chemistry and theoretical chemistry This also requires vocabulary and minimum requirements for the simple semantic description of analytical tools, methods and results. We will increase the efforts in the area of computational and theoretical chemistry towards machine-readable and potentially automated computational protocols to allow for generic descriptions beyond individual simulation software solutions and workflows.</p>
        <p>With a growing set of MIChIs in hand, we can identify a common chemistry core (CCC) of concepts that are applicable and re-usable in multiple subdisciplines. Harmonising their descriptions will lead to an interoperable CCC to be the basis of our modular and interoperable metadata standards These discussions will also include the Data and Service providers in NFDI4Chem to moderate and push harmonisation efforts across our federation of services (see M3.3 and M6.3).</p>
        <p>
          <italic>T4.1.2 Modelling and Mapping metadata, linking to terminologies and existing standard models</italic>
        </p>
        <p>Based on the description of CCC and subdiscipline-specific concepts resulting from MIChIs developed in T4.1.1, we will model and map the concepts into metadata schemas for the annotation of datasets that can be pushed and hosted in the MSS (see M6.3) We will ensure that generic domain-independent metadata in schemas of DataCite and Crossref can be linked with domain-specific chemistry specific metadata schemas and that the metadata is suitable to annotate and package datasets using e.g., RO-crate in our federation of repositories (see M3.3). Under the umbrella of computational chemistry community actions (e.g., euroSAMPL, TA5), the standardisation of computational chemistry protocols will be fostered.</p>
        <p>The modular modelling of metadata schemas ensures that information is harmonised and can be mapped via cross-walks to various widely adopted and established metadata standards and will follow the recently published recommendations on the Cross-Domain Interoperability Framework (CDIF) developed as part of the WorldFAIR project (<xref ref-type="bibr" rid="B13520070">Gregory et al. 2024</xref>). The specifications of metadata schemas will aim at</p>
        <p>
          <list list-type="order">
            <list-item>
              <p>improving the findability of data in both our generic and chemistry-specific repositories, also through the NFDI4Chem Search Service,</p>
            </list-item>
            <list-item>
              <p>ensuring the searchability and accessibility via MSS (both in collaboration with M6.3), and</p>
            </list-item>
            <list-item>
              <p>providing a rich description of chemistry data to improve interoperability and reusability aimed at knowledge graphs developed in M6.3, while using broadly applicable languages for its representation.</p>
            </list-item>
          </list>
        </p>
        <p>In all cases, we will make use of persistent identifiers and work with the PID4NFDI base service under development. We will document the use of the schemas, e.g. in the NFDI4Chem Knowledge Base and the MSS documentation, how to properly write, read, validate, and harvest metadata, considering both low-technology and high-level solutions. Through the partners PTB and BAM, we expect to drive the adoption of the vocabularies and metadata schemas in norms and convey them to the industry, e.g., via regulatory requirements.</p>
        <p>We will explore and recommend APIs to access and harvest metadata, including the well-established OAI-PMH protocol, where the FIZ OAI provider also supports cross-walks (see T6.3.4) between metadata schemes (e.g., DataCite, Dublin Core, RADAR). Newer approaches may integrate better with today’s repository architectures, including Event Notifications following the push principle or the ResourceSync specification for Sitemap-based access.</p>
        <p>
          <bold>M4.2 Development and maintenance of standards for data exchange and archival</bold>
        </p>
        <p><bold>Goals</bold>: Develop and specify standards for specific data types in chemical research, contributing to O4.1, O4.2, and O4.5.</p>
        <p><bold>Description</bold>: Data exchange and LTA require open formats for analytical data, as well as open formats to describe molecules and characterise chemical reactions. Existing open data formats will be examined, and areas of potential development will be determined, along with packaging methods with source vendor formats. The key goal is the implementation of metadata schemes, based on the MIChI standard developed in M4.1, for related data types/groups for a broad user base to maximise general acceptance and allow for a systematic extension/differentiation according to specific sub-community needs. Additionally, we will accommodate the experience of partners working on machine learning (ML) methods as key requirements for standards to improve the level of AI-readiness of standards-compliant data.</p>
        <p>
          <italic>T4.2.1 Molecule and chemical reaction standards</italic>
        </p>
        <p>In this task, we will further develop specifications of data standards for chemical data on molecules and chemical reactions also, including characterisation of enzymatic reactions, leveraging the experience of our partners in standardisation initiatives and data exchange formats while working with chemists, software and ontology developers to ensure a balanced focus on the chemical representation and the suitable use of the file formats in software and repositories. Our partner BI (in-kind) and USt will extend the EnzymeML data model to document analytics- and process-related metadata. Through partner PTB, we will include chemical safety as an integral part of our specifications. We will ensure that our models cover the extended concept of chemical reactions, including thermochemical conversion with its kinetics while implementing and contributing to the development of identifier systems for chemical mixtures and molecules of unknown structure through our activities in the InChI Trust. IUPAC´s International Chemical Identifier (InChI) is a unique representation of molecules, which is the basis for linking the data in ELNs and repositories. In FP1, we focused on the implementation of molecular inorganic chemistry into the InChI, which had been ignored for more than 20 years. This work is now almost accomplished (<xref ref-type="bibr" rid="B13574014">Herres-Pawlis et al. 2024</xref>) by the team of our co-applicant S. Herres-Pawlis (RWTH) in the Board of the InChI Trust. In the next phase, inorganic stereochemistry and polymer chemistry will be integrated. Polymer chemistry in particular, represents a highly interesting industrial use case (see M5.5) because an international standard is lacking and urgently needed. BigSMILES (<xref ref-type="bibr" rid="B13579683">Lin et al. 2019</xref>) can deal with simple polymers but not complex architectures. The extension of InChI will be implemented into other services such as Chemotion ELN and repository (see T2.4.1). For the ML community, the new identifier MolBar also gains importance and will be regarded here (<xref ref-type="bibr" rid="B13579700">van Staalduinen and Bannwarth 2024</xref>).</p>
        <p>
          <italic>T4.2.2 Analytical data standards</italic>
        </p>
        <p>In this task, we will work with software developers, instrumentation companies, industry collaborators, publishers, repository operators and our international network (IUPAC, PSDI) on the specification of data standards for spectral data such as mzML, Allotrope Simple/Data Model (ASM/ADM), NMReData, nmrML and JCAMP-DX. This will include the enrichment of metadata based on the metadata schemes derived from MIChIs (see M4.1), thus improving the FAIRness of data format standards. Moreover, the community-established STAR format type CIF and NMR-STAR will be combined and augmented by further analytical and computational data for which standards and tags have to be defined. This results in the already described Molecular Information File (MIF), which will be revived, adapted and harnessed for synthetic and analytic molecular data.</p>
        <p>An important aspect is automated metadata extraction, which improves the documentation of analytical data formats, along with ensuring unique and persistent instrument identifiers via the PIDINST initiative (<xref ref-type="bibr" rid="B13579709">Stocker et al. 2020</xref>, <xref ref-type="bibr" rid="B13579722">Krahl et al. 2021</xref>). Data sources include, but are not limited to, measurement devices such as NMR, mass spectrometry, X-ray diffraction, UV-Vis, IR, Raman, EPR, photoluminescence spectroscopy, and electrochemistry. The proper packaging of chemical data with provenance, usage policies, and contribution references will boost efficient data exchange between researchers, ELNs and repositories, where initiatives such as RO-Crate (see M2.3, M2.6, M3.2) will be explored.</p>
        <p>
          <bold>M4.3 Implementation and support of software components for creation, validation, and consumption of standardised data formats</bold>
        </p>
        <p><bold>Goals</bold>: M4.3 contributes to O4.3, and O4.5.</p>
        <p><bold>Description</bold>: The availability of reference implementations is important to foster the broad adoption of data standards developed in M4.1 and M4.2. This requires readers, writers, validators, and converters, either as standalone software libraries or integrated into widely used chemistry software and libraries for commonly used programming languages, such as Python or Java. We will provide extensions to existing software libraries for standardised data formats such as EnzymeML (USt, Bi in-kind), mzML, ASM/ADM, NMReData, nmrML and JCAMP-DX, or where needed, develop tools supporting the data standards. Existing OS converters require broad test data. For use within workflow systems, tools like basic conversion and validation need to be described, e.g., the Common Workflow Language (CWL) (<xref ref-type="bibr" rid="B13579735">Crusoe et al. 2022</xref>).</p>
        <p>
          <italic>T4.3.1 Reference implementation of conversion, extraction and validation libraries</italic>
        </p>
        <p>Data standards defined in M4.2 need a software ecosystem that supports the input and output functionality to be available for software developers processing such data. The software needs to be usable both standalone and by users and allow batch execution in connection with Chemotion ELN and repositories in NFDI4Chem. In conjunction with the Semantic Data Hub (see M6.3), we will develop the extraction of metadata from data formats through the software libraries. The tool description of the Common Workflow Language (CWL) (<xref ref-type="bibr" rid="B13579735">Crusoe et al. 2022</xref>) allows encoding rich software metadata from authors and contributors to ontology-backed information about data formats for inputs and outputs. The CWL descriptions we develop will be deposited to public repositories like the <ext-link ext-link-type="uri" xlink:href="https://github.com/common-workflow-library/">common-workflow-library</ext-link> or WorkflowHub (<xref ref-type="bibr" rid="B13520881">Goble et al. 2021</xref>).</p>
        <p>
          <italic>T4.3.2 Workflows for processing of standards-compliant data</italic>
        </p>
        <p>Extensions for seamless data processing greatly enhance the value of standardised data formats: ingesting analytical and process-related data and metadata, enabling modelling of analytical data, including time course data, relating parameters with metadata, and publishing datasets in repositories. Such implementations should form an ecosystem that can be used in non-trivial workflows with little to no human intervention.</p>
        <p>
          <bold>M4.4 Improving re-usability of scientific data through data standards</bold>
        </p>
        <p><bold>Goals</bold>: M4.1 contributes to O4.4, O4.1, O4.2.</p>
        <p><bold>Description</bold>: In this measure, we will collect, adapt, and demonstrate approaches to standardising the access to and re-use of scientific chemistry data. This involves specifically standards and standardised APIs to integrate between ELNs, repositories, and data processing and analytics infrastructures.</p>
        <p>
          <italic>T4.4.1: Adopt and improve approaches for machine-actionable data and metadata</italic>
        </p>
        <p>This includes efforts to establish prototypes of ML-ready data pools based on existing data. These data pools will be augmented and annotated and also published in NFDI4Chem repositories. The suitability for AI tasks will be directly assessed via the MLOps workflows (see next task), and described in user and developer-facing documentation and articles. Additionally, work in this task improves the FAIRness scores obtained through automated FAIR assessment tools. We will make sure that all improvements actually simplify data reuse, rather than just play games to game FAIR assessment tools.</p>
        <p>
          <italic>T4.4.2: Enable machine learning on chemistry datasets</italic>
        </p>
        <p>In recent years, ML has been established in chemistry for the analysis of data as well as the development of predictive and generative models. Nevertheless, the research of the application of ML methods and algorithms is a complex task that requires not only knowledge of ML but sufficient, unbiased data, computing resources, and tools. Thus, we will develop and provide workflows (MLOps) for chemists to consume the standards-compliant data specified in this TA from our services. We will integrate existing tools, e.g. ML libraries, container orchestration (Kubernetes), ML development environments (collaborating with the JupyterHub-based service), and version control (GitLab) to create an easy-to-use ML development, testing, and execution infrastructure.</p>
        <p>This will include, among other things, interfaces to data repositories, improving standardised access to data (in cooperation with M4.2 and M4.3), integrating Cloud and High-Performance Computing resources, encapsulating standard ML development procedures, automatic documentation for reproducibility of the development steps, and a user interface specific for chemists.</p>
        <p>The development of this service by the partner TUDr will be in close cooperation with the chemists (e.g., requirements analysis, agile development with fast feedback cycles, joint testing, and evaluation) and include AI tools like MEGAN (<xref ref-type="bibr" rid="B13520196">Teufel et al. 2022</xref>, <xref ref-type="bibr" rid="B13520931">Sacha et al. 2020</xref>), and application of the EnzymeML platform to demonstrate the reuse of data by reanalysing previously published datasets which have been stored in standardised data formats.</p>
        <p>
          <italic>T4.4.3: Approaches for the development and integration of hybrid experimental/computational datasets</italic>
        </p>
        <p>This task ensures that the data standards are applicable for integrating experimental and simulated (atomistic) data. Expanding the chemical space or covered properties in datasets has become an increasing trend by padding the latter with simulation results (the most prominent examples coming from material sciences). This is not yet a widespread practice in chemistry (particularly solution chemistry), but it would hold large potential for the streamlining of data acquisition and requires that data standards between them are interoperable. Some of the biggest challenges are cross-validation and normalisation, ensuring that the resulting hybrid datasets are internally consistent. There are also theoretical datasets across different areas with different provenance and, therefore, not interoperable (due to different levels of theory, numerical thresholds, etc.).</p>
        <p>In this task, we will pursue the development of validation tools for repetitive measurements and closely related simulation experiments using multiple models. Data outliers can be identified through learning models applied on rather diverse chemical datasets, including but not limited to kinetic (<xref ref-type="bibr" rid="B13579773">Proppe and Kircher 2022</xref>), reaction thermodynamics (<xref ref-type="bibr" rid="B13579782">Tielker et al. 2020</xref>) and spectral data (<xref ref-type="bibr" rid="B13579793">Fischer et al. 2022</xref>). Another strength of the approach is that it is not only domain-independent but can also be applied to experimental and simulated datasets (and subsets thereof). The tools developed will provide standards for testing compatibility between different methods of data acquisition, enable aggregated datasets, and provide or improve uncertainty quantification in existing datasets.</p>
        <p>
          <bold>M4.5 Integration with scholarly publishing</bold>
        </p>
        <p><bold>Goals</bold>: M4.5 contributes to O4.4.</p>
        <p><bold>Description</bold>: Academic publishing is the primary mode of communication for scientists, and publishing is an integral part of research on all levels. Many institutions and funders are beginning to mandate that research data be open, findable, and measurable. Publishers of academic journals have a keen interest in publishing high-quality articles to avoid jeopardising their reputations. Given the integral role of data as the foundation of any scholarly publication, academic publishers also recognise the importance of the publication, curation, and review of research data. Almost all have a data availability policy. However, researchers and publishers lack the tools and workflows necessary for the seamless curation, publication, and dissemination of research data. This is especially true in the area of the chemical sciences.</p>
        <p>In this measure, we pursue tasks to improve data publishing processes, quality control mechanisms for research data, and simplify the reuse of machine-readable research data for scientists. This will require interaction between authors, editors of journals, reviewers, and developers of data and metadata infrastructures.</p>
        <p>This measure also has great synergy potential with other NFDI consortia due to its domain-independent aspects, including processes to encourage, validate, review, and disseminate deposited and associated data and efficient retrieval and monitoring.</p>
        <p>
          <italic>T4.5.1 Co-development of academic data publishing with publishers</italic>
        </p>
        <p>As an integral part of academic publishing, data publishing is handled at different points along the publishing process. This may include the manuscript and data submission step, review processes (also see T3.3.5), data processing and formatting for machine-readability, metadata registration and linking, and presentation of the repository metadata in the published article and its DOI landing page, in addition to the delivery of the information to relevant databases and repositories.</p>
        <p>We will work within our existing Editors4Chem format with publishers, where we can connect them with developers and repositories (see M5.6) to initiate pilot projects that would allow us to determine the feasibility, propose workflows to streamline data publishing in conjunction with research articles, define and recommend exchange standards and APIs, and identify required developments that will be summarised as recommendations (see also M4.1) to publishers and chemistry repositories.</p>
        <p>
          <italic>T4.5.2 The Editors4Chem workshop</italic>
        </p>
        <p>While each pilot project from T4.5.1 will be conducted with an individual or a smaller group of academic publishers under the umbrella of Editors4Chem, we will use the Editors4Chem Workshop to communicate the lessons learnt, standards, and best practices developed to streamline data publishing workflows and recommend APIs for (meta)data exchange to all academic publishers active in the field of chemistry. The Editors4Chem Workshop is a biennial workshop series that brings together journal editors of diverse academic publishers, developers of standards and infrastructures and enthusiastic chemists to work on measures to increase the deposition and appreciation of FAIR chemistry data associated with scientific publications. The workshop organisation is a joint effort with the Committee on Publications and Cheminformatics Data Standards of the IUPAC (see M6.5).</p>
        <p>Table <xref ref-type="table" rid="T13519849">5</xref></p>
      </sec>
      <sec sec-type="5.5 TA5 Community and Training">
        <title>5.5 TA5 Community and Training</title>
        <p>Research data management (RDM) has received increasing attention in the scientific community in recent years. Major funding bodies such as the DFG and the EC have introduced requirements for research data, such as DMPs and RDM strategies. While the issue can no longer be ignored and is being embraced by some, it still faces much confusion and sometimes rejection in the community.</p>
        <p>Facilitating the cultural change towards FAIR research data remains a long-term challenge. In our TA, it is crucial to be aware of the community's needs while supporting researchers in their challenges in producing and publishing FAIR research data. The cornerstones of our strategy are a professional communications strategy (Fig. <xref ref-type="fig" rid="F13519937">6</xref>), providing guidance through intensive training activities, and providing a wide range of best practice examples and use cases. To ensure the sustainability of our activities, we will focus on developing modular and multidimensional training elements, with a strong emphasis on train-the-trainer approaches.</p>
        <p>We will also provide concepts for embedding RDM into curricula, ideally by integrating it into existing courses without requiring formal, time-consuming changes. We will make our open educational resources available in our NFDI4Chem knowledge base, YouTube, Zenodo, etc., and they will be documented via the BMBF-funded DALIA platform. DALIA is the result of cross-consortium work in the Edutrain section. To best meet the community's needs, we will work closely with all other TAs to ensure that these needs are met.</p>
        <p>TA5 will contribute to the key objectives KO3, KO4, KO5, and KO6. More specifically, the <bold>objectives</bold> of TA5 are:</p>
        <p><bold>O5.1</bold>: Continuously mediating a cultural change to the community</p>
        <p><bold>O5.2</bold>: Collecting requirements from the community</p>
        <p><bold>O5.3</bold>: Training of the community and the next generation of scientists</p>
        <p><bold>O5.4</bold>: Highlight best practices and FAIR-compliant machine learning applications</p>
        <p>These objectives will be pursued through the following measures:</p>
        <p>
          <bold>M5.1: Community requirements</bold>
        </p>
        <p><bold>Goals</bold>: Continuously collect community requirements and transform them into actionable tasks.</p>
        <p><bold>Description</bold>: This measure aims to continuously gather community requirements through surveys and events to understand and promote adopting FAIR data practices. These requirements will then be analysed, prioritised, and translated into actionable tasks to improve RDM tools and practices in different task areas.</p>
        <p>
          <italic>T5.1.1: Continuous collection of requirements and needs from the community</italic>
        </p>
        <p>As in FP1 (s. 3.1, 4.1), we will continue to gather the needs of our community and its subdisciplines in FP2. The next surveys are planned for 2026 and 2029. In addition to the surveys, we have found that collecting requirements at the NFDI4Chem conference booths and in workshops (Chemistry Data Days, RDM and Chemotion workshops) is also very efficient in obtaining high quality detailed requirements.Pharmacy-specific requirements for RDM are being collected via the DPhG and TUBr-UB (FID Pharmacy).</p>
        <p>
          <italic>T5.1.2: Transformation of requirements into feasible tasks for other Task Areas</italic>
        </p>
        <p>From the surveys and the directly communicated requirements, TA5 distils the requirements and discusses the prioritisation with the other TAs. Technically, many requirements for ELNs and repositories are correlated and joint solutions need to be found between TA2 and TA3. Here, the desired features of the RDM tools, new ideas for workshops and pages in our knowledge base are transformed into feasible tasks for TA2-TA6.</p>
        <p>
          <bold>M5.2: Awareness</bold>
        </p>
        <p><bold>Goal</bold>: Raise awareness by communicating with the community in a variety of ways</p>
        <p><bold>Description</bold>: This measure uses the website, newsletters, and social media and societies to reach diverse stakeholders. Direct engagement with the chemical community will be sought through conference stands, presentations, and workshops.</p>
        <p>
          <italic>T5.2.1: Website contents, newsletters, and social media in cooperation with societies</italic>
        </p>
        <p>The communication strategy developed in FP1 includes the maintenance of the NFDI4Chem website as the first point of contact for news, events, and general information and as an entry point to the knowledge base (see T5.3.1). The touchpoint analysis (Fig. <xref ref-type="fig" rid="F13519937">6</xref>) shows that the full range of analogue and digital media (including social media such as LinkedIn, X, Instagram, Bluesky, Mastodon, etc.) is needed to reach all stakeholder groups ranging from pre-/post-graduate students, senior researchers to PIs, data stewards, librarians, publishers and many more (cite communication strategy when published). The societies play an important role as multipliers through their newsletters, but also through their social media accounts. The frequency of the NFDI4Chem newsletter will be increased to a bi-monthly basis as more results and news need to be communicated. A special feature of NFDI4Chem is the regular monthly "Stammtisch" (all-digital), where researchers report on their RDM solutions but also on topics such as machine learning in chemistry, news from the InChI development and new repos or ELN solutions. Besides the talk, which is recorded and posted on <ext-link ext-link-type="uri" xlink:href="https://www.youtube.com/watch?v=rxTpJ6fRZnc&amp;list=PLlTKDYkC1Ls8qss_8q7qefE8WNOrAnn0D">YouTube</ext-link>, the "Stammtisch" features a longer and lively discussion between a mixed audience of chemoinformatics and RDM experts and benchtop chemists.</p>
        <p>
          <italic>T5.2.2: Conference booths and presentations</italic>
        </p>
        <p>Direct contact with the chemical community can be obtained easily via booths at general chemical conferences and rather specific conferences for chemical sub-disciplines. In FP1, NFDI4Chem was present at more than 30 conferences, which we plan to continue in FP2 to bring the new tools into the community. To present our results, we follow two strategies: a) Direct results are presented in talks at conferences, and we also invite talks to colloquia and webinars. These presentations are more interesting to the RDM and chemoinformatics audience and serve the (inter)national networking. b) To inform the chemical community, we present best practices on how to use the ELNs, repos and other new RDM tools at all important conferences in chemistry (many GDCh, DPhG, EuChemS, IUPAC, and selected ACS conferences). The Chemiedozententagung and the Spring Symposium of the GDCh Jungchemikerforum play an important role in special multiplier conferences. We have been present here with booths and workshops for the last few years and will continue this. We will also be present at RDM community conferences such as RDA-DE, CoRDI or E-Science Days to share developments and adapt new ideas to the needs of chemists.</p>
        <p>
          <bold>M5.3: Training and Support</bold>
        </p>
        <p><bold>Goal</bold>: Provide training and support resources to enable the community in RDM</p>
        <p><bold>Description</bold>: This measure is about enhancing the NFDI4Chem Knowledge Base, developing tailored RDM training modules, conducting extensive training sessions, operating a help desk for support, and creating train-the-trainer resources for local RDM multipliers.</p>
        <p>
          <italic>T5.3.1: Improve and extend existing information resources</italic>
        </p>
        <p>During FP1, we established the <ext-link ext-link-type="uri" xlink:href="https://knowledgebase.nfdi4chem.de/">NFDI4Chem Knowledge Base</ext-link> as a community effort based on <ext-link ext-link-type="uri" xlink:href="https://github.com/NFDI4Chem/knowledge_base">GitHub</ext-link> and hosted at JGU,, which offers a repository guide and an interactive best practice section with examples of actual data publications. During FP2, we will continuously improve and extend the <ext-link ext-link-type="uri" xlink:href="https://knowledgebase.nfdi4chem.de/">NFDI4Chem Knowledge Base</ext-link>. In particular, we will work on making it visually more appealing and reducing the length of the article's text without omitting important information. New participants are asked to add specific information about domains not currently represented in the knowledgebase (e.g. electrochemistry).</p>
        <p>
          <italic>T5.3.2: Development of granular target- and phase-specific training modules</italic>
        </p>
        <p>Comprehensive training is essential for a successful cultural change towards RDM. This training must be tailored to different audiences at different stages of their scientific careers. This requires modular training elements that can be interchanged to meet different needs. In particular, these modules should enable data stewards and local RDM multipliers to develop chemistry-specific training themselves (see T5.3.5). In this respect, these modules are key to establishing a sustainable training infrastructure.</p>
        <p>
          <italic>T5.3.3: Extensive on-site training activities on general RDM topics and ELNs</italic>
        </p>
        <p>Training courses in general chemistry RDM and Chemotion ELN will become more important during FP2, and we will allocate more human resources to them. The general RDM in chemistry training comprises the basics of FAIR data, ELNs, repos, metadata, and DMPs. DMPs for chemists are a special focus of TA5 since the community requests them for numerous funded projects as well as collaborative projects. While these courses serve an important purpose, they also serve as a testing ground for optimising the training modules developed in T5.3.2.</p>
        <p>
          <italic>T5.3.4: Operate a helpdesk unit</italic>
        </p>
        <p>We have seen that the demand for direct support increases as new tools and workflows are implemented in the community. During FP1, we successfully implemented the <ext-link ext-link-type="uri" xlink:href="https://www.nfdi4chem.de/helpdesk/">NFDI4Chem Helpdesk</ext-link> at TIB (707 successfully closed tickets from 384 requesters since 04/2021), which is the first point of contact for all kinds of questions or doubts. The helpdesk is operated by a first-level team that classifies incoming requests and forwards them to the appropriate second-level experts while maintaining communication with the requesters.</p>
        <p>This activity will continue with a focus on improving efficiency. This will include the creation of SOPs from the cases to be disseminated through the knowledge base to facilitate self-service and to enable second-level support from more local stakeholders after FP2 to ensure improved sustainability.</p>
        <p>
          <italic>T5.3.5: Develop comprehensive train-the-trainer resources to empower local RDM multipliers</italic>
        </p>
        <p>During FP1, we have gained extensive experience in implementing RDM and ELN activities in research groups in CH, CZ, DE, DK, ES, Estonia, FR, IN, IT, NL, PT, SK, Slovenia, Thailand, TR, UK, and USA. We are, therefore, well aware of the challenges faced not only by researchers but also by local RDM stakeholders. We will identify suitable regional stakeholders to collaborate intensively in the creation of train-the-trainer resources. Local RDM teams at the universities are the ideal partners as multipliers. We strive for the sustainable integration of our materials into the RDM structures of universities. We will use the synergies arising from the activities in T5.3.3 to facilitate sustainable and long-term decentralised training activities, ultimately independent of NFDI4Chem.</p>
        <p>
          <bold>M5.4: Curricular teaching</bold>
        </p>
        <p><bold>Goal</bold>: Implement chemistry-specific RDM early in academic education</p>
        <p><bold>Description</bold>: This measure will develop and promote curricular recommendations for integrating RDM content into existing chemistry curricula through practical exercises and refine these models for wider implementation in chemistry departments.</p>
        <p>
          <italic>T5.4.1: Develop and promote curricular recommendations</italic>
        </p>
        <p>In FP1 in 2021, the GDCh published the recommendations for the new chemistry curricula (<xref ref-type="bibr" rid="B13579919">Gesellschaft Deutscher Chemiker e.V. (GDCh) 2021</xref>). This was an important step with a strong signalling effect on the chemistry community, but curricula may only be changed very slowly. For FP2, we will work on the curricular recommendations and promote them further in the community, as well as continuously survey progress from direct contacts with chemistry departments. Besides the targeted inclusion of RDM content into chemistry curricula, we observed in FP1 that the sub-curricular implementation was easier and, in many cases, straightforward. Without changing credit points or administering lecture hours between chemical subdisciplines, RDM content can be successfully implemented in lab stages (<xref ref-type="bibr" rid="B13569079">Fink et al. 2023</xref>) and selected lectures.</p>
        <p>
          <italic>T5.4.2: Develop and implement material for existing curricula</italic>
        </p>
        <p>The implementation of RDM content in existing curricula is guided by practical experience: laboratory phases, which are an important part of chemistry studies, are enriched by RDM seminars and the use of ELNs by students. In FP1, we have gained several years of experience with the implementation of RDM content in Master's lectures (e.g. in the Inorganic Master's lecture in Aachen and an RDM lecture at the TU Darmstadt) and the use of ELNs in bachelor's laboratory courses (e.g. Inorganic Chemistry in Aachen and Organic Chemistry in Kaiserslautern). A student survey helped to monitor the implementation of the ELN and the integration of RDM and to improve the teaching materials and concepts (<xref ref-type="bibr" rid="B13569079">Fink et al. 2023</xref>). The three-year follow-up showed a growing awareness of RDM and increased acceptance of ELNs among students. The survey results highlight the need for and progress made in teaching RDM early in chemistry studies. Moreover, the possibility of integrating the topic as a practical experience is an easy way to integrate it quickly into teaching without changing the whole curriculum. Students like the hands-on approach and connect the theoretical knowledge of RDM directly to the synthesis of compounds in the laboratory. They can easily experience the benefits of RDM tools and gain meta-competence as digital skills for their future careers. For FP2, we plan to refine this model and roll it out to other chemistry departments. Additional materials for students will be prepared. In addition, RDM content will be implemented in the chemistry teaching degrees.</p>
        <p>
          <bold>M5.5: Best practice</bold>
        </p>
        <p><bold>Goal</bold>: Highlighting best practice and machine learning applications with FAIR data</p>
        <p><bold>Summary</bold>: This measure highlights best practices across chemical disciplines and monitors evolving RDM tools, fostering industrial collaboration on standards and solutions. A particular focus will be on FAIR-compliant machine learning applications, such as blind prediction challenges, to promote reproducible workflows and enable machine learning applications in FP2.</p>
        <p>
          <italic>T5.5.1: Assemble use cases, visions, success stories</italic>
        </p>
        <p>RDM poses varying challenges for different chemistry sub-disciplines, especially ELN interoperability when exchanging data. We will highlight best practices in our Knowledge Base and training workshops, attracting partners from all subdisciplines to provide diverse visions and success stories (see T2.4.5, T4.4.2). Given the dynamic nature of RDM tool development, continuous monitoring of new developments and their acceptance is necessary.We also aim for closer collaboration with industry, including joint development of standards (see TA4) and identifying best practices. A focus on patents and embargoes will enable new RDM solutions. For example, we are collaborating with BASF to develop a community-wide standard for polymers, such as the PolymerInChI (see TA4). Identifying homopolymers, cross-linked polymers, copolymers, and blends is crucial for recycling polymeric materials in the chemical industry.</p>
        <p>
          <italic>T5.5.2: Maximising reproducibility by blind prediction challenge use cases</italic>
        </p>
        <p>For FP2, we are planning next-generation blind prediction challenges, extending the scope of previous <ext-link ext-link-type="uri" xlink:href="https://github.com/samplchallenges">SAMPL</ext-link> and Fe-MAN (<xref ref-type="bibr" rid="B13579927">Rahrt et al. 2024</xref>) challenges, where the community will peer-evaluate submissions, in particular for FAIR+Rness ("fairerness", extending the FAIR principles by adding a reproducibility requirement), combining prediction accuracy with a FAIR score (Fig. <xref ref-type="fig" rid="F13519939">7</xref>). In this way, we aim at the "gold standard" of scientific publications at the interface of experimental and computational work, as described in Ref. (<xref ref-type="bibr" rid="B13579944">Heil et al. 2021</xref>), which will allow full reproduction of workflows "at the push of a button", thus enabling future continuous ML model training and deployment. We will develop an infrastructure for a "containerised" challenge, integrating experimental and theoretical data and ensuring low-threshold data transfer between local ELNs and federated infrastructures. We will extend the target observables to include predictions for compounds with high experimental uncertainty, thereby improving the reliability of ML models.</p>
        <p>
          <italic>T5.5.3: Enabling machine learning applications as use cases derived from NFDI4Chem repositories</italic>
        </p>
        <p>ML methods will require standardisation efforts (see T4.4.2) and community outreach. The use cases where data from repositories are reused for ML analyses are also highly valuable for the synthetic chemistry community. In particular, the lack of 'negative' data (i.e. plausibly expected but failed experimental approaches or measurements), which biases ML predictions, will be exploited by considering 'real world' data). To this end, standardisation efforts for computational chemistry will be essential to estimate experimental error from theoretical predictions (see T4.4.2).</p>
        <p>
          <italic>T5.5.4: Select and present flagship labs with exemplary RDM implementations</italic>
        </p>
        <p>Flagship labs inspire chemists to work more efficiently with RDM tools. In FP1, we developed a concept for using the Chemotion ELN in research groups with members ranging from interns to the PI (<xref ref-type="bibr" rid="B13579955">Fink et al. 2022</xref>). This addresses concerns about loss of laboratory time when ELNs are introduced. In the long term, groups will be more productive with a group-wide ELN, allowing members to share data more efficiently and quickly find older information.</p>
        <p>During FP1, we initiated the FAIR4Chem award to highlight excellent RDM practices from all corners of the community. The awardees presented their data-sharing solutions at the JCF conference, the Stammtisch and in a video. We will continue to run the FAIR4Chem Award to highlight further excellent FAIR data contributions from the community for the community. Flagship labs from all chemistry subdisciplines will be showcased in the Stammtisch (T5.2.1) and other formats.</p>
        <p>
          <bold>M5.6: Community stakeholders</bold>
        </p>
        <p><bold>Goal</bold>: Networking between a multitude of stakeholders and contributing to standardisation</p>
        <p><bold>Description</bold>: This measure maintains ongoing stakeholder engagement to implement NFDI4Chem recommendations. It includes active participation in international standardisation bodies and communication of results to promote community involvement in standardisation efforts.</p>
        <p>
          <italic>T5.6.1: Exchange between community stakeholders continuously to ensure the implementation of NFDI4Chem recommendations</italic>
        </p>
        <p>Ongoing interaction between the various stakeholders in the community is an important ongoing process. These stakeholders include, for example, learned societies, chemistry faculties, publishers (in collaboration with M4.5), industry or instrument manufacturers. We will continue to facilitate a continuous exchange between these groups, particularly on the work programme of the other actions in TA5 and other NFDI4Chem activities in general, such as standardisation or ontology development.</p>
        <p>
          <italic>T5.6.2: Involvement in international standardisation bodies and communication of the process to the community</italic>
        </p>
        <p>A particular aspect of NFDI4Chem's networking is its collaboration with international standards bodies such as IUPAC or the InChI trust (see T.4.3.1). In close coordination with TA4 (especially M4.1 to M4.3) and TA6 (M6.1, M6.5), we actively collaborate with these bodies at many levels and will continuously disseminate the results of this work to the community. This work has always been done on a largely voluntary basis. Therefore, parties willing to make an effort to work with standards bodies and working groups will have a tremendous impact on the outcome. We will encourage interested parties from the community to contribute to standardisation.</p>
        <p>Table <xref ref-type="table" rid="T13519889">6</xref></p>
      </sec>
      <sec sec-type="5.6 TA6 Synergies and Cross-Cutting Topics">
        <title>5.6 TA6 Synergies and Cross-Cutting Topics</title>
        <p>A hallmark of NFDI is the collaborative effort of consortia to create an overarching infrastructure of interconnected and interoperable services. NFDI4Chem has the same objectives in the field of chemistry. TA6 ensures the harmonisation and integration of services and data into NFDI4Chem and the NFDI-wide infrastructure, providing the Terminology and Search Service. These services will be extended to strengthen the semantic basis of chemistry research data and NFDI4Chem services. The main initiative of TA6 in FP2 is the Semantic Data Hub (SDH) (Fig. <xref ref-type="fig" rid="F13519941">8</xref>), which provides machine-readable FAIR chemistry research data and introduces the Metadata Schema Service and the Chemistry Knowledge Graph. TA6 will continue to formalise and coordinate the development of terminologies and contribute to data and metadata standards. TA6 also coordinates NFDI4Chem's contributions to NFDI-wide initiatives and working groups, including Base4NFDI and TS4NFDI, while integrating existing NFDI services into NFDI4Chem (e.g. IAM4NFDI). An overview of the contributions of NFDI4Chem is described in section 3.2. In addition, collaboration with international bodies such as RDA, IUPAC and projects such as PSDI in the UK will be strengthened. The overall goal for FP2 is to improve the interoperability, AI-readiness and machine-actionability of chemical research data, making it even more FAIR.</p>
        <p>To create synergies, TA6 will contribute to individual aspects of most of the key objectives.</p>
        <p>
          <list list-type="bullet">
            <list-item>
              <p>Key objective 1: seamless integration of distributed data sources and uniform access to data;</p>
            </list-item>
            <list-item>
              <p>key objectives 2: minimum information standards and semantically rich linked data;</p>
            </list-item>
            <list-item>
              <p>key objective 3: seamless digital data workflows,</p>
            </list-item>
            <list-item>
              <p>key objective 4: technically reliable RDM infrastructure;</p>
            </list-item>
            <list-item>
              <p>key objective 5: collaboration with other consortia and promote cross-cutting developments and</p>
            </list-item>
            <list-item>
              <p>key objective 6: data re-use and enabling AI in chemistry.</p>
            </list-item>
          </list>
        </p>
        <p>The following objectives are derived for TA6:</p>
        <p><bold>O6.1</bold> Users can develop, curate and apply terminologies to encode their domain knowledge into machine-actionable research data.</p>
        <p><bold>O6.2</bold> Users can find and re-use research data across the NFDI4Chem federation and harness the full potential of semantically rich data.</p>
        <p><bold>O6.3</bold> Users can use and access NFDI4Chem's services and data based on shared standards in a uniform and user-friendly manner.</p>
        <p><bold>O6.4</bold> The services and data of NFDI4Chem are well-integrated and available within the NFDI and beyond.</p>
        <p>
          <bold>M6.1: Ontology development, curation and harmonisation</bold>
        </p>
        <p><bold>Goal</bold>: Continue improving existing and developing new ontologies needed for FAIR chemical research data.</p>
        <p><bold>Description</bold>: To enable a circular use of research data, it must be annotated with rich and machine-actionable metadata mapped to FAIR terminologies. During FP1, we initiated community-driven actions to improve the availability and access to terminologies relevant to NFDI4Chem (<xref ref-type="bibr" rid="B13568831">Strömert et al. 2022b</xref>). Collaborating with data providers, curators, ontology engineers and researchers, we established workflows for curating ontologies like RXNO and CHMO. Addressing subdisciplines lacking coverage, we are developing the Vibrational Spectroscopy Ontology (VIBSO, <xref ref-type="bibr" rid="B13577477">Strömert et al. 2024c</xref>, <xref ref-type="bibr" rid="B13579965">Strömert et al. 2024b</xref>) with domain experts. With the annual Ontologies4Chem Workshop, we bring together all major stakeholders of the worldwide chemistry ontology community to elaborate on harmonising standards and pipelines for ontology management. In FP2, we will continue and increase our efforts to improve, develop and harmonise ontologies needed by the chemistry community by working on standardised pipelines for curation and deployment. Tasks will be supported by tools and features developed in the TS (M6.2) and the SDH (M6.3).</p>
        <p>
          <italic>T6.1.1 Standardisation of ontology development workflows</italic>
        </p>
        <p>This task focuses on establishing and promoting efficient workflows for developing and curating chemical ontologies, leveraging common tools and methodologies such as the Ontology Development Kit (ODK) (<xref ref-type="bibr" rid="B13579975">Matentzoglu et al. 2022</xref>) or shared design principles and patterns to enhance efficiency and interoperability. Embracing collaborative platforms like GitHub for ontology maintenance and development calls for using the same tools, workflows and best practices to allow fast, iterative and coherent development by diverse contributors and to foster modular interoperability between ontologies. In FP1, we gained knowledge from developing VIBSO and contributing to existing ontologies in this regard (see 6.1.2.), which we aim to refine in FP2 to derive mature methodologies and best practices for the chemistry community, such as migrating RXNO, MOP and CHMO to an ODK-based setup. We will also evaluate the methodology behind the Voc4Cat SKOS (Simple Knowledge Organization System) thesaurus (<xref ref-type="bibr" rid="B13520648">Linke and Moustakas 2023</xref>) to streamline the ontology development process by creating a SKOS thesaurus for urgently needed common chemistry concepts. These efforts aim to improve the standardisation of ontology development, ensuring alignment with community needs and international standards.</p>
        <p>
          <italic>T6.1.2 Domain ontology development</italic>
        </p>
        <p>This task involves continuously contributing to community ontologies like RXNO, CHMO, CHEMINF, ChEBI, MOP, OBI, IAO and nmrCV, and developing new ontologies within NFDI4Chem, like VIBSO. We have identified the need to develop or extend ontologies for electrochemistry to enable the semantic data annotation of new data resources (<xref ref-type="bibr" rid="B13580007">Clark et al. 2021</xref>, <xref ref-type="bibr" rid="B13580023">Pingarrón et al. 2020</xref>), complementing TA4's MIChIs development (see M4.1) and TA2's semantic data annotation within ELNs. We follow a collaborative approach for ontology development, pairing domain experts (e.g. ETOS Cluster, UUlm) with ontology experts, ensuring robust and domain-informed ontologies. Building on T6.1.1’s standardisation efforts and TS features (see M6.2), we will apply, evaluate and provide feedback on the workflows established in T6.1.1. in real-world scenarios to ensure their efficiency. We will also collaborate closely with NFDI consortia related to chemistry, like NFDI4Cat, NFDI4ING, NFDI4Health, NFDI4MatWerk or Dataplant, to ensure the interoperability between the used ontologies and to share the workload.</p>
        <p>
          <italic>T6.1.3. Community engagement - workshop series on ontology development</italic>
        </p>
        <p>We will continue the Ontologies4Chem workshop series in this task to develop and disseminate guidelines and best practices for ontology development and curation. These outcomes will be accessible to the broader chemistry community to promote adoption and establish ongoing collaboration and support. We will engage the chemistry ontology community, including members of the OBO Foundry, PSDI, and NFDI consortia related to chemistry and industry stakeholders like the Pistoia Alliance and Allotrope Foundation. We will deepen our collaboration with RDA working and interest groups (<xref ref-type="bibr" rid="B13580060">Research Data Alliance 2024a</xref>, <xref ref-type="bibr" rid="B13580068">Research Data Alliance 2024b</xref>, <xref ref-type="bibr" rid="B13580076">Research Data Alliance 2024c</xref>, <xref ref-type="bibr" rid="B13580092">Research Data Alliance 2024d</xref>, <xref ref-type="bibr" rid="B13580100">Research Data Alliance 2024e</xref>, <xref ref-type="bibr" rid="B13580108">Research Data Alliance 2024f</xref>, <xref ref-type="bibr" rid="B13580116">Research Data Alliance 2024g</xref>) and IUPAC (<xref ref-type="bibr" rid="B13580051">IUPAC 2024</xref>) to enhance international harmonisation. Additionally, we will participate in NFDI-related events and working groups to foster cross-domain ontology interoperability, continuing our leading role in the NFDI Section (Meta)data WG Ontology Harmonization and Mapping.</p>
        <p>
          <bold>M6.2: Terminology service and mapping service</bold>
        </p>
        <p><bold>Goal</bold>: Enable researchers and services within NFDI4Chem and the broader NFDI community to access, curate, and update terminologies pertinent to chemistry and related domains.</p>
        <p><bold>Description</bold>: The NFDI4Chem Terminology Service (TS) is pivotal in promoting the interoperability, discovery and use of semantic data within NFDI4Chem and beyond. Built on EBI’s Ontology Lookup Service (OLS) framework, we are currently upgrading the TS to the OLS4 codebase for enhanced functionality and performance. Following the analysis of suitable chemistry ontologies, we established the NFDI4Chem ontology collection and continuously integrated user requirements to support ontology development and curation during FP1 (see also M6.1). This systematic expansion aims to transform the TS into a comprehensive platform for ontology management, allowing users to perform curation tasks while monitoring dependencies with other chemical ontologies. Consequently, the TS has become a reference source for discovering and interacting with chemistry ontologies. In FP2, we aim to integrate more features derived from user requirements, including a mapping service in collaboration with the TS4NFDI Mapping Service.</p>
        <p>
          <italic>T6.2.1 Collaborative ontology management integration</italic>
        </p>
        <p>In this task, we focus on enhancing collaborative ontology management in the TS by integrating ontology update pipelines and providing the latest ontology version based on commits in the original repository. We will also archive TS-defined versions every six months, making them available via the API for downstream services. We will extend and integrate the prototypical NFDI4Ing TS Semantic Diff Tool to facilitate version comparison. Additionally, collaborative curation features developed in FP1 will be improved within the TS frontend by enhancing discussion mechanisms that leverage the existing notes and GitHub integration feature and by prototyping an extension of the existing term request feature with the SKOS thesaurus solution evaluated in T6.1.1.</p>
        <p>
          <italic>T6.2.2 Mapping service</italic>
        </p>
        <p>Mapping services are essential for integrating or transforming data from various repositories or research communities. Despite efforts to harmonise ontology development, mapping between overlapping or conflicting terminologies remains crucial due to the inevitable emergence of subdisciplines and projects with their own sets of terms and ontologies. In this task, we will implement the Mapping Service developed and provided by the TS4NFDI basic service. Mappings will be stored using the Simple Standard for Sharing Ontology Mappings (SSSOM). This implementation includes integrating widgets into the NFDI4Chem Terminology Service frontend to create, curate, and analyse mappings between ontologies and connecting to the TS4NFDI API. These mappings will also be utilised in the Metadata Schema Service (MSS) described in T6.3.3. We will also explore how complex mappings can be created and stored, either within NFDI4Chem or in TS4NFDI, to ensure comprehensive and coherent data integration.</p>
        <p>
          <italic>T6.2.3 Integration of TS in basic terminology service</italic>
        </p>
        <p>The backend of the NFDI4Chem Terminology Service is a component of the TS4NFDI basic service backend architecture, providing NFDI-wide access to a federation of terminology services. This task involves coordinating our contributions to the TS4NFDI project and addressing required developments for integration into the NFDI4Chem Terminology Service not covered by the TS4NFDI project. Development efforts will focus on extending the NFDI4Chem API and underlying backend functionalities to provide necessary API endpoints for the basic service API Gateway.</p>
        <p>
          <bold>M6.3 Semantic Data Hub</bold>
        </p>
        <p><bold>Goals</bold>: Provide a central point of access to harmonised and integrated FAIR data from NFDI4Chem, culminating in a chemistry knowledge graph.</p>
        <p><bold>Description</bold>: The digitisation of chemistry data workflows and the integration of all developed services enable us to fully leverage the benefits of machine-actionable data. This measure aims to converge and link activities related to MIChI development, metadata schemas (see M4.1), and semantic data annotation (see M4.2), addressing shortcomings regarding semantic interoperability. (<xref ref-type="bibr" rid="B13521315">Vogt et al. 2024</xref>) FAIR Metadata generation happens early in the Smart Lab or later in repositories. It relies on terminologies and MIChI, provided by the Terminology Service (TS) and the Metadata Schema Service (MSS), which will be developed in this measure. The Search Service harvests this semantically harmonised metadata from repositories, with the ability to index new metadata by loading blueprints for corresponding new metadata schemas from the MSS. This approach enables seamless metadata ingestion into a knowledge graph from the Search Service later, facilitating sophisticated querying across all resources. The MSS for MIChI-derived metadata schemas will improve the development and application of schemas for FAIR data annotations. Combining it with the TS Mapping Service will allow schema crosswalks and, thus, data transformations.</p>
        <p>
          <italic>T6.3.1 Search Service</italic>
        </p>
        <p>The NFDI4Chem Search Service provides central, semantically harmonised access to the subdiscipline-specific repositories of the NFDI4Chem federation. During FP1, in collaboration with TA2, TA3 and TA4, we identified shared principles and requirements for metadata and semantic descriptions, empowering repositories to apply MIChIs for more detailed data descriptions. The harvesting and indexing by the Search Service, which now provides access to over 140,000 datasets from five repositories, are optimised and extended continuously for enhanced search options (i.e. by adding a molecule index or using the TS term look-up API). In FP2, we will extend the Search Service to apply MIChI schemas, allowing for the continuous integration of more repositories and subdiscipline MIChIs. We aim to extend searchable entities to include datasets, reactions, samples, and molecules. The user interface and APIs will also be extended for improved cross-repository data exploration and reuse.</p>
        <p>
          <italic>T6.3.2 Development and implementation of a Chemistry Knowledge Graph</italic>
        </p>
        <p>In this task, we will develop a Chemistry Knowledge Graph (KG) fed by the Search Service data stream (T6.3.1). We will provide a SPARQL endpoint for expert or programmatic access to the KG. To make this SPARQL endpoint more accessible, we will create an intuitive UI with graphical query builders and a library of customisable query templates, reducing the need for users to write SPARQL code directly. Additionally, we will explore natural language processing (NLP) capabilities to allow entering queries in natural language. We will collaborate with the KG4NFDI project to align our work with NFDI's basic service activities.</p>
        <p>
          <italic>T6.3.3 Metadata Schema Service (MSS) for MIChI</italic>
        </p>
        <p>We will develop a Metadata Schema Service (MSS) as a repository and registry for MIChI-based metadata schemas (see M4.1). The MSS will provide a GUI for TA4 to develop, store and serve metadata schemas, one for browsing, understanding, and relating these and other metadata schemas, and an API for machine-actionable access and operations such as metadata validation and schema crosswalks. This centralised service will save resources for chemistry data repositories and data scientists while ensuring standardised data outputs. It will partially depend on the TS4NFDI base service's mapping service, referencing mapping sets as metadata and using them for schema crosswalks. Additionally, the MSS aims to enable the creation and storage of complex mappings needed for schema crosswalks, extending the simple entity-to-entity mapping approach planned for the TS4NFDI mapping service.</p>
        <p>
          <bold>M6.4 NFDI4Chem within the NFDI and basic services</bold>
        </p>
        <p><bold>Goals</bold>: Engage in NFDI sections, working groups, and task forces and contribute to cross-cutting topics relevant to the consortium, shaping processes in our best interest. Contribute to NFDI basic services and successfully integrate these into NFDI4Chem services.</p>
        <p><bold>Description</bold>: NFDI4Chem identifies itself as an integral part of NFDI. We are involved in the NFDI bodies and embody the NFDI vision and strategy to provide data as a common good</p>
        <p>for excellent research organised by the scientific community in Germany. Members of NFDI4Chem contribute to the long-term development of the overarching architecture, the research data commons. We contribute our knowledge and expertise to the NFDI sections to facilitate overall developments and processes. We see the NFDI basic services, based on cross-community requirements and rooted in the NFDI sections and Base4NFDI, as integral components of the NFDI4Chem infrastructure. Following the objectives set out in FP1, we will continue to participate actively in developing and integrating such services.</p>
        <p>
          <italic>T6.4.1 NFDI4Chem contributions to sections, working groups and task forces</italic>
        </p>
        <p>Coordinating NFDI4Chem's contributions to NFDI sections is crucial. We ensure active participation in sections, working groups, and task forces established in FP1 or to be created in FP2. This task aligns NFDI4Chem's expertise with other consortia and feeds results into the consortium via workshops, guidelines, position papers, and shared use cases. NFDI4Chem members are represented in all sections and work groups, such as WG Ontology Harmonization and Mapping, WG Terminology Services, and Task Force Metadata within the section metadata; WG Data Management Planning, WG Electronic Lab Notebooks, and WG Identity and Access Management within the section common infrastructure; section ELSA covering legal aspects, and WP8 Error Culture in Science within the section Edutrain. Future work in the industry engagement section will be done with our industry advisory board.</p>
        <p>
          <italic>T6.4.2 Coordination of basic services integration into NFDI4Chem infrastructure</italic>
        </p>
        <p>Base4NFDI services are integral to NFDI4Chem. During the initialisation phase, we contributed to IAM4NFDI, TS4NFDI, KG4NFDI, and PID4NFDI by completing surveys, participating in workshops or incubator projects, i.e. testing the AAI test instances with the NFDI4Chem TS and Chemotion ELN. These efforts will continue in the integration phase by connecting the authorisation layer and using the IAM4NFDI infrastructure proxy, integrating our TS backend into the TS4NFDI infrastructure and contributing to its API Gateway, as well as collaborating on a mapping service and terminology curation. For PID4NFDI, we will contribute to developing PIDs for samples and instruments. For future basic services, we will introduce generic methodologies and processes for NFDI4Chem that will coordinate and actively support integrating basic services into NFDI4Chem’s infrastructure and services, including incubator projects with basic service projects. We also envision collaborating with KG4NFDI for the Chemistry Knowledge Graph in the Semantic Data Hub.</p>
        <p>
          <bold>M6.5 Integration into the landscape of existing infrastructure and initiatives</bold>
        </p>
        <p><bold>Goal</bold>: Ensure NFDI4Chem's integration within the international infrastructure landscape to enhance interoperability, discoverability, and sustainability of chemistry data and services.</p>
        <p><bold>Description</bold>: Integrating existing infrastructures and initiatives maximises NFDI4Chem's visibility and impact. This involves strategic collaborations with international projects, monitoring relevant groups, and developing sustainable standards-based business models. NFDI4Chem is already involved in initiatives promoting interoperability, standardisation, and visibility of Smart Lab components. Expanding these efforts in FP2 will improve the FAIRness of NFDI4Chem data in chemistry portals and general search engines, making our data and services FAIR for the global research community.</p>
        <p>
          <italic>T6.5.1 Identify and collaborate with relevant international infrastructure projects</italic>
        </p>
        <p>This task focuses on identifying and establishing collaborations with relevant international infrastructure projects. We will actively monitor and engage with RDA, EOSC, and PSDI groups that share common goals. We aim to strengthen existing strategic collaborations with organisations like IUPAC and CODATA, contributing to sustainable business models for standard development and curation. With our engagement within this global network, we will work on long-term solutions for MIChI (see M4.1), metadata schema and terminology curation, as well as on fostering the interoperability and standardisation of Smart Lab components, related workflows and formats, like the *.eln format and RO-Crate.Additionally, we contribute to initiatives like the ELN-finder, making international solutions more visible and understandable. With these diverse efforts, we aim to position NFDI4Chem as a pivotal player in the global chemistry data ecosystem.</p>
        <p>
          <italic>T6.5.2 Improvement of findability of chemistry data resources in general search engines</italic>
        </p>
        <p>For scholarly literature, numerous search, aggregation, and monitoring services exist and are widely used by researchers, including the NFDI4Chem Search Service. This task aims to improve the visibility of chemistry data resources in general search engines like OpenAIRE Explorer, Google Dataset Search, and DataCite Commons. By mapping our data to (Bio)schemas.org, we enhance its representation in general search results while preserving chemistry-specific metadata. We will highlight use cases such as finding data by individuals or institutions, data linked to publications, and publications citing datasets. We will engage with repositories and search services to identify bottlenecks and provide improved metadata. Using our international network, we will develop common approaches and data transformation guidelines for NFDI4Chem repositories to enhance their visibility.</p>
        <p>Table <xref ref-type="table" rid="T13519890">7</xref></p>
      </sec>
    </sec>
    <sec sec-type="6 Additional Aspects.">
      <title>6 Additional Aspects.</title>
      <sec sec-type="6.1 Equal opportunity and diversity">
        <title>6.1 Equal opportunity and diversity</title>
        <p>Equal opportunity and diversity are key aspects of staff and team development and will be ensured as outlined in M1.4. As part of this, NFDI4Chem strongly supports the <ext-link ext-link-type="uri" xlink:href="https://www.nfdi.de/wp-content/uploads/2023/08/NFDI-Verhaltenskodex_NFDI-code-of-conduct.pdf">Code of Conduct</ext-link> adopted by the NFDI and has published an <ext-link ext-link-type="uri" xlink:href="https://www.nfdi4chem.de/wp-content/uploads/2023/09/NFDI4Chem-Addendum-Verhaltenskodex.pdf">addendum</ext-link> with additional points of particular importance regarding equal opportunities. Other activities to promote equal opportunity and diversity are integrated in the paragraphs above but will be highlighted here:</p>
        <p>To promote equal opportunities in our target community, NFDI4Chem has participated in two <ext-link ext-link-type="uri" xlink:href="https://iupac.org/gwb/">IUPAC Global women’s breakfasts</ext-link>, as well as in a panel discussion on critical reflections on RDM at the <ext-link ext-link-type="uri" xlink:href="https://www.zef.de/fileadmin/downloads/2023_06_-_DSSP_SDGs_summary.pdf">SDG Graduate Schools Alliance midterm conference</ext-link>, focusing on equal opportunities for researchers in the global south. We strongly believe that free access to our services promotes equal opportunity in science, as it supports researchers regardless of their institution or background. With free training programs and multilingual instruction materials, we enable scientists of all genders and ethnicities at any stage of their careers to digitalise their workflows, store their data in a FAIR way, and hence prepare for future digital developments both in academia and industry. Our helpdesk provides additional support for those with limited resources or experience. In surveys and personal consultations, we collect feedback from users, particularly those from underrepresented groups, to improve our services. In several online and in-person events, such as the Chemistry Data Days or the Stammtisch series, we create a platform for exchange and networking possibilities, especially for early career scientists, to help them succeed in their research careers. Our services are developed with a focus on user-friendly design and accessibility to ensure usability by a wide range of scientists.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ack>
      <title>Acknowledgements</title>
      <p>This work was done by the participants of the NFDI4Chem consortium, funded by the Deutsche Forschungsgemeinschaft (DFG, German Research Foundation) under the National Research Data Infrastructure – NFDI4/1 – <bold>Project number 441958208</bold> (NFDI4Chem). Further, we want to thank Sabrina Krohm for her intenisve support in redacting and formatting this manuscript.</p>
      <p>Disclosure: During writing, large language models (LLMs) were used to translate the summary and for editorial polishing, <italic>i.e.</italic> English language improvements and moderate shortening of human-written paragraphs. All LLM output was vetted by human authors before inclusion in the document.</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="B13521250">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Amelung</surname>
              <given-names>Lisa</given-names>
            </name>
            <name name-style="western">
              <surname>Anthofer</surname>
              <given-names>Verena</given-names>
            </name>
            <name name-style="western">
              <surname>Danabalan</surname>
              <given-names>Renita</given-names>
            </name>
            <name name-style="western">
              <surname>Demandt</surname>
              <given-names>Évariste</given-names>
            </name>
            <name name-style="western">
              <surname>Ebert</surname>
              <given-names>Barbara</given-names>
            </name>
            <name name-style="western">
              <surname>Elschner</surname>
              <given-names>Elisabeth</given-names>
            </name>
            <name name-style="western">
              <surname>Espinoza</surname>
              <given-names>Sara</given-names>
            </name>
            <name name-style="western">
              <surname>Eufinger</surname>
              <given-names>Jan</given-names>
            </name>
            <name name-style="western">
              <surname>Fuchsloch</surname>
              <given-names>Stefanie</given-names>
            </name>
            <name name-style="western">
              <surname>Götz</surname>
              <given-names>Barbara</given-names>
            </name>
            <name name-style="western">
              <surname>Henzen</surname>
              <given-names>Christin</given-names>
            </name>
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Idda</surname>
              <given-names>Theresa</given-names>
            </name>
            <name name-style="western">
              <surname>Jansen</surname>
              <given-names>Lukas</given-names>
            </name>
            <name name-style="western">
              <surname>Krieger</surname>
              <given-names>Ulrich</given-names>
            </name>
            <name name-style="western">
              <surname>Rodrigues</surname>
              <given-names>Cristina M</given-names>
            </name>
            <name name-style="western">
              <surname>Meister</surname>
              <given-names>Maria</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>Bernhard</given-names>
            </name>
            <name name-style="western">
              <surname>Pitroff</surname>
              <given-names>Sarah</given-names>
            </name>
            <name name-style="western">
              <surname>Popp</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Pushkina</surname>
              <given-names>Aleksandra</given-names>
            </name>
            <name name-style="western">
              <surname>Schatlowski</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Schimmler</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Schneide</surname>
              <given-names>Christiane</given-names>
            </name>
            <name name-style="western">
              <surname>Schörner</surname>
              <given-names>Thomas</given-names>
            </name>
            <name name-style="western">
              <surname>Schwetje</surname>
              <given-names>Thorsten</given-names>
            </name>
            <name name-style="western">
              <surname>Seegert</surname>
              <given-names>Jörg</given-names>
            </name>
            <name name-style="western">
              <surname>Trippel</surname>
              <given-names>Thorsten</given-names>
            </name>
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>Judith</given-names>
            </name>
            <name name-style="western">
              <surname>Wössner</surname>
              <given-names>Elena</given-names>
            </name>
            <name name-style="western">
              <surname>Zinke</surname>
              <given-names>Wolf</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>White Paper: Interim report reference</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.7688729</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520248">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bach</surname>
              <given-names>Felix</given-names>
            </name>
            <name name-style="western">
              <surname>Binder</surname>
              <given-names>Kunigunde</given-names>
            </name>
            <name name-style="western">
              <surname>Bonatto Minella</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Lutz</surname>
              <given-names>Benjamin</given-names>
            </name>
            <name name-style="western">
              <surname>Razum</surname>
              <given-names>Matthias</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>NFDI4Chem - Deliverable D3.3.1: Gap analysis report for selected repositories</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.7602101</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579381">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wissenschaften</surname>
              <given-names>Beilstein-Institut zur Förderung der Chemischen</given-names>
            </name>
          </person-group>
          <article-title>STRENDA DB</article-title>
          <uri>https://www.beilstein-strenda-db.org/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13552928">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bender</surname>
              <given-names>Theo</given-names>
            </name>
          </person-group>
          <article-title>Successful Workshop on FAIR Terminology Services</article-title>
          <uri>https://www.nfdi4chem.de/successful-workshop-on-fair-terminology-services/</uri>
          <date-in-citation content-type="access-date">2024-07-23T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13553257">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bertelmann</surname>
              <given-names>Roland</given-names>
            </name>
            <name name-style="western">
              <surname>Holzer</surname>
              <given-names>Angela Cornelia</given-names>
            </name>
            <name name-style="western">
              <surname>Horstmann</surname>
              <given-names>Wolfram</given-names>
            </name>
            <name name-style="western">
              <surname>Kressin</surname>
              <given-names>Lisa</given-names>
            </name>
            <name name-style="western">
              <surname>Lange</surname>
              <given-names>Rainer</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Schwerpunkt "Digitalität in der Wissenschaft" der Allianz der deutschen Wissenschaftsorganisationen. Digitalität gestalten – Offenheit und Souveränität vorantreiben. 2023 - 2028</article-title>
          <source>Zenodo</source>
          <pub-id pub-id-type="doi">10.5281/zenodo.11189484</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579345">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Labs</surname>
              <given-names>Biedermann</given-names>
            </name>
          </person-group>
          <article-title>SupraBank</article-title>
          <uri>https://suprabank.org/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13551839">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Biernacka</surname>
              <given-names>Katarzyna</given-names>
            </name>
            <name name-style="western">
              <surname>Bierwirth</surname>
              <given-names>Maik</given-names>
            </name>
            <name name-style="western">
              <surname>Buchholz</surname>
              <given-names>Petra</given-names>
            </name>
            <name name-style="western">
              <surname>Dolzycka</surname>
              <given-names>Dominika</given-names>
            </name>
            <name name-style="western">
              <surname>Helbig</surname>
              <given-names>Kerstin</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Janna</given-names>
            </name>
            <name name-style="western">
              <surname>Odebrecht</surname>
              <given-names>Carolin</given-names>
            </name>
            <name name-style="western">
              <surname>Wiljes</surname>
              <given-names>Cord</given-names>
            </name>
            <name name-style="western">
              <surname>Wuttke</surname>
              <given-names>Ulrike</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Train-the-Trainer Concept on Research Data Management (3.0)</article-title>
          <source>Zenodo</source>
          <pub-id pub-id-type="doi">10.34657/5179</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520868">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bierwirth</surname>
              <given-names>Maik</given-names>
            </name>
            <name name-style="western">
              <surname>Glöckner</surname>
              <given-names>Frank Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Grimm</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Schimmler</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Boehm</surname>
              <given-names>Franziska</given-names>
            </name>
            <name name-style="western">
              <surname>Busse</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Degkwitz</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Neuroth</surname>
              <given-names>Heike</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Leipzig-Berlin-Erklärung zu NFDI-Querschnittsthemen der Infrastrukturentwicklung</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.3895208</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579611">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bizer</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Heath</surname>
              <given-names>Tom</given-names>
            </name>
            <name name-style="western">
              <surname>Berners-Lee</surname>
              <given-names>Tim</given-names>
            </name>
          </person-group>
          <year>2009</year>
          <article-title>Linked Data - The Story So Far</article-title>
          <source>International Journal on Semantic Web and Information Systems</source>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="doi">10.4018/jswis.2009081901</pub-id>
        </element-citation>
      </ref>
      <ref id="B13521115">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Boehm</surname>
              <given-names>Franziska</given-names>
            </name>
            <name name-style="western">
              <surname>Buchner</surname>
              <given-names>Benedikt</given-names>
            </name>
            <name name-style="western">
              <surname>Kipker</surname>
              <given-names>Dennis-Kenji</given-names>
            </name>
            <name name-style="western">
              <surname>Kuntz</surname>
              <given-names>Alessandra</given-names>
            </name>
            <name name-style="western">
              <surname>Petri</surname>
              <given-names>Grischka</given-names>
            </name>
            <name name-style="western">
              <surname>Sax</surname>
              <given-names>Ulrich</given-names>
            </name>
            <name name-style="western">
              <surname>Schaar</surname>
              <given-names>Katrin</given-names>
            </name>
            <name name-style="western">
              <surname>von Suchodoletz</surname>
              <given-names>Dirk</given-names>
            </name>
            <name name-style="western">
              <surname>Vettermann</surname>
              <given-names>Oliver</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Sektionskonzept "Ethical, Legal &amp; Social Aspects" (section-ELSA)</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.5646929</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579500">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bonatto Minella</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>Tillmann G</given-names>
            </name>
            <name name-style="western">
              <surname>Jolliffe</surname>
              <given-names>John D</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Analysis of the Landscape of Repositories for Chemistry in re3data</article-title>
          <source>Zenodo</source>
          <pub-id pub-id-type="doi">10.5281/zenodo.8347993</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520269">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bonatto Minella</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Bach</surname>
              <given-names>Felix</given-names>
            </name>
            <name name-style="western">
              <surname>Jolliffe</surname>
              <given-names>John D</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>Tillmann G</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Repos4Chem - criteria for acquisition - for suggestion by NFDI4Chem for data providers</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.8199754</pub-id>
        </element-citation>
      </ref>
      <ref id="B13574209">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Castro</surname>
              <given-names>Leyla Jael</given-names>
            </name>
            <name name-style="western">
              <surname>Fluck</surname>
              <given-names>Juliane</given-names>
            </name>
            <name name-style="western">
              <surname>Arend</surname>
              <given-names>Daniel</given-names>
            </name>
            <name name-style="western">
              <surname>Lange</surname>
              <given-names>Matthias</given-names>
            </name>
            <name name-style="western">
              <surname>Martini</surname>
              <given-names>Daniel</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
            <name name-style="western">
              <surname>Schimmler</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Rebholz-Schuhmann</surname>
              <given-names>Dietrich</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Schema.org as a Lightweight Harmonization Approach for NFDI</article-title>
          <source>Proceedings of the Conference on Research Data Infrastructure</source>
          <volume>1</volume>
          <pub-id pub-id-type="doi">10.52825/cordi.v1i.280</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579620">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chalk</surname>
              <given-names>Stuart</given-names>
            </name>
            <name name-style="western">
              <surname>McEwen</surname>
              <given-names>Leah</given-names>
            </name>
          </person-group>
          <year>2017</year>
          <article-title>The IUPAC Gold Book</article-title>
          <source>Chemistry International</source>
          <volume>39</volume>
          <issue>3</issue>
          <fpage>25</fpage>
          <lpage>30</lpage>
          <pub-id pub-id-type="doi">10.1515/ci-2017-0307</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520630">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chalk</surname>
              <given-names>Stuart</given-names>
            </name>
            <name name-style="western">
              <surname>Munday</surname>
              <given-names>Sam</given-names>
            </name>
            <name name-style="western">
              <surname>Kroenlein</surname>
              <given-names>Ken</given-names>
            </name>
            <name name-style="western">
              <surname>McEwen</surname>
              <given-names>Leah</given-names>
            </name>
            <name name-style="western">
              <surname>Mustafa</surname>
              <given-names>Fatima</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>WorldFAIR (D3.2) Training Package: FAIR Chemistry Cookbook</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.10711949</pub-id>
        </element-citation>
      </ref>
      <ref id="B13569154">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>contributors</surname>
              <given-names>Chemotion ELN</given-names>
            </name>
          </person-group>
          <article-title>Chemotion ELN and repository</article-title>
          <uri>https://www.youtube.com/watch?v=tZHaP6DW-Dw</uri>
          <date-in-citation content-type="access-date">2024-07-29T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13569096">
        <element-citation publication-type="software">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>contributors</surname>
              <given-names>Chemotion ELN</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Chemotion Electronic Lab Notebook (ELN)</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/zenodo.6797527</pub-id>
          <comment content-type="Version">v1.3.0</comment>
        </element-citation>
      </ref>
      <ref id="B13574411">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>contributors</surname>
              <given-names>Chemotion ELN</given-names>
            </name>
          </person-group>
          <year>n.d.</year>
          <article-title>A CLI tool to create and manage instances of Chemotion ELN</article-title>
          <publisher-name>Github</publisher-name>
          <uri>https://github.com/Chemotion/ChemOrc</uri>
        </element-citation>
      </ref>
      <ref id="B13580007">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>Simon</given-names>
            </name>
            <name name-style="western">
              <surname>Bleken</surname>
              <given-names>Francesca L</given-names>
            </name>
            <name name-style="western">
              <surname>Stier</surname>
              <given-names>Simon</given-names>
            </name>
            <name name-style="western">
              <surname>Flores</surname>
              <given-names>Eibar</given-names>
            </name>
            <name name-style="western">
              <surname>Andersen</surname>
              <given-names>Casper Welzel</given-names>
            </name>
            <name name-style="western">
              <surname>Marcinek</surname>
              <given-names>Marek</given-names>
            </name>
            <name name-style="western">
              <surname>Szczesna‐Chrzan</surname>
              <given-names>Anna</given-names>
            </name>
            <name name-style="western">
              <surname>Gaberscek</surname>
              <given-names>Miran</given-names>
            </name>
            <name name-style="western">
              <surname>Palacin</surname>
              <given-names>M Rosa</given-names>
            </name>
            <name name-style="western">
              <surname>Uhrin</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>Friis</surname>
              <given-names>Jesper</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Toward a Unified Description of Battery Data</article-title>
          <source>Advanced Energy Materials</source>
          <volume>12</volume>
          <issue>17</issue>
          <pub-id pub-id-type="doi">10.1002/aenm.202102702</pub-id>
        </element-citation>
      </ref>
      <ref id="B13577509">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>ComPlat</surname>
            </name>
          </person-group>
          <article-title>Repository-Tracker</article-title>
          <uri>https://github.com/ComPlat/Repository-Tracker</uri>
          <date-in-citation content-type="access-date">2024-08-03T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13579735">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Crusoe</surname>
              <given-names>Michael R</given-names>
            </name>
            <name name-style="western">
              <surname>Abeln</surname>
              <given-names>Sanne</given-names>
            </name>
            <name name-style="western">
              <surname>Iosup</surname>
              <given-names>Alexandru</given-names>
            </name>
            <name name-style="western">
              <surname>Amstutz</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Chilton</surname>
              <given-names>John</given-names>
            </name>
            <name name-style="western">
              <surname>Tijanić</surname>
              <given-names>Nebojša</given-names>
            </name>
            <name name-style="western">
              <surname>Ménager</surname>
              <given-names>Hervé</given-names>
            </name>
            <name name-style="western">
              <surname>Soiland-Reyes</surname>
              <given-names>Stian</given-names>
            </name>
            <name name-style="western">
              <surname>Gavrilović</surname>
              <given-names>Bogdan</given-names>
            </name>
            <name name-style="western">
              <surname>Goble</surname>
              <given-names>Carole</given-names>
            </name>
            <name name-style="western">
              <surname>Community</surname>
              <given-names>The CWL</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Methods included: standardizing computational reuse and portability with the Common Workflow Language</article-title>
          <source>Communications of the ACM</source>
          <volume>65</volume>
          <issue>6</issue>
          <fpage>54</fpage>
          <lpage>63</lpage>
          <pub-id pub-id-type="doi">10.1145/3486897</pub-id>
        </element-citation>
      </ref>
      <ref id="B13578466">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Davies</surname>
              <given-names>Antony</given-names>
            </name>
            <name name-style="western">
              <surname>Patiny</surname>
              <given-names>Luc</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>NMRium browser-based nuclear magnetic resonance data processing</article-title>
          <source>Spectroscopy Europe</source>
          <pub-id pub-id-type="doi">10.1255/sew.2021.a18</pub-id>
        </element-citation>
      </ref>
      <ref id="B13552916">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dolcet</surname>
              <given-names>Paolo</given-names>
            </name>
            <name name-style="western">
              <surname>Schulte</surname>
              <given-names>Mariam L.</given-names>
            </name>
            <name name-style="western">
              <surname>Maurer</surname>
              <given-names>Florian</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Chacko</surname>
              <given-names>Rinu</given-names>
            </name>
            <name name-style="western">
              <surname>Deutschmann</surname>
              <given-names>Olaf</given-names>
            </name>
            <name name-style="western">
              <surname>Grunwaldt</surname>
              <given-names>Jan-Dierk</given-names>
            </name>
          </person-group>
          <year>2003</year>
          <article-title>LabIMotion Electronic Lab Notebook as Research Data Management Tool in Catalysis</article-title>
          <source>Proceedings of the Conference on Research Data Infrastructure</source>
          <volume>1</volume>
          <pub-id pub-id-type="doi">10.52825/cordi.v1i.334</pub-id>
        </element-citation>
      </ref>
      <ref id="B13553375">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Eberl</surname>
              <given-names>Franziska</given-names>
            </name>
            <name name-style="western">
              <surname>Jansen</surname>
              <given-names>Lukas</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>Bernhard</given-names>
            </name>
            <name name-style="western">
              <surname>Amelung</surname>
              <given-names>Lisa</given-names>
            </name>
            <name name-style="western">
              <surname>Danabalan</surname>
              <given-names>Renita</given-names>
            </name>
            <name name-style="western">
              <surname>Demandt</surname>
              <given-names>Évariste</given-names>
            </name>
            <name name-style="western">
              <surname>Deschler</surname>
              <given-names>Katharina</given-names>
            </name>
            <name name-style="western">
              <surname>Eggert</surname>
              <given-names>Maja</given-names>
            </name>
            <name name-style="western">
              <surname>Engel</surname>
              <given-names>Judith</given-names>
            </name>
            <name name-style="western">
              <surname>Espinoza</surname>
              <given-names>Sara</given-names>
            </name>
            <name name-style="western">
              <surname>Ferenz</surname>
              <given-names>Stephan</given-names>
            </name>
            <name name-style="western">
              <surname>Fritzsche</surname>
              <given-names>Franziska</given-names>
            </name>
            <name name-style="western">
              <surname>Goedicke</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Götz</surname>
              <given-names>Barbara</given-names>
            </name>
            <name name-style="western">
              <surname>Hennig</surname>
              <given-names>Christine</given-names>
            </name>
            <name name-style="western">
              <surname>Hofmann</surname>
              <given-names>Adina</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffmann</surname>
              <given-names>Carsten</given-names>
            </name>
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Idda</surname>
              <given-names>Teresa</given-names>
            </name>
            <name name-style="western">
              <surname>Jojo</surname>
              <given-names>Tolin</given-names>
            </name>
            <name name-style="western">
              <surname>Jutz</surname>
              <given-names>Regina</given-names>
            </name>
            <name name-style="western">
              <surname>Krieger</surname>
              <given-names>Ulrich</given-names>
            </name>
            <name name-style="western">
              <surname>Meister</surname>
              <given-names>Maria</given-names>
            </name>
            <name name-style="western">
              <surname>Nüst</surname>
              <given-names>Daniel</given-names>
            </name>
            <name name-style="western">
              <surname>Pittroff</surname>
              <given-names>Sarah</given-names>
            </name>
            <name name-style="western">
              <surname>Sauerland</surname>
              <given-names>Kristin</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Schneide</surname>
              <given-names>Christiane</given-names>
            </name>
            <name name-style="western">
              <surname>Schwarz</surname>
              <given-names>Annett</given-names>
            </name>
            <name name-style="western">
              <surname>Schwetje</surname>
              <given-names>Thorsten</given-names>
            </name>
            <name name-style="western">
              <surname>Seegert</surname>
              <given-names>Jörg</given-names>
            </name>
            <name name-style="western">
              <surname>Trippel</surname>
              <given-names>Thorsten</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Collaborative work in NFDI</article-title>
          <source>Zenodo</source>
          <pub-id pub-id-type="doi">10.5281/zenodo.15880071</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520557">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ebert</surname>
              <given-names>Barbara</given-names>
            </name>
            <name name-style="western">
              <surname>Fluck</surname>
              <given-names>Juliane</given-names>
            </name>
            <name name-style="western">
              <surname>Glöckner</surname>
              <given-names>Frank Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>Bernhard</given-names>
            </name>
            <name name-style="western">
              <surname>Schmitt</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Schrade</surname>
              <given-names>Torsten</given-names>
            </name>
            <name name-style="western">
              <surname>Stegle</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Steinbeck</surname>
              <given-names>Christoph</given-names>
            </name>
            <name name-style="western">
              <surname>von Suchodoletz</surname>
              <given-names>Dirk</given-names>
            </name>
            <name name-style="western">
              <surname>Wagemann</surname>
              <given-names>Kurt</given-names>
            </name>
            <name name-style="western">
              <surname>Knebes</surname>
              <given-names>Jennifer</given-names>
            </name>
            <name name-style="western">
              <surname>Kraft</surname>
              <given-names>Sophie</given-names>
            </name>
            <name name-style="western">
              <surname>Seitz-Moskaliuk</surname>
              <given-names>Hendrik</given-names>
            </name>
            <name name-style="western">
              <surname>Sure-Vetter</surname>
              <given-names>York</given-names>
            </name>
            <name name-style="western">
              <surname>Wössner</surname>
              <given-names>Elena</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>NFDI Cross-cutting Topics Workshop Report</article-title>
          <publisher-name>Zendo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.4593769</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579955">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fink</surname>
              <given-names>Fabian</given-names>
            </name>
            <name name-style="western">
              <surname>Hüppe</surname>
              <given-names>Henrika M</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffmann</surname>
              <given-names>Alexander</given-names>
            </name>
            <name name-style="western">
              <surname>Herres‐Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Sharing is Caring: Guidelines for Sharing in the Electronic Laboratory Notebook (ELN) Chemotion as applied by a Synthesis‐oriented Working Group</article-title>
          <source>Chemistry–Methods</source>
          <volume>2</volume>
          <issue>10</issue>
          <pub-id pub-id-type="doi">10.1002/cmtd.202200026</pub-id>
        </element-citation>
      </ref>
      <ref id="B13569079">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fink</surname>
              <given-names>Fabian</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffmann</surname>
              <given-names>Alexander</given-names>
            </name>
            <name name-style="western">
              <surname>Herres-Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Results of a Three-Year Survey on the Implementation of Research Data Management and the Electronic Laboratory Notebook (ELN) Chemotion in an Advanced Inorganic Lab Course</article-title>
          <source>ChemRxiv</source>
          <pub-id pub-id-type="doi">10.26434/chemrxiv-2023-09ljg</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520706">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>Tillmann G</given-names>
            </name>
            <name name-style="western">
              <surname>Ditfe</surname>
              <given-names>Toni</given-names>
            </name>
            <name name-style="western">
              <surname>Rauh</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Parks</surname>
              <given-names>Nicole A</given-names>
            </name>
            <name name-style="western">
              <surname>Liermann</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Schulze</surname>
              <given-names>Tobias</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>NFDI4Chem - Deliverable D4.4.1: 50 Experimental processes and data publications using NFDI4Chem infrastructure and beyond</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.8137599</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579793">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>Taija L</given-names>
            </name>
            <name name-style="western">
              <surname>Bödecker</surname>
              <given-names>Margarethe</given-names>
            </name>
            <name name-style="western">
              <surname>Zehnacker-Rentien</surname>
              <given-names>Anne</given-names>
            </name>
            <name name-style="western">
              <surname>Mata</surname>
              <given-names>Ricardo A</given-names>
            </name>
            <name name-style="western">
              <surname>Suhm</surname>
              <given-names>Martin A</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Setting up the HyDRA blind challenge for the microhydration of organic molecules</article-title>
          <source>Physical Chemistry Chemical Physics</source>
          <volume>24</volume>
          <issue>19</issue>
          <fpage>11442</fpage>
          <lpage>11454</lpage>
          <pub-id pub-id-type="doi">10.1039/d2cp01119k</pub-id>
        </element-citation>
      </ref>
      <ref id="B13578275">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>GmbH</surname>
              <given-names>FIZ Karlsruhe – Leibniz-Institut für Informationsinfrastruktur</given-names>
            </name>
          </person-group>
          <article-title>RADAR4Chem</article-title>
          <uri>https://radar.products.fiz-karlsruhe.de/de/ueber-uns/impressum-rechtliches</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13579118">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wissenschaftskonferenz</surname>
              <given-names>Gemeinsame</given-names>
            </name>
          </person-group>
          <article-title>Bund-Länder-Vereinbarung zu Aufbau und Förderung einer Nationalen Forschungsdateninfrastruktur (NFDI) vom 26. November 2018</article-title>
          <uri>https://www.gwk-bonn.de/fileadmin/Redaktion/Dokumente/Papers/NFDI.pdf</uri>
          <date-in-citation content-type="access-date">2024-07-30T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13579919">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>(GDCh)</surname>
              <given-names>Gesellschaft Deutscher Chemiker e. V.</given-names>
            </name>
          </person-group>
          <article-title>Empfehlungen der GDCh-Studienkommission zum Bachelorstudium Chemie an Universitäten</article-title>
          <uri>https://www.gdch.de/fileadmin/downloads/Service_und_Informationen/Downloads/Schule_Studium/PDF/2021_GDCh_Studienkommission_Druckversion.pdf</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13521128">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Glöckner</surname>
              <given-names>Frank Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Diepenbroek</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Felden</surname>
              <given-names>Janine</given-names>
            </name>
            <name name-style="western">
              <surname>Overmann</surname>
              <given-names>Jörg</given-names>
            </name>
            <name name-style="western">
              <surname>Bonn</surname>
              <given-names>Aletta</given-names>
            </name>
            <name name-style="western">
              <surname>Gemeinholzer</surname>
              <given-names>Birgit</given-names>
            </name>
            <name name-style="western">
              <surname>Güntsch</surname>
              <given-names>Anton</given-names>
            </name>
            <name name-style="western">
              <surname>König-Ries</surname>
              <given-names>Birgitta</given-names>
            </name>
            <name name-style="western">
              <surname>Seeger</surname>
              <given-names>Bernhard</given-names>
            </name>
            <name name-style="western">
              <surname>Pollex-Krüger</surname>
              <given-names>Annette</given-names>
            </name>
            <name name-style="western">
              <surname>Fluck</surname>
              <given-names>Juliane</given-names>
            </name>
            <name name-style="western">
              <surname>Pigeot</surname>
              <given-names>Iris</given-names>
            </name>
            <name name-style="western">
              <surname>Toralf</surname>
              <given-names>Kirsten</given-names>
            </name>
            <name name-style="western">
              <surname>Mühlhaus</surname>
              <given-names>Timo</given-names>
            </name>
            <name name-style="western">
              <surname>Wolf</surname>
              <given-names>Christof</given-names>
            </name>
            <name name-style="western">
              <surname>Heinrich</surname>
              <given-names>Uwe</given-names>
            </name>
            <name name-style="western">
              <surname>Steinbeck</surname>
              <given-names>Christoph</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Stegle</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Weimann</surname>
              <given-names>Joachim</given-names>
            </name>
            <name name-style="western">
              <surname>Schörner-Sadenius</surname>
              <given-names>Thomas</given-names>
            </name>
            <name name-style="western">
              <surname>Gutt</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Stahl</surname>
              <given-names>Florian</given-names>
            </name>
            <name name-style="western">
              <surname>Wagemann</surname>
              <given-names>Kurt</given-names>
            </name>
            <name name-style="western">
              <surname>Schrade</surname>
              <given-names>Torsten</given-names>
            </name>
            <name name-style="western">
              <surname>Schmitt</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Eberl</surname>
              <given-names>Chris</given-names>
            </name>
            <name name-style="western">
              <surname>Gauterin</surname>
              <given-names>Frank</given-names>
            </name>
            <name name-style="western">
              <surname>Schultz</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>Bernard</surname>
              <given-names>Lars</given-names>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>Berlin Declaration on NFDI Cross-Cutting Topics</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.3457212</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520881">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Goble</surname>
              <given-names>Carole</given-names>
            </name>
            <name name-style="western">
              <surname>Soiland-Reyes</surname>
              <given-names>Stian</given-names>
            </name>
            <name name-style="western">
              <surname>Bacall</surname>
              <given-names>Finn</given-names>
            </name>
            <name name-style="western">
              <surname>Owen</surname>
              <given-names>Stuart</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>Alan</given-names>
            </name>
            <name name-style="western">
              <surname>Eguinoa</surname>
              <given-names>Ignacio</given-names>
            </name>
            <name name-style="western">
              <surname>Droesbeke</surname>
              <given-names>Bert</given-names>
            </name>
            <name name-style="western">
              <surname>Leo</surname>
              <given-names>Simone</given-names>
            </name>
            <name name-style="western">
              <surname>Pireddu</surname>
              <given-names>Luca</given-names>
            </name>
            <name name-style="western">
              <surname>Rodríguez-Navas</surname>
              <given-names>Laura</given-names>
            </name>
            <name name-style="western">
              <surname>Fernández</surname>
              <given-names>José M</given-names>
            </name>
            <name name-style="western">
              <surname>Capella-Gutierrez</surname>
              <given-names>Salvador</given-names>
            </name>
            <name name-style="western">
              <surname>Ménager</surname>
              <given-names>Hervé</given-names>
            </name>
            <name name-style="western">
              <surname>Grüning</surname>
              <given-names>Björn</given-names>
            </name>
            <name name-style="western">
              <surname>Serrano-Solano</surname>
              <given-names>Beatriz</given-names>
            </name>
            <name name-style="western">
              <surname>Ewels</surname>
              <given-names>Philip</given-names>
            </name>
            <name name-style="western">
              <surname>Coppens</surname>
              <given-names>Frederik</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Implementing FAIR Digital Objects in the EOSC-Life Workflow Collaboratory</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.4605654</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579491">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>González–Cebrián</surname>
              <given-names>Alba</given-names>
            </name>
            <name name-style="western">
              <surname>Bradford</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Chis</surname>
              <given-names>Adriana E</given-names>
            </name>
            <name name-style="western">
              <surname>González–Vélez</surname>
              <given-names>Horacio</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Standardised Versioning of Datasets: a FAIR–compliant Proposal</article-title>
          <source>Scientific Data</source>
          <volume>11</volume>
          <issue>1</issue>
          <pub-id pub-id-type="doi">10.1038/s41597-024-03153-y</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520070">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gregory</surname>
              <given-names>Arofan</given-names>
            </name>
            <name name-style="western">
              <surname>Bell</surname>
              <given-names>Darren</given-names>
            </name>
            <name name-style="western">
              <surname>Brickley</surname>
              <given-names>Dan</given-names>
            </name>
            <name name-style="western">
              <surname>Buttigieg</surname>
              <given-names>Pier Luigi</given-names>
            </name>
            <name name-style="western">
              <surname>Cox</surname>
              <given-names>Simon</given-names>
            </name>
            <name name-style="western">
              <surname>Edwards</surname>
              <given-names>Michelle</given-names>
            </name>
            <name name-style="western">
              <surname>Doug</surname>
              <given-names>Fils</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez Morales</surname>
              <given-names>Luis Gerardo</given-names>
            </name>
            <name name-style="western">
              <surname>Heus</surname>
              <given-names>Pascal</given-names>
            </name>
            <name name-style="western">
              <surname>Hodson</surname>
              <given-names>Simon</given-names>
            </name>
            <name name-style="western">
              <surname>Kanjala</surname>
              <given-names>Chifundo</given-names>
            </name>
            <name name-style="western">
              <surname>Le Franc</surname>
              <given-names>Yann</given-names>
            </name>
            <name name-style="western">
              <surname>Maxwell</surname>
              <given-names>Lauren</given-names>
            </name>
            <name name-style="western">
              <surname>Molloy</surname>
              <given-names>Laura</given-names>
            </name>
            <name name-style="western">
              <surname>Richard</surname>
              <given-names>Steve</given-names>
            </name>
            <name name-style="western">
              <surname>Rizzolo</surname>
              <given-names>Flavio</given-names>
            </name>
            <name name-style="western">
              <surname>Winstanley</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Wyborn</surname>
              <given-names>Lesley</given-names>
            </name>
            <name name-style="western">
              <surname>Burton</surname>
              <given-names>Adrian</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>WorldFAIR (D2.3) Cross-Domain Interoperability Framework (CDIF) (Report Synthesising Recommendations for Disciplines and Cross-Disciplinary Research Areas)</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.11236870</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579944">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Heil</surname>
              <given-names>Benjamin J</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffman</surname>
              <given-names>Michael M</given-names>
            </name>
            <name name-style="western">
              <surname>Markowetz</surname>
              <given-names>Florian</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Su-In</given-names>
            </name>
            <name name-style="western">
              <surname>Greene</surname>
              <given-names>Casey S</given-names>
            </name>
            <name name-style="western">
              <surname>Hicks</surname>
              <given-names>Stephanie C</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Reproducibility standards for machine learning in the life sciences</article-title>
          <source>Nature Methods</source>
          <volume>18</volume>
          <issue>10</issue>
          <fpage>1132</fpage>
          <lpage>1135</lpage>
          <pub-id pub-id-type="doi">10.1038/s41592-021-01256-7</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520506">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Herres-Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Pelz</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Kockmann</surname>
              <given-names>Norbert</given-names>
            </name>
            <name name-style="western">
              <surname>Gläser</surname>
              <given-names>Roger</given-names>
            </name>
            <name name-style="western">
              <surname>Richter</surname>
              <given-names>Manuela</given-names>
            </name>
            <name name-style="western">
              <surname>Liermann</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Ortmeyer</surname>
              <given-names>Jochen</given-names>
            </name>
            <name name-style="western">
              <surname>Heine</surname>
              <given-names>Ina</given-names>
            </name>
            <name name-style="western">
              <surname>Metzmacher</surname>
              <given-names>Amelie</given-names>
            </name>
            <name name-style="western">
              <surname>Andres</surname>
              <given-names>Ann-Christin</given-names>
            </name>
            <name name-style="western">
              <surname>Münzmay</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Heuer</surname>
              <given-names>Jan-Ocko</given-names>
            </name>
            <name name-style="western">
              <surname>Hagener</surname>
              <given-names>Malte</given-names>
            </name>
            <name name-style="western">
              <surname>Dierkes</surname>
              <given-names>Jens</given-names>
            </name>
            <name name-style="western">
              <surname>Wiljes</surname>
              <given-names>Cord</given-names>
            </name>
            <name name-style="western">
              <surname>Lindstädt</surname>
              <given-names>Birte</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Sektionskonzept Training &amp; Education zur Einrichtung einer Sektion im Verein Nationale Forschungsdateninfrastruktur (NFDI) e.V.</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.5599770</pub-id>
        </element-citation>
      </ref>
      <ref id="B13547994">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Herres-Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
          </person-group>
          <article-title>How to initiate the cultural change towards digital chemistry.</article-title>
          <uri>https://blogs.rsc.org/chemspider/files/2023/11/Vortrag-Herrespawlis-RSC-071223a.pdf</uri>
          <date-in-citation content-type="access-date">2024-08-03T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13520029">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Herres-Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Bach</surname>
              <given-names>Felix</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Liermann</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
            <name name-style="western">
              <surname>Razum</surname>
              <given-names>Matthias</given-names>
            </name>
            <name name-style="western">
              <surname>Steinbeck</surname>
              <given-names>Christoph</given-names>
            </name>
            <name name-style="western">
              <surname>Fink</surname>
              <given-names>Fabian</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffmann</surname>
              <given-names>Alexander</given-names>
            </name>
            <name name-style="western">
              <surname>Ortmeyer</surname>
              <given-names>Jochen</given-names>
            </name>
            <name name-style="western">
              <surname>Jollife</surname>
              <given-names>John</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>NFDI4Chem: from chemical research data management to digital chemistry</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.8340453</pub-id>
        </element-citation>
      </ref>
      <ref id="B13574014">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Herres-Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Blanke</surname>
              <given-names>Gerd</given-names>
            </name>
            <name name-style="western">
              <surname>Brammer</surname>
              <given-names>Jan</given-names>
            </name>
            <name name-style="western">
              <surname>Baljozovic</surname>
              <given-names>Djordje</given-names>
            </name>
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>Nauman</given-names>
            </name>
            <name name-style="western">
              <surname>Lange</surname>
              <given-names>Frank</given-names>
            </name>
            <name name-style="western">
              <surname>Bänsch</surname>
              <given-names>Felix</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Making the InChI FAIR and sustainable by moving to open-source on GitHub</article-title>
          <source>ChemRxiv</source>
          <pub-id pub-id-type="doi">10.26434/chemrxiv-2024-w6kws</pub-id>
        </element-citation>
      </ref>
      <ref id="B13551429">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Herres‐Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Liermann</surname>
              <given-names>Johannes C</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Research Data in Chemistry – Results of the first NFDI4Chem Community Survey</article-title>
          <source>Zeitschrift für anorganische und allgemeine Chemie</source>
          <volume>646</volume>
          <issue>21</issue>
          <fpage>1748</fpage>
          <lpage>1757</lpage>
          <pub-id pub-id-type="doi">10.1002/zaac.202000339</pub-id>
        </element-citation>
      </ref>
      <ref id="B13519322">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Herres‐Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Bach</surname>
              <given-names>Felix</given-names>
            </name>
            <name name-style="western">
              <surname>Bruno</surname>
              <given-names>Ian J.</given-names>
            </name>
            <name name-style="western">
              <surname>Chalk</surname>
              <given-names>Stuart J.</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Liermann</surname>
              <given-names>Johannes C.</given-names>
            </name>
            <name name-style="western">
              <surname>McEwen</surname>
              <given-names>Leah R.</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
            <name name-style="western">
              <surname>Steinbeck</surname>
              <given-names>Christoph</given-names>
            </name>
            <name name-style="western">
              <surname>Razum</surname>
              <given-names>Matthias</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Minimum Information Standards in Chemistry: A Call for Better Research Data Management Practices</article-title>
          <source>Angewandte Chemie International Edition</source>
          <volume>61</volume>
          <issue>51</issue>
          <pub-id pub-id-type="doi">10.1002/anie.202203038</pub-id>
        </element-citation>
      </ref>
      <ref id="B13553625">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Herrmann</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Hodapp</surname>
              <given-names>Patrick</given-names>
            </name>
            <name name-style="western">
              <surname>Starman</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Pei-Chi</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Chia-Lin</given-names>
            </name>
            <name name-style="western">
              <surname>Le</surname>
              <given-names>Lan</given-names>
            </name>
            <name name-style="western">
              <surname>Klar</surname>
              <given-names>Jochen</given-names>
            </name>
            <name name-style="western">
              <surname>Bizzarri</surname>
              <given-names>Claudia</given-names>
            </name>
            <name name-style="western">
              <surname>Roese</surname>
              <given-names>Philipp</given-names>
            </name>
            <name name-style="western">
              <surname>Oppel</surname>
              <given-names>Niklas</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>Tillmann G</given-names>
            </name>
            <name name-style="western">
              <surname>Tremouilhac</surname>
              <given-names>Pierre</given-names>
            </name>
            <name name-style="western">
              <surname>Holzhauer</surname>
              <given-names>Laura</given-names>
            </name>
            <name name-style="western">
              <surname>Herres-pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffmann</surname>
              <given-names>Alexander</given-names>
            </name>
            <name name-style="western">
              <surname>Seitz</surname>
              <given-names>Tobias</given-names>
            </name>
            <name name-style="western">
              <surname>Zeitler</surname>
              <given-names>Kirsten</given-names>
            </name>
            <name name-style="western">
              <surname>Dorn</surname>
              <given-names>Alrik</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Bräse</surname>
              <given-names>Stefan</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Enhancing FAIRdata by providing digital workflows from data generation to the publication of data: an open source approach described for cyclic voltammetry</article-title>
          <source>ChemRxiv</source>
          <pub-id pub-id-type="doi">10.26434/chemrxiv-2023-95s19</pub-id>
        </element-citation>
      </ref>
      <ref id="B13553728">
        <element-citation publication-type="software">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Pei-Chi</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Chia-Lin</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>LabIMotion</article-title>
          <publisher-name>Zenodo</publisher-name>
          <uri>https://zenodo.org/records/15083705</uri>
        </element-citation>
      </ref>
      <ref id="B13569112">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Yu-Chieh</given-names>
            </name>
            <name name-style="western">
              <surname>Tremouilhac</surname>
              <given-names>Pierre</given-names>
            </name>
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>An</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Bräse</surname>
              <given-names>Stefan</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>ChemSpectra: a web-based spectra editor for analytical data</article-title>
          <source>Journal of Cheminformatics</source>
          <volume>13</volume>
          <issue>1</issue>
          <pub-id pub-id-type="doi">10.1186/s13321-020-00481-0</pub-id>
        </element-citation>
      </ref>
      <ref id="B13578489">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Yu-Chieh</given-names>
            </name>
            <name name-style="western">
              <surname>Tremouilhac</surname>
              <given-names>Pierre</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>Stefan</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Pei-Chi</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Chia-Lin</given-names>
            </name>
            <name name-style="western">
              <surname>Schlörer</surname>
              <given-names>Nils</given-names>
            </name>
            <name name-style="western">
              <surname>Taubert</surname>
              <given-names>Oskar</given-names>
            </name>
            <name name-style="western">
              <surname>Götz</surname>
              <given-names>Markus</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Bräse</surname>
              <given-names>Stefan</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>(Semi-) Automatic Review Process for Common Compound Characterization Data in Organic Synthesis</article-title>
          <source>ChemRxiv</source>
          <pub-id pub-id-type="doi">10.26434/chemrxiv-2024-1r9tb</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520148">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>von Maltzan</surname>
              <given-names>Stephanie</given-names>
            </name>
            <name name-style="western">
              <surname>Klix</surname>
              <given-names>Michael</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Activity Update - Report of relevant cross-cutting topics for NFDI4Chem</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.8334137</pub-id>
        </element-citation>
      </ref>
      <ref id="B13577493">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>IAM4NFDI</surname>
            </name>
          </person-group>
          <article-title>Incubator Dashboard</article-title>
          <uri>https://incubators.nfdi-aai.de/</uri>
          <date-in-citation content-type="access-date">2024-08-02T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13580051">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>IUPAC</surname>
            </name>
          </person-group>
          <article-title>IUPAC Committees</article-title>
          <uri>https://iupac.org/who-we-are/committees/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13579482">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jacob</surname>
              <given-names>Christoph</given-names>
            </name>
            <name name-style="western">
              <surname>Mück-Lichtenfeld</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Wolter</surname>
              <given-names>Mario</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Research Data Management in Theoretical Chemistry</article-title>
          <source>Institut für Physikalische und Theoretische Chemie</source>
          <pub-id pub-id-type="doi">10.24355/dbbs.084-202407310658-0</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579658">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Metrology</surname>
              <given-names>Joint Committee for Guides in</given-names>
            </name>
          </person-group>
          <year>2012</year>
          <source>International Vocabulary of Metrology – Basic and general concepts and associated terms (VIM)</source>
          <edition>3rd edition</edition>
          <publisher-name>JGCM</publisher-name>
          <pub-id pub-id-type="doi">10.59161/jcgm200-2012</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579675">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Joint Committee for Guides in Metrology</surname>
              <given-names>Working Group 1</given-names>
            </name>
          </person-group>
          <year>2008</year>
          <source>Evaluation of measurement data — Guide to the expression of uncertainty in measurement</source>
          <publisher-name>JCGM</publisher-name>
          <pub-id pub-id-type="doi">10.59161/jcgm100-2008e</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579638">
        <element-citation publication-type="book">
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>Richard G</given-names>
            </name>
            <name name-style="western">
              <surname>Wilks</surname>
              <given-names>Edward S</given-names>
            </name>
            <name name-style="western">
              <surname>Metanomski</surname>
              <given-names>W Val</given-names>
            </name>
            <name name-style="western">
              <surname>Kahovec</surname>
              <given-names>Jaroslav</given-names>
            </name>
            <name name-style="western">
              <surname>Hess</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Stepto</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Kitayama</surname>
              <given-names>Tatsuki</given-names>
            </name>
          </person-group>
          <year>2009</year>
          <source>Compendium of Polymer Terminology and Nomenclature: IUPAC Recommendations 2008</source>
          <publisher-name>Royal Society of Chemistry</publisher-name>
          <isbn>978-1-84755-942-5</isbn>
          <pub-id pub-id-type="doi">10.1039/9781847559425</pub-id>
        </element-citation>
      </ref>
      <ref id="B13521065">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Tremouilhac</surname>
              <given-names>Pierre</given-names>
            </name>
            <name name-style="western">
              <surname>Hodapp</surname>
              <given-names>Patrick</given-names>
            </name>
            <name name-style="western">
              <surname>Herrmann</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Starman</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>Mehzabin</surname>
              <given-names>Tasnim</given-names>
            </name>
            <name name-style="western">
              <surname>Klar</surname>
              <given-names>Jochen</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Integrating devices and converting data with Chemotion ELN</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.13120738</pub-id>
        </element-citation>
      </ref>
      <ref id="B13574190">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jupp</surname>
              <given-names>Simon</given-names>
            </name>
            <name name-style="western">
              <surname>Burdett</surname>
              <given-names>Tony</given-names>
            </name>
            <name name-style="western">
              <surname>Malone</surname>
              <given-names>James</given-names>
            </name>
            <name name-style="western">
              <surname>Leroy</surname>
              <given-names>Catherine</given-names>
            </name>
            <name name-style="western">
              <surname>Pearce</surname>
              <given-names>Matt</given-names>
            </name>
            <name name-style="western">
              <surname>McMurry</surname>
              <given-names>Julie</given-names>
            </name>
            <name name-style="western">
              <surname>Parkinson</surname>
              <given-names>Helen</given-names>
            </name>
          </person-group>
          <article-title>A new Ontology Lookup Service at EMBL-EBI. Workshop on Semantic Web Applications and Tools for Life Sciences</article-title>
          <uri>https://www.semanticscholar.org/paper/A-new-Ontology-Lookup-Service-at-EMBL-EBI-Jupp-Burdett/b83bfbfc1f2f08e5b88af5ef65ef2a8687ac4112</uri>
          <date-in-citation content-type="access-date">2024-07-29T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13579223">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>(KIT)</surname>
              <given-names>Karlsruhe Institute of Technology</given-names>
            </name>
          </person-group>
          <article-title>LabIMotion Template Hub</article-title>
          <uri>https://www.chemotion-repository.net/home/genericHub</uri>
          <date-in-citation content-type="access-date">2024-07-29T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13579329">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>(KIT)</surname>
              <given-names>Karlsruhe Institute of Technology</given-names>
            </name>
          </person-group>
          <article-title>Chemotion Repository</article-title>
          <uri>https://chemotion-repository.net/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13577501">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Technology</surname>
              <given-names>KIT Karlsruhe Institute of</given-names>
            </name>
          </person-group>
          <article-title>Chemotion Docker repository</article-title>
          <uri>https://hub.docker.com/r/ptrxyz/chemotion/tags</uri>
          <date-in-citation content-type="access-date">2024-07-29T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13553491">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Liermann</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Schön</surname>
              <given-names>Florian</given-names>
            </name>
            <name name-style="western">
              <surname>Herres‐Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Forschungsdatenmanagement ‐ Zeit für den Abschied vom analogen Laborbuch</article-title>
          <source>Nachrichten aus der Chemie</source>
          <volume>68</volume>
          <issue>12</issue>
          <fpage>20</fpage>
          <lpage>23</lpage>
          <pub-id pub-id-type="doi">10.1002/nadc.20204095910</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520126">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Schrade</surname>
              <given-names>Torsten</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
            <name name-style="western">
              <surname>Stotzka</surname>
              <given-names>Rainer</given-names>
            </name>
            <name name-style="western">
              <surname>Wiljes</surname>
              <given-names>Cord</given-names>
            </name>
            <name name-style="western">
              <surname>Blümel</surname>
              <given-names>Ina</given-names>
            </name>
            <name name-style="western">
              <surname>Bracht</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Hamann</surname>
              <given-names>Tobias</given-names>
            </name>
            <name name-style="western">
              <surname>Arndt</surname>
              <given-names>Susanne</given-names>
            </name>
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>Johannes</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Sektionskonzept Meta(daten), Terminologien und Provenienz zur Einrichtung einer Sektion im Verein Nationale Forschungsdateninfrastruktur (NFDI) e.V.</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.5619089</pub-id>
        </element-citation>
      </ref>
      <ref id="B13551688">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Strömert</surname>
              <given-names>Philip</given-names>
            </name>
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>Johannes</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Activity Update - Report on 2nd Ontologies4Chem Workshop 2023</article-title>
          <source>Zenodo</source>
          <pub-id pub-id-type="doi">10.5281/zenodo.10260337</pub-id>
        </element-citation>
      </ref>
      <ref id="B13552896">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>e.V.</surname>
              <given-names>Konsortialversammlung des Vereins Nationale Forschungsdateninfrastruktur (NFDI)</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Stellungnahme der NFDI-Konsortien zu Basisdiensten</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/zenodo.6091657</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579722">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Krahl</surname>
              <given-names>Rolf</given-names>
            </name>
            <name name-style="western">
              <surname>Darroch</surname>
              <given-names>Louise</given-names>
            </name>
            <name name-style="western">
              <surname>Huber</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Devaraju</surname>
              <given-names>Anusuriya</given-names>
            </name>
            <name name-style="western">
              <surname>Klump</surname>
              <given-names>Jens</given-names>
            </name>
            <name name-style="western">
              <surname>Habermann</surname>
              <given-names>Ted</given-names>
            </name>
            <name name-style="western">
              <surname>Stocker</surname>
              <given-names>Markus</given-names>
            </name>
            <name name-style="western">
              <surname>Members</surname>
              <given-names>RDA PIDINST WG</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Metadata Schema for the Persistent Identification of Instruments</article-title>
          <source>Research Data Alliance</source>
          <pub-id pub-id-type="doi">10.15497/rda00070</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520648">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Linke</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Moustakas</surname>
              <given-names>Nikolaos G</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>voc4cat - A SKOS vocabulary for the catalysis disciplines. From proof of concept to a reliable service.</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.10200693</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579683">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Tzyy-Shyang</given-names>
            </name>
            <name name-style="western">
              <surname>Coley</surname>
              <given-names>Connor W</given-names>
            </name>
            <name name-style="western">
              <surname>Mochigase</surname>
              <given-names>Hidenobu</given-names>
            </name>
            <name name-style="western">
              <surname>Beech</surname>
              <given-names>Haley K</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Wencong</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Zi</given-names>
            </name>
            <name name-style="western">
              <surname>Woods</surname>
              <given-names>Eliot</given-names>
            </name>
            <name name-style="western">
              <surname>Craig</surname>
              <given-names>Stephen L</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>Jeremiah A</given-names>
            </name>
            <name name-style="western">
              <surname>Kalow</surname>
              <given-names>Julia A</given-names>
            </name>
            <name name-style="western">
              <surname>Jensen</surname>
              <given-names>Klavs F</given-names>
            </name>
            <name name-style="western">
              <surname>Olsen</surname>
              <given-names>Bradley D</given-names>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>BigSMILES: A Structurally-Based Line Notation for Describing Macromolecules</article-title>
          <source>ACS Central Science</source>
          <volume>5</volume>
          <issue>9</issue>
          <fpage>1523</fpage>
          <lpage>1531</lpage>
          <pub-id pub-id-type="doi">10.1021/acscentsci.9b00476</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579337">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>consortium</surname>
              <given-names>MassBank</given-names>
            </name>
          </person-group>
          <article-title>MassBank</article-title>
          <uri>https://massbank.eu/MassBank/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13579975">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Matentzoglu</surname>
              <given-names>Nicolas</given-names>
            </name>
            <name name-style="western">
              <surname>Goutte-Gattat</surname>
              <given-names>Damien</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>Shawn Zheng Kai</given-names>
            </name>
            <name name-style="western">
              <surname>Balhoff</surname>
              <given-names>James P</given-names>
            </name>
            <name name-style="western">
              <surname>Carbon</surname>
              <given-names>Seth</given-names>
            </name>
            <name name-style="western">
              <surname>Caron</surname>
              <given-names>Anita R</given-names>
            </name>
            <name name-style="western">
              <surname>Duncan</surname>
              <given-names>William D</given-names>
            </name>
            <name name-style="western">
              <surname>Flack</surname>
              <given-names>Joe E</given-names>
            </name>
            <name name-style="western">
              <surname>Haendel</surname>
              <given-names>Melissa</given-names>
            </name>
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>Nomi L</given-names>
            </name>
            <name name-style="western">
              <surname>Hogan</surname>
              <given-names>William R</given-names>
            </name>
            <name name-style="western">
              <surname>Hoyt</surname>
              <given-names>Charles Tapley</given-names>
            </name>
            <name name-style="western">
              <surname>Jackson</surname>
              <given-names>Rebecca C</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>HyeongSik</given-names>
            </name>
            <name name-style="western">
              <surname>Kir</surname>
              <given-names>Huseyin</given-names>
            </name>
            <name name-style="western">
              <surname>Larralde</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>McMurry</surname>
              <given-names>Julie A</given-names>
            </name>
            <name name-style="western">
              <surname>Overton</surname>
              <given-names>James A</given-names>
            </name>
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>Bjoern</given-names>
            </name>
            <name name-style="western">
              <surname>Pilgrim</surname>
              <given-names>Clare</given-names>
            </name>
            <name name-style="western">
              <surname>Stefancsik</surname>
              <given-names>Ray</given-names>
            </name>
            <name name-style="western">
              <surname>Robb</surname>
              <given-names>Sofia MC</given-names>
            </name>
            <name name-style="western">
              <surname>Toro</surname>
              <given-names>Sabrina</given-names>
            </name>
            <name name-style="western">
              <surname>Vasilevsky</surname>
              <given-names>Nicole A</given-names>
            </name>
            <name name-style="western">
              <surname>Walls</surname>
              <given-names>Ramona</given-names>
            </name>
            <name name-style="western">
              <surname>Mungall</surname>
              <given-names>Christopher J</given-names>
            </name>
            <name name-style="western">
              <surname>Osumi-Sutherland</surname>
              <given-names>David</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Ontology Development Kit: a toolkit for building, maintaining and standardizing biomedical ontologies</article-title>
          <source>Database</source>
          <volume>2022</volume>
          <pub-id pub-id-type="doi">10.1093/database/baac087</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520311">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McEwen</surname>
              <given-names>Leah</given-names>
            </name>
            <name name-style="western">
              <surname>Bruno</surname>
              <given-names>Ian</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>WorldFAIR Project (D3.1) Digital recommendations for Chemistry FAIR data policy and practice</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.7887283</pub-id>
        </element-citation>
      </ref>
      <ref id="B13553459">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
            <name name-style="western">
              <surname>Bach</surname>
              <given-names>Felix</given-names>
            </name>
            <name name-style="western">
              <surname>Castro</surname>
              <given-names>Leyla Jael</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>Tillmann</given-names>
            </name>
            <name name-style="western">
              <surname>Hofmann</surname>
              <given-names>Stefan</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Pei-Chi</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Katabathuni</surname>
              <given-names>Bhavin</given-names>
            </name>
            <name name-style="western">
              <surname>Mauz</surname>
              <given-names>Fabian</given-names>
            </name>
            <name name-style="western">
              <surname>Meier</surname>
              <given-names>René</given-names>
            </name>
            <name name-style="western">
              <surname>Nainala</surname>
              <given-names>Venkata Chandra Sekhar</given-names>
            </name>
            <name name-style="western">
              <surname>Rayya</surname>
              <given-names>Noura</given-names>
            </name>
            <name name-style="western">
              <surname>Steinbeck</surname>
              <given-names>Christoph</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Harmonising, Harvesting, and Searching Metadata Across a Repository Federation</article-title>
          <source>Proceedings of the Conference on Research Data Infrastructure</source>
          <volume>1</volume>
          <pub-id pub-id-type="doi">10.52825/cordi.v1i.202</pub-id>
        </element-citation>
      </ref>
      <ref id="B13553161">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
            <name name-style="western">
              <surname>Andres</surname>
              <given-names>Ann-Christin</given-names>
            </name>
            <name name-style="western">
              <surname>Bach</surname>
              <given-names>Felix</given-names>
            </name>
            <name name-style="western">
              <surname>Bender</surname>
              <given-names>Theo</given-names>
            </name>
            <name name-style="western">
              <surname>Bonatto Minella</surname>
              <given-names>Christian</given-names>
            </name>
            <name name-style="western">
              <surname>Eberl</surname>
              <given-names>Franziska</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>Tillmann</given-names>
            </name>
            <name name-style="western">
              <surname>Golub</surname>
              <given-names>Benjamin</given-names>
            </name>
            <name name-style="western">
              <surname>Harivyasi</surname>
              <given-names>Shashank S</given-names>
            </name>
            <name name-style="western">
              <surname>Herres-Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Pei-Chi</given-names>
            </name>
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Jollife</surname>
              <given-names>John D</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Liermann</surname>
              <given-names>Johannes C</given-names>
            </name>
            <name name-style="western">
              <surname>Nainala</surname>
              <given-names>Venkata C</given-names>
            </name>
            <name name-style="western">
              <surname>Razum</surname>
              <given-names>Matthias</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Steinbeck</surname>
              <given-names>Christoph</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Interim Report NFDI4Chem 2023</article-title>
          <source>Research Ideas and Outcomes</source>
          <volume>10</volume>
          <pub-id pub-id-type="doi">10.3897/rio.10.e124977</pub-id>
        </element-citation>
      </ref>
      <ref id="B13552954">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>NFDI4Chem</surname>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Ontologies4Chem Workshop Series</article-title>
          <publisher-name>German National Library of Science and Technology (TIB)</publisher-name>
          <pub-id pub-id-type="doi">10.25798/27ny-xb37</pub-id>
        </element-citation>
      </ref>
      <ref id="B13574452">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>NFDI4Chem</surname>
            </name>
          </person-group>
          <article-title>Helpdesk</article-title>
          <uri>https://www.nfdi4chem.de/helpdesk/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13574427">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>NFDI4Chem</surname>
            </name>
          </person-group>
          <article-title>Chemistry Repositories</article-title>
          <uri>https://www.nfdi4chem.de/repos/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13574379">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>NFDI4Chem</surname>
            </name>
          </person-group>
          <article-title>Electronic Lab Notebooks ELN</article-title>
          <uri>https://www.nfdi4chem.de/eln/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13574321">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>NFDI4Chem</surname>
            </name>
          </person-group>
          <article-title>NFDI4Chem Knowledge Base</article-title>
          <uri>https://knowledgebase.nfdi4chem.de/knowledge_base/de/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13552970">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>NFDI4Chem</surname>
            </name>
          </person-group>
          <article-title>TS4NFDI Community Hands-On Workshop</article-title>
          <uri>https://www.nfdi4chem.de/event/ts4nfdi-community-hands-on-workshop/</uri>
          <date-in-citation content-type="access-date">2024-07-23T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13574419">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>NFDI4Chem</surname>
            </name>
          </person-group>
          <article-title>Demo ELNs</article-title>
          <uri>https://demo.chemotion.scc.kit.edu/</uri>
          <date-in-citation content-type="access-date">2024-07-29T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13578424">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>NFDI4Chem</surname>
            </name>
          </person-group>
          <article-title>A workshop for institutions: FAIR Research Data Management: Basics for Chemists</article-title>
          <uri>https://www.nfdi4chem.de/de/fdm-grundlagen/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13578432">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>NFDI4Chem</surname>
            </name>
          </person-group>
          <article-title>Chemotion ELN Hands-on Workshop</article-title>
          <uri>https://www.nfdi4chem.de/event/chemotion-eln-hands-on-workshop/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13578440">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>NFDI4Chem</surname>
            </name>
          </person-group>
          <article-title>LabIMotion: Online Hands-on Workshop</article-title>
          <uri>https://www.nfdi4chem.de/event/labimotion-online-hands-on-workshop/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13578408">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Group</surname>
              <given-names>nmrXiv Project</given-names>
            </name>
          </person-group>
          <article-title>nmrXiv</article-title>
          <uri>https://nmrxiv.org/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13578448">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Foundation</surname>
              <given-names>OPC</given-names>
            </name>
          </person-group>
          <article-title>LADS - laboratory and analytical device standard</article-title>
          <uri>https://opcfoundation.org/markets-collaboration/lads/</uri>
          <date-in-citation content-type="access-date">2024-07-29T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13574047">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Parks</surname>
              <given-names>Nicole A</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>Tillmann G</given-names>
            </name>
            <name name-style="western">
              <surname>Blankenburg</surname>
              <given-names>Claudia</given-names>
            </name>
            <name name-style="western">
              <surname>Scalfani</surname>
              <given-names>Vincent F</given-names>
            </name>
            <name name-style="western">
              <surname>McEwen</surname>
              <given-names>Leah R</given-names>
            </name>
            <name name-style="western">
              <surname>Herres-Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>The current landscape of author guidelines in chemistry through the lens of research data sharing</article-title>
          <source>Pure and Applied Chemistry</source>
          <volume>95</volume>
          <issue>4</issue>
          <fpage>439</fpage>
          <lpage>450</lpage>
          <pub-id pub-id-type="doi">10.1515/pac-2022-1001</pub-id>
        </element-citation>
      </ref>
      <ref id="B13521359">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Parks</surname>
              <given-names>Nicole Andrea</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>Tillmann G</given-names>
            </name>
            <name name-style="western">
              <surname>Herres-Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Editors4Chem: Implementing Publication Standards in Chemistry</article-title>
          <publisher-name>RWTH Aachen University</publisher-name>
          <pub-id pub-id-type="doi">10.18154/RWTH-2023-10440</pub-id>
        </element-citation>
      </ref>
      <ref id="B13569122">
        <element-citation publication-type="software">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Patiny</surname>
              <given-names>Luc</given-names>
            </name>
            <name name-style="western">
              <surname>Musallam</surname>
              <given-names>Hamed</given-names>
            </name>
            <name name-style="western">
              <surname>Zasso</surname>
              <given-names>Michaël</given-names>
            </name>
            <name name-style="western">
              <surname>Bolaños</surname>
              <given-names>Alejandro</given-names>
            </name>
            <name name-style="western">
              <surname>Kostro</surname>
              <given-names>Daniel</given-names>
            </name>
            <name name-style="western">
              <surname>Wenk</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Ahkrin</surname>
              <given-names>Sébastien</given-names>
            </name>
            <name name-style="western">
              <surname>Jeannerat</surname>
              <given-names>Damien</given-names>
            </name>
            <name name-style="western">
              <surname>Ziegler</surname>
              <given-names>Eva</given-names>
            </name>
            <name name-style="western">
              <surname>Liermann</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Schloerer</surname>
              <given-names>Nil</given-names>
            </name>
            <name name-style="western">
              <surname>Wist</surname>
              <given-names>Julien</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>NMRium: ReactJS component to display and process NMR spectra</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/zenodo.8345822</pub-id>
          <comment content-type="Version">v0.44.0</comment>
        </element-citation>
      </ref>
      <ref id="B13578475">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Patiny</surname>
              <given-names>Luc</given-names>
            </name>
            <name name-style="western">
              <surname>Musallam</surname>
              <given-names>Hamed</given-names>
            </name>
            <name name-style="western">
              <surname>Bolaños</surname>
              <given-names>Alejandro</given-names>
            </name>
            <name name-style="western">
              <surname>Zasso</surname>
              <given-names>Michaël</given-names>
            </name>
            <name name-style="western">
              <surname>Wist</surname>
              <given-names>Julien</given-names>
            </name>
            <name name-style="western">
              <surname>Karayilan</surname>
              <given-names>Metin</given-names>
            </name>
            <name name-style="western">
              <surname>Ziegler</surname>
              <given-names>Eva</given-names>
            </name>
            <name name-style="western">
              <surname>Liermann</surname>
              <given-names>Johannes C</given-names>
            </name>
            <name name-style="western">
              <surname>Schlörer</surname>
              <given-names>Nils E</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>NMRium: Teaching nuclear magnetic resonance spectra interpretation in an online platform</article-title>
          <source>Beilstein Journal of Organic Chemistry</source>
          <volume>20</volume>
          <fpage>25</fpage>
          <lpage>31</lpage>
          <pub-id pub-id-type="doi">10.3762/bjoc.20.4</pub-id>
        </element-citation>
      </ref>
      <ref id="B13520622">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pearman-Kanza</surname>
              <given-names>Samantha</given-names>
            </name>
            <name name-style="western">
              <surname>Knight</surname>
              <given-names>Nicola</given-names>
            </name>
            <name name-style="western">
              <surname>Joliffe</surname>
              <given-names>John</given-names>
            </name>
            <name name-style="western">
              <surname>Ortmeyer</surname>
              <given-names>Jochen</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Mitigating Barriers and Maximising Opportunities in Chemistry Research</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/ZENODO.12723678</pub-id>
        </element-citation>
      </ref>
      <ref id="B13580023">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pingarrón</surname>
              <given-names>José M</given-names>
            </name>
            <name name-style="western">
              <surname>Labuda</surname>
              <given-names>Ján</given-names>
            </name>
            <name name-style="western">
              <surname>Barek</surname>
              <given-names>Jiří</given-names>
            </name>
            <name name-style="western">
              <surname>Brett</surname>
              <given-names>Christopher M. A</given-names>
            </name>
            <name name-style="western">
              <surname>Camões</surname>
              <given-names>Maria Filomena</given-names>
            </name>
            <name name-style="western">
              <surname>Fojta</surname>
              <given-names>Miroslav</given-names>
            </name>
            <name name-style="western">
              <surname>Hibbert</surname>
              <given-names>D Brynn</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Terminology of electrochemical methods of analysis (IUPAC Recommendations 2019)</article-title>
          <source>Pure and Applied Chemistry</source>
          <volume>92</volume>
          <issue>4</issue>
          <fpage>641</fpage>
          <lpage>694</lpage>
          <pub-id pub-id-type="doi">10.1515/pac-2018-0109</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579773">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Proppe</surname>
              <given-names>Jonny</given-names>
            </name>
            <name name-style="western">
              <surname>Kircher</surname>
              <given-names>Johannes</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Uncertainty Quantification of Reactivity Scales</article-title>
          <source>ChemPhysChem</source>
          <volume>23</volume>
          <issue>8</issue>
          <pub-id pub-id-type="doi">10.1002/cphc.202200061</pub-id>
        </element-citation>
      </ref>
      <ref id="B13569179">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Proteau</surname>
              <given-names>Philip J</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Journal of Natural Products – New NMR Data Requirements and Editor Changes</article-title>
          <source>Journal of Natural Products</source>
          <volume>86</volume>
          <issue>4</issue>
          <fpage>653</fpage>
          <lpage>654</lpage>
          <pub-id pub-id-type="doi">10.1021/acs.jnatprod.3c00281</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579927">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rahrt</surname>
              <given-names>Rene</given-names>
            </name>
            <name name-style="western">
              <surname>Hein-Janke</surname>
              <given-names>Björn</given-names>
            </name>
            <name name-style="western">
              <surname>Amarasinghe</surname>
              <given-names>Kosala N</given-names>
            </name>
            <name name-style="western">
              <surname>Shafique</surname>
              <given-names>Muhammad</given-names>
            </name>
            <name name-style="western">
              <surname>Feldt</surname>
              <given-names>Milica</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>Luxuan</given-names>
            </name>
            <name name-style="western">
              <surname>Harvey</surname>
              <given-names>Jeremy N</given-names>
            </name>
            <name name-style="western">
              <surname>Pollice</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Koszinowski</surname>
              <given-names>Konrad</given-names>
            </name>
            <name name-style="western">
              <surname>Mata</surname>
              <given-names>Ricardo A</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>The Fe-MAN Challenge: Ferrates–Microkinetic Assessment of Numerical Quantum Chemistry</article-title>
          <source>The Journal of Physical Chemistry A</source>
          <volume>128</volume>
          <issue>23</issue>
          <fpage>4663</fpage>
          <lpage>4673</lpage>
          <pub-id pub-id-type="doi">10.1021/acs.jpca.4c01361</pub-id>
        </element-citation>
      </ref>
      <ref id="B13574034">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rauh</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Blankenburg</surname>
              <given-names>Claudia</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>Tillmann G</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>Stefan</given-names>
            </name>
            <name name-style="western">
              <surname>Schatzschneider</surname>
              <given-names>Ulrich</given-names>
            </name>
            <name name-style="western">
              <surname>Schulze</surname>
              <given-names>Tobias</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Data format standards in analytical chemistry</article-title>
          <source>Pure and Applied Chemistry</source>
          <volume>94</volume>
          <issue>6</issue>
          <fpage>725</fpage>
          <lpage>736</lpage>
          <pub-id pub-id-type="doi">10.1515/pac-2021-3101</pub-id>
        </element-citation>
      </ref>
      <ref id="B13580060">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alliance</surname>
              <given-names>Research Data</given-names>
            </name>
          </person-group>
          <article-title>Harmonised terminologies and schemas for FAIR data in materials science and related domains WG</article-title>
          <uri>https://www.rd-alliance.org/groups/harmonised-terminologies-and-schemas-fair-data-materials-science-and-related-domains-wg/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:28+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13580068">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alliance</surname>
              <given-names>Research Data</given-names>
            </name>
          </person-group>
          <article-title>Vocabulary Services IG04/08/2024</article-title>
          <uri>https://www.rd-alliance.org/groups/vocabulary-services-interest-group/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13580076">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alliance</surname>
              <given-names>Research Data</given-names>
            </name>
          </person-group>
          <article-title>InteroperAble Descriptions of Observable Property Terminology WG (I-ADOPT WG)</article-title>
          <uri>https://www.rd-alliance.org/groups/interoperable-descriptions-observable-property-terminology-wg-i-adopt-wg/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13580092">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alliance</surname>
              <given-names>Research Data</given-names>
            </name>
          </person-group>
          <article-title>Chemistry Research Data IG</article-title>
          <uri>https://www.rd-alliance.org/groups/chemistry-research-data-interest-group/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13580100">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alliance</surname>
              <given-names>Research Data</given-names>
            </name>
          </person-group>
          <article-title>Metadata IG</article-title>
          <uri>https://www.rd-alliance.org/groups/metadata-ig/members/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13580108">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alliance</surname>
              <given-names>Research Data</given-names>
            </name>
          </person-group>
          <article-title>Research Metadata Schemas WG</article-title>
          <uri>https://www.rd-alliance.org/groups/research-metadata-schemas-wg/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13580116">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alliance</surname>
              <given-names>Research Data</given-names>
            </name>
          </person-group>
          <article-title>Metadata Standards Catalog WG</article-title>
          <uri>https://www.rd-alliance.org/groups/metadata-standards-catalog-working-group/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13520931">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sacha</surname>
              <given-names>Mikołaj</given-names>
            </name>
            <name name-style="western">
              <surname>Błaż</surname>
              <given-names>Mikołaj</given-names>
            </name>
            <name name-style="western">
              <surname>Byrski</surname>
              <given-names>Piotr</given-names>
            </name>
            <name name-style="western">
              <surname>Dąbrowski-Tumański</surname>
              <given-names>Paweł</given-names>
            </name>
            <name name-style="western">
              <surname>Chromiński</surname>
              <given-names>Mikołaj</given-names>
            </name>
            <name name-style="western">
              <surname>Loska</surname>
              <given-names>Rafał</given-names>
            </name>
            <name name-style="western">
              <surname>Włodarczyk-Pruszyński</surname>
              <given-names>Paweł</given-names>
            </name>
            <name name-style="western">
              <surname>Jastrzębski</surname>
              <given-names>Stanisław</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Molecule Edit Graph Attention Network: Modeling Chemical Reactions as Sequences of Graph Edits</article-title>
          <publisher-name>arXiv</publisher-name>
          <pub-id pub-id-type="doi">10.48550/ARXIV.2006.15426</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579431">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Scheidgen</surname>
              <given-names>Markus</given-names>
            </name>
            <name name-style="western">
              <surname>Himanen</surname>
              <given-names>Lauri</given-names>
            </name>
            <name name-style="western">
              <surname>Ladines</surname>
              <given-names>Alvin Noe</given-names>
            </name>
            <name name-style="western">
              <surname>Sikter</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Nakhaee</surname>
              <given-names>Mohammad</given-names>
            </name>
            <name name-style="western">
              <surname>Fekete</surname>
              <given-names>Ádám</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>Theodore</given-names>
            </name>
            <name name-style="western">
              <surname>Golparvar</surname>
              <given-names>Amir</given-names>
            </name>
            <name name-style="western">
              <surname>Márquez</surname>
              <given-names>José A</given-names>
            </name>
            <name name-style="western">
              <surname>Brockhauser</surname>
              <given-names>Sandor</given-names>
            </name>
            <name name-style="western">
              <surname>Brückner</surname>
              <given-names>Sebastian</given-names>
            </name>
            <name name-style="western">
              <surname>Ghiringhelli</surname>
              <given-names>Luca M</given-names>
            </name>
            <name name-style="western">
              <surname>Dietrich</surname>
              <given-names>Felix</given-names>
            </name>
            <name name-style="western">
              <surname>Lehmberg</surname>
              <given-names>Daniel</given-names>
            </name>
            <name name-style="western">
              <surname>Denell</surname>
              <given-names>Thea</given-names>
            </name>
            <name name-style="western">
              <surname>Albino</surname>
              <given-names>Andrea</given-names>
            </name>
            <name name-style="western">
              <surname>Näsström</surname>
              <given-names>Hampus</given-names>
            </name>
            <name name-style="western">
              <surname>Shabih</surname>
              <given-names>Sherjeel</given-names>
            </name>
            <name name-style="western">
              <surname>Dobener</surname>
              <given-names>Florian</given-names>
            </name>
            <name name-style="western">
              <surname>Kühbach</surname>
              <given-names>Markus</given-names>
            </name>
            <name name-style="western">
              <surname>Mozumder</surname>
              <given-names>Rubel</given-names>
            </name>
            <name name-style="western">
              <surname>Rudzinski</surname>
              <given-names>Joseph F</given-names>
            </name>
            <name name-style="western">
              <surname>Daelman</surname>
              <given-names>Nathan</given-names>
            </name>
            <name name-style="western">
              <surname>Pizarro</surname>
              <given-names>José M</given-names>
            </name>
            <name name-style="western">
              <surname>Kuban</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>Salazar</surname>
              <given-names>Cuauhtemoc</given-names>
            </name>
            <name name-style="western">
              <surname>Ondračka</surname>
              <given-names>Pavel</given-names>
            </name>
            <name name-style="western">
              <surname>Bungartz</surname>
              <given-names>Hans-Joachim</given-names>
            </name>
            <name name-style="western">
              <surname>Draxl</surname>
              <given-names>Claudia</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>NOMAD: A distributed web-based platform for managingmaterials science research data</article-title>
          <source>Journal of Open Source Software</source>
          <volume>8</volume>
          <issue>90</issue>
          <pub-id pub-id-type="doi">10.21105/joss.05388</pub-id>
        </element-citation>
      </ref>
      <ref id="B13578549">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Soltau</surname>
              <given-names>Kerstin</given-names>
            </name>
            <name name-style="western">
              <surname>Hofmann</surname>
              <given-names>Stefan</given-names>
            </name>
            <name name-style="western">
              <surname>Jasinska</surname>
              <given-names>Agnes</given-names>
            </name>
            <name name-style="western">
              <surname>Linés</surname>
              <given-names>Clara</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>FAIRness assessment as a catalyst of chemistry research repository transformation in Germany</article-title>
          <source>Zenodo</source>
          <pub-id pub-id-type="doi">10.5281/zenodo.13135009</pub-id>
        </element-citation>
      </ref>
      <ref id="B13569104">
        <element-citation publication-type="software">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Starman</surname>
              <given-names>Martin</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>StarmanMartin/EfwBuilder: v1.0</article-title>
          <publisher-name>Zenodo</publisher-name>
          <pub-id pub-id-type="doi">10.5281/zenodo.8337273</pub-id>
          <comment content-type="Version">v1.0</comment>
        </element-citation>
      </ref>
      <ref id="B13578456">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Starman</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>Held</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Kirchner</surname>
              <given-names>Fabian</given-names>
            </name>
            <name name-style="western">
              <surname>Eschke</surname>
              <given-names>Catriona</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>ChemotionAPI</article-title>
          <source>Zenodo</source>
          <pub-id pub-id-type="doi">10.5281/zenodo.12569190</pub-id>
        </element-citation>
      </ref>
      <ref id="B13519287">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Steinbeck</surname>
              <given-names>Christoph</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Bach</surname>
              <given-names>Felix</given-names>
            </name>
            <name name-style="western">
              <surname>Herres-Pawlis</surname>
              <given-names>Sonja</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Liermann</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
            <name name-style="western">
              <surname>Razum</surname>
              <given-names>Matthias</given-names>
            </name>
            <name name-style="western">
              <surname>Baldauf</surname>
              <given-names>Carsten</given-names>
            </name>
            <name name-style="western">
              <surname>Biedermann</surname>
              <given-names>Frank</given-names>
            </name>
            <name name-style="western">
              <surname>Bocklitz</surname>
              <given-names>Thomas</given-names>
            </name>
            <name name-style="western">
              <surname>Boehm</surname>
              <given-names>Franziska</given-names>
            </name>
            <name name-style="western">
              <surname>Broda</surname>
              <given-names>Frank</given-names>
            </name>
            <name name-style="western">
              <surname>Czodrowski</surname>
              <given-names>Paul</given-names>
            </name>
            <name name-style="western">
              <surname>Engel</surname>
              <given-names>Thomas</given-names>
            </name>
            <name name-style="western">
              <surname>Hicks</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>Kast</surname>
              <given-names>Stefan</given-names>
            </name>
            <name name-style="western">
              <surname>Kettner</surname>
              <given-names>Carsten</given-names>
            </name>
            <name name-style="western">
              <surname>Koch</surname>
              <given-names>Wolfram</given-names>
            </name>
            <name name-style="western">
              <surname>Lanza</surname>
              <given-names>Giacomo</given-names>
            </name>
            <name name-style="western">
              <surname>Link</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Mata</surname>
              <given-names>Ricardo</given-names>
            </name>
            <name name-style="western">
              <surname>Nagel</surname>
              <given-names>Wolfgang</given-names>
            </name>
            <name name-style="western">
              <surname>Porzel</surname>
              <given-names>Andrea</given-names>
            </name>
            <name name-style="western">
              <surname>Schlörer</surname>
              <given-names>Nils</given-names>
            </name>
            <name name-style="western">
              <surname>Schulze</surname>
              <given-names>Tobias</given-names>
            </name>
            <name name-style="western">
              <surname>Weinig</surname>
              <given-names>Hans-Georg</given-names>
            </name>
            <name name-style="western">
              <surname>Wenzel</surname>
              <given-names>Wolfgang</given-names>
            </name>
            <name name-style="western">
              <surname>Wessjohann</surname>
              <given-names>Ludger</given-names>
            </name>
            <name name-style="western">
              <surname>Wulle</surname>
              <given-names>Stefan</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>NFDI4Chem - Towards a National Research Data Infrastructure for Chemistry in Germany</article-title>
          <source>Research Ideas and Outcomes</source>
          <volume>6</volume>
          <pub-id pub-id-type="doi">10.3897/rio.6.e55852</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579709">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stocker</surname>
              <given-names>Markus</given-names>
            </name>
            <name name-style="western">
              <surname>Darroch</surname>
              <given-names>Louise</given-names>
            </name>
            <name name-style="western">
              <surname>Krahl</surname>
              <given-names>Rolf</given-names>
            </name>
            <name name-style="western">
              <surname>Habermann</surname>
              <given-names>Ted</given-names>
            </name>
            <name name-style="western">
              <surname>Devaraju</surname>
              <given-names>Anusuriya</given-names>
            </name>
            <name name-style="western">
              <surname>Schwardmann</surname>
              <given-names>Ulrich</given-names>
            </name>
            <name name-style="western">
              <surname>D’Onofrio</surname>
              <given-names>Claudio</given-names>
            </name>
            <name name-style="western">
              <surname>Häggström</surname>
              <given-names>Ingemar</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Persistent Identification of Instruments</article-title>
          <source>Data Science Journal</source>
          <volume>19</volume>
          <pub-id pub-id-type="doi">10.5334/dsj-2020-018</pub-id>
        </element-citation>
      </ref>
      <ref id="B13596187">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Strömert</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>1st Ontologies4Chem Workshop – Ontologies for chemistry.German National Library of Science and Technology</article-title>
          <uri>https://www.nfdi4chem.de/event/ontologies4chem-workshop/</uri>
          <pub-id pub-id-type="doi">10.25798/frnp-sn04</pub-id>
        </element-citation>
      </ref>
      <ref id="B13568831">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Strömert</surname>
              <given-names>Philip</given-names>
            </name>
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Castro</surname>
              <given-names>André</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Ontologies4Chem: the landscape of ontologies in chemistry</article-title>
          <source>Pure and Applied Chemistry</source>
          <volume>94</volume>
          <issue>6</issue>
          <fpage>605</fpage>
          <lpage>622</lpage>
          <pub-id pub-id-type="doi">10.1515/pac-2021-2007</pub-id>
        </element-citation>
      </ref>
      <ref id="B13568869">
        <element-citation publication-type="chapter">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Strömert</surname>
              <given-names>Philip</given-names>
            </name>
            <name name-style="western">
              <surname>Limbachia</surname>
              <given-names>Vatsal</given-names>
            </name>
            <name name-style="western">
              <surname>Oladazimi</surname>
              <given-names>Pooya</given-names>
            </name>
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <chapter-title>Towards a Versatile Terminology Service for Empowering FAIR Research Data: Enabling Ontology Discovery, Design, Curation, and Utilization Across Scientific Communities</chapter-title>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Acosta</surname>
              <given-names>Maribel</given-names>
            </name>
            <name name-style="western">
              <surname>Peroni</surname>
              <given-names>Silvio</given-names>
            </name>
            <name name-style="western">
              <surname>Vahdati</surname>
              <given-names>Sahar</given-names>
            </name>
            <name name-style="western">
              <surname>Gentile</surname>
              <given-names>Anna-Lisa</given-names>
            </name>
            <name name-style="western">
              <surname>Pellegrini</surname>
              <given-names>Tassilo</given-names>
            </name>
            <name name-style="western">
              <surname>Kalo</surname>
              <given-names>Jan-Christoph</given-names>
            </name>
          </person-group>
          <source>Knowledge Graphs: Semantics, Machine Learning, and Languages</source>
          <volume>56</volume>
          <publisher-name>IOS Press</publisher-name>
          <isbn>978-1-64368-425-3</isbn>
          <pub-id pub-id-type="doi">10.3233/ssw230005</pub-id>
        </element-citation>
      </ref>
      <ref id="B13553613">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Strömert</surname>
              <given-names>Philip</given-names>
            </name>
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Chalk</surname>
              <given-names>Stuart</given-names>
            </name>
            <name name-style="western">
              <surname>McEwen</surname>
              <given-names>Leah</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Guidance on how to use the IUPAC Gold Book as a canonical source for textual definitions in chemical ontologies</article-title>
          <source>ChemRxiv</source>
          <pub-id pub-id-type="doi">10.26434/chemrxiv-2024-fvzpq</pub-id>
        </element-citation>
      </ref>
      <ref id="B13579965">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Strömert</surname>
              <given-names>Philip</given-names>
            </name>
            <name name-style="western">
              <surname>Lanza</surname>
              <given-names>Giacomo</given-names>
            </name>
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
            <name name-style="western">
              <surname>karillio</surname>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>NFDI4Chem/VibrationalSpectroscopyOntology: v2024-09-23</article-title>
          <source>Zenodo</source>
          <pub-id pub-id-type="doi">10.5281/zenodo.10410722</pub-id>
        </element-citation>
      </ref>
      <ref id="B13577477">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Strömert</surname>
              <given-names>Philip</given-names>
            </name>
            <name name-style="western">
              <surname>Lanza</surname>
              <given-names>Giacomo</given-names>
            </name>
            <name name-style="western">
              <surname>Hunold</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Stosch</surname>
              <given-names>Rainer</given-names>
            </name>
            <name name-style="western">
              <surname>karillo</surname>
            </name>
          </person-group>
          <article-title>VibrationalSpectroscopyOntology</article-title>
          <uri>https://github.com/NFDI4Chem/VibrationalSpectroscopyOntology</uri>
          <date-in-citation content-type="access-date">2024-08-03T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13520196">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Teufel</surname>
              <given-names>Jonas</given-names>
            </name>
            <name name-style="western">
              <surname>Torresi</surname>
              <given-names>Luca</given-names>
            </name>
            <name name-style="western">
              <surname>Reiser</surname>
              <given-names>Patrick</given-names>
            </name>
            <name name-style="western">
              <surname>Friederich</surname>
              <given-names>Pascal</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>MEGAN: Multi-explanation graph attention network</article-title>
          <publisher-name>arXiv</publisher-name>
          <pub-id pub-id-type="doi">10.48550/ARXIV.2211.13236</pub-id>
        </element-citation>
      </ref>
      <ref id="B13577183">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Technology</surname>
              <given-names>TIB-Leibniz Information Centre for Science and</given-names>
            </name>
          </person-group>
          <article-title>NFDI4Chem Search Service</article-title>
          <uri>https://search.nfdi4chem.de/</uri>
          <date-in-citation content-type="access-date">2024-07-29T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13574337">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Technology</surname>
              <given-names>TIB-Leibniz Information Centre for Science and</given-names>
            </name>
          </person-group>
          <article-title>Terminology Service</article-title>
          <uri>https://terminology.nfdi4chem.de/ts/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13574444">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Technology</surname>
              <given-names>TIB-Leibniz Information Centre for Science and</given-names>
            </name>
          </person-group>
          <article-title>NFDI4Chem Search Service</article-title>
          <uri>https://search.nfdi4chem.de/</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13574361">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Technology</surname>
              <given-names>TIB-Leibniz Information Centre for Science and</given-names>
            </name>
          </person-group>
          <article-title>TIB Terminology Service Backend Swagger API Documentation</article-title>
          <uri>https://service.tib.eu/ts4tib/swagger-ui.html#</uri>
          <date-in-citation content-type="access-date">2024-07-29T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13579782">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tielker</surname>
              <given-names>Nicolas</given-names>
            </name>
            <name name-style="western">
              <surname>Eberlein</surname>
              <given-names>Lukas</given-names>
            </name>
            <name name-style="western">
              <surname>Hessler</surname>
              <given-names>Gerhard</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>K Friedemann</given-names>
            </name>
            <name name-style="western">
              <surname>Güssregen</surname>
              <given-names>Stefan</given-names>
            </name>
            <name name-style="western">
              <surname>Kast</surname>
              <given-names>Stefan M</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Quantum–mechanical property prediction of solvated drug molecules: what have we learned from a decade of SAMPL blind prediction challenges?</article-title>
          <source>Journal of Computer-Aided Molecular Design</source>
          <volume>35</volume>
          <issue>4</issue>
          <fpage>453</fpage>
          <lpage>472</lpage>
          <pub-id pub-id-type="doi">10.1007/s10822-020-00347-5</pub-id>
        </element-citation>
      </ref>
      <ref id="B13569162">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tremouilhac</surname>
              <given-names>Pierre</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Chia‐Lin</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Pei‐Chi</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Yu‐Chieh</given-names>
            </name>
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>An</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>Nicole</given-names>
            </name>
            <name name-style="western">
              <surname>Bach</surname>
              <given-names>Felix</given-names>
            </name>
            <name name-style="western">
              <surname>Ulrich</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Neumair</surname>
              <given-names>Bernhard</given-names>
            </name>
            <name name-style="western">
              <surname>Streit</surname>
              <given-names>Achim</given-names>
            </name>
            <name name-style="western">
              <surname>Bräse</surname>
              <given-names>Stefan</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>The Repository Chemotion: Infrastructure for Sustainable Research in Chemistry**</article-title>
          <source>Angewandte Chemie International Edition</source>
          <volume>59</volume>
          <issue>50</issue>
          <fpage>22771</fpage>
          <lpage>22778</lpage>
          <pub-id pub-id-type="doi">10.1002/anie.202007702</pub-id>
        </element-citation>
      </ref>
      <ref id="B13574273">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Van de Sompel</surname>
              <given-names>Herbert</given-names>
            </name>
            <name name-style="western">
              <surname>Klein</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>Shawn</given-names>
            </name>
            <name name-style="western">
              <surname>Nelson</surname>
              <given-names>Michael L</given-names>
            </name>
            <name name-style="western">
              <surname>Warner</surname>
              <given-names>Simeon</given-names>
            </name>
            <name name-style="western">
              <surname>Devaraju</surname>
              <given-names>Anusuriya</given-names>
            </name>
            <name name-style="western">
              <surname>Huber</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Steinhoff</surname>
              <given-names>Wilko</given-names>
            </name>
            <name name-style="western">
              <surname>Tykhonov</surname>
              <given-names>Vyacheslav</given-names>
            </name>
            <name name-style="western">
              <surname>Boruta</surname>
              <given-names>Luc</given-names>
            </name>
            <name name-style="western">
              <surname>Meijers</surname>
              <given-names>Enno</given-names>
            </name>
            <name name-style="western">
              <surname>Soiland-Reyes</surname>
              <given-names>Stian</given-names>
            </name>
            <name name-style="western">
              <surname>Wilkinson</surname>
              <given-names>Mark</given-names>
            </name>
          </person-group>
          <article-title>FAIR Signposting Profile</article-title>
          <uri>https://signposting.org/FAIR/</uri>
          <date-in-citation content-type="access-date">2024-08-03T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13579700">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Staalduinen</surname>
              <given-names>Nils</given-names>
            </name>
            <name name-style="western">
              <surname>Bannwarth</surname>
              <given-names>Christoph</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>MolBar: A Molecular Identifier for Inorganic and Organic Molecules with Full Support of Stereoisomerism</article-title>
          <source>ChemRxiv</source>
          <pub-id pub-id-type="doi">10.26434/chemrxiv-2024-k40v5-v2</pub-id>
        </element-citation>
      </ref>
      <ref id="B13574369">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Venkata</surname>
              <given-names>Chandrasekhar</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>Nisha</given-names>
            </name>
            <name name-style="western">
              <surname>Koepler</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>Steffen</given-names>
            </name>
            <name name-style="western">
              <surname>Steinbeck</surname>
              <given-names>Christoph</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Ontology Elements</article-title>
          <source>Zenodo</source>
          <pub-id pub-id-type="doi">10.5281/zenodo.8212133</pub-id>
        </element-citation>
      </ref>
      <ref id="B13521315">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vogt</surname>
              <given-names>Lars</given-names>
            </name>
            <name name-style="western">
              <surname>Strömert</surname>
              <given-names>Philip</given-names>
            </name>
            <name name-style="western">
              <surname>Matentzoglu</surname>
              <given-names>Nicolas</given-names>
            </name>
            <name name-style="western">
              <surname>Karam</surname>
              <given-names>Naouel</given-names>
            </name>
            <name name-style="western">
              <surname>Konrad</surname>
              <given-names>Marcel</given-names>
            </name>
            <name name-style="western">
              <surname>Prinz</surname>
              <given-names>Manuel</given-names>
            </name>
            <name name-style="western">
              <surname>Baum</surname>
              <given-names>Roman</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>FAIR 2.0: Extending the FAIR Guiding Principles to Address Semantic Interoperability</article-title>
          <publisher-name>arXiv</publisher-name>
          <uri>https://arxiv.org/abs/2405.03345</uri>
          <pub-id pub-id-type="doi">10.48550/arXiv.2405.03345</pub-id>
        </element-citation>
      </ref>
      <ref id="B13574238">
        <element-citation publication-type="other">
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Wahlster</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Winterhalter</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>German Standardization Roadmap on Artificial Intelligence (2nd edition)</article-title>
          <publisher-name>German Institute for Standardization (DIN e.V.)</publisher-name>
          <uri>www.din.de/go/roadmap-ai</uri>
        </element-citation>
      </ref>
      <ref id="B13579215">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wiley-VCH</surname>
            </name>
          </person-group>
          <article-title>Notice to Authors</article-title>
          <uri>https://onlinelibrary.wiley.com/page/journal/15213773/homepage/notice-to-authors</uri>
          <date-in-citation content-type="access-date">2024-08-04T00:34:29+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13579509">
        <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>Aalbersberg</surname>
              <given-names>IJsbrand Jan</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>’t Hoen</surname>
              <given-names>Peter A C</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>2016</year>
          <article-title>The FAIR Guiding Principles for scientific data management and stewardship</article-title>
          <source>Scientific Data</source>
          <volume>3</volume>
          <issue>1</issue>
          <pub-id pub-id-type="doi">10.1038/sdata.2016.18</pub-id>
        </element-citation>
      </ref>
    </ref-list>
  </back>
  <floats-group>
    <fig id="F13519912" position="float" orientation="portrait">
      <object-id content-type="arpha">492432E3-60B3-5A52-AFDB-135E06FE3E16</object-id>
      <object-id content-type="doi">10.3897/rio.11.e177037.figure7</object-id>
      <object-id content-type="zenodo_dep_id">17747331</object-id>
      <label>Figure 1.</label>
      <caption>
        <p>In-person workshops on RDM and Chemotion held by NFDI4Chem until date of submission (2024/08), and still planned in 2024.</p>
      </caption>
      <graphic xlink:href="rio-11-e177037-g001.png" position="float" id="oo_1423889.png" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1423889</uri>
      </graphic>
    </fig>
    <fig id="F13519927" position="float" orientation="portrait">
      <object-id content-type="arpha">6A778CB0-206E-52D9-AA3C-A3BCD49A1BB2</object-id>
      <object-id content-type="doi">10.3897/rio.11.e177037.figure7</object-id>
      <object-id content-type="zenodo_dep_id">17747331</object-id>
      <label>Figure 2.</label>
      <caption>
        <p>NFDI4Chem governance structure.</p>
      </caption>
      <graphic xlink:href="rio-11-e177037-g002.png" position="float" id="oo_1454296.png" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1454296</uri>
      </graphic>
    </fig>
    <fig id="F13519929" position="float" orientation="portrait">
      <object-id content-type="arpha">05542408-1865-5207-95AB-0A6858220F2C</object-id>
      <object-id content-type="doi">10.3897/rio.11.e177037.figure4</object-id>
      <object-id content-type="zenodo_dep_id">17747325</object-id>
      <label>Figure 3.</label>
      <caption>
        <p>The role and relationship of services and task areas in the user-facing (top), underlying (bottom) and infrastructure layer (middle) of the NFDI4Chem work program.</p>
      </caption>
      <graphic xlink:href="rio-11-e177037-g003.png" position="float" id="oo_1423893.png" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1423893</uri>
      </graphic>
    </fig>
    <fig id="F13519931" position="float" orientation="portrait">
      <object-id content-type="arpha">A32A34C5-020E-56BB-8F3E-815112271A01</object-id>
      <object-id content-type="doi">10.3897/rio.11.e177037.figure7</object-id>
      <object-id content-type="zenodo_dep_id">17747331</object-id>
      <label>Figure 4.</label>
      <caption>
        <p>Components of TA2, Smart Lab, and its connections/interactions to TA3-TA6. Orange: other TAs of NFDI4Chem; purple: modular, general software plugins, usable in diverse NFDI4Chem services; white: software developed for the ELN; blue: tasks related to the smart lab but with considerable content from other stakeholders/projects.</p>
      </caption>
      <graphic xlink:href="rio-11-e177037-g004.png" position="float" id="oo_1423896.png" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1423896</uri>
      </graphic>
    </fig>
    <fig id="F13519933" position="float" orientation="portrait">
      <object-id content-type="arpha">D9B002AC-75E3-5D05-951C-48E2790CB714</object-id>
      <object-id content-type="doi">10.3897/rio.11.e177037.figure7</object-id>
      <object-id content-type="zenodo_dep_id">17747331</object-id>
      <label>Figure 5.</label>
      <caption>
        <p>The structure of TA 3, Federation of repositories, and its connections/interactions with other task areas.</p>
      </caption>
      <graphic xlink:href="rio-11-e177037-g005.png" position="float" id="oo_1423897.png" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1423897</uri>
      </graphic>
    </fig>
    <fig id="F13519937" position="float" orientation="portrait">
      <object-id content-type="arpha">8F2AF7F2-BBAA-5474-943D-0AC69F0C9874</object-id>
      <object-id content-type="doi">10.3897/rio.11.e177037.figure7</object-id>
      <object-id content-type="zenodo_dep_id">17747331</object-id>
      <label>Figure 6.</label>
      <caption>
        <p>Touchpoint analysis for the communication strategy of NFDI4Chem.</p>
      </caption>
      <graphic xlink:href="rio-11-e177037-g006.png" position="float" id="oo_1445630.png" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1445630</uri>
      </graphic>
    </fig>
    <fig id="F13519939" position="float" orientation="portrait">
      <object-id content-type="arpha">B0AACBDD-09D0-59F5-8A34-6EB3FB990BFD</object-id>
      <object-id content-type="doi">10.3897/rio.11.e177037.figure7</object-id>
      <object-id content-type="zenodo_dep_id">17747331</object-id>
      <label>Figure 7.</label>
      <caption>
        <p>Outline of the 1st euroSAMPL challenge. In line with the NFDI4Chem strategy, this blind prediction challenge serves as a best practice example of combined experimental and theoretical workflows with FAIR and reproducible data and code.</p>
      </caption>
      <graphic xlink:href="rio-11-e177037-g007.png" position="float" id="oo_1423901.png" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1423901</uri>
      </graphic>
    </fig>
    <fig id="F13519941" position="float" orientation="portrait">
      <object-id content-type="arpha">F9F71326-3CD5-58E4-B91B-A8150B99C9EF</object-id>
      <object-id content-type="doi">10.3897/rio.11.e177037.figure7</object-id>
      <object-id content-type="zenodo_dep_id">17747331</object-id>
      <label>Figure 8.</label>
      <caption>
        <p>NFDI4Chem services and data evolving into a Semantic Data Hub.</p>
      </caption>
      <graphic xlink:href="rio-11-e177037-g008.png" position="float" id="oo_1423902.png" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1423902</uri>
      </graphic>
    </fig>
    <table-wrap id="T13519834" position="float" orientation="portrait">
      <label>Table 1.</label>
      <caption>
        <p>Overview of the six task areas (TA) of NFDI4Chem.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Task area</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Measures</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Responsible Co-spokes- person</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>TA1</bold> Management and Coordination</td>
            <td rowspan="1" colspan="1"><bold>M 1.1</bold>: Overall legal, contractual, ethical, financialand administrative management of the consortium<break/><bold>M 1.2</bold>: Coordination at consortium level of the technical, outreach, training activities and their future sustainability<break/><bold>M 1.3</bold>: Coordination of long-term knowledge management, internet publishing system and other innovation-related activities<break/><bold>M1.4</bold>: Overseeing the promotion of equal opportunity in the project</td>
            <td rowspan="1" colspan="1">Christoph Steinbeck</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>TA2</bold> Smart Laboratory</td>
            <td rowspan="1" colspan="1"><bold>M 2.1</bold>: Device integration and management<break/><bold>M 2.2</bold>: Establishment and maintenance of the electronic lab notebook<break/><bold>M 2.3</bold>: Viewers, processors, and editors for structures and data<break/><bold>M 2.4</bold>: Development and extension of topic-related ELN functions<break/><bold>M 2.5</bold>: Services provided to the community<break/><bold>M 2.6</bold>: ELN as part of a digital ecosystem</td>
            <td rowspan="1" colspan="1">Nicole Jung</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>TA3</bold> Repositories</td>
            <td rowspan="1" colspan="1"><bold>M 3.1</bold>: Enhancement and sustainable operation and maintenanceof the federation of chemistry repositories<break/><bold>M3.2</bold>: Advanced FAIRification: optimise interoperability,data reuse, AI-readiness and user experience<break/><bold>M3.3</bold>: Consolidation, Harmonisation and Standardisationof the federation of repositories<break/><bold>M3.4</bold>: Developing and implementing sustainable service operating models<break/><bold>M3.5</bold>: Extension of the federation of repositories</td>
            <td rowspan="1" colspan="1">Felix Bach</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>TA4</bold> Metadata, Data Standards, and Publication Standards</td>
            <td rowspan="1" colspan="1"><bold>M4.1</bold>: Development and Harmonisation of Minimum Information Metadata Standards<break/><bold>M4.2</bold>: Development and maintenance of standards for data exchangeand archival<break/><bold>M4.3</bold>: Implementation and support of software components for creation, validation, and consumption of standardised data formats<break/><bold>M4.4</bold>: Improving re-usability of scientific data through data standards<break/><bold>M4.5</bold>: Integration with scholarly publishing</td>
            <td rowspan="1" colspan="1">Steffen Neumann, Christoph Steinbeck</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>TA5</bold> Community and Training</td>
            <td rowspan="1" colspan="1"><bold>M5.1</bold>: Community requirements<break/><bold>M5.2</bold>: Awareness<break/><bold>M5.3</bold>: Training and support<break/><bold>M5.4</bold>: Curricular teaching<break/><bold>M5.5</bold>: Best practice<break/><bold>M5.6</bold>: Community stakeholders</td>
            <td rowspan="1" colspan="1">Sonja Herres-Pawlis, Johannes Liermann</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>TA6</bold> Synergies and Cross-Cutting Topics</td>
            <td rowspan="1" colspan="1"><bold>M6.1</bold>: Ontology development, curation and harmonisation<bold>M6.2</bold>: Terminology service, mapping service, pattern/shape service<bold>M6.3</bold>: Semantic data hub<bold>M6.4</bold>: NFDI4Chem within the NFDI and basic services<bold>M6.5</bold>: Integration into the landscape of existing infrastructure and initiatives<bold>M6.6</bold>: Enable machine learning</td>
            <td rowspan="1" colspan="1">Oliver Koepler</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13519835" position="float" orientation="portrait">
      <label>Table 2.</label>
      <caption>
        <p>Potential risks of the TA1 work programme and measures for their mitigation.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Description of management risks</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Proposed risk-mitigation measures</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM1: Ambitious scale</bold>. Coordinating a project requiring many different expertises across institutions needs in a vivid scientific field. A loss of focus could lead to poor delivery.<break/><bold>Likelihood</bold>: Low</td>
            <td rowspan="1" colspan="1">Simple and tight structure in the proposal allows straightforward assessment. Frequent internal electronic and video communication of the SC,quarterly flash reports, the annual review process at the consortium meetings and review by the NFDI and DFG, which will track progress. Ultimately, the governance structure has been optimised throughout the first funding<break/><bold>TA(s) involved</bold>: All</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM 2: Competitive labour market.</bold> Difficulties in hiring of skilled staff in a highly competitive job market might be a risk. Computer Scientists with expertise in infrastructure development and distributed computing are under very high international demand.<break/><bold>Likelihood</bold>: Medium</td>
            <td rowspan="1" colspan="1">The project will need to have enough time between the funding decision and the start of the 2nd funding phase in order to prolong contracts of existing staff or advertise new positions where applicable. A long-term career perspective in the NFDI system would increase the attraction of jobs in the consortium but is a matter of political decisions.<break/><bold>TA(s) involved</bold>: all.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM: Budget cuts.</bold> Due to budget cuts, we can not onboard additional stakeholders as partners, limiting the expansion of the consortium and will lose highly trained, dedicated staff. <break/><bold>Likelihood</bold>: High</td>
            <td rowspan="1" colspan="1">We will need to prioritise measures and tasks and decide on measures to be dropped to ensure the overall stability of operations.<break/><bold>TA(s) involved</bold>: all</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13519836" position="float" orientation="portrait">
      <label>Table 3.</label>
      <caption>
        <p>Potential risks of the TA2 work programme and measures for their mitigation.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Description of management risks</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Proposed risk-mitigation measures</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM1</bold>: The development and international agreement on (new) standards is not fast enough and the NFDI4Chem consortium is missing basic models on how to generate interfaces, and to export, and transfer data.<break/><bold>Likelihood</bold>: medium</td>
            <td rowspan="1" colspan="1">Solutions to the given risks are described in TA4 and TA6 and were successful in FP1. NFDI4Chem starts with reasonable models that are not agreed on internationally but can be extended in a flexible manner. Adaptation to international agreements in a second step.<break/><bold>TA(s) involved</bold>: TA4, TA6</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM2</bold>: Security risks and data leakage for the decentrally installed ELNs and ELN as a Service.<break/><bold>Likelihood</bold>: low</td>
            <td rowspan="1" colspan="1">The ELN software will undergo regular security checks as part of the CI process and penetration tests. The ELN as a service is hosted in professionally operated data centres at KIT-SCC and FIZ with established security architecture, intrusion detection systems and virus scanners maintained by experienced administrators.<break/><bold>TA(s) involved</bold>: TA2</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM3</bold>: Risks in the case of budget cuts.<break/><bold>Likelihood</bold>: high</td>
            <td rowspan="1" colspan="1">See general description of this risk in TA1.<break/><bold>TA(s) involved</bold>: all task areas</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13519839" position="float" orientation="portrait">
      <label>Table 4.</label>
      <caption>
        <p>Potential risks of the TA3 work programme and measures for their mitigation.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Description of management risks</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Proposed risk-mitigation measures</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM1</bold>: Hiring and keeping qualified staff (software developers, DevOp- and IT-service operation experts).<break/><bold>Likelihood</bold>: medium.</td>
            <td rowspan="1" colspan="1">Use multiple channels to reach candidates.<break/><bold>TA(s) involved</bold>: all</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM2</bold>: Continuous support for components developers.<break/><bold>Likelihood</bold>: medium.</td>
            <td rowspan="1" colspan="1">Embedding in frameworks such as deRSE, RSE4NFDI (see LoS).<break/><bold>TA(s) involved</bold>: TA2, TA3, TA6</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM3</bold>: Reduction in funding with the effect that reliable infrastructure operation and maintenance cannot be guaranteed.<break/><bold>Likelihood</bold>: medium.</td>
            <td rowspan="1" colspan="1">Apply for additional funding.<break/><bold>TA(s) involved</bold>: TA2, TA3, TA6</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM4</bold>: Risks in the case of budget cuts.<break/><bold>Likelihood</bold>: high</td>
            <td rowspan="1" colspan="1">See general description of this risk in TA1<break/><bold>TA(s) involved</bold>: all task areas</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13519849" position="float" orientation="portrait">
      <label>Table 5.</label>
      <caption>
        <p>Potential risks of the TA4 work programme and measures for their mitigation.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Description of management risks</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Proposed risk-mitigation measures</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM1</bold>: Inability by the community to <bold>agree on MIChI standards</bold> due to incompatible assumptions.<break/><bold>Likelihood</bold>: Medium</td>
            <td rowspan="1" colspan="1">We aim for a modular set of recommendations for the subdisciplines, avoiding that one standard has to fit all subdisciplines. Acceptance is promoted through community actions.<break/><bold>TA(s) involved</bold>: TA2, TA3, TA6 and TA4</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM2</bold>: Unwillingness of instrument manufacturers to implement open data format standards or updates to already implemented formats to their software. <bold>Likelihood</bold>: Medium</td>
            <td rowspan="1" colspan="1">We will engage with instrument manufacturers, include them in the MIChI-based metadata schema development as well as the subsequent specification of data format standards and support the implementation.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM3</bold>: Technical hurdles to decode proprietary vendor formats, licensing issues for proprietary Windows DLLs. <bold>Likelihood</bold>: Medium</td>
            <td rowspan="1" colspan="1">Positive experience engaging with mass spectrometry vendors. Training of users to include Open Formats in tender requirements.<break/><bold>TA(s) involved</bold>: TA4, TA6</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM4</bold>: <bold>Objection by publishers</bold> to adopt stringent author guidelines ensuring good scientific practice, especially those with a business model based on APC.<break/><bold>Likelihood</bold>: Medium</td>
            <td rowspan="1" colspan="1">Existing Editors4Chem workshop series allows Editors to listen to the chemistry community and adopt realistic author guidelines.<break/><bold>TA(s) involved</bold>: TA3, TA2, TA4, TA5</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM5</bold>: Risks in the case of budget cuts.<break/><bold>Likelihood</bold>: high</td>
            <td rowspan="1" colspan="1">See general description of this risk in TA1<break/><bold>TA(s) involved</bold>: all task areas</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13519889" position="float" orientation="portrait">
      <label>Table 6.</label>
      <caption>
        <p>Potential risks of the TA5 work programme and measures for their mitigation.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Description of risks</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Proposed risk-mitigation measures</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM1: Biased or incomplete requirement assessment.</bold> Assessment of RDM needs may not reach a representative fraction of the community and lead to biased or incomplete results. <break/><bold>Likelihood</bold>: Medium</td>
            <td rowspan="1" colspan="1">Results must be reviewed and critically discussed by the survey panel.Research communities must get involved in targeting the surveys.<break/><bold>TA(s) involved</bold>: TA1, TA5</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM2: Developed tools, standards and materials are not adopted by the community</bold>, either by a mismatch of expectations or by ignorance.<break/><bold>Likelihood</bold>: High</td>
            <td rowspan="1" colspan="1">Development must constantly be monitored and critically discussed by the Steering Committee.Development activities must include early-stage hands-on testing by PhD students.External expertise and review must be acquired.<break/><bold>TA(s) involved</bold>: TA1-5</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM3: Premature frustration of the community.</bold> The lack of usability or practicality of developed products may propagate reluctance to face challenges involved with RDM in everyday research.<break/><bold>Likelihood</bold>: Medium</td>
            <td rowspan="1" colspan="1">Careful testing of all products with representative user groups.User-friendliness by design.<break/><bold>TA(s) involved</bold>: TA2, TA5</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM4</bold>: Risks in the case of budget cuts.<break/><bold>Likelihood</bold>: high</td>
            <td rowspan="1" colspan="1">See general description of this risk in TA1<break/><bold>TA(s) involved</bold>: all task areas</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <table-wrap id="T13519890" position="float" orientation="portrait">
      <label>Table 7.</label>
      <caption>
        <p>Potential risks of the TA6 work programme and measures for their mitigation.</p>
      </caption>
      <table rules="all">
        <tbody>
          <tr>
            <td rowspan="1" colspan="1">
              <bold>Description of management risks</bold>
            </td>
            <td rowspan="1" colspan="1">
              <bold>Proposed risk-mitigation measures</bold>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM1: Unwillingness</bold> of the ontology curators to join collaborative ontology development efforts.<break/><bold>Likelihood</bold>: low</td>
            <td rowspan="1" colspan="1">Transparent community strategy about motivation, roadmaps, guidelines for contributions and collaborations.<break/><bold>TA(s) involved</bold>: TA4, TA5</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM2</bold>: Increased personal resources required to cooperate with future basic services and their implementation. <break/><bold>Likelihood</bold>: medium</td>
            <td rowspan="1" colspan="1">Close communication NFDI sections and Base4NFDI. Prioritising implementations based on community needs.<break/><bold>TA(s) involved</bold>: TA4, TA2, TA3, TA5</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM3</bold>: Required APIs and functionality of TS4NFDI are not provided in time or not at all. <break/><bold>Likelihood</bold>: medium</td>
            <td rowspan="1" colspan="1">Close coordination with the TS4NFDI project to identify rising time delays and initiate counter measures. Mapping may be stored in MSS meanwhile.<break/><bold>TA(s) involved</bold>: TA4, TA6 and TS4NFDI project</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1"><bold>RM4</bold>: Risks in the case of budget cuts.<break/><bold>Likelihood</bold>: high</td>
            <td rowspan="1" colspan="1">See general description of this risk in TA1<break/><bold>TA(s) involved</bold>: all task areas</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
  </floats-group>
</article>
