<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body smarttemplateinserted="true">
    <div id="smartTemplate4-template">That's correct - the ORCID Support
      Advance plugin wouldn't delete any ORCIDs once the circumstances
      described in your email below are met. However, as I mentioned in
      my previous email, the Advance plugin won't delete automatically
      anyway as this functionality is disabled by default, but it would
      stop you from editing the ORCIDs by making the field read-only.<br>
      <br>
      With regards to permissions, these are decided by the user when
      they're connecting their repository account to their ORCID
      account. The user is given the option to select if they want the
      repository to be able to "Create and update activities on your
      ORCID record" and to be able to "Retrieve restricted details from
      your ORCID record".<br>
      <br>
      Many thanks,<br>
      <br>
      Will<br>
    </div>
    <br>
    <div id="smartTemplate4-quoteHeader"><br>
      <hr>
      <b>From:</b> Tomasz Neugebauer [<a class="moz-txt-link-abbreviated" href="mailto:Tomasz.Neugebauer@concordia.ca">Tomasz.Neugebauer@concordia.ca</a>]
      <b>Sent:</b> 02 August 2018 22:01
      <b>To:</b> Eprints-tech
      <b>Subject:</b> Re: [EP-tech] ORCID Support Advance Update
      <br>
    </div>
    <span type="cite"
cite="mid:EMEW3|0ea8198b9b749959dd3d7027c898ca13u71M3I14eprints-tech-bounces|ecs.soton.ac.uk|0f4fc124278a414495633dee1d3dfc07@UMS-LOY-MBS1.concordia.ca"
      style="display: block; word-break: break-all; margin: 9px 0 0 0;
      padding: 0; line-height:0"></span>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <meta name="Generator" content="Microsoft Word 15 (filtered medium)">
    <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
    <style><!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
        {font-family:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0cm;
        margin-right:0cm;
        margin-bottom:0cm;
        margin-left:36.0pt;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Tahoma",sans-serif;
        color:#1F497D;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle23
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle24
        {mso-style-type:personal;
        font-family:"Tahoma",sans-serif;
        color:#1F497D;}
span.EmailStyle26
        {mso-style-type:personal-compose;
        font-family:"Tahoma",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:945885312;
        mso-list-type:hybrid;
        mso-list-template-ids:1548663114 269025297 269025305 269025307 269025295 269025305 269025307 269025295 269025305 269025307;}
@list l0:level1
        {mso-level-text:"%1\)";
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l1
        {mso-list-id:1059326522;
        mso-list-type:hybrid;
        mso-list-template-ids:694194776 269025281 269025283 269025285 269025281 269025283 269025285 269025281 269025283 269025285;}
@list l1:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Symbol;}
@list l1:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:"Courier New";}
@list l1:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Wingdings;}
@list l1:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Symbol;}
@list l1:level5
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:"Courier New";}
@list l1:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Wingdings;}
@list l1:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Symbol;}
@list l1:level8
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:"Courier New";}
@list l1:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Wingdings;}
ol
        {margin-bottom:0cm;}
ul
        {margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
    <div class="WordSection1">
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D">Thank
          you for this useful information, I really appreciate it!<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D">If
          I understand correctly, then, in order not to lose the ORCIDs
          for authors collected through ORCID Support plugin, we would
          have to do the following:<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"><o:p> </o:p></span></p>
      <p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1
        level1 lfo2"><!--[if !supportLists]--><span
          style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span
            style="mso-list:Ignore">·<span style="font:7.0pt &quot;Times
              New Roman&quot;">        
            </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D">Ensure
          that every ORCID in an author field matched on the email field
          with a user profile record.  This would require adding the
          ORCID id to user profiles and/or the email address to the
          author field whenever ORCID is included.<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"><o:p> </o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D">If
          that is done, then the ORCID Support Advance plugin will not
          delete any of these ORCIDs, right?  What sorts of permissions
          will it assign to them?<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"><o:p> </o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D">Best
          wishes,<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D">Tomasz<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"><o:p> </o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D">Thank
          you also to Will, Jan and John for the broader discussion
          about ORCID IDs that I do believe we need (<a
            href="https://twitter.com/photomediathink/status/1012051960676212738"
            moz-do-not-send="true">https://twitter.com/photomediathink/status/1012051960676212738</a>). 
          If we are going to promote ORCID, it has to make sense as a
          system.  If we can only refer to ORCID IDs of authors who have
          an account on our IR, then we would need another global
          identifier for the other authors that we can’t use an ORCID
          for.<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"><o:p> </o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"><o:p> </o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"><o:p> </o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"><o:p> </o:p></span></p>
      <div>
        <div style="border:none;border-top:solid #E1E1E1
          1.0pt;padding:3.0pt 0cm 0cm 0cm">
          <p class="MsoNormal"><b><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">From:</span></b><span
              style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US"> <a class="moz-txt-link-abbreviated" href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">eprints-tech-bounces@ecs.soton.ac.uk</a>
              <a class="moz-txt-link-rfc2396E" href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">&lt;eprints-tech-bounces@ecs.soton.ac.uk&gt;</a>
              <b>On Behalf Of </b>John Salter<br>
              <b>Sent:</b> August 2, 2018 7:14 AM<br>
              <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:eprints-tech@ecs.soton.ac.uk">eprints-tech@ecs.soton.ac.uk</a><br>
              <b>Subject:</b> Re: [EP-tech] ORCID Support Advance Update<o:p></o:p></span></p>
        </div>
      </div>
      <p class="MsoNormal"><o:p> </o:p></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">Hi Will,<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">Thanks for that clarification - I was a bit
          worried there for a moment!<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB"><o:p> </o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">I think the ORCID landscape is shifting from a
          'get people to sign up for an ORCID' to 'sharing the data
          sensibly/properly'.<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">We are a key part of that!<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB"><o:p> </o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">Cheers,<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">John<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB"><o:p> </o:p></span></p>
      <div>
        <div style="border:none;border-top:solid #E1E1E1
          1.0pt;padding:3.0pt 0cm 0cm 0cm">
          <p class="MsoNormal"><b><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">From:</span></b><span
              style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US">
            </span><a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"
              moz-do-not-send="true"><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">eprints-tech-bounces@ecs.soton.ac.uk</span></a><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US"> [</span><a
              href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"
              moz-do-not-send="true"><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">mailto:eprints-tech-bounces@ecs.soton.ac.uk</span></a><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US">]
              <b>On Behalf Of </b>Will Fyson<br>
              <b>Sent:</b> 02 August 2018 12:03<br>
              <b>To:</b> </span><a
              href="mailto:eprints-tech@ecs.soton.ac.uk"
              moz-do-not-send="true"><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">eprints-tech@ecs.soton.ac.uk</span></a><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US"><br>
              <b>Subject:</b> Re: [EP-tech] ORCID Support Advance Update<o:p></o:p></span></p>
        </div>
      </div>
      <p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
      <div id="smartTemplate4-template">
        <p class="MsoNormal" style="margin-bottom:12.0pt"><span
            lang="EN-GB">Apologies, my previous email was a little bit
            flippant on this issue! I agree we need to try and store
            authenticated ORCIDs wherever possible. To that end we're
            working on adding an annotation system so that where an
            ORCID is imported from a trustworthy upstream system, this
            bit of provenance is stored and we know not to try and check
            this ORCID against a user account.<br>
            <br>
            The alternative approach would be to introduce a notion of
            guest/external users to EPrints so that when external
            authors are added we can store the fact that this user was
            added via a trustworthy upstream system and we have an
            actual user object for them.<br>
            <br>
            Ultimately I believe ORCID themselves would prefer the idea
            that the repository emails the external author and so the
            author can authenticate their ORCID - this too would no
            doubt be easier to do with a guest/external user type, but
            should the ORCID plugin(s) be introducing new user types and
            muddying the user dataset?<br>
            <br>
            Many thanks,<br>
            <br>
            Will<o:p></o:p></span></p>
        <p><span lang="EN-GB"><br>
             <o:p></o:p></span></p>
      </div>
      <p class="MsoNormal" style="margin-bottom:12.0pt"><span
          lang="EN-GB"><o:p> </o:p></span></p>
      <div id="smartTemplate4-quoteHeader">
        <p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
        <div class="MsoNormal" style="text-align:center" align="center"><span
            lang="EN-GB">
            <hr width="100%" size="2" align="center">
          </span></div>
        <p class="MsoNormal"><b><span lang="EN-GB">From:</span></b><span
            lang="EN-GB"> John Salter [</span><a
            href="mailto:J.Salter@leeds.ac.uk" moz-do-not-send="true"><span
              lang="EN-GB">J.Salter@leeds.ac.uk</span></a><span
            lang="EN-GB">]
            <b>Sent:</b> 02 August 2018 11:32 <b>To:</b> Eprints-tech <b>Subject:</b>
            Re: [EP-tech] ORCID Support Advance Update
            <o:p></o:p></span></p>
      </div>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">&gt;</span><span lang="EN-GB"> This naturally
          poses a problem for storing ORCIDs for external authors, but
          in my experience most repositories are happy storing ORCIDs
          for just their own users.<o:p></o:p></span></p>
      <p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">This concerns me. We (repository developers)
          shouldn't be encouraging a blinkered approach to ORCIDs (or
          other persistent identifiers).</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">You wouldn't exclude a DOI for a paper if it
          wasn't minted by your institution - so why would you choose to
          discard ORCIDs for non-local members?</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">If the ORCID has come from a trustworthy upstream
          system (e.g. CrossRef, PubsRouter), then the ORCID should stay
          with the author.</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">Local ORCIDs can supplement this data - so a
          record harvested from your repository is 'improved'.</span><span
          lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">I was reading this:
        </span><a
href="https://support.crossref.org/hc/en-us/articles/214567746-Authors-and-editors"
          moz-do-not-send="true"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;mso-fareast-language:EN-US"
            lang="EN-GB">https://support.crossref.org/hc/en-us/articles/214567746-Authors-and-editors</span></a><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB"> recently - and wondering what the
          'authenticated="true"' attribute actually meant - and how the
          this assertion should be passed between systems.</span><span
          lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">If a *<b>trusted</b>* upstream system states that
          an ORCID is authenticated - can we as a consumer of that data
          also state that the ORCID is authenticated when relaying data
          from our system?</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">The ORCIDs should be seen as an 'additive' set of
          data - if your system can state that an author now has an
          ORCID - do it.</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">Just don't throw away data that already exists
          for non-local authors.</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">Cheers,</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB">John</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <div>
        <div style="border:none;border-top:solid #E1E1E1
          1.0pt;padding:3.0pt 0cm 0cm 0cm">
          <p class="MsoNormal"><b><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">From:</span></b><span
              style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US">
            </span><a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"
              moz-do-not-send="true"><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">eprints-tech-bounces@ecs.soton.ac.uk</span></a><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US"> [</span><a
              href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"
              moz-do-not-send="true"><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">mailto:eprints-tech-bounces@ecs.soton.ac.uk</span></a><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US">]
              <b>On Behalf Of </b>Will Fyson<br>
              <b>Sent:</b> 02 August 2018 10:59<br>
              <b>To:</b> </span><a
              href="mailto:eprints-tech@ecs.soton.ac.uk"
              moz-do-not-send="true"><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">eprints-tech@ecs.soton.ac.uk</span></a><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US"><br>
              <b>Subject:</b> Re: [EP-tech] ORCID Support Advance Update</span><span
              lang="EN-GB"><o:p></o:p></span></p>
        </div>
      </div>
      <p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
      <div id="smartTemplate4-template">
        <p class="MsoNormal"><span lang="EN-GB">Hi Tomasz,<br>
            <br>
            The ORCID Support Advance plugin does only allow ORCIDs to
            be stored against creators/editors if they can be matched to
            a user via the 'Email' column in all circumstances (to
            facilitate the read-only nature of the field). Therefore
            ORCIDs added through use of the ORCID Support plugin are
            affected by this too.<br>
            <br>
            When we've been installing the Advance plugin on
            repositories we've been encouraging administrators to tidy
            up their ORCID data so that the ORCIDs stored are matched
            with user profiles. This naturally poses a problem for
            storing ORCIDs for external authors, but in my experience
            most repositories are happy storing ORCIDs for just their
            own users.<br>
            <br>
            If an email isn't present in the creator/editor field, but
            an ORCID is, the ORCID would be removed the next time the
            EPrint is recommitted. The ORCID Support Advance plugin
            contains a pre-commit trigger that updates the ORCID field
            based on the email column to help keep the record up to
            date. These triggers are disabled by default when the plugin
            is installed however to prevent any accidental erasing of
            data by installing the plugin. (the fields are read-only
            upon installing the plugin however and so until the triggers
            are re-enabled the content of the creator/editor ORCID
            fields is essentially fixed.)<br>
            <br>
            I hope this helps answer your questions!<br>
            <br>
            Many thanks,<br>
            <br>
            Will <o:p></o:p></span></p>
      </div>
      <p class="MsoNormal" style="margin-bottom:12.0pt"><span
          lang="EN-GB"><br>
          <br>
          <o:p></o:p></span></p>
      <div id="smartTemplate4-quoteHeader">
        <p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
        <div class="MsoNormal" style="text-align:center" align="center"><span
            lang="EN-GB">
            <hr width="100%" size="2" align="center">
          </span></div>
        <p class="MsoNormal"><b><span lang="EN-GB">From:</span></b><span
            lang="EN-GB"> Tomasz Neugebauer [</span><a
            href="mailto:Tomasz.Neugebauer@concordia.ca"
            moz-do-not-send="true"><span lang="EN-GB">Tomasz.Neugebauer@concordia.ca</span></a><span
            lang="EN-GB">]
            <b>Sent:</b> 01 August 2018 17:50 <b>To:</b> Eprints-tech <b>Subject:</b>
            Re: [EP-tech] ORCID Support Advance Update
            <o:p></o:p></span></p>
      </div>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB">Hi everyone who has installed the ORCID Support
          Advance plugin, Will…</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB">I am still looking to get a clearer picture of
          what I can expect to happen when I install the ORCID Support
          Advance plugin on top of the ORCID Support plugin that we
          currently have working.</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB">What will happen to the ORCID ID’s that we have
          already collected in the author field of publications?</span><span
          lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB">The description from Will below about ORCIDs from
          a DOI import says this:</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB">“</span><span lang="EN-GB">, the ORCID field uses
          the creator/editor 'Email' column to lookup user profiles in
          the repository that have connected to orcid.org so that the
          creator/editor ORCID field can be verified. As such any ORCID
          added via a DOI import, might then be erased if the user
          profile lookup cannot be made. “<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB">Does the above also apply to any ORCIDs that we
          have been collecting using the ORCID Support plugin?</span><span
          lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB">I don’t think that our depositors have been
          diligently filling in the email column in the author field
          during the deposit process, does that mean that the user
          profile lookup will fail and the ORCID will be deleted for any
          author that doesn’t have an email listed in the author
          column? 
        </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB">When does this deletion happen, during indexing?
          Is there any way to prevent it from happening?</span><span
          lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB">Thanks so much for any insight or advice on this
          is really appreciated.</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB">Tomasz</span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Tahoma&quot;,sans-serif;color:#1F497D"
          lang="EN-GB"> </span><span lang="EN-GB"><o:p></o:p></span></p>
      <div>
        <div style="border:none;border-top:solid #E1E1E1
          1.0pt;padding:3.0pt 0cm 0cm 0cm">
          <p class="MsoNormal"><b><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">From:</span></b><span
              style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US">
            </span><a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"
              moz-do-not-send="true"><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">eprints-tech-bounces@ecs.soton.ac.uk</span></a><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">
            </span><a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"
              moz-do-not-send="true"><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">&lt;eprints-tech-bounces@ecs.soton.ac.uk&gt;</span></a><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">
              <b><span lang="EN-US">On Behalf Of </span></b><span
                lang="EN-US">Will Fyson<br>
                <b>Sent:</b> July 11, 2018 10:16 AM<br>
                <b>To:</b> </span></span><a
              href="mailto:eprints-tech@ecs.soton.ac.uk"
              moz-do-not-send="true"><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">eprints-tech@ecs.soton.ac.uk</span></a><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US"><br>
              <b>Subject:</b> [EP-tech] ORCID Support Advance Update</span><span
              lang="EN-GB"><o:p></o:p></span></p>
        </div>
      </div>
      <p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
      <div id="smartTemplate4-template">
        <p class="MsoNormal"><span lang="EN-GB">Hi Everyone,<br>
            <br>
            A couple of minor updates have been applied to the ORCID
            Support Advance plugin, bringing it up to version 1.3.2.<br>
            <br>
            The updates are only very minor, fixing issues where the
            plugin was generating a few too many messages in the indexer
            and error logs. A Change Log documenting these most recent
            changes is available at
          </span><a href="https://wiki.eprints.org/w/ORCID_Support"
            moz-do-not-send="true"><span lang="EN-GB">https://wiki.eprints.org/w/ORCID_Support</span></a><span
            lang="EN-GB"><br>
            <br>
            Regarding the discussion a couple of emails above in the
            EP-Tech list ("Import by DOI in ORCID plugin"), a new DOI
            imported that takes ORCIDs into account is not available at
            present. Due to the requirements that the ORCID field must
            be readonly when connected to the member API so that ORCIDs
            can only be added via an authoritative source, the ORCID
            field that is added to the creator/editor tables cannot be
            edited. Therefore to stop values from being entered, which
            then later cannot be removed, the ORCID field uses the
            creator/editor 'Email' column to lookup user profiles in the
            repository that have connected to orcid.org so that the
            creator/editor ORCID field can be verified. As such any
            ORCID added via a DOI import, might then be erased if the
            user profile lookup cannot be made. <br>
            <br>
            This is an issue we're looking into resolving however and so
            hopefully we should have some updates on it in the future!<br>
            <br>
            Many thanks,<br>
            <br>
            Will<o:p></o:p></span></p>
      </div>
      <p class="MsoNormal" style="margin-bottom:12.0pt"><span
          lang="EN-GB"><br>
          <br>
          <br>
          <o:p></o:p></span></p>
      <pre><span lang="EN-GB">*** Options: </span><a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" moz-do-not-send="true"><span lang="EN-GB">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</span></a><span lang="EN-GB"><o:p></o:p></span></pre>
      <pre><span lang="EN-GB">*** Archive: </span><a href="http://www.eprints.org/tech.php/" moz-do-not-send="true"><span lang="EN-GB">http://www.eprints.org/tech.php/</span></a><span lang="EN-GB"><o:p></o:p></span></pre>
      <pre><span lang="EN-GB">*** EPrints community wiki: </span><a href="http://wiki.eprints.org/" moz-do-not-send="true"><span lang="EN-GB">http://wiki.eprints.org/</span></a><span lang="EN-GB"><o:p></o:p></span></pre>
      <pre><span lang="EN-GB">*** EPrints developers Forum: </span><a href="http://forum.eprints.org/" moz-do-not-send="true"><span lang="EN-GB">http://forum.eprints.org/</span></a><span lang="EN-GB"><o:p></o:p></span></pre>
      <p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-bottom:12.0pt"><span
          lang="EN-GB"><br>
          <br>
          <o:p></o:p></span></p>
      <pre><span lang="EN-GB">*** Options: </span><a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" moz-do-not-send="true"><span lang="EN-GB">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</span></a><span lang="EN-GB"><o:p></o:p></span></pre>
      <pre><span lang="EN-GB">*** Archive: </span><a href="http://www.eprints.org/tech.php/" moz-do-not-send="true"><span lang="EN-GB">http://www.eprints.org/tech.php/</span></a><span lang="EN-GB"><o:p></o:p></span></pre>
      <pre><span lang="EN-GB">*** EPrints community wiki: </span><a href="http://wiki.eprints.org/" moz-do-not-send="true"><span lang="EN-GB">http://wiki.eprints.org/</span></a><span lang="EN-GB"><o:p></o:p></span></pre>
      <pre><span lang="EN-GB">*** EPrints developers Forum: </span><a href="http://forum.eprints.org/" moz-do-not-send="true"><span lang="EN-GB">http://forum.eprints.org/</span></a><span lang="EN-GB"><o:p></o:p></span></pre>
      <p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
    </div>
    <br>
    <fieldset class="mimeAttachmentHeader"></fieldset>
    <br>
    <pre wrap="">*** Options: <a class="moz-txt-link-freetext" href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a>
*** Archive: <a class="moz-txt-link-freetext" href="http://www.eprints.org/tech.php/">http://www.eprints.org/tech.php/</a>
*** EPrints community wiki: <a class="moz-txt-link-freetext" href="http://wiki.eprints.org/">http://wiki.eprints.org/</a>
*** EPrints developers Forum: <a class="moz-txt-link-freetext" href="http://forum.eprints.org/">http://forum.eprints.org/</a>
</pre>
    <br>
  </body>
</html>