<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="+1">The DOI can be looked up and from it you can obtain
a URL and other meta-data about the digital object. The URL is
intended to be very persistent, so think of it in simple terms as
pointing to a web page which is permanent, and that web page
contains instructions on how to pull it from (for example) the
JLab tape library (where files are essentially eternal).<br>
<br>
</font>
<div class="moz-cite-prefix">On 7/28/14 3:57 PM, Curtis A. Meyer
wrote:<br>
</div>
<blockquote cite="mid:6A1EBDA0-C6CB-4658-B7B0-C4CD32795BBB@cmu.edu"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
It would be useful of someone could explain this to us. I have
read through a number of the pages, but it is
<div>not real obvious what we will need to do. In particular, does
the fact that we give a data set a DOI mean that</div>
<div>anyone has access to it? Does it mean that we must maintain
it in the designated site forever? </div>
<div><br>
</div>
<div>Curtis</div>
<div><br>
</div>
<div><br>
<div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse:
separate; color: rgb(0, 0, 0); font-family: Helvetica;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; ">
<div>
<div>---------</div>
<div>Curtis A. Meyer<span class="Apple-tab-span"
style="white-space: pre; "> </span>MCS Associate Dean
for Faculty and Graduate Affairs</div>
<div>Wean: (412) 268-2745<span class="Apple-tab-span"
style="white-space: pre; "> </span>Professor of
Physics</div>
<div>Doherty: (412) 268-3090<span class="Apple-tab-span"
style="white-space: pre; "> </span>Carnegie Mellon
University</div>
<div>Fax: (412) 681-0648<span
class="Apple-tab-span" style="white-space: pre; "> </span>Pittsburgh,
PA 15213</div>
<div><a moz-do-not-send="true"
href="mailto:curtis.meyer@cmu.edu">curtis.meyer@cmu.edu</a><span
class="Apple-tab-span" style="white-space: pre; "> </span><a class="moz-txt-link-freetext" href="http://www.curtismeyer.com/">http://www.curtismeyer.com/</a></div>
</div>
<div><br>
</div>
</span><br class="Apple-interchange-newline">
</div>
<br>
<div>
<div>On Jul 28, 2014, at 1:44 PM, Mark M. Ito <<a
moz-do-not-send="true" href="mailto:marki@jlab.org">marki@jlab.org</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<div bgcolor="#FFFFFF" text="#000000"> From Chip Watson, FYI<br>
<div class="moz-forward-container"><br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0"
cellpadding="0" cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap"
valign="BASELINE">Subject: </th>
<td>Data Management Plans</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap"
valign="BASELINE">Date: </th>
<td>Mon, 28 Jul 2014 11:20:18 -0400</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap"
valign="BASELINE">From: </th>
<td>Chip Watson <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:watson@jlab.org"><watson@jlab.org></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap"
valign="BASELINE">To: </th>
<td>Mark Ito <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:marki@jlab.org"><marki@jlab.org></a>,
David Lawrence <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:davidl@jlab.org"><davidl@jlab.org></a>,
Graham Heyes <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:heyes@jlab.org"><heyes@jlab.org></a>,
Sandy Philpott <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sandy.philpott@jlab.org"><sandy.philpott@jlab.org></a>,
Kari Heffner <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:heffner@jlab.org"><heffner@jlab.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<font size="+1">All,<br>
<br>
Effective Oct 1, all new proposals for funding to NP
will require Data Management Plans (DMP) that meet a
set of requirements. Here is the announcement and
base document:<br>
<br>
<a moz-do-not-send="true"
href="http://science.energy.gov/funding-opportunities/digital-data-management/">http://science.energy.gov/funding-opportunities/digital-data-management/</a><br>
<br>
This document references additional documents (tree
like) and these following web pages should all be
read:<br>
<br>
NP: <a moz-do-not-send="true"
href="http://science.energy.gov/np/funding-opportunities/digital-data-management/">http://science.energy.gov/np/funding-opportunities/digital-data-management/</a><br>
(this document references JLab's document)<br>
<br>
<a moz-do-not-send="true"
href="http://science.energy.gov/funding-opportunities/digital-data-management/suggested-elements-for-a-dmp/">http://science.energy.gov/funding-opportunities/digital-data-management/suggested-elements-for-a-dmp/</a><br>
<br>
<a moz-do-not-send="true"
href="http://science.energy.gov/funding-opportunities/digital-data-management/faqs/">http://science.energy.gov/funding-opportunities/digital-data-management/faqs/<br>
</a><br>
One component not yet addressed in the JLab / GlueX
data management plans is providing unique identifiers
to particular data sets, and how to find and download
data of interest. So far we have documented
principles, but not details on how to get to the data
and how to reference particular data. I believe that
this scope must eventually be addressed in the JLab/IT
and /GlueX documents. DOE is offering a Digital
Object Identifier service:<br>
<br>
<a moz-do-not-send="true"
href="https://www.osti.gov/elink/aboutDataIDService.jsp">https://www.osti.gov/elink/aboutDataIDService.jsp<br>
</a><br>
The OSTI web page suggests this could point to a
landing page with additional links to data
components. So, we need to plan how we want to manage
DOI's and landing pages, and what ability to download
data we want to grant to outsiders (non-JLab users,
presumably).<br>
<br>
Since GlueX is up first, I would like you to take the
lead in working through this one. Everyone on this
email distribution can have a role to play and should
think about a path forward. I suggest that we have a
joint meeting later this month when everyone is
available. Please reply or reply/all to suggest a
replacement if you would like to delegate this to
someone else or don't feel you are the appropriate
person, and perhaps suggest which week in August would
be good for you.<br>
<br>
Chip<br>
<br>
<br>
</font> <br>
</div>
<br>
</div>
_______________________________________________<br>
Halld-offline mailing list<br>
<a moz-do-not-send="true"
href="mailto:Halld-offline@jlab.org">Halld-offline@jlab.org</a><br>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/halld-offline">https://mailman.jlab.org/mailman/listinfo/halld-offline</a></blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Halld-offline mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Halld-offline@jlab.org">Halld-offline@jlab.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/halld-offline">https://mailman.jlab.org/mailman/listinfo/halld-offline</a></pre>
</blockquote>
<br>
</body>
</html>