<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Affiliations on Crossref</title><link>https://www-crossref-org.pluma.sjfc.edu/categories/affiliations/</link><description>Recent content in Affiliations on Crossref</description><generator>Hugo 0.139.4</generator><language>en-us</language><managingEditor>support@crossref.org (Crossref/Cazinc/Benoît Benedetti)</managingEditor><webMaster>support@crossref.org (Crossref/Cazinc/Benoît Benedetti)</webMaster><lastBuildDate>Thu, 22 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www-crossref-org.pluma.sjfc.edu/categories/affiliations/" rel="self" type="application/rss+xml"/><item><title>Insights from a roundtable on author affiliation metadata</title><link>https://www-crossref-org.pluma.sjfc.edu/blog/insights-from-a-roundtable-on-author-affiliation-metadata/</link><pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate><author>Amanda French</author><guid>https://www-crossref-org.pluma.sjfc.edu/blog/insights-from-a-roundtable-on-author-affiliation-metadata/</guid><description>&lt;p>It’s been said that Americans are unusual in tending to ask “Where do you work?” as an initial question upon introduction to a new acquaintance, indicating a perhaps unhealthy preoccupation with work as identity. But in the context of published research, “What is this author&amp;rsquo;s affiliation?” is a question of global importance that goes beyond just wanting to know the name &amp;ndash; and perhaps prestige level &amp;ndash; of the place a researcher works.&lt;/p>
&lt;p>When collected, used, and analyzed at scale, data about author affiliations can provide intriguing insights about international collaboration trends, signal trust and lack of trust in particular research institutions, generate business intelligence for publishers, help universities track the work their researchers do, help funders demonstrate the impact of their funding, and much more.&lt;/p>
&lt;p>In November we partnered with &lt;a href="https://oaswitchboard.org/" target="_blank">OA Switchboard&lt;/a> to organize a roundtable on author affiliation metadata for the Crossref community, service and infrastructure providers, production vendors, data scientists, researchers, and librarians. We aimed to bring together scholarly information professionals with many diverse perspectives; ultimately, participants from more than 40 organizations joined the roundtable to share their experiences and their thoughts.&lt;/p>
&lt;p>In focusing on a single type of metadata, we hoped to focus our discussions, as well. Similarly, in October the Barcelona Declaration on Open Research Information organized &lt;a href="https://barcelona-declaration.org/news/20251023_community_roundtable/" target="_blank">a roundtable on &amp;ldquo;Moving Funding Metadata Forward&amp;rdquo;&lt;/a> in which it became clear that “improving the quality and coverage of funding metadata was on the agenda of many organisations and there was a strong interest in collaborating on practical next steps.”&lt;/p>
&lt;p>While many of the issues and solutions discussed at both roundtables are similar, in the course of the author affiliation metadata roundtable we identified some unique challenges as well as benefits related to this particular flavor of information. In this blog post, I’ll share these insights.&lt;/p>
&lt;h2 id="insights-from-presenters">Insights from presenters&lt;/h2>
&lt;p>I opened the roundtable with a brief introduction and a working definition of affiliation metadata: names and/or identifiers such as &lt;a href="https://www-crossref-org.pluma.sjfc.edu/services/ror/" target="_blank">Research Organization Registry (ROR)&lt;/a> IDs for organizations where research was conducted or with which authors and contributors are associated, usually officially, as in their place of employment.&lt;/p>
&lt;p>Next, to create a shared context for discussion, we heard four presentations on the current state of author affiliation metadata, its importance, and Crossref’s ongoing initiative to enhance it automatically.&lt;/p>
&lt;p>Nees Jan van Eck of Leiden University’s &lt;a href="https://www.universiteitleiden.nl/en/social-behavioural-sciences/cwts" target="_blank">Center for Science and Technology Studies (CWTS)&lt;/a> shared observations on the state of author affiliations from a preprint titled “&lt;a href="https://doi-org.pluma.sjfc.edu/10.31222/osf.io/smxe5_v2" target="_blank">Crossref as a source of open bibliographic metadata&lt;/a>” that presents the findings of an analysis performed annually since 2021. Nees’s key points:&lt;/p>
&lt;ul>
&lt;li>Crossref is a foundational data source for bibliographic metadata.&lt;/li>
&lt;li>Affiliation metadata is available for only 1 out of 3 journal articles in Crossref for the period 2023-2024.&lt;/li>
&lt;li>There is considerable variation in the extent to which Crossref members deposit affiliation metadata.&lt;/li>
&lt;li>Downstream sources try to fill gaps using suboptimal approaches, leading to missing, inaccurate, and inconsistent linking of publications to institutions.&lt;/li>
&lt;li>Publications lacking affiliation metadata in Crossref are less visible in bibliometric applications, analyses, studies, and tools (such as the &lt;a href="https://open.leidenranking.com/" target="_blank">open edition of the Leiden Ranking&lt;/a> of over 2800 universities).&lt;/li>
&lt;/ul>
&lt;p>&lt;figure>&lt;img src="https://www-crossref-org.pluma.sjfc.edu/images/blog/2026/aff-roundtable-01.png"
alt="Crossref as a source of open bibliographic metadata.">
&lt;/figure>
&lt;br />&lt;/p>
&lt;p>Next, Yvonne Campfens of OA Switchboard reiterated the desirability of the Crossref community providing complete and accurate author affiliation metadata at the source. Yvonne called upon publishers to “Integrate metadata creation in your systems and workflows before publication and relay it throughout the editorial, production, and publication processes.”&lt;/p>
&lt;p>Yvonne pointed out that in the context of managing Open Access agreements, publishers ought to keep in mind that providing good affiliation metadata improves customer satisfaction, since institutions and consortia need to have that information in order to connect research to the correct organization. In closing, Yvonne featured best practices from &lt;a href="https://www.oaswitchboard.org/dqc-publisherbestpractices" target="_blank">OA Switchboard’s Data Quality Challenge&lt;/a>:&lt;/p>
&lt;ul>
&lt;li>eLife captures affiliations at submissions with “author select,” ensuring that ROR IDs are introduced early and verified before publication, coupled with a quality assurance process during proofing. (See also our piece on &lt;a href="https://doi-org.pluma.sjfc.edu/10.64000/3gcdf-23s29" target="_blank">Metadata Excellence Award winner eLife&lt;/a>.)&lt;/li>
&lt;li>EMS Press captures metadata via manuscript extraction as early as at submission, building on globally valid identifiers whenever possible (ROR IDs, DOIs, ORCIDs).&lt;/li>
&lt;li>Pensoft Publishers uses AI-assisted metadata extraction with human review and in-house metadata validation.&lt;/li>
&lt;li>Beilstein-Institut performs post-acceptance metadata quality assurance through automation and expert review.&lt;/li>
&lt;li>The Royal Society embeds metadata in OA payment and agreement workflows.&lt;/li>
&lt;li>American Chemical Society (ACS) has a multi-method persistent identifier matching strategy with near-complete coverage.&lt;/li>
&lt;li>The American Society for Microbiology (ASM) combines AI-powered submission tools with editorial oversight via expert manual checks. (See also our piece on &lt;a href="https://doi-org.pluma.sjfc.edu/10.64000/xxwy3-xhf38" target="_blank">Metadata Excellence Award winner ASM&lt;/a>.)&lt;/li>
&lt;li>Rockefeller University Press (RUP) maintains ROR IDs across the full publishing workflow with “author select” at submission through metadata deposits upon publication. (See also the &lt;a href="https://doi-org.pluma.sjfc.edu/10.71938/t63t-g186" target="_blank">ROR case study on RUP&lt;/a>.)&lt;/li>
&lt;/ul>
&lt;p>&lt;figure>&lt;img src="https://www-crossref-org.pluma.sjfc.edu/images/blog/2026/aff-roundtable-02.png"
alt="Having great metadata improves your operational excellence.">
&lt;/figure>
&lt;br />&lt;/p>
&lt;p>Adam Day of &lt;a href="https://clear-skies.co.uk/" target="_blank">Clear Skies Ltd&lt;/a> began his talk by wryly framing the first and second rules of data science as contradictory: “Never fix data: always use sources that produce high-quality data in the first place,” but also “Get good at fixing data, because you will have to.” Adam went on to demonstrate the central role author affiliation metadata plays in research integrity investigations, displaying anonymized data for institutions with a high number of alerts. In conclusion, Adam reiterated the importance of author affiliation metadata to research integrity efforts:&lt;/p>
&lt;ul>
&lt;li>Data analysis is critical to research integrity.&lt;/li>
&lt;li>Quality data helps enormously by giving oversight, saving time, and assisting investigations.&lt;/li>
&lt;/ul>
&lt;p>&lt;figure>&lt;img src="https://www-crossref-org.pluma.sjfc.edu/images/blog/2026/aff-roundtable-03.png"
alt="Value comes from data.">
&lt;/figure>
&lt;br />&lt;/p>
&lt;p>Lastly, our own Director of Technology &lt;a href="https://www-crossref-org.pluma.sjfc.edu/people/dominika-tkaczyk" target="_blank">Dominika Tkaczyk&lt;/a> gave an account of our plans to enrich author affiliation metadata by matching organization name text strings to &lt;a href="https://ror.org" target="_blank">ROR IDs&lt;/a> as part of our &lt;a href="https://www-crossref-org.pluma.sjfc.edu/community/special-programs/metadata-matching/" target="_blank">metadata matching&lt;/a> initiative. A strategy for performing such matching has already been developed and tested and an &lt;a href="https://doi-org.pluma.sjfc.edu/10.5281/zenodo.15254993" target="_blank">open dataset of results made available&lt;/a>. Tests on a set of 3,000 affiliations sampled from our metadata show that the strategy can be expected to match 95 million ROR IDs to organization names with 97.35% precision, an astronomical increase over the less than 1 million ROR IDs deposited in Crossref records to date.&lt;/p>
&lt;p>Dominika concluded the presentation portion of the session by reiterating that our planned enrichment of author affiliation metadata&lt;/p>
&lt;ul>
&lt;li>Will use flexible and transparent matching strategies (and &lt;a href="https://gitlab.com/crossref/labs/marple/-/tree/main/strategies_available/affiliation_single_search" target="_blank">open code&lt;/a>),&lt;/li>
&lt;li>Will welcome community participation in developing new strategies, and&lt;/li>
&lt;li>Will be available in the REST API.&lt;/li>
&lt;/ul>
&lt;p>&lt;figure>&lt;img src="https://www-crossref-org.pluma.sjfc.edu/images/blog/2026/aff-roundtable-04.png"
alt="Matching affiliation strings to ROR IDs.">
&lt;/figure>
&lt;br />&lt;/p>
&lt;p>Automatic matching of organization names to ROR IDs in author affiliations cannot solve the problem of missing organization names, of course, but it represents a huge leap forward in addressing metadata quality issues.&lt;/p>
&lt;p>All of our speakers&amp;rsquo; presentations are available on Zenodo at &lt;a href="https://doi-org.pluma.sjfc.edu/10.13003/661591chqlyw" target="_blank">https://doi-org.pluma.sjfc.edu/10.13003/661591chqlyw&lt;/a>.&lt;/p>
&lt;h2 id="insights-into-challenges">Insights into challenges&lt;/h2>
&lt;p>In the next stage of the event, participants broke into six breakout groups to identify factors contributing to incomplete or inaccurate affiliation metadata. Participants were pre-assigned to groups randomly by role to ensure a variety of perspectives in every discussion.&lt;/p>
&lt;p>At least two participants, it should be noted, pointed out that it would be helpful to agree on a definition of “complete” and “accurate” affiliation metadata, which in itself is a challenge, and one we did not address in this roundtable. For instance, practices most recently have trended away from defining a complete author affiliation in open metadata as including an institutional address, although many internal databases might include such information separately.&lt;/p>
&lt;p>Even without such definitions, however, all six groups were able to identify several general areas for attention, and one participant provided a particularly helpful categorization of these areas that is largely reused here.&lt;/p>
&lt;h3 id="inherent-data-complexity">Inherent data complexity&lt;/h3>
&lt;ul>
&lt;li>Research organizations have names in different languages, abbreviations, and many other name variants.&lt;/li>
&lt;li>Research organizations have frequent name changes, mergers, and rebranding.&lt;/li>
&lt;li>Research organizations have different degrees, levels, and complexity of hierarchical granularity, and authors, publishers, and software systems are often misaligned as to which level in an organization&amp;rsquo;s structure is appropriate to use in a particular instance.&lt;/li>
&lt;li>Research organizations often lack official policies on how affiliations should be written, leading to hundreds of variations for a single institution.&lt;/li>
&lt;/ul>
&lt;h3 id="author-related-issues">Author-related issues&lt;/h3>
&lt;ul>
&lt;li>Corresponding authors often submit information for all co-authors, which can lead to inaccuracies.&lt;/li>
&lt;li>Many authors have multiple profiles across multiple submission systems, which can introduce errors.&lt;/li>
&lt;li>Authors may have “octopus affiliations,” claiming affiliations with many institutions that are difficult to verify.&lt;/li>
&lt;li>Authors may fail to update affiliations when changing institutions between manuscript acceptance and publication.&lt;/li>
&lt;li>Authors may demonstrate &amp;ldquo;apathy&amp;rdquo; when repeatedly filling out submission forms, sometimes providing incomplete, inconsistent, or incorrect information.&lt;/li>
&lt;li>On occasion, authors might even provide false or purchased affiliations, which of course is a significant research integrity concern.&lt;/li>
&lt;/ul>
&lt;h3 id="technical-barriers">Technical barriers&lt;/h3>
&lt;ul>
&lt;li>Many manuscript tracking and peer review systems, especially legacy systems, lack structured fields for affiliations or don&amp;rsquo;t support open organization identifiers like ROR.&lt;/li>
&lt;li>Some systems limit authors to a single affiliation, despite many researchers having multiple institutional connections.&lt;/li>
&lt;li>Some systems only collect affiliation information for the corresponding author.&lt;/li>
&lt;li>Some systems link affiliations to user accounts instead of to publications.&lt;/li>
&lt;li>Different systems use competing identifier registries, including proprietary identifier registries, creating interoperability challenges.&lt;/li>
&lt;/ul>
&lt;h3 id="publisher-practices">Publisher practices&lt;/h3>
&lt;ul>
&lt;li>Even when publishers improve current metadata collection practices, historical data correction is resource-intensive and often not prioritized.&lt;/li>
&lt;li>Publishers collect affiliation information at submission but don’t ensure that it is maintained throughout all stages of the publication process and deposited in metadata.&lt;/li>
&lt;li>Some publishers are unaware of the importance of author affiliation metadata or do not prioritize its improvement.&lt;/li>
&lt;li>Some publishers deliberately choose not to deposit affiliation metadata to Crossref, viewing it as value-added information they&amp;rsquo;ve invested in curating.&lt;/li>
&lt;/ul>
&lt;h2 id="insights-into-solutions">Insights into solutions&lt;/h2>
&lt;p>Naturally, we didn’t rest at identifying challenges: after a break, we gathered in the same groups to brainstorm approaches to improving author affiliation metadata.&lt;/p>
&lt;h3 id="adopt-collective-approaches">Adopt collective approaches&lt;/h3>
&lt;ul>
&lt;li>Collective action, where corrections and improvements made by various stakeholders flow back into shared systems, has historically worked for proprietary systems and could be even more powerful with open infrastructure.&lt;/li>
&lt;li>Since those who do not provide metadata “upstream” will inevitably have it provided for them “downstream” by multiple separate entities using multifarious methods, provenance metadata indicating who asserted author affiliations and how (whether automatically or with the author’s or editor’s input) would help metadata users assess trust levels.&lt;/li>
&lt;/ul>
&lt;h3 id="engage-authors-and-institutions">Engage authors and institutions&lt;/h3>
&lt;ul>
&lt;li>Reach out to authors and institutions to educate them on the need for more consistent affiliation reporting, especially in terms of language, name format, and degree of hierarchical granularity.&lt;/li>
&lt;li>Demonstrate the benefit to institutions of maintaining accurate records in registries like ROR, including abbreviations and name variants.&lt;/li>
&lt;li>Publishers and/or software systems should allow authors to review (though not necessarily edit) affiliation information during the proofing process to verify accuracy. Authors should not, however, need to know, see, or use ROR IDs.&lt;/li>
&lt;/ul>
&lt;h3 id="improve-the-tech">Improve the tech&lt;/h3>
&lt;ul>
&lt;li>Publishers would welcome submission systems that incorporate structured fields for author affiliations with well-designed auto-suggestions linked to ROR or other organization identifiers.&lt;/li>
&lt;li>Making affiliation data mandatory at submission could significantly improve capture rates, although it would be important to ensure that independent researchers can use these systems as well.&lt;/li>
&lt;li>Enable collection of affiliations for all authors, not just the corresponding author.&lt;/li>
&lt;li>Pull in &lt;a href="https://info.orcid.org/trust-markers-in-orcid-records-verified-email-domains/" target="_blank">verified affiliation information from ORCID&lt;/a>.&lt;/li>
&lt;li>Increasingly, intelligent matching systems can be implemented to reduce author burden and perhaps also increase accuracy and completeness of metadata.&lt;/li>
&lt;li>Better crosswalks between different organization identifier systems would make it vastly easier for publishers to maintain better metadata. Since open registries cannot include proprietary information, proprietary registries should provide their customers with crosswalks to all standard open identifiers.&lt;/li>
&lt;/ul>
&lt;h3 id="encourage-publisher-best-practices">Encourage publisher best practices&lt;/h3>
&lt;ul>
&lt;li>Publishers can use already-available tools to help assess and improve the quality of both new and legacy author affiliation metadata.
&lt;ul>
&lt;li>&lt;a href="https://crossref-org.pluma.sjfc.edu/members/prep/" target="_blank">Crossref’s Participation Reports&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://graph.openaire.eu/docs/10.5.1/graph-production-workflow/enrichment-by-mining/affiliation_matching/" target="_blank">OpenAIRE&amp;rsquo;s affiliation matching methods and validation systems&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://ror.readme.io/docs/api-affiliation" target="_blank">ROR API affiliation matching service&lt;/a>&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Share the benefits of improved author affiliation metadata for internal and external analytics, customer satisfaction, and research integrity.&lt;/li>
&lt;li>Identify best practices in collecting and structuring author affiliation metadata.&lt;/li>
&lt;li>Understand that the entire research ecosystem would benefit from publishers sharing collected affiliation data with Crossref.&lt;/li>
&lt;/ul>
&lt;p>It’s worth mentioning that these solutions are heterogeneous: not all strategies can be implemented by any one actor nor even by any one sector of our profession. Clearly, collaborative action is necessary for substantive change.&lt;/p>
&lt;h2 id="moving-forward">Moving forward&lt;/h2>
&lt;p>The affiliations metadata roundtable represented an important step in addressing affiliation metadata challenges in a productive and collaborative way. If there was a consensus, it was that while perfect completeness and accuracy of author affiliation metadata may not be achievable (or even definable), incremental improvements can substantially enhance the quality and availability of affiliation metadata for the entire scholarly information community.&lt;/p>
&lt;p>Here at Crossref, we intend to use the insights from this roundtable to inform our support of the Crossref community, including publishers, service providers, and metadata users. We welcome your comments, questions, and suggestions on this issue! &lt;strong>Share your thoughts with Amanda French at &lt;a href="mailto:alfrench@crossref.org">alfrench@crossref.org&lt;/a>.&lt;/strong>&lt;/p>
&lt;h3 id="references">References&lt;/h3>
&lt;ol>
&lt;li>van Eck, N. J., &amp;amp; Waltman, L. (2025). Crossref as a source of open bibliographic metadata (No. smxe5_v2). MetaArXiv. &lt;a href="https://doi-org.pluma.sjfc.edu/10.31222/osf.io/smxe5_v2" target="_blank">https://doi-org.pluma.sjfc.edu/10.31222/osf.io/smxe5_v2&lt;/a>&lt;/li>
&lt;li>Tkaczyk, D. (2025). Crossref relationships involving research organisations [Dataset]. Zenodo. &lt;a href="https://doi-org.pluma.sjfc.edu/10.5281/zenodo.15254993" target="_blank">https://doi-org.pluma.sjfc.edu/10.5281/zenodo.15254993&lt;/a>&lt;/li>
&lt;li>French, A., van Eck, N. J., Campfens, Y., Day, A., &amp;amp; Tkaczyk, D. (2026, January 19). Affiliations Metadata Roundtable 2025—All Presentations. &lt;a href="https://doi-org.pluma.sjfc.edu/10.13003/661591chqlyw" target="_blank">https://doi-org.pluma.sjfc.edu/10.13003/661591chqlyw&lt;/a>&lt;/li>
&lt;/ol>
&lt;h3 id="participating-organizations">Participating organizations&lt;/h3>
&lt;table>
&lt;thead>
&lt;tr>
&lt;th style="text-align: center">&lt;/th>
&lt;th>&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td style="text-align: center">Africa PID Alliance / TCC Africa&lt;/td>
&lt;td style="text-align: center">Frontiers Media SA&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">American Association of Cancer Research (AACR)&lt;/td>
&lt;td style="text-align: center">Iowa State&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">American Chemical Society (ACS)&lt;/td>
&lt;td style="text-align: center">Kriyadocs / Exeter Premedia Services&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">American Physical Society (APS)&lt;/td>
&lt;td style="text-align: center">MDPI&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">American Society for Microbiology (ASM)&lt;/td>
&lt;td style="text-align: center">Noyam Publishers&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Aptara&lt;/td>
&lt;td style="text-align: center">OpenAIRE / OpenOrgs&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Australian Research Data Commons (ARDC)&lt;/td>
&lt;td style="text-align: center">Optica Publishing Group&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Atypon&lt;/td>
&lt;td style="text-align: center">ORCID&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Beilstein-Institut&lt;/td>
&lt;td style="text-align: center">Oxford University Press&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">California Digital Library (CDL)&lt;/td>
&lt;td style="text-align: center">Public Knowledge Project (PKP)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Cambridge University Press&lt;/td>
&lt;td style="text-align: center">Public Library of Science (PLOS)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Carnegie Mellon University&lt;/td>
&lt;td style="text-align: center">River Valley Technologies&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">CHORUS&lt;/td>
&lt;td style="text-align: center">Rockefeller University Press&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Clarivate / Web of Science &lt;/td>
&lt;td style="text-align: center">SAGE Publications&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Copernicus GmBH&lt;/td>
&lt;td style="text-align: center">Barcelona Declaration on Open Research Information &lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Curtin University / Curtin Open Knowledge Initiative (COKI)&lt;/td>
&lt;td style="text-align: center">Silverchair / ScholarOne&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">De Gruyter Brill&lt;/td>
&lt;td style="text-align: center">Springer Science &amp;amp; Business&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Digital Science / Figshare&lt;/td>
&lt;td style="text-align: center">TNQTech&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Digital Science / Symplectic Elements&lt;/td>
&lt;td style="text-align: center">University of Laval&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">eLife&lt;/td>
&lt;td style="text-align: center">University of Chicago Press&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Elsevier BV&lt;/td>
&lt;td style="text-align: center">University of Split&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: center">Enago&lt;/td>
&lt;td>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table></description></item><item><title>Some rip-RORing news for affiliation metadata</title><link>https://www-crossref-org.pluma.sjfc.edu/blog/some-rip-roring-news-for-affiliation-metadata/</link><pubDate>Mon, 26 Jul 2021 00:00:00 +0000</pubDate><author>Ginny Hendricks</author><discourseUsername>ginny</discourseUsername><guid>https://www-crossref-org.pluma.sjfc.edu/blog/some-rip-roring-news-for-affiliation-metadata/</guid><description>&lt;p>We’ve just added to our input schema the ability to include affiliation information using ROR identifiers. Members who register content using XML can now include ROR IDs, and we’ll add the capability to our manual content registration form, participation reports, and metadata retrieval APIs in the near future. And we are inviting members to a &lt;a href="https://crossref.zoom.us/webinar/register/WN_M5EFzTZCSBqsnbWiMMmMLQ" target="_blank">Crossref/ROR webinar&lt;/a> on 29th September at 3pm UTC.&lt;/p>
&lt;h2 id="the-background">The background&lt;/h2>
&lt;p>We’ve been working on the &lt;a href="https://ror.org" target="_blank">Research Organization Registry (ROR)&lt;/a> as a community initiative for the last few years. Along with the California Digital Library and DataCite, our staff has been involved in setting the strategy, planning governance and sustainability, developing technical infrastructure, hiring/loaning staff, and engaging with people in person and online. In our view, it’s the best current model of a collaborative initiative between like-minded &lt;a href="http://openscholarlyinfrastructure.org" target="_blank">open scholarly infrastructure (OSI)&lt;/a> organisations.&lt;/p>
&lt;p>Last year, Project Manager Maria Gould described &lt;a href="https://doi-org.pluma.sjfc.edu/10.64000/wxc0w-hcq28" target="_blank">the case for publishers adopting ROR&lt;/a> and ROR was ranked the number one priority at our last in-person annual meeting. Now it’s time that Crossref’s services themselves took up the baton to meet the growing demand.&lt;/p>
&lt;p>The inclusion of ROR in the Crossref metadata will help everyone in the scholarly ecosystem make critical connections more easily. For example, research institutions need to monitor and measure their output by the articles and other resources their researchers have produced. Journals need to know with which institutions authors are affiliated to determine eligibility for institutionally sponsored publishing agreements. Funders need to be able to discover and track the research and researchers they have supported. Academic librarians need to easily find all of the publications associated with their campus.&lt;/p>
&lt;p>Earlier this month, GRID and ROR &lt;a href="https://www.digital-science.com/press-release/grid-passes-torch-to-ror" target="_blank">announced&lt;/a> that after working together to seed the community-run Research Organization Registry, GRID would be retiring from public service and handing the proverbial torch over to ROR as the scholarly community’s reliable universal open identifier for affiliations. That means that our members who have been using GRID now need to consider their move to ROR and think about how they can add ROR IDs into the metadata that they manage and share through Crossref.&lt;/p>
&lt;h2 id="the-plan">The plan&lt;/h2>
&lt;p>We’ve been able to include ROR IDs for our grant metadata schema as affiliation information for two years, since July 2019. And the Australia Research Data Commons (ARDC) was the first member to add ROR IDs to the Crossref system in 2020. In early July, we completed the work to accept ROR IDs for affiliation assertions for all other types of records with an &lt;code>affiliation&lt;/code> or &lt;code>institution&lt;/code> element, such as journal articles, book chapters, preprints, datasets, dissertations, and many more.&lt;/p>
&lt;p>Next, we will commence the plans to support ROR in our other tools and services, such as Participation Reports. We’ll work on alignment with the Open Funder Registry and share our plans to collect the information via the &lt;a href="https://doi-org.pluma.sjfc.edu/10.64000/30vzx-r5x16" target="_blank">new user interface we’re developing for registering and managing metadata&lt;/a>. Open Journal Systems (OJS) already has a ROR Plugin, developed by the German National Library of Science and Technology (TIB). This supports the collection of ROR IDs and future releases of this plugin and the OJS DOI plugin will allow including ROR IDs in the metadata sent to Crossref, to support thousands of our members to share ROR IDs via their Crossref metadata.
We also aim to add ROR to our metadata retrieval options, including the REST API, which recently saw the start of an unblocking with our &lt;a href="https://doi-org.pluma.sjfc.edu/10.64000/nxwqn-x9m73" target="_blank">move to a more robust technical foundation&lt;/a>.&lt;/p>
&lt;h2 id="the-call-for-participation">The call for participation&lt;/h2>
&lt;p>Many Crossref publishers, funders, and service providers are already planning to integrate ROR with their systems, &lt;a href="https://ror.readme.io/docs/map-other-organisation-id-types-to-ror" target="_blank">map their affiliation data to ROR&lt;/a>, and include ROR in Crossref metadata. In addition to publishers and funders, libraries, repositories, and other stakeholders are developing support for ROR. For example, the &lt;a href="https://journalcheckertool.org" target="_blank">Plan S Journal Checker tool&lt;/a> uses ROR IDs to let people check whether a particular journal is compliant with an author&amp;rsquo;s funder and institutional open access policies. In addition, the ROR website shows a growing list of &lt;a href="https://ror.org/integrations" target="_blank">active and in-progress ROR integrations&lt;/a>.&lt;/p>
&lt;figure>&lt;img src="https://www-crossref-org.pluma.sjfc.edu/images/blog/2021/crossref-ror-workflow-diagram.png" width="100%">
&lt;/figure>
&lt;p>Crossref members registering research grants via Altum’s ProposalCentral system can already add ROR IDs. Now those registering articles, books, preprints, datasets, dissertations, and other research objects, can start including much clearer and all-important affiliation metadata as part of their content registration going forward. As with all newly-introduced metadata elements, we recommend adding ROR IDs from now and ongoing, but planning a distinct project to backfill older records. We know that more than 80% of records have been updated and enriched at least once with additional and cleaner metadata, so as members do this routinely, they can include ROR IDs alongside updating URLs, license or funding information, and other metadata.&lt;/p>
&lt;p>For information on how ROR will be supported in the Crossref metadata, take a look at &lt;a href="https://gitlab.com/crossref/schema/-/releases/0.2.0" target="_blank">our latest schema release (version 5.3.0) &lt;/a> or in this &lt;a href="https://gitlab.com/crossref/schema/-/blob/master/best-practice-examples/journal.article5.3.0.xml" target="_blank">journal article example XML&lt;/a>.&lt;/p>
&lt;p>Join the discussion in our forum below and register for the &lt;a href="https://www-crossref-org.pluma.sjfc.edu/services/content-registration/">Crossref/ROR webinar on September 29th at 3pm UTC&lt;/a> to learn all you need to know about incorporating ROR into your Crossref metadata.&lt;/p></description></item><item><title>Publishers, are you ready to ROR?</title><link>https://www-crossref-org.pluma.sjfc.edu/blog/publishers-are-you-ready-to-ror/</link><pubDate>Tue, 25 Aug 2020 00:00:00 +0000</pubDate><author>Maria Gould</author><guid>https://www-crossref-org.pluma.sjfc.edu/blog/publishers-are-you-ready-to-ror/</guid><description>&lt;p>If you manage a publishing system or workflow, you know how crucial—and how challenging!—it is to have clean, consistent, and comprehensive affiliation metadata. Author affiliations, and the ability to link them to publications and other scholarly outputs, are vital for numerous stakeholders across the research landscape. Institutions need to monitor and measure their research output by the articles their researchers have published. Funders need to be able to discover and track the research and researchers they have supported. Academic librarians need to easily find all of the publications associated with their campus. Journals need to know where authors are affiliated so they can determine eligibility for institutionally sponsored publishing agreements.&lt;/p>
&lt;p>Until recently, an open, unambiguous, and persistent identifier for research organisation affiliations has been a missing layer of the scholarly ecosystem. DOIs could identify articles and datasets and other research outputs, and ORCID IDs could identify researchers, but no equivalent solution was available to identify institutions. With the launch of the &lt;a href="https://ror.org" target="_blank">Research Organization Registry (ROR)&lt;/a> in 2019 (which Crossref has &lt;a href="https://ror.org/about" target="_blank">helped to develop&lt;/a>), the landscape is changing. ROR IDs are an opportunity to make affiliation details easier for publishers to use and easier for those who rely on this data.&lt;/p>
&lt;p>Affiliations are a key piece of Crossref metadata that has been missing, but will soon be &lt;a href="https://doi-org.pluma.sjfc.edu/10.64000/cmxdb-n4v31" target="_blank">supported in the Crossref metadata schema&lt;/a>. This means that content registered with Crossref can be associated with a ROR IDs to  enable better tracking and discovery of research and other publication outputs by institution.&lt;/p>
&lt;h2 id="what-is-ror">What is ROR?&lt;/h2>
&lt;p>ROR is the Research Organization Registry––&lt;strong>open, noncommercial, community-led infrastructure&lt;/strong> for research organisation identifiers. The registry currently includes globally unique persistent identifiers and associated metadata for more than &lt;a href="https://ror.org/search" target="_blank">98,000 research organisations&lt;/a> (as of August 2020).&lt;/p>
&lt;p>ROR IDs are specifically designed to be &lt;strong>implemented in any system&lt;/strong> that captures institutional affiliations and to enable connections (via persistent identifiers and networked research infrastructure) between research organisations, research outputs, and researchers.&lt;/p>
&lt;p>ROR IDs are &lt;strong>interoperable with those in other identifier registries&lt;/strong>, including GRID (which provided the seed data that ROR launched with), Crossref Funder Registry, ISNI, and Wikidata. ROR data is available under a CC0 waiver and can be accessed via a public &lt;a href="https://api.ror.org/organisations" target="_blank">API&lt;/a> and &lt;a href="https://doi-org.pluma.sjfc.edu/10.6084/m9.figshare.c.4596503" target="_blank">data dump&lt;/a>.&lt;/p>
&lt;p>ROR is not the first organisation identifier to exist. But ROR is distinct because it is &lt;strong>completely &lt;a href="https://github.com/ror-community" target="_blank">open&lt;/a>, specifically focused on &lt;a href="https://ror.org/scope" target="_blank">identifying affiliations&lt;/a>&lt;/strong>, and &lt;strong>&lt;a href="https://ror.org/supporters" target="_blank">collaboratively developed by, with, and for key stakeholders&lt;/a>&lt;/strong> in scholarly communications. ROR is operated as a joint initiative by Crossref, &lt;a href="https://datacite.org" target="_blank">DataCite&lt;/a>, and &lt;a href="https://cdlib.org" target="_blank">California Digital Library&lt;/a>, and was launched with seed data from GRID in collaboration with Digital Science. These organisations have invested resources into building an open registry of research organisation identifiers that can be embedded in scholarly infrastructure to effectively link research to organisations.&lt;/p>
&lt;h2 id="why-care-about-ror-ids-in-crossref-metadata">Why care about ROR IDs in Crossref metadata?&lt;/h2>
&lt;p>Ed Pentz, Crossref’s Executive Director, explains the key role ROR can play in enriching Crossref metadata:&lt;/p>
&lt;p>&lt;em>“Over the years Crossref has expanded the metadata it collects (for example, ORCID IDs and license URLs) based on the changing needs of our members and the scholarly research community. A key type of metadata that is missing from Crossref is affiliations. We’ve had a lot of feedback from members that adding affiliations should be a priority. At &lt;a href="https://www-crossref-org.pluma.sjfc.edu/crossref-annual-meeting/archive/#2019">Crossref LIVE19 in Amsterdam&lt;/a>, ROR was ranked joint first place for Crossref by the 100 plus attendees at the meeting. For the last few years we’ve been diligently working on the initiative and are very happy that ROR is now coming to fruition.”&lt;/em>&lt;/p>
&lt;p>Crossref metadata does include some affiliations already. But this data is not comprehensive or consistent, and appears as free-text strings only (even if originally sourced from a list of institutions). A search for UC Berkeley, for instance, returns multiple variants of the university’s name:&lt;/p>
&lt;ul>
&lt;li>University of California, Berkeley&lt;/li>
&lt;li>University of California-Berkeley&lt;/li>
&lt;li>University of California Berkeley&lt;/li>
&lt;li>UC Berkeley&lt;/li>
&lt;li>And likely more&amp;hellip;&lt;/li>
&lt;/ul>
&lt;p>While it isn&amp;rsquo;t too difficult for a human to guess that &amp;ldquo;UC Berkeley,&amp;rdquo; &amp;ldquo;University of California, Berkeley,&amp;rdquo; and &amp;ldquo;University of California at Berkeley&amp;rdquo; are all referring to the same university, a machine interpreting this information wouldn&amp;rsquo;t necessarily make the same connections. If you are trying to easily find all of the publications associated with UC Berkeley, you would need to run and reconcile multiple searches at best, or miss data completely at worst. This is where an affiliation identifier comes in: a single, unambiguous, standardized identifier that will always stay the same (for UC Berkeley, that would be &lt;a href="https://ror.org/01an7q238" target="_blank">https://ror.org/01an7q238&lt;/a>).&lt;/p>
&lt;p>ROR IDs for affiliations can transform the usability of Crossref metadata. While it&amp;rsquo;s crucial to have IDs for affiliations, it&amp;rsquo;s equally important that the affiliation data can be easily used. The ROR dataset is CC0, so ROR IDs and associated affiliation data can be freely and openly used and reused without any restrictions.&lt;/p>
&lt;h2 id="what-does-this-mean-for-publishers">What does this mean for publishers?&lt;/h2>
&lt;p>As the Crossref schema update is being cleared for takeoff, this is a good time for publishers and publishing service providers to be thinking about adopting ROR.&lt;/p>
&lt;p>ROR IDs can be useful in publishing workflows in a variety of ways. They can easily be implemented into manuscript tracking systems to identify the affiliations of submitting authors and co-authors. This can be done via a simple institution lookup that connects to the ROR API. Authors choose their affiliation from a dropdown list populated from ROR; they do not have to provide a ROR ID or even know that a ROR ID is being collected.&lt;/p>
&lt;p>&lt;a href="https://gyazo.com/65ef42890287ae978f61add5d36b1d31">&lt;img src="https://i.gyazo.com/65ef42890287ae978f61add5d36b1d31.gif" alt="Image from Gyazo" width="780"/>&lt;/a>&lt;/p>
&lt;p>Upon publication, ROR affiliation data can be included when content is registered with Crossref. ROR IDs are also supported in the JATS XML format that many publishers use. Crossref metadata can be searched and crawled, and the Crossref API will make ROR IDs available so affiliation data can be captured by tools and services and fed into downstream reporting and tracking systems.&lt;/p>
&lt;h2 id="get-ready-to-ror">Get ready to ROR!&lt;/h2>
&lt;p>ROR is already working with a number of publishers and service providers that are planning to integrate ROR in their systems, map their affiliation data to ROR IDs, and/or include ROR IDs in publication metadata.&lt;/p>
&lt;p>For example: &lt;a href="https://rupress-org.pluma.sjfc.edu/" target="_blank">Rockefeller University Press&lt;/a> has already added the collection of ROR IDs to their publication workflow. Upon submission, the author selects an institutional affiliation from a dropdown list of options that comes from ROR. Rockefeller University Press also relies on this affiliation data for billing and licensing purposes to coordinate Gold Open Access publishing agreements.&lt;/p>
&lt;p>In addition to publishers, libraries and repositories and other stakeholders are building in support for ROR. You can also see the list of active and in-progress ROR integrations &lt;a href="https://ror.org/integrations" target="_blank">here&lt;/a>.&lt;/p>
&lt;p>We know decisions about identifier adoption aren&amp;rsquo;t easy or immediate, so &lt;a href="mailto:info@ror.org">get in touch with ROR&lt;/a> if you have questions or want to be more involved in the project. ROR holds regular community meetings and &lt;a href="https://www.youtube.com/watch?v=W61JMsC3Dho" target="_blank">webinars&lt;/a> and supports several community working groups for those interested in implementing ROR IDs and working with ROR data. This is a community-driven effort so we want to hear from you!&lt;/p></description></item></channel></rss>