<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Consolas, monospace" size="2">
<div>*** Apologies for cross posting ***</div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D"> </font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D">Dear all</font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D"> </font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D">Many thanks to those of you who replied on and off list to the RoaDMaP project enquiry about different levels of access to research data. There was a lot of interest in the topic; of course, providing
granular access raises several issues. We have collated the responses so far here:</font></div>
<div><font face="Calibri, sans-serif" size="2"><a href="http://bit.ly/1adI6jT"><font face="Calibri, sans-serif" color="#0000FF"><u>http://bit.ly/1adI6jT</u></font></a><font face="Calibri, sans-serif" color="#1F497D"> </font></font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D"> </font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D">We are putting together use cases and potential workflows to take forward the discussions & will share these for comment soon. </font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D"> </font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D">Best wishes</font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D"> </font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D">Rachel</font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D"> </font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D">***<br>
Rachel Proudfoot<br>
Project Manager</font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D">RoaDMaP: Leeds Research Data Management Pilot<br>
<a href="http://library.leeds.ac.uk/roadmap-project">http://library.leeds.ac.uk/roadmap-project</a>
<br>
Tel: 0113 343 4554</font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D"> </font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D"> </font></div>
<div><font face="Calibri, sans-serif" size="2" color="#1F497D"> </font></div>
<div><font face="Tahoma, sans-serif" size="2">_____________________________________________<br>
<b>From:</b> Rachel Proudfoot <br>
<b>Sent:</b> 08 May 2013 16:27<br>
<b>To:</b> JISCMRD@JISCMAIL.AC.UK<br>
<b>Subject:</b> Controlled access to data in EPrints</font></div>
<div><font face="Calibri, sans-serif" size="2"> </font></div>
<div><font face="Calibri, sans-serif" size="2"> </font></div>
<div>*** Apologies for cross posting ***</div>
<div> </div>
<div>Dear colleagues</div>
<div> </div>
<div>We are looking at how to manage temporary or longer term restricted access to data within an institutional research data repository. Our starting point is that, where possible, data should be made openly available with as few restrictions as possible.
However, we're aware that there are various reasons why it may not be possible - or appropriate - to share data openly.</div>
<div> </div>
<div>We are piloting EPrints for research data. We need the means to create different access levels within EPrints which can then be assigned to users.</div>
<div> </div>
<div>Broadly, we're looking at an access model where research data can be:</div>
<div> </div>
<div>(i) Public - openly available without any registration requirement</div>
<div> </div>
<div>(ii) Registered - the user is required to register to access content; this could be linked to authentication protocols such as Shibboleth. Access may be time limited.</div>
<div> </div>
<div>(iii) Approved – the potential user makes a case to use the data; approval relates to specified data within the repository. Access may be time limited.</div>
<div> </div>
<div>(iv) Embargoed – metadata and data held in the dark for a specific period</div>
<div> </div>
<div>We are interested in whether other institutions are planning - or have put in practice - granular access to research data and what this looks like. </div>
<div> </div>
<div>We would also like to feed back requirements to Southampton EPrints Services; if we can scope requirements before July, Leeds has funds to put towards development costs. </div>
<div> </div>
<div>Is anyone else interested in this functionality?</div>
<div> </div>
<div>Thanks for any comments</div>
<div> </div>
<div>Best wishes</div>
<div> </div>
<div>Rachel</div>
<div> </div>
<div>***</div>
<div>Rachel Proudfoot</div>
<div>Project Manager</div>
<div>RoaDMaP: Leeds Research Data Management Pilot</div>
<div><a href="http://library.leeds.ac.uk/roadmap-project">http://library.leeds.ac.uk/roadmap-project</a> </div>
<div>Tel: 0113 343 4554</div>
<div> </div>
<div> </div>
<div> </div>
</font>
</body>
</html>