CINXE.COM

<!doctype html><html lang=en><head><meta charset=utf-8><link rel=apple-touch-icon sizes=76x76 href=/img/apple-touch-icon.png><link rel=icon type=image/png href=/img/favicon.png><meta http-equiv=x-ua-compatible content="IE=edge,chrome=1"><title>Research Organization Registry (ROR) | Using ROR for Funder Identification</title><meta name=description content="Several widely used scholarly systems are using ROR IDs to identify and disambiguate funders. In this post, we’ll give you a glimpse of how and why these systems use ROR IDs for funder identifiers."><meta content="width=device-width,initial-scale=1,maximum-scale=1,user-scalable=0,shrink-to-fit=no" name=viewport><link rel=preconnect href=https://fonts.googleapis.com><link rel=preconnect href=https://fonts.gstatic.com crossorigin><link rel=stylesheet href=https://ror.org/vendor/fontawesome/css/fontawesome.css><link rel=stylesheet href=https://ror.org/vendor/fontawesome/css/brands.css><link rel=stylesheet href=https://ror.org/vendor/fontawesome/css/solid.css><link href=//cdnjs.cloudflare.com/ajax/libs/cc-icons/1.2.1/css/cc-icons.min.css rel=stylesheet><link href=//cdn-images.mailchimp.com/embedcode/classic-10_7.css rel=stylesheet type=text/css><meta property="og:title" content="Using ROR for Funder Identification"><meta property="og:description" content="Several widely used scholarly systems are using ROR IDs to identify and disambiguate funders. In this post, we’ll give you a glimpse of how and why these systems use ROR IDs for funder identifiers."><meta property="og:type" content="article"><meta property="og:url" content="https://ror.org/blog/2024-08-06-using-ror-for-funder-identification/"><meta property="og:image" content="https://ror.org/img/blog/use-case-funders/ror-for-funders.png"><meta property="article:section" content="blog"><meta property="article:published_time" content="2024-08-06T00:00:00+00:00"><meta property="article:modified_time" content="2024-08-06T00:00:00+00:00"><meta property="og:site_name" content="Research Organization Registry (ROR)"><link rel=stylesheet href=https://ror.org/css/hugo-ror.css><link href="https://fonts.googleapis.com/icon?family=Material+Icons+Outlined" rel=stylesheet><link rel="shortcut icon" href="https://ror.org/img/favicon.ico?v=2" type=image/x-icon><link rel=apple-touch-icon href="https://ror.org/img/apple-touch-icon.png?v=2"><link rel=alternate href=https://ror.org/index.xml type=application/rss+xml title="Research Organization Registry (ROR)"><link rel=alternate href=https://ror.org/feed.xml type=application/atom+xml title="Research Organization Registry (ROR)"><script>var _paq=window._paq=window._paq||[];_paq.push(["setDomains",["*.ror.org"]]),_paq.push(["trackPageView"]),_paq.push(["enableLinkTracking"]),function(){t="https://crossref.matomo.cloud/",_paq.push(["setTrackerUrl",t+"matomo.php"]),_paq.push(["setSiteId","30"]);var t,n=document,e=n.createElement("script"),s=n.getElementsByTagName("script")[0];e.async=!0,e.src="https://cdn.matomo.cloud/crossref.matomo.cloud/matomo.js",s.parentNode.insertBefore(e,s)}()</script></head><body class=blog><div class=wrapper id=all><header><nav class="navbar navbar-expand-lg bg-white"><div class=container-fluid><a class="navbar-brand d-block" href=https://ror.org/><img class="pl-0 pr-0" src=https://ror.org/img/ror-logo.svg alt="Research Organization Registry logo"></a> <button class=navbar-toggler type=button data-toggle=collapse data-target=#navbarCollapse aria-controls=navbarSupportedContent aria-expanded=false aria-label="Toggle navigation"> <span class="navbar-toggler-bar bar1"></span> <span class="navbar-toggler-bar bar2"></span> <span class="navbar-toggler-bar bar3"></span></button><div class="collapse navbar-collapse" id=navbarCollapse><ul class="nav navbar-nav ml-auto"><li class=nav-item><a class=nav-link href=/about><p>About</p></a></li><li class=nav-item><a class=nav-link href=/registry><p>Registry</p></a></li><li class=nav-item><a class=nav-link href=/community><p>Community</p></a></li><li class=nav-item><a class=nav-link href=/blog><p>Blog</p></a></li><li class=nav-item><a class="nav-link external" href=https://ror.readme.io/><p>Documentation <i class="fa-solid fa-external-link"></i></p></a></li></ul></div></div></nav></header><section class="section section-banner" id=content><div class="page-banner jumbotron" style="background:url(/img/banners/ROR_Banner-green.png)50% no-repeat"><div class=container><div class=row><div class="col-md-12 mr-auto"><h1 id=page-title>Using ROR for Funder Identification</h1></div></div></div></div><section class=breadcrumbs-wrap><div class="container breadcrumbs-wrap"><div class=row><div class="col-md-9 mr-auto"><div role=navigation aria-label="breadcrumbs navigation"><ul class=breadcrumbs><li><a href=https://ror.org/>Home</a><span>></span></li><li><a href=/blog/>Blog</a><span>></span></li><li>Using ROR for Funder Identification</li></ul></div></div></div></div></section><div class="section container"><div class=row><div class=col-md-9 id=blog-post><p class=author>By Amanda French | August 6, 2024</p><div id=post-content><figure class=featured-figure><img src=/img/blog/use-case-funders/ror-for-funders.png alt="ROR logo and funder icon"></figure><p>Several widely used scholarly systems are using ROR IDs to identify and disambiguate funding organizations. In this post, we’ll give you a glimpse of how and why these systems use ROR IDs as funder identifiers.</p><p>If you’re reading this post, you probably know that for the last ten years, <a href=https://www.crossref.org/services/funder-registry/>the Crossref Open Funder Registry</a> (formerly FundRef) has been the default identifier for funding organizations. You might also know that last fall, Crossref <a href=https://www.crossref.org/blog/open-funder-registry-to-transition-into-research-organization-registry-ror/>announced</a> “a long-term plan to deprecate the Open Funder Registry” in favor of ROR so that publishing systems and workflows can use one open registry, not two, to identify organizations. If you’re interested in learning more about that transition, you can consult our <a href=https://ror.readme.io/docs/funder-registry>Open Funder Registry transition guide</a> or read <a href=https://ror.org/tags/funders/>previous ROR blog posts</a>. But if you’re interested in learning more about <strong>early adopters who are already using ROR to identify funders now</strong>, read on.</p><h2 id=repositories-are-ahead-of-the-curve>Repositories are ahead of the curve <a href=#repositories-are-ahead-of-the-curve><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" class="ha ha-link" width="16" height="16"><path d="M579.8 267.7c56.5-56.5 56.5-148 0-204.5-50-50-128.8-56.5-186.3-15.4l-1.6 1.1c-14.4 10.3-17.7 30.3-7.4 44.6s30.3 17.7 44.6 7.4l1.6-1.1c32.1-22.9 76-19.3 103.8 8.6 31.5 31.5 31.5 82.5.0 114L422.3 334.8c-31.5 31.5-82.5 31.5-114 0-27.9-27.9-31.5-71.8-8.6-103.8l1.1-1.6c10.3-14.4 6.9-34.4-7.4-44.6s-34.4-6.9-44.6 7.4l-1.1 1.6C206.5 251.2 213 330 263 380c56.5 56.5 148 56.5 204.5.0L579.8 267.7zM60.2 244.3c-56.5 56.5-56.5 148 0 204.5 50 50 128.8 56.5 186.3 15.4l1.6-1.1c14.4-10.3 17.7-30.3 7.4-44.6s-30.3-17.7-44.6-7.4l-1.6 1.1c-32.1 22.9-76 19.3-103.8-8.6C74 372 74 321 105.5 289.5L217.7 177.2c31.5-31.5 82.5-31.5 114 0 27.9 27.9 31.5 71.8 8.6 103.9l-1.1 1.6c-10.3 14.4-6.9 34.4 7.4 44.6s34.4 6.9 44.6-7.4l1.1-1.6C433.5 260.8 427 182 377 132c-56.5-56.5-148-56.5-204.5.0L60.2 244.3z"/></svg></a></h2><p>In general, <strong>repository systems are doing better than publishing systems</strong> in terms of adopting ROR for identifying funding organizations. One major factor in this phenomenon is undoubtedly <strong>DataCite’s early support</strong> for this use case. <a href=https://datacite.org>DataCite</a>, the DOI registration agency that most data repositories use, has <a href=https://datacite.org/blog/identify-your-affiliation-with-metadata-schema-4-3/>supported ROR identifiers in the <code>fundingReferences</code> element of its metadata schema</a> since August of 2019. This early schema change encouraged data repositories to send ROR IDs to DataCite in DOI metadata. Note, too, that DataCite is now <a href=https://datacite.org/blog/guidance-for-registering-datacite-dois-for-awards/>encouraging funders to register DOIs for awards</a>, and ROR is DataCite’s recommended funder identifier in award metadata.</p><p>DataCite’s API shows that <strong>nearly one-third of DataCite DOIs with an identifier in the funding reference use ROR</strong> as the funder identifier. Out of a total of about 1.4 million DataCite DOIs with funding identifiers, over 432,000 of them include ROR IDs.</p><figure><img src=/img/blog/use-case-funders/datacite-funder-ids-by-type.png alt="Funder identifiers by ID type in DataCite"><figcaption><p>DataCite records that have a value in <code>fundingReferences.funderIdentifier</code> as of July 15, 2024, broken down by <code>fundingReferences.funderIdentifier.Type</code>. See <a href=https://docs.google.com/spreadsheets/d/e/2PACX-1vQU_zvKDRXOFY56Zq6gAZyWBXWivQxPyDgAVP18bYDpNTgrM2pQFz4EzNc6I44kgTmhoVqkTJfef-HN/pubhtml>ROR DOI stats</a> spreadsheet for queries and data.</p></figcaption></figure><p>Another factor that has driven early adoption of ROR for funder identification in repository systems is the U.S. National Institutes of Health (NIH) <a href=https://datascience.nih.gov/data-ecosystem/generalist-repository-ecosystem-initiative>Generalist Repository Ecosystem Initiative (GREI)</a>, whose primary aim is to develop “a common set of cohesive and consistent capabilities, services, metrics, and social infrastructure across generalist repositories” so that NIH-funded researchers can more easily discover and share their research data. Seven generalist repository systems are participating: <a href=https://dataverse.org/>Dataverse</a>, <a href=https://datadryad.org/stash>Dryad</a>, <a href=https://figshare.com>Figshare</a>, <a href=https://data.mendeley.com>Mendeley Data</a>, the <a href=https://osf.io>Open Science Framework (OSF)</a>, <a href=https://vivli.org>Vivli</a>, and <a href=https://zenodo.org>Zenodo</a>. All seven have <a href=https://medium.com/@blog-grei/kicking-off-greis-third-year-b8709ab45a48>agreed to implement ROR for author affiliations</a>, and some have also taken the opportunity to implement ROR for funder identification sooner rather than later. Dryad, Figshare, Zenodo, and Vivli implemented ROR to identify funders in 2023; Dataverse and OSF are actively planning to use ROR for funders soon, and Mendeley Data will do so at some point in the future. When data repositories use ROR as a standard funder identifier, it enables all funders, including the NIH, to track research datasets resulting from their funding more easily.</p><p>DataCite’s API shows that all but one of the top five providers of ROR IDs for funders are GREI participants: Dryad, Zenodo, and Figshare together have registered over 100,000 DOIs that use ROR IDs in funding references. An additional repository operated by the Leibniz Institute DSMZ, <a href=https://straininfo.dsmz.de/>StrainInfo</a> (a collection of data about microorganisms and cell cultures), has used ROR IDs for funder identification in over 300,000 DataCite DOIs.</p><figure class=blog-figure><img src=/img/blog/use-case-funders/datacite-funder-ids-by-client.png alt="Funder IDs by client in DataCite"><figcaption><p>DataCite’s API shows the top providers of ROR IDs in funding references. Note that <code>figshare.ars</code> includes figshare.com, Figshare+, and other Figshare repositories. Query: <code>https://api.datacite.org/dois?query=fundingReferences.funderIdentifierType:ROR&page[size]=0</code></p></figcaption></figure><p>Let’s take a look at each of these systems to see how they’ve implemented ROR for funders.</p><h2 id=dryad-is-the-first-to-switch-to-ror-for-funder-ids>Dryad is the first to switch to ROR for funder IDs <a href=#dryad-is-the-first-to-switch-to-ror-for-funder-ids><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" class="ha ha-link" width="16" height="16"><path d="M579.8 267.7c56.5-56.5 56.5-148 0-204.5-50-50-128.8-56.5-186.3-15.4l-1.6 1.1c-14.4 10.3-17.7 30.3-7.4 44.6s30.3 17.7 44.6 7.4l1.6-1.1c32.1-22.9 76-19.3 103.8 8.6 31.5 31.5 31.5 82.5.0 114L422.3 334.8c-31.5 31.5-82.5 31.5-114 0-27.9-27.9-31.5-71.8-8.6-103.8l1.1-1.6c10.3-14.4 6.9-34.4-7.4-44.6s-34.4-6.9-44.6 7.4l-1.1 1.6C206.5 251.2 213 330 263 380c56.5 56.5 148 56.5 204.5.0L579.8 267.7zM60.2 244.3c-56.5 56.5-56.5 148 0 204.5 50 50 128.8 56.5 186.3 15.4l1.6-1.1c14.4-10.3 17.7-30.3 7.4-44.6s-30.3-17.7-44.6-7.4l-1.6 1.1c-32.1 22.9-76 19.3-103.8-8.6C74 372 74 321 105.5 289.5L217.7 177.2c31.5-31.5 82.5-31.5 114 0 27.9 27.9 31.5 71.8 8.6 103.9l-1.1 1.6c-10.3 14.4-6.9 34.4 7.4 44.6s34.4 6.9 44.6-7.4l1.1-1.6C433.5 260.8 427 182 377 132c-56.5-56.5-148-56.5-204.5.0L60.2 244.3z"/></svg></a></h2><p>As the <a href=https://ror.org/blog/2019-07-10-ror-ing-together-with-dryad/>very first system to adopt ROR</a> in 2019, Dryad has been using ROR for author affiliations longer than anyone else, and Dryad was almost as quick to adopt ROR for funding identification. Like many publishing and repository systems, Dryad originally used Crossref’s Open Funder Registry to identify funders, but with the announcement that the Open Funder Registry is headed for deprecation, Dryad moved speedily to switch from Funder IDs to ROR IDs, completing the transition in <a href=https://github.com/datadryad/dryad-product-roadmap/issues/2840>October 2023</a>. This transition involved four main tasks:</p><ul><li>Changing Dryad’s submission form funder lookup to use ROR instead of the Funder Registry</li><li>Converting existing Funder IDs in Dryad’s data to ROR IDs</li><li>Enabling the capacity to send ROR IDs in new metadata deposits to DataCite</li><li>Updating the funder identifiers in Dryad’s existing DataCite DOI records</li></ul><p>We can see the result of Dryad’s work in their submission form. Now, in Dryad, the typeahead fields for “Institutional affiliation” and “Granting organization” both use ROR, and both helpfully reveal organization names, acronyms, and locations based on what the user types, just as we recommend in our <a href=https://ror.readme.io/v2/docs/forms>form guidelines</a>.</p><figure><img src=/img/blog/use-case-funders/ror-dryad.gif alt="Dryad's affiliation and funder fields use ROR to power typeahead lookups."><figcaption><p>Dryad’s affiliation and funder fields use ROR to power typeahead lookups.</p></figcaption></figure><p><strong>Dryad is the only system of those we’re discussing here to have transitioned entirely from using the Crossref Open Funder Registry for funder identification to using ROR for funder identification</strong>: other systems have either started fresh with ROR or continue to use multiple registries.</p><h2 id=zenodos-funder-model-is-based-on-ror>Zenodo’s funder model is based on ROR <a href=#zenodos-funder-model-is-based-on-ror><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" class="ha ha-link" width="16" height="16"><path d="M579.8 267.7c56.5-56.5 56.5-148 0-204.5-50-50-128.8-56.5-186.3-15.4l-1.6 1.1c-14.4 10.3-17.7 30.3-7.4 44.6s30.3 17.7 44.6 7.4l1.6-1.1c32.1-22.9 76-19.3 103.8 8.6 31.5 31.5 31.5 82.5.0 114L422.3 334.8c-31.5 31.5-82.5 31.5-114 0-27.9-27.9-31.5-71.8-8.6-103.8l1.1-1.6c10.3-14.4 6.9-34.4-7.4-44.6s-34.4-6.9-44.6 7.4l-1.1 1.6C206.5 251.2 213 330 263 380c56.5 56.5 148 56.5 204.5.0L579.8 267.7zM60.2 244.3c-56.5 56.5-56.5 148 0 204.5 50 50 128.8 56.5 186.3 15.4l1.6-1.1c14.4-10.3 17.7-30.3 7.4-44.6s-30.3-17.7-44.6-7.4l-1.6 1.1c-32.1 22.9-76 19.3-103.8-8.6C74 372 74 321 105.5 289.5L217.7 177.2c31.5-31.5 82.5-31.5 114 0 27.9 27.9 31.5 71.8 8.6 103.9l-1.1 1.6c-10.3 14.4-6.9 34.4 7.4 44.6s34.4 6.9 44.6-7.4l1.1-1.6C433.5 260.8 427 182 377 132c-56.5-56.5-148-56.5-204.5.0L60.2 244.3z"/></svg></a></h2><p>Also in October 2023, the generalist data repository <a href=https://zenodo.org>Zenodo</a> completed its <a href=https://blog.zenodo.org/2023/10/13/2023-10-13-zenodo-rdm/>migration</a> to an open source research data management system called <a href=https://inveniosoftware.org/products/rdm/>InvenioRDM</a>. InvenioRDM was architected from the beginning with ROR for both author affiliations and funders, and other repositories that use InvenioRDM (e.g., <a href=https://data.caltech.edu>CaltechData</a>) therefore have similar capabilities as Zenodo.</p><p>Zenodo takes an “award-first” approach to connecting items to funders, asking the user to search for and select a specific award and then using the award identifier to pull in information about the funder who granted that award. Users also have the option to filter awards by a limited number of funders who participate in <a href=https://www.openaire.eu/>OpenAIRE</a>. Zenodo’s “standard award” field pulls award and funder data from the <a href=https://doi.org/10.5281/zenodo.10488385>OpenAIRE Graph dataset</a>, which uses ROR as one of several organization identifier schemes.</p><figure><img src=/img/blog/use-case-funders/ror-zenodo-standard.gif alt="Zenodo's award lookup pulls in both award and funder information from OpenAIRE"><figcaption><p>Zenodo’s award lookup pulls in both award and funder information from OpenAIRE. See the InvenioRDM documentation of <a href=https://inveniordm.docs.cern.ch/customize/vocabularies/funding/#awards-openaire>Awards (OpenAIRE)</a> for more information.</p></figcaption></figure><p>Users can also add a custom award – for instance, one that isn’t provided by OpenAIRE – and the custom award lookup in Zenodo is powered exclusively by ROR data to suggest funders in the award lookup funder field. Zenodo shows both the country code and the unique portion of the ROR identifier next to the name of the funder in the list of suggestions.</p><figure><img src=/img/blog/use-case-funders/ror-zenodo-custom.gif alt="Zenodo's custom award lookup uses ROR data to suggest funders."><figcaption><p>Zenodo’s custom award lookup uses ROR data to suggest funders.</p></figcaption></figure><p>Zenodo communities can also be hosted by funders, and these funders can also be identified by ROR IDs, as is the case for the GREI community managed by NIH.</p><figure><img src=/img/blog/use-case-funders/ror-zenodo-grei.png alt="The NIH-funded GREI initiative maintains a community on Zenodo in which the NIH is associated with its ROR ID."><figcaption><p>The NIH-funded GREI initiative maintains a community on Zenodo at <a href=https://zenodo.org/communities/grei/>https://zenodo.org/communities/grei/</a> in which the NIH is associated with its ROR ID.</p></figcaption></figure><p>Zenodo also exposes funder information in its API at <code>https://zenodo.org/api/funders</code>.</p><p>It’s important to reiterate that this functionality isn’t confined to Zenodo: the ROR-powered funder lookup is built into the system that runs Zenodo, <a href=https://inveniosoftware.org/products/rdm/>InvenioRDM</a>, so that anyone who uses InvenioRDM can also use ROR to identify funders. InvenioRDM’s excellent documentation explains in detail how award and funder lookups work in the system and gives more detail about the ROR-based data model for funders.</p><figure><img src=/img/blog/use-case-funders/ror-inveniordm.png alt="Documentation of the ROR-based funder model and award lookup in InvenioRDM, the open source system that runs Zenodo"><figcaption><p>Documentation of the ROR-based funder model and award lookup in InvenioRDM, the open source system that runs Zenodo, available at <a href=https://inveniordm.docs.cern.ch/customize/vocabularies/funding/>https://inveniordm.docs.cern.ch/customize/vocabularies/funding/</a>.</p></figcaption></figure><p><strong>InvenioRDM is the first new repository system to launch with ROR as the basis of its organizational data model</strong>, but it surely won’t be the last new repository system to do so.</p><h2 id=figshare-imports-ror-from-dimensions>Figshare imports ROR from Dimensions <a href=#figshare-imports-ror-from-dimensions><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" class="ha ha-link" width="16" height="16"><path d="M579.8 267.7c56.5-56.5 56.5-148 0-204.5-50-50-128.8-56.5-186.3-15.4l-1.6 1.1c-14.4 10.3-17.7 30.3-7.4 44.6s30.3 17.7 44.6 7.4l1.6-1.1c32.1-22.9 76-19.3 103.8 8.6 31.5 31.5 31.5 82.5.0 114L422.3 334.8c-31.5 31.5-82.5 31.5-114 0-27.9-27.9-31.5-71.8-8.6-103.8l1.1-1.6c10.3-14.4 6.9-34.4-7.4-44.6s-34.4-6.9-44.6 7.4l-1.1 1.6C206.5 251.2 213 330 263 380c56.5 56.5 148 56.5 204.5.0L579.8 267.7zM60.2 244.3c-56.5 56.5-56.5 148 0 204.5 50 50 128.8 56.5 186.3 15.4l1.6-1.1c14.4-10.3 17.7-30.3 7.4-44.6s-30.3-17.7-44.6-7.4l-1.6 1.1c-32.1 22.9-76 19.3-103.8-8.6C74 372 74 321 105.5 289.5L217.7 177.2c31.5-31.5 82.5-31.5 114 0 27.9 27.9 31.5 71.8 8.6 103.9l-1.1 1.6c-10.3 14.4-6.9 34.4 7.4 44.6s34.4 6.9 44.6-7.4l1.1-1.6C433.5 260.8 427 182 377 132c-56.5-56.5-148-56.5-204.5.0L60.2 244.3z"/></svg></a></h2><p>Both Figshare’s central repository at <a href=figshare.com>figshare.com</a> and Oxford University’s Figshare-powered institutional repository at <a href=https://portal.sds.ox.ac.uk/>https://portal.sds.ox.ac.uk/</a> (also available via <a href=https://oxford.figshare.com>https://oxford.figshare.com</a>) are contributing a significant number of ROR IDs as funder identifiers to DataCite metadata. Figshare, like Zenodo, asks the user to enter an award number or title and then pulls in funding information based on that award; in this case, Figshare pulls the grant title, grant ID, funder name, and ROR ID from <a href=https://www.dimensions.ai/>Dimensions</a> grant data and includes it in the Figshare item’s metadata record.</p><figure><img src=/img/blog/use-case-funders/ror-figshare.gif alt="Figshare's award lookup pulls data from Dimensions, which includes ROR IDs."><figcaption><p>Figshare’s award lookup pulls data from Dimensions, which includes ROR IDs.</p></figcaption></figure><p>ROR was <a href=https://ror.org/about/#launch-of-the-ror-mvr>originally seeded</a> with the GRID organization identifiers and data used by Dimensions, so there is a <a href=https://grid.ac/>close relationship between ROR IDs and GRID IDs</a>, and most ROR and GRID records are <a href=https://ror.readme.io/v2/docs/data-structure#external_ids>mapped to each other</a>. Dimensions’s support documentation <a href=https://dimensions.freshdesk.com/support/solutions/articles/23000025993-how-are-organizations-represented-in-dimensions->explains how ROR IDs are incorporated into its data</a>:</p><div class='callout beige'><div class=row><div class=col-md-12><span><p><strong>How are new ROR IDs added to Dimensions organization records?</strong></p><p>As part of every new organization data release we identify new ROR records, and examine each one of these for relevance to Dimensions, according to our inclusion criteria. Records that meet these criteria are added to Dimensions along with the relevant metadata.</p><p><strong>How is the ROR metadata maintained in Dimensions?</strong></p><p>We are also regularly checking for changes to ROR records which are already mapped to Dimensions organization records. When a mapped record changes in ROR, we examine if that change is also relevant for Dimensions and update relevant metadata as applicable.</p></span></div></div></div><p>The curation work that Dimensions performs means that organization information in Figshare, including ROR metadata for funding organizations, remains up to date.</p><h2 id=straininfo-uses-ror-for-funders>StrainInfo uses ROR for funders <a href=#straininfo-uses-ror-for-funders><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" class="ha ha-link" width="16" height="16"><path d="M579.8 267.7c56.5-56.5 56.5-148 0-204.5-50-50-128.8-56.5-186.3-15.4l-1.6 1.1c-14.4 10.3-17.7 30.3-7.4 44.6s30.3 17.7 44.6 7.4l1.6-1.1c32.1-22.9 76-19.3 103.8 8.6 31.5 31.5 31.5 82.5.0 114L422.3 334.8c-31.5 31.5-82.5 31.5-114 0-27.9-27.9-31.5-71.8-8.6-103.8l1.1-1.6c10.3-14.4 6.9-34.4-7.4-44.6s-34.4-6.9-44.6 7.4l-1.1 1.6C206.5 251.2 213 330 263 380c56.5 56.5 148 56.5 204.5.0L579.8 267.7zM60.2 244.3c-56.5 56.5-56.5 148 0 204.5 50 50 128.8 56.5 186.3 15.4l1.6-1.1c14.4-10.3 17.7-30.3 7.4-44.6s-30.3-17.7-44.6-7.4l-1.6 1.1c-32.1 22.9-76 19.3-103.8-8.6C74 372 74 321 105.5 289.5L217.7 177.2c31.5-31.5 82.5-31.5 114 0 27.9 27.9 31.5 71.8 8.6 103.9l-1.1 1.6c-10.3 14.4-6.9 34.4 7.4 44.6s34.4 6.9 44.6-7.4l1.1-1.6C433.5 260.8 427 182 377 132c-56.5-56.5-148-56.5-204.5.0L60.2 244.3z"/></svg></a></h2><p>The largest provider of ROR IDs in DataCite funding references is a repository called <a href=https://straininfo.dsmz.de/>StrainInfo</a>, which is “a service developed to provide a resolution of microbial strain identifiers by storing culture collection numbers, their relations, and culture-associated data.” StrainInfo is currently supported by the <a href=https://nfdi4microbiota.de/>NFDI4Microbiota</a> consortium, which is funded by the <a href="https://gepris.dfg.de/gepris/projekt/460129525?language=en">German Research Foundation (DFG)</a>, and is developed and maintained by <a href=https://www.dsmz.de/>Leibniz Institute DSMZ</a>.</p><figure><img src=/img/blog/use-case-funders/ror-straininfo.png alt="Example of a strain catalogued in StrainInfo. Note the DataCite DOI in the upper left."><figcaption><p>Example of a strain catalogued in StrainInfo. Note the DataCite DOI in the upper left.</p></figcaption></figure><p>StrainInfo indexes more than 290,000 microbial strains, each of which has its own DOI registered with DataCite, and each of which contains a funding reference in the metadata to award 460129525 issued by the German Research Foundation (DFG), whose ROR ID is <a href=https://ror.org/018mejw64>https://ror.org/018mejw64</a>.</p><figure class=blog-figure><img src=/img/blog/use-case-funders/ror-straininfo-datacite.png alt="DataCite metadata for https://doi.org/10.60712/SI-ID34969.2"><figcaption><p>DataCite metadata for <a href=https://doi.org/10.60712/SI-ID34969.2>https://doi.org/10.60712/SI-ID34969.2</a> available at <code>https://api.datacite.org/dois/10.60712/SI-ID34969.2</code>.</p></figcaption></figure><p>Thus, while StrainInfo is currently responsible for the largest number of DOI records with ROR IDs in the <code>funderIdentifier</code> field to DataCite, all 300,000+ of those records (including versions with updated data for several strains) reference a single funder with a single ROR ID. As Ted Habermann noted in his 2019 piece <a href=https://doi.org/10.59350/4tbaw-m9382>How Many RORs Do We Need?</a>, it’s good news for ROR adoption that “some DataCite members only need to know a small number of RORs,” since this can make implementation of ROR quite a bit easier.</p><h2 id=many-more-systems-use-ror-for-funders>Many more systems use ROR for funders <a href=#many-more-systems-use-ror-for-funders><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" class="ha ha-link" width="16" height="16"><path d="M579.8 267.7c56.5-56.5 56.5-148 0-204.5-50-50-128.8-56.5-186.3-15.4l-1.6 1.1c-14.4 10.3-17.7 30.3-7.4 44.6s30.3 17.7 44.6 7.4l1.6-1.1c32.1-22.9 76-19.3 103.8 8.6 31.5 31.5 31.5 82.5.0 114L422.3 334.8c-31.5 31.5-82.5 31.5-114 0-27.9-27.9-31.5-71.8-8.6-103.8l1.1-1.6c10.3-14.4 6.9-34.4-7.4-44.6s-34.4-6.9-44.6 7.4l-1.1 1.6C206.5 251.2 213 330 263 380c56.5 56.5 148 56.5 204.5.0L579.8 267.7zM60.2 244.3c-56.5 56.5-56.5 148 0 204.5 50 50 128.8 56.5 186.3 15.4l1.6-1.1c14.4-10.3 17.7-30.3 7.4-44.6s-30.3-17.7-44.6-7.4l-1.6 1.1c-32.1 22.9-76 19.3-103.8-8.6C74 372 74 321 105.5 289.5L217.7 177.2c31.5-31.5 82.5-31.5 114 0 27.9 27.9 31.5 71.8 8.6 103.9l-1.1 1.6c-10.3 14.4-6.9 34.4 7.4 44.6s34.4 6.9 44.6-7.4l1.1-1.6C433.5 260.8 427 182 377 132c-56.5-56.5-148-56.5-204.5.0L60.2 244.3z"/></svg></a></h2><p>The systems reviewed here are by no means the only ones using ROR IDs to identify funders. Here’s an alphabetical list of additional systems that are currently using ROR IDs for funder identification:</p><ul><li><a href=https://www.chorusaccess.org>CHORUS Dashboard and Reporting Services</a></li><li><a href=https://chronoshub.io/>ChronosHub Open Access Management Platform</a></li><li><a href=https://www.osti.gov/award-doi-service/>DOE Award DOI Service</a></li><li><a href=https://wiki.lyrasis.org/display/DSDOC8x/DSpace+8.x+Documentation>DSpace 8</a></li><li><a href=https://wiki.lyrasis.org/display/DSPACECRIS>DSpace-CRIS</a></li><li><a href=https://fairsharing.org>FAIRsharing</a></li><li><a href=https://gold.jgi.doe.gov/index>Genomes OnLine Database (GOLD)</a></li><li><a href=https://japanlinkcenter.org/>Japan Link Center (JALC)</a></li><li><a href=https://www.datasalon.com/web/index.htm>MasterVision and PaperStack by DataSalon</a></li><li><a href=https://oa.report>OA.Report</a></li><li><a href=https://openalex.org>OpenAlex</a></li><li><a href=https://orcid.org>ORCID</a></li><li><a href=https://proposalcentral.com/>ProposalCentral by Altum</a></li><li><a href=https://radar.products.fiz-karlsruhe.de/en/radarabout/ueber-radar>RADAR</a></li><li><a href=https://www.sherpa.ac.uk/>Sherpa Services</a></li><li><a href=https://vivli.org>Vivli Center for Global Clinical Research Data</a></li></ul><p>See the <a href=https://bit.ly/ror-integrations>full list of ROR Integrations</a> to see more systems that are using or planning to use ROR for all kinds of purposes beyond funder identification – author affiliations, Open Access deal management, publisher identification, internal statistics, and more. If you’re managing a system that uses ROR for funder identification and you don’t see it listed here, <a href=https://bit.ly/ror-integration-form>let us know</a>!</p><h2 id=whats-next>What’s next <a href=#whats-next><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" class="ha ha-link" width="16" height="16"><path d="M579.8 267.7c56.5-56.5 56.5-148 0-204.5-50-50-128.8-56.5-186.3-15.4l-1.6 1.1c-14.4 10.3-17.7 30.3-7.4 44.6s30.3 17.7 44.6 7.4l1.6-1.1c32.1-22.9 76-19.3 103.8 8.6 31.5 31.5 31.5 82.5.0 114L422.3 334.8c-31.5 31.5-82.5 31.5-114 0-27.9-27.9-31.5-71.8-8.6-103.8l1.1-1.6c10.3-14.4 6.9-34.4-7.4-44.6s-34.4-6.9-44.6 7.4l-1.1 1.6C206.5 251.2 213 330 263 380c56.5 56.5 148 56.5 204.5.0L579.8 267.7zM60.2 244.3c-56.5 56.5-56.5 148 0 204.5 50 50 128.8 56.5 186.3 15.4l1.6-1.1c14.4-10.3 17.7-30.3 7.4-44.6s-30.3-17.7-44.6-7.4l-1.6 1.1c-32.1 22.9-76 19.3-103.8-8.6C74 372 74 321 105.5 289.5L217.7 177.2c31.5-31.5 82.5-31.5 114 0 27.9 27.9 31.5 71.8 8.6 103.9l-1.1 1.6c-10.3 14.4-6.9 34.4 7.4 44.6s34.4 6.9 44.6-7.4l1.1-1.6C433.5 260.8 427 182 377 132c-56.5-56.5-148-56.5-204.5.0L60.2 244.3z"/></svg></a></h2><p><strong>More and more systems will be using ROR to identify funders</strong> in the coming months and years as the deprecation of the Open Funder Registry nears. Crossref <a href=https://www.crossref.org/blog/roring-ahead-using-ror-in-place-of-the-open-funder-registry/>has been working hard</a> on building support for publishers to deposit ROR IDs as funder identifiers, and this capacity will be released before the end of the year. Moreover, as more and more funders register DOIs for awards using <a href=https://support.datacite.org/docs/registering-datacite-dois-for-awards>DataCite</a> or <a href=https://www.crossref.org/documentation/research-nexus/grants/>Crossref</a>, they will undoubtedly begin by using ROR IDs to identify their own organization as well as other funding institutions.</p><p>“<strong>Open funding metadata is arguably the next big thing</strong>,” <a href=https://www.crossref.org/blog/open-funding-metadata-community-workshop-report/>avers a recap of a funding metadata workshop</a> convened by Crossref last year, for many reasons: “meta-researchers need this information in order to analyze research on research, editors are concerned with research integrity, including funding trends, and funders themselves need to track the reach and return of their support.” This year alone, several lively discussions of how to improve funding metadata through the use of persistent identifiers in published research have been held, including:</p><ul><li>ROR Annual Meeting, <a href=https://ror.org/events/2024-01-31-why-we-all-need-good-funding-metadata/>Why We All Need Good Funding Metadata</a>, January 2024</li><li>Altum webinar, <a href=https://pages.altum.com/persistent-identifier-webinar>Advancing Research with Persistent Identifier (PID) Innovations</a>, February 2024</li><li>CHORUS Forum, <a href=https://www.chorusaccess.org/events/chorus-forum-navigating-the-future-of-persistent-identifiers-pids-in-scholarly-publishing-challenges-risks-and-opportunities/>Navigating the Future of PIDs in Scholarly Publishing</a>, May 2024</li></ul><p>The other commonly mentioned “next big thing,” AI, or more precisely machine learning, also has a bearing on funding metadata: Crossref and ROR are collaborating on an exciting project to build and evaluate robust, large-scale <a href=https://ror.org/tags/matching>matching</a> strategies that can reliably connect tens of thousands of funder names in Crossref metadata to ROR IDs. Nevertheless, because any such automated post-processing of metadata is bound to have some errors, it’s important that good funding metadata be created and reviewed by humans as far upstream as possible, ideally during the manuscript submission process or publishing production process.</p><p><strong>So, in short, if you’re in charge of a scholarly publishing system or workflow that’s using the Open Funder Registry or one that isn’t using funder identifiers at all, you should be thinking about using ROR.</strong> We’re here to help!</p><ul><li>Are you using the Open Funder Registry? Start by consulting our <a href=https://ror.readme.io/docs/funder-registry>Funder Registry Transition Guide</a>.</li><li>Are you new to persistent identifiers and/or ROR? Start by browsing through our <a href=https://ror.readme.io>technical documentation</a>.</li></ul><p>ROR is a responsive, open, community-led endeavor, and we’re happy to work with you to integrate ROR IDs into your scholarly publication metadata.</p><div class=callout><div class=row><div class=col-md-2 style=text-align:center><i class='fa-solid fa-envelope'></i></div><div class=col-md-10><span>Still have questions? Write to us at <a href=mailto:support@ror.org>support@ror.org</a>.</span></div></div></div></div></div><div class=col-md-3><div class="card card-plain"><h3 class=card-title><a href=/feed.xml><i class="fa-solid fa-rss" aria-hidden=true></i> <span>Feed</span></a></h3><div class="card card-plain taxonomy"><div class=card-body><h3 class=card-title>Categories</h3><ul class="nav nav-pills nav-stacked categories"><li><a href=https://ror.org/categories/adoption-news><span>Adoption News (8)</span></a></li><li><a href=https://ror.org/categories/case-studies><span>Case Studies (13)</span></a></li><li><a href=https://ror.org/categories/event-recaps><span>Event Recaps (8)</span></a></li><li><a href=https://ror.org/categories/explainers><span>Explainers (13)</span></a></li><li><a href=https://ror.org/categories/general-updates><span>General Updates (14)</span></a></li><li><a href=https://ror.org/categories/requests><span>Requests (6)</span></a></li><li><a href=https://ror.org/categories/team-updates><span>Team Updates (7)</span></a></li><li><a href=https://ror.org/categories/technical-news><span>Technical News (7)</span></a></li><li><a href=https://ror.org/categories/use-cases><span>Use Cases (1)</span></a></li><li><a href=https://ror.org/categories/year-in-review><span>Year in Review (5)</span></a></li></ul></div></div><div class="card card-plain taxonomy"><div class=card-body><h3 class=card-title>Archives</h3><ul class="nav nav-pills nav-stacked"><li><a href=/archives/2025>2025</a> <span class=blog-count>(2)</span></li><li><a href=/archives/2024>2024</a> <span class=blog-count>(19)</span></li><li><a href=/archives/2023>2023</a> <span class=blog-count>(20)</span></li><li><a href=/archives/2022>2022</a> <span class=blog-count>(13)</span></li><li><a href=/archives/2021>2021</a> <span class=blog-count>(9)</span></li><li><a href=/archives/2020>2020</a> <span class=blog-count>(7)</span></li><li><a href=/archives/2019>2019</a> <span class=blog-count>(10)</span></li><li><a href=/archives/2018>2018</a> <span class=blog-count>(2)</span></li></ul></div></div><div class="card card-plain taxonomy"><div class=card-body><h3 class=card-title>Tags</h3><ul class=list-unstyled><li><a href=https://ror.org/tags/adoption><i class="fa fa-tags"></i> <span>adoption</span></a></li><li><a href=https://ror.org/tags/annual-meeting><i class="fa fa-tags"></i> <span>annual-meeting</span></a></li><li><a href=https://ror.org/tags/api><i class="fa fa-tags"></i> <span>api</span></a></li><li><a href=https://ror.org/tags/aps><i class="fa fa-tags"></i> <span>aps</span></a></li><li><a href=https://ror.org/tags/caltechdata><i class="fa fa-tags"></i> <span>caltechdata</span></a></li><li><a href=https://ror.org/tags/clarivate><i class="fa fa-tags"></i> <span>clarivate</span></a></li><li><a href=https://ror.org/tags/clear-skies><i class="fa fa-tags"></i> <span>clear-skies</span></a></li><li><a href=https://ror.org/tags/coki><i class="fa fa-tags"></i> <span>coki</span></a></li><li><a href=https://ror.org/tags/communication><i class="fa fa-tags"></i> <span>communication</span></a></li><li><a href=https://ror.org/tags/community><i class="fa fa-tags"></i> <span>community</span></a></li><li><a href=https://ror.org/tags/cross-post><i class="fa fa-tags"></i> <span>cross-post</span></a></li><li><a href=https://ror.org/tags/crossref><i class="fa fa-tags"></i> <span>crossref</span></a></li><li><a href=https://ror.org/tags/curation><i class="fa fa-tags"></i> <span>curation</span></a></li><li><a href=https://ror.org/tags/data><i class="fa fa-tags"></i> <span>data</span></a></li><li><a href=https://ror.org/tags/datacite><i class="fa fa-tags"></i> <span>datacite</span></a></li><li><a href=https://ror.org/tags/datasalon><i class="fa fa-tags"></i> <span>datasalon</span></a></li><li><a href=https://ror.org/tags/development><i class="fa fa-tags"></i> <span>development</span></a></li><li><a href=https://ror.org/tags/dryad><i class="fa fa-tags"></i> <span>dryad</span></a></li><li><a href=https://ror.org/tags/europepmc><i class="fa fa-tags"></i> <span>europepmc</span></a></li><li><a href=https://ror.org/tags/facilities><i class="fa fa-tags"></i> <span>facilities</span></a></li><li><a href=https://ror.org/tags/fairsharing><i class="fa fa-tags"></i> <span>fairsharing</span></a></li><li><a href=https://ror.org/tags/feedback><i class="fa fa-tags"></i> <span>feedback</span></a></li><li><a href=https://ror.org/tags/figshare><i class="fa fa-tags"></i> <span>figshare</span></a></li><li><a href=https://ror.org/tags/funders><i class="fa fa-tags"></i> <span>funders</span></a></li><li><a href=https://ror.org/tags/governance><i class="fa fa-tags"></i> <span>governance</span></a></li><li><a href=https://ror.org/tags/grei><i class="fa fa-tags"></i> <span>grei</span></a></li><li><a href=https://ror.org/tags/grid><i class="fa fa-tags"></i> <span>grid</span></a></li><li><a href=https://ror.org/tags/guest-post><i class="fa fa-tags"></i> <span>guest-post</span></a></li><li><a href=https://ror.org/tags/hierarchy><i class="fa fa-tags"></i> <span>hierarchy</span></a></li><li><a href=https://ror.org/tags/implementation><i class="fa fa-tags"></i> <span>implementation</span></a></li><li><a href=https://ror.org/tags/integrations><i class="fa fa-tags"></i> <span>integrations</span></a></li><li><a href=https://ror.org/tags/interviews><i class="fa fa-tags"></i> <span>interviews</span></a></li><li><a href=https://ror.org/tags/inveniordm><i class="fa fa-tags"></i> <span>inveniordm</span></a></li><li><a href=https://ror.org/tags/jobs><i class="fa fa-tags"></i> <span>jobs</span></a></li><li><a href=https://ror.org/tags/latin-america><i class="fa fa-tags"></i> <span>latin-america</span></a></li><li><a href=https://ror.org/tags/machine-learning><i class="fa fa-tags"></i> <span>machine-learning</span></a></li><li><a href=https://ror.org/tags/matching><i class="fa fa-tags"></i> <span>matching</span></a></li><li><a href=https://ror.org/tags/metadata><i class="fa fa-tags"></i> <span>metadata</span></a></li><li><a href=https://ror.org/tags/metadata-game-changers><i class="fa fa-tags"></i> <span>metadata-game-changers</span></a></li><li><a href=https://ror.org/tags/mvr><i class="fa fa-tags"></i> <span>mvr</span></a></li><li><a href=https://ror.org/tags/open-access><i class="fa fa-tags"></i> <span>open-access</span></a></li><li><a href=https://ror.org/tags/open-infrastructure><i class="fa fa-tags"></i> <span>open-infrastructure</span></a></li><li><a href=https://ror.org/tags/openalex><i class="fa fa-tags"></i> <span>openalex</span></a></li><li><a href=https://ror.org/tags/optica><i class="fa fa-tags"></i> <span>optica</span></a></li><li><a href=https://ror.org/tags/orcid><i class="fa fa-tags"></i> <span>orcid</span></a></li><li><a href=https://ror.org/tags/osf><i class="fa fa-tags"></i> <span>osf</span></a></li><li><a href=https://ror.org/tags/persistent-identifiers><i class="fa fa-tags"></i> <span>persistent-identifiers</span></a></li><li><a href=https://ror.org/tags/pidapalooza><i class="fa fa-tags"></i> <span>pidapalooza</span></a></li><li><a href=https://ror.org/tags/pids><i class="fa fa-tags"></i> <span>pids</span></a></li><li><a href=https://ror.org/tags/prototype><i class="fa fa-tags"></i> <span>prototype</span></a></li><li><a href=https://ror.org/tags/publishers><i class="fa fa-tags"></i> <span>publishers</span></a></li><li><a href=https://ror.org/tags/publishing><i class="fa fa-tags"></i> <span>publishing</span></a></li><li><a href=https://ror.org/tags/registry><i class="fa fa-tags"></i> <span>registry</span></a></li><li><a href=https://ror.org/tags/research-integrity><i class="fa fa-tags"></i> <span>research-integrity</span></a></li><li><a href=https://ror.org/tags/researchequals><i class="fa fa-tags"></i> <span>researchequals</span></a></li><li><a href=https://ror.org/tags/resources><i class="fa fa-tags"></i> <span>resources</span></a></li><li><a href=https://ror.org/tags/rockefeller-university-press><i class="fa fa-tags"></i> <span>rockefeller-university-press</span></a></li><li><a href=https://ror.org/tags/rrid><i class="fa fa-tags"></i> <span>rrid</span></a></li><li><a href=https://ror.org/tags/schema><i class="fa fa-tags"></i> <span>schema</span></a></li><li><a href=https://ror.org/tags/scholastica><i class="fa fa-tags"></i> <span>scholastica</span></a></li><li><a href=https://ror.org/tags/silverchair><i class="fa fa-tags"></i> <span>silverchair</span></a></li><li><a href=https://ror.org/tags/steering-group><i class="fa fa-tags"></i> <span>steering-group</span></a></li><li><a href=https://ror.org/tags/straininfo><i class="fa fa-tags"></i> <span>straininfo</span></a></li><li><a href=https://ror.org/tags/sustainability><i class="fa fa-tags"></i> <span>sustainability</span></a></li><li><a href=https://ror.org/tags/team><i class="fa fa-tags"></i> <span>team</span></a></li><li><a href=https://ror.org/tags/web-of-science><i class="fa fa-tags"></i> <span>web-of-science</span></a></li><li><a href=https://ror.org/tags/working-group><i class="fa fa-tags"></i> <span>working-group</span></a></li><li><a href=https://ror.org/tags/zenodo><i class="fa fa-tags"></i> <span>zenodo</span></a></li></ul></div></div></div></div></div></section></div><section class="section section-subscribe" data-background-color=green><div class=container><div class=row><div class="col-md-6 text-center"><div class=contact-shortcode><div><h2>Subscribe to the ROR newsletter</h2><a target=_blank class="btn btn-sm btn-round red" rel=noopener href=http://eepurl.com/gjkT9H>Subscribe</a></div></div></div><div class="col-md-6 text-center"><div><h2>Suggest an addition or update to ROR</h2><a target=_blank class="btn btn-sm btn-round red" rel=noopener href=https://curation-request.ror.org>Suggest</a></div></div></div></div></section><section class="section section-socials" data-background-color=light-grey><div class=container><div class="row justify-content-between no-gutters ml-auto mr-auto text-center"><div class="col-sm-6 col-md"><a href=mailto:info@ror.org><i class="fa-solid fa-envelope"></i> <span>Email</span></a></div><div class="col-sm-6 col-md"><a href=https://www.linkedin.com/company/ror-research-organization-registry/><i class="fa-brands fa-linkedin"></i> <span>LinkedIn</span></a></div><div class="col-sm-6 col-md"><a rel=me href=https://mastodon.social/@ResearchOrgs><i class="fa-brands fa-mastodon"></i> <span>Mastodon</span></a></div><div class="col-sm-6 col-md"><a href=https://bsky.app/profile/researchorgs.bsky.social><i class="fa-brands fa-bluesky"></i> <span>Bluesky</span></a></div><div class="col-sm-6 col-md"><a href=https://www.youtube.com/channel/UCQBOpOpW-JEKoVCUlmCK1Eg><i class="fa-brands fa-youtube"></i> <span>YouTube</span></a></div><div class="col-sm-6 col-md"><a href=https://github.com/ror-community><i class="fa-brands fa-github"></i> <span>GitHub</span></a></div><div class="col-sm-6 col-md"><a href=https://ror.readme.io/><i class="fa-solid fa-book"></i> <span>Documentation</span></a></div></div></div></section><footer class="section footer" data-background-color=black><div class=container-fluid><div class=row><div class="col-md-12 ml-auto mr-auto text-center"><p class=text-white id=copyright>All ROR IDs and metadata are provided under the <a target=_blank rel=noopener href=https://creativecommons.org/publicdomain/zero/1.0//>Creative Commons CC0 1.0 Universal Public Domain Dedication.</a><br>All other content of this site is licensed under the <a target=_blank rel=noopener href=https://creativecommons.org/licenses/by/4.0/>Creative Commons Attribution 4.0 International License.</a><br>Read the <a href=/privacy/>ROR Privacy Policy</a> and <a href=/terms-of-use/>Terms of Use.</a></p></div></div></div></footer><script src=https://code.jquery.com/jquery-3.4.1.min.js integrity="sha256-CSXorXvZcTkaix6Yvo6HppcZGetbYMGWSFlBw8HfCJo=" crossorigin=anonymous></script> <script src=https://cdn.plyr.io/2.0.13/plyr.js></script> <script>plyr.setup()</script><script src=//cdnjs.cloudflare.com/ajax/libs/jquery-cookie/1.4.1/jquery.cookie.min.js></script> <script src=//cdnjs.cloudflare.com/ajax/libs/waypoints/4.0.1/jquery.waypoints.min.js></script> <script src=//cdnjs.cloudflare.com/ajax/libs/Counter-Up/1.0/jquery.counterup.min.js></script> <script src=//cdnjs.cloudflare.com/ajax/libs/jquery-parallax/1.1.3/jquery-parallax.js></script> <script src=https://ror.org/js/front.js></script> <script src=https://ror.org/js/owl.carousel.min.js></script></body></html>