<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Hi, all!</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
This is about DOIs for articles that have more than one "canonical"/official publisher home.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
That can happen, and does frequently, when a journal changes publishers and BOTH publishers maintain an official archive for PCA libraries.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
For instance, the 2006-2011 of the journal, Frontiers of History in China, where Brill has 2006-present and Springer-Nature, the previous publisher, has 2006-2011. Our only access is on SN because we did not continue the subscription in 2012 when Brill got
it. But the DOI in our discovery service only leads to Brill, not SN.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
The NISO Journal Transfer database, <a class="OWAAutoLink" id="OWA58b308ba-971a-e227-023d-597f17b73b90" href="https://journaltransfer.issn.org/">
https://journaltransfer.issn.org/</a>, documents when journals transfer and includes whether the archive up to that point will be hosted by the transferring or receiving publisher. Sometimes it is actually both.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
It was recently brought to my attention that Crossref has a "multiple resolution" (MR) system, such that when following some DOI links, the user gets a list of links to each of the publisher platforms that are still "official" (I think by NISO's concept of
that).</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
I asked Crossref about what I should do to get an "MR" for this journal.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
This is part of the reply I got:</div>
<div style="margin-left: 40px; font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
However, just to set expectations, multiple resolution is used quite rarely. Most publishers prefer that DOIs resolved directly to the version of the content on their particular platform. And, the feedback we get from librarians about multiple resolution
has honestly been primarily negative, because they don't like users to be faced with another decision point or extra friction in accessing the content. (we do have a workaround to 'bypass' multiple resolution, for that reason, and resolve directly to either
the primary or one of the secondary URLs) </div>
<div style="margin-left: 40px; font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
</div>
<div style="margin-left: 40px; font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
That said, the more typical solution is for libraries to link to content, not directly via the DOI, but using an OpenURL link resolver or discovery tool integration that will direct users to the appropriate subscription version for which they have full text
access. It's possible to integrate metadata from Crossref into such a tool, to facilitate linking more effectively. </div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
As I read and re-read that answer, it occurred to me to question whether the entire point of the DOI system is breaking down. When Crossref itself tells me not to use DOI links, but instead openurl links, which is where we were 20 years ago and whose problems
were a big part of the reason for supporting the adoption of the DOI ecosystem in the first place, I feel like we are moving backwards in a context that I thought we had solved already.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
I know that DOI still works for "most" situations. But openurl also worked for "most situations", and still does. I worked at a library that was one of the very earliest adopters of openurl, and even wrote my own openurl resolver for my library before the commercial
products existed. I have a long memory of how we got from there to here.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
So I wanted to consult your collective wisdom about this issue, both from the immediate "best service to patrons today" perspective and the "long-term where should our ecosystem be going next?" perspective.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Your thought would be most welcome!</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div class="elementToProof" id="Signature">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="background-color: rgb(255, 255, 255); margin: 0px;" class="elementToProof">
<div style="text-align: left; font-family: Arial, Helvetica, sans-serif; font-size: 9.75pt; color: rgb(32, 33, 36);" class="elementToProof">
<span style="background-color: white;">Melissa Belvadi</span></div>
<div style="text-align: left; background-color: white; margin: 0px; font-family: Arial, Helvetica, sans-serif; font-size: 9.75pt; color: rgb(32, 33, 36);" class="elementToProof">
Collections Librarian</div>
<div style="text-align: left; background-color: white; margin: 0px; font-family: Arial, Helvetica, sans-serif; font-size: 9.75pt; color: rgb(32, 33, 36);" class="elementToProof">
University of Prince Edward Island</div>
<div style="text-align: left; background-color: white; margin: 0px; font-family: Arial, Helvetica, sans-serif; color: rgb(32, 33, 36);" class="elementToProof">
<span style="font-size: 9.75pt;"><a style="margin: 0px;" data-loopstyle="linkonly" data-linkindex="0" class="OWAAutoLink" id="OWAe63fe498-d226-68f6-d322-43fb68d5095d" href="mailto:mbelvadi@upei.ca">mbelvadi@upei.ca</a> 9</span><span style="font-size: 12.79px;">02-566-0581</span></div>
<div style="text-align: left; background-color: white; margin: 0px; font-family: Arial, Helvetica, sans-serif; font-size: 12.79px; color: rgb(32, 33, 36);" class="elementToProof">
ORCID iD: 0000-0002-4433-0189</div>
<div style="text-align: left; background-color: white; margin: 0px; font-family: Arial, Helvetica, sans-serif; font-size: 9.75pt; color: rgb(32, 33, 36);" class="elementToProof">
my <a style="margin: 0px;" data-loopstyle="linkonly" data-linkindex="1" data-auth="NotApplicable" rel="noopener noreferrer" title="https://outlook.office365.com/owa/calendar/0fbab27c909e4493be65313bd66d66b6@upei.ca/5fa60af92c6d451c9ddf90c0bb11e00f15552192987609852692/calendar.html" class="OWAAutoLink" id="OWAf5627d5c-49ce-9098-2175-a31cb1273d4c" target="_blank" href="https://outlook.office365.com/owa/calendar/0fbab27c909e4493be65313bd66d66b6@upei.ca/5fa60af92c6d451c9ddf90c0bb11e00f15552192987609852692/calendar.html">
public calendar</a></div>
<div style="text-align: left; font-family: Arial, Helvetica, sans-serif; font-size: 9.75pt; color: rgb(32, 33, 36);" class="elementToProof">
<span style="background-color: white;"><a style="margin: 0px;" data-loopstyle="linkonly" data-linkindex="2" data-auth="NotApplicable" rel="noopener noreferrer" class="OWAAutoLink" id="OWA52f3bc0f-a138-30ec-051c-4da616305d8e" target="_blank" href="https://mbelvadi.youcanbook.me/">Make
an appointment</a> via YouCanBookMe</span></div>
</div>
<div style="text-align: left; background-color: rgb(255, 255, 255); margin: 0px;" class="elementToProof">
<span style="font-family: Arial, Helvetica, sans-serif; font-size: 9.75pt; color: rgb(32, 33, 36); background-color: white;">My pronouns are
</span><span style="font-family: "Google Sans", Roboto, Arial, sans-serif; font-size: 14px; color: rgb(31, 31, 31); background-color: rgba(68, 71, 70, 0.08);">ಅವರು/ಅವರನ್ನು</span></div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 9.75pt; color: rgb(32, 33, 36);" class="elementToProof">
<span style="background-color: white;">My emails are sent during the hours that I work and I understand that you will respond during the hours that you work.</span></div>
</div>
</body>
</html>