<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaTempEditStyle"></style><style title="owaParaStyle"><!--P {
MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px
}
--></style>
</head>
<body ocsi="x">
<div style="FONT-SIZE: 13px; FONT-FAMILY: Tahoma; COLOR: #000000; DIRECTION: ltr">
<div></div>
<div dir="ltr"><font color="#000000" size="2" face="Tahoma">Dear All,</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">Per Hilton's email below, indeed yes, I wish to see ORCID and DSpace-CRIS made core to future DSpace development.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">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.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">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.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">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.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">Hoping for more dance partners,</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">David Palmer</font></div>
<div dir="ltr"><font size="2" face="tahoma">The University of Hong Kong</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">From: Hilton Gibson <hilton.gibson@gmail.com><br>
To: "irtalk@lists.lib.sun.ac.za" <irtalk@lists.lib.sun.ac.za>,<br>
Duraspace <duraspace@lists.lib.sun.ac.za><br>
Subject: [Irtalk] Fwd: [Dspace-devel] Draft Agenda for Open<br>
Repositories 2013 DSpace Developers/DCAT Meeting<br>
Message-ID:<br>
<CAAV1Wv40RbjrH7a9GUj0Cabo9fzkrgngQcgGs=5WzHNZqV5OHg@mail.gmail.com><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</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"> </div>
</div>
</body>
</html>