<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
For the action items, please find the following examples of
documents to be managed during each project phase and share any
suggestions for improvement.<br>
<br>
3.2.1 Project Initiation<br>
<br>
Examples of documents to begin managing during project initiation
include the list of project participants and organizations
represented,<br>
the criteria for repositories where the project data and
documentation will be preserved, agreements among participants
regarding authorship ownership of intellectual property produced by
the project as well as relevant policies of participating
organizations regarding such rights, ... .<br>
<br>
3.2.2 Project Planning<br>
<br>
Examples of documents to be managed during project planning include
the project management plan, the communication plan, the risk
management plan, assignments for roles and responsibilities of team
members, the list of project deliverables, the list of candidate
repositories and how they meet the established criteria for managing
data and documents produced by the project, ... .<br>
<br>
3.2.3 Project Execution<br>
<br>
Examples of documents to be managed during project execution include
signed contracts, approvals received from stakeholders or other
authorities, and ... <br>
<br>
3.2.4 Project Closing <br>
<br>
Examples of documents to be managed during project closing include
invoices, signed acceptances, procurement documents, evidence of
payments received, and ... . <br>
<br>
3.2.5 Project Monitoring and Controlling<br>
<br>
Examples of documents to be managed during project monitoring and
closing include Configuration Change Requests and other documents
describing proposed changes, documented decisions of the Change
Management Board or other decision bodies, ...<br>
<br>
Thanks,<br>
<br>
Robert R. Downs, PhD<br>
Senior Digital Archivist and Senior Staff Associate Officer of
Research<br>
Acting Head of Cyberinfrastructure and Informatics Research and
Development<br>
Center for International Earth Science Information Network (CIESIN),<br>
The Earth Institute, Columbia University<br>
P.O. Box 1000, 61 Route 9W, Palisades, NY 10964 USA<br>
Voice: 845-365-8985; fax: 845-365-8922<br>
E-mail: <a class="moz-txt-link-abbreviated" href="mailto:rdowns@ciesin.columbia.edu">rdowns@ciesin.columbia.edu</a><br>
Columbia University CIESIN Web site: <a class="moz-txt-link-freetext" href="http://www.ciesin.columbia.edu">http://www.ciesin.columbia.edu</a><br>
ORCID: 0000-0002-8595-5134 <br>
<br>
<div class="moz-cite-prefix">On 7/5/2016 11:27 AM, Mark Conrad
wrote:<br>
</div>
<blockquote
cite="mid:CAB===VyoGS+nmwBqSTx7O=vpVSmKAG0ubsyg38f26mSy7WmJ_A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Present: John Garrett, Mike Kearney, Robert Downs, Terry
Longstreth, Mark Conrad</div>
<div><br>
</div>
We discussed section 3.2.
<div><br>
</div>
<div>I came up with the following set of points that we need to
be sure to make explicit in this document:
<div><br>
</div>
<div>
<div>During the course of a project you are likely to create
the following types of additional information</div>
<div><br>
</div>
<div>a. If you are not creating this additional information,
you should be.</div>
<div><br>
</div>
<div>b. You should create this additional information in a
responsible manner.</div>
<div><br>
</div>
<div>c. This additional information should be preserved with
the data you are producing.</div>
<div><br>
</div>
<div><br>
</div>
<div>Bob Downs came up with the following points related
specifically to data management and data management plans:</div>
<div><br>
</div>
<div>
<div>Data Management Plan is created at the beginning of
the project.</div>
<div><br>
</div>
<div>Organizational policies related to data management.</div>
<div><br>
</div>
<div>Potential repositories</div>
<div><br>
</div>
<div>Intellectual property rights</div>
<div><br>
</div>
<div>Access to the data</div>
<div><br>
</div>
<div>Will you make the software available</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Action: All</div>
<div>The group decided that it would be a good idea to come
up with a list of example documents that might be created
for each process group in sections 3.2.1 - 3.2.5.</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>Mark Conrad<br>
NARA Information Services</div>
<div>IAS<br>
The National Archives and Records
Administration<br>
Erma Ora Byrd Conference and Learning Center<br>
Building 494, Room 225<br>
610 State Route 956<br>
Rocket Center, WV 26726<br>
<br>
Phone: 304-726-7820<br>
Fax: 304-726-7802<br>
Email: <a moz-do-not-send="true"
href="mailto:mark.conrad@nara.gov"
target="_blank">mark.conrad@nara.gov</a> <br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Moims-dai mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Moims-dai@mailman.ccsds.org">Moims-dai@mailman.ccsds.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai</a>
</pre>
</blockquote>
<br>
</body>
</html>