<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (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:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:HelveticaNeue-Light;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Verdana","sans-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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Verdana","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Georgia","serif";
color:#003366;
mso-ligatures:standardcontextual;
mso-number-form:lining;
mso-number-spacing:tabular;}
.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;}
--></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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-family:"Georgia","serif";color:#003366;mso-ligatures:standardcontextual;mso-number-form:lining;mso-number-spacing:tabular'>+1<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Georgia","serif";color:#003366;mso-ligatures:standardcontextual;mso-number-form:lining;mso-number-spacing:tabular'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Georgia","serif";color:#003366;mso-ligatures:standardcontextual;mso-number-form:lining;mso-number-spacing:tabular'>Yes please! Let’s work on integrating this. An identical project has been on our books for years, but we’ve never had the resourcing to attack it properly.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Georgia","serif";color:#003366;mso-ligatures:standardcontextual;mso-number-form:lining;mso-number-spacing:tabular'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-AU style='font-size:6.0pt;font-family:"Verdana","sans-serif";color:#003366'>-- <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-AU style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#7A7A7A'>Matthew</span></b><span lang=EN-AU style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#7A7A7A'> <b>Kerwin</b></span><span lang=EN-AU style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#F4F4F4'> </span><span lang=EN-AU style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#7A7A7A'>| QUT Library eServices</span><span lang=EN-AU style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#7A7A7A'> | <u><a href="mailto:matthew.kerwin@qut.edu.au"><u><span style='color:#7A7A7A'>matthew.kerwin@qut.edu.au</span></u></a></u></span><span lang=EN-AU style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:#7A7A7A'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-family:"Georgia","serif";color:#003366;mso-ligatures:standardcontextual;mso-number-form:lining;mso-number-spacing:tabular'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] <b>On Behalf Of </b>Matthew Brady<br><b>Sent:</b> Monday, 19 January 2015 08:39<br><b>To:</b> eprints-tech@ecs.soton.ac.uk<br><b>Subject:</b> [EP-tech] Re: ORCiD<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoPlainText><span lang=EN-AU>Hi Ian, everyone else..<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>We have our system with 2 extra datasets (Author and Author Instance)<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>The author contains everything about the person including 1 to many identifiers. (google scholarID, scopusAuthorID, ORCiD, etc etc etc....)<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>The author instance contains a link to a point in time, their affiliation with institutions/dept etc etc<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>The instance ID is then stored in the vanilla creator_id field.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>This allows a single unique author to be displayed, along with all their cited versions of their name, so the citations render correctly, and still get assigned to the correct person.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>(Example image also displays the statistics icon, which links to that authors stats page. – from <a href="https://eprints.usq.edu.au/view/uniqueauthor/">https://eprints.usq.edu.au/view/uniqueauthor/</a> )<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU style='mso-fareast-language:EN-AU'><img border=0 width=273 height=360 id="Picture_x0020_1" src="cid:image001.png@01D033CD.DED6DD80"></span><span lang=EN-AU><o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>I have tried to get this pushed into the ePrints Core, but Seb hasn’t got back in touch about who to send it to.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>I would like it incorporated into the base product, so we all have the same version, rather than a dozen or more splintered versions of code all trying to do the same thing. This will make the support on this email list more fruitful, if we are all on the same page.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>If anyone knows who is maintaining the base ePrints codebase these days, let me know and I will forward on the .zip file of all the code we have for inclusion into the base product.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>Cheers<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU style='mso-fareast-language:EN-AU'>Matt <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU style='mso-fareast-language:EN-AU'><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span style='mso-fareast-language:EN-AU'>-----Original Message-----<br>From: <a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">eprints-tech-bounces@ecs.soton.ac.uk</a> [<a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">mailto:eprints-tech-bounces@ecs.soton.ac.uk</a>] On Behalf Of Ian Stuart<br>Sent: Saturday, 17 January 2015 2:01 AM<br>To: <a href="mailto:eprints-tech@ecs.soton.ac.uk">eprints-tech@ecs.soton.ac.uk</a><br>Subject: [EP-tech] Re: ORCiD</span><span lang=EN-AU><o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>On 16/01/15 14:09, John Salter wrote:<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>> Hi, How is anyone storing an ORCiD in EPrints?<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>> Out-of-the-box, EPrints has creators with a name component, and an id <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>> component. The default name of this field is 'Email':<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>> <a href="https://github.com/eprints/eprints/blob/3.3/lib/lang/en/phrases/system"><span style='color:windowtext;text-decoration:none'>https://github.com/eprints/eprints/blob/3.3/lib/lang/en/phrases/system</span></a><o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>> .xml#L396<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>> I was thinking or using it to store the ORCiD instead of the email <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>> address, but didn't know if any 'best practice' was emerging yet?<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>Like lots of people have already said, I've just added an extra field to "creator" however Martin's point is well made: authors are not normalised across records - meaning the same [identical] name is listed for each record it appears in.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>This is, perhaps, something to feed into the EPrints 3.4 or 4.0 roadmap?<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>-- <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>Ian Stuart.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>Developer: ORI, RJ-Broker, and OpenDepot.org Bibliographics and Multimedia Service Delivery team, EDINA, The University of Edinburgh.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU><a href="http://edina.ac.uk/"><span style='color:windowtext;text-decoration:none'>http://edina.ac.uk/</span></a><o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>This email was sent via the University of Edinburgh.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-AU>*** Options: <a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech"><span style='color:windowtext;text-decoration:none'>http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</span></a><o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>*** Archive: <a href="http://www.eprints.org/tech.php/"><span style='color:windowtext;text-decoration:none'>http://www.eprints.org/tech.php/</span></a><o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>*** EPrints community wiki: <a href="http://wiki.eprints.org/"><span style='color:windowtext;text-decoration:none'>http://wiki.eprints.org/</span></a><o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-AU>*** EPrints developers Forum: <a href="http://forum.eprints.org/"><span style='color:windowtext;text-decoration:none'>http://forum.eprints.org/</span></a><o:p></o:p></span></p><pre><span lang=EN-AU><o:p> </o:p></span></pre><pre><span lang=EN-AU>_____________________________________________________________<o:p></o:p></span></pre><pre><span lang=EN-AU>This email (including any attached files) is confidential and is for the intended recipient(s) only. If you received this email by mistake, please, as a courtesy, tell the sender, then delete this email.<o:p></o:p></span></pre><pre><span lang=EN-AU><o:p> </o:p></span></pre><pre><span lang=EN-AU>The views and opinions are the originator's and do not necessarily reflect those of the University of Southern Queensland. Although all reasonable precautions were taken to ensure that this email contained no viruses at the time it was sent we accept no liability for any losses arising from its receipt.<o:p></o:p></span></pre><pre><span lang=EN-AU><o:p> </o:p></span></pre><pre><span lang=EN-AU>The University of Southern Queensland is a registered provider of education with the Australian Government.<o:p></o:p></span></pre><pre><span lang=EN-AU>(CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081 )<o:p></o:p></span></pre></div></body></html>