<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
From Chip Watson, FYI<br>
<div class="moz-forward-container"><br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" cellpadding="0"
cellspacing="0" border="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 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 class="moz-txt-link-rfc2396E" href="mailto:marki@jlab.org"><marki@jlab.org></a>, David Lawrence
<a class="moz-txt-link-rfc2396E" href="mailto:davidl@jlab.org"><davidl@jlab.org></a>, Graham Heyes
<a class="moz-txt-link-rfc2396E" href="mailto:heyes@jlab.org"><heyes@jlab.org></a>, Sandy Philpott
<a class="moz-txt-link-rfc2396E" href="mailto:sandy.philpott@jlab.org"><sandy.philpott@jlab.org></a>, Kari Heffner
<a 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>
</body>
</html>