<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style>
<!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
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
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
span.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
span.EmailStyle20
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:72.0pt 72.0pt 72.0pt 72.0pt}
div.WordSection1
{}
-->
</style>
</head>
<body lang="EN-ZA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> dtpalmer [mailto:dtpalmer@hku.hk]
<br>
<b>Sent:</b> 01 July 2013 11:05 PM<br>
<b>To:</b> dspace-general@lists.sourceforge.net; irtalk@lists.lib.sun.ac.za; duraspace@lists.lib.sun.ac.za<br>
<b>Cc:</b> dtpalmer; s.moranti@cineca.it<br>
<b>Subject:</b> Re: [Dspace-general] Draft Agenda for Open Repositories 2013 DSpace Developers/DCAT Meeting</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">Dear All,</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">Per Hilton's email below, indeed yes, I wish to see ORCID and DSpace-CRIS made core to future DSpace development.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">I've been scratching my head wondering how to get more traction for DSpace-CRIS within the DSpace community. After presenting on this topic at the ALA conference
this week in Chicago, I discussed the situation with colleagues here.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">Most libraries in the US run DSpace for publications of one sort or another. Author profile initiatives such as Vivo seem to be moving to depts other than the
library. Then Vivo for author profiles and DSpace for publications will remain separate systems, managed by different depts.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">However for most institutions, collecting, describing and contextualizing research objects beyond publications is still blue sky. Most institutions have not done
it yet. It is an area that libraries, already with a publication respository, could move into very easily now in these early days. The work we have done for DSpace-CRIS could facilitate.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">Hoping for more dance partners,</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">David Palmer</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">The University of Hong Kong</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">From: Hilton Gibson <<a href="mailto:hilton.gibson@gmail.com">hilton.gibson@gmail.com</a>><br>
To: "<a href="mailto:irtalk@lists.lib.sun.ac.za">irtalk@lists.lib.sun.ac.za</a>" <<a href="mailto:irtalk@lists.lib.sun.ac.za">irtalk@lists.lib.sun.ac.za</a>>,<br>
Duraspace <<a href="mailto:duraspace@lists.lib.sun.ac.za">duraspace@lists.lib.sun.ac.za</a>><br>
Subject: [Irtalk] Fwd: [Dspace-devel] Draft Agenda for Open<br>
Repositories 2013 DSpace Developers/DCAT Meeting<br>
Message-ID:<br>
<<a href="mailto:CAAV1Wv40RbjrH7a9GUj0Cabo9fzkrgngQcgGs=5WzHNZqV5OHg@mail.gmail.com">CAAV1Wv40RbjrH7a9GUj0Cabo9fzkrgngQcgGs=5WzHNZqV5OHg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi All<br>
<br>
Please review the agenda.<br>
I see the matter of researcher ID's is not on the agenda.<br>
How do we prove to researchers the impact of openness if we cannot properly<br>
identify them in the first place.<br>
I think this is crucial for advocacy in the long term.<br>
The CRIS module recently released by the HKU should be a core part of<br>
DSpace and so should ORCID ID's.<br>
If you agree then please send an email to:<br>
<a href="http://lists.sourceforge.net/lists/listinfo/dspace-general" target="_blank">http://lists.sourceforge.net/lists/listinfo/dspace-general</a> requesting these<br>
core additions to DSpace before the meeting.<br>
<br>
Cheers<br>
<br>
hg</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
</div>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
E-pos vrywaringsklousule Hierdie e-pos mag vertroulike inligting bevat en mag regtens geprivilegeerd wees en is slegs bedoel vir die persoon aan wie dit geadresseer is. Indien u nie die bedoelde ontvanger is nie, word u hiermee in kennis gestel dat u hierdie
dokument geensins mag gebruik, versprei of kopieer nie. Stel ook asseblief die sender onmiddellik per telefoon in kennis en vee die e-pos uit. Die Universiteit aanvaar nie aanspreeklikheid vir enige skade, verlies of uitgawe wat voortspruit uit hierdie e-pos
en/of die oopmaak van enige lêers aangeheg by hierdie e-pos nie. E-mail disclaimer This e-mail may contain confidential information and may be legally privileged and is intended only for the person to whom it is addressed. If you are not the intended recipient,
you are notified that you may not use, distribute or copy this document in any manner whatsoever. Kindly also notify the sender immediately by telephone, and delete the e-mail. The University does not accept liability for any damage, loss or expense arising
from this e-mail and/or accessing any files attached to this e-mail. <br>
</font>
</body>
</html>