<div dir="ltr">"<b style="font-size:13.3333px;background-color:rgb(242,242,242)"><span style="color:red"> both during the mission lifetime, and in long-term archives post-mission.</span></b><span style="font-size:13.3333px;color:red;background-color:rgb(242,242,242)"> "</span><div><span style="font-size:13.3333px;color:red;background-color:rgb(242,242,242)"><br></span></div><div><span style="font-size:13.3333px;color:red;background-color:rgb(242,242,242)">If the mission is more than a few years long, they will probably need long-term archives during the mission.</span></div></div><div class="gmail_extra"><br clear="all"><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 href="mailto:mark.conrad@nara.gov" target="_blank">mark.conrad@nara.gov</a> <br><br></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Wed, Sep 14, 2016 at 8:07 AM, Mike Kearney <span dir="ltr"><<a href="mailto:kearneysolutions@gmail.com" target="_blank">kearneysolutions@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="#0563C1" vlink="#954F72"><div><p class="MsoNormal"><a name="m_-5582551412819744312__MailEndCompose"><span style="color:#1f497d">It would probably be good to tell them a from/to statement… you have explained the background, but you don’t quite tell them what you want the document to say. Something like this? <u></u><u></u></span></a></p><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><p><span lang="EN-GB"><u></u> <u></u></span></p><table border="0" cellspacing="0" cellpadding="0" width="784" style="width:588.25pt;margin-left:35.2pt;border-collapse:collapse"><tbody><tr><td width="432" valign="top" style="width:323.7pt;border:solid windowtext 1.0pt;background:red;padding:0in 5.4pt 0in 5.4pt"><p class="MsoNormal"><b><span lang="EN-CA" style="font-size:12.0pt">Integration levels<u></u><u></u></span></b></p><p class="MsoNormal"><b><span lang="EN-CA" style="font-size:12.0pt">Archiving<u></u><u></u></span></b></p></td><td width="353" valign="top" style="width:264.55pt;border:solid windowtext 1.0pt;border-left:none;background:#acb9ca;padding:0in 5.4pt 0in 5.4pt"><p class="MsoNormal"><b><span lang="EN-CA" style="font-size:12.0pt">Degree<u></u><u></u></span></b></p><p class="MsoNormal"><b><span lang="EN-CA" style="font-size:12.0pt">of Interoperability<u></u><u></u></span></b></p></td></tr><tr style="height:31.25pt"><td width="432" valign="top" style="width:323.7pt;border:solid windowtext 1.0pt;border-top:none;background:#f2f2f2;padding:0in 5.4pt 0in 5.4pt;height:31.25pt"><p style="margin-left:0in"><span lang="EN-CA" style="font-size:10.0pt">Ops, engineering <b><span style="color:red">and science</span></b><span style="color:red"> </span>teams from various space agencies need to integrate their data in a<b><span style="color:red">n</span></b> <s>common</s> archive <b><span style="color:red">or set of archives,</span></b><span style="color:red"> </span>and update/retrieve from <b><span style="color:red">them, both during the mission lifetime, and in long-term archives post-mission.</span></b><span style="color:red"> </span><u></u><u></u></span></p></td><td width="353" valign="top" style="width:264.55pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;background:#f2f2f2;padding:0in 5.4pt 0in 5.4pt;height:31.25pt"><p class="MsoNormal"><span lang="EN-CA" style="font-size:10.0pt">Agreed common data formats (data standard), agreements on metadata content, <s>central archive server and clients. </s><b><span style="color:red">compliance with long-term digital preservation practices, such as CCSDS standards for OAIS, PAIS and future protocol-level standards yet to be developed by CCSDS. </span></b><u></u><u></u></span></p></td></tr></tbody></table><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#1f497d">I think they might contest the need to share long-term archives of engineering and ops data post-mission, so I added Science teams to their list… that’s clearly not contestable. <u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#1f497d">Also, I don’t know why they said they had to agree on a central archive server and clients. Distributed archives would work also. Don’t think that should be necessary for archive interoperability. So I scratched it out. Am I missing something? Also scratched out “common” archive in the left box and suggested “an archive or set of archives”. Seems like a “common, central” archive is old-school and constraining. <u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><div><p class="MsoNormal"><span style="color:#1f497d"> -=- Mike<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#1f497d">Mike Kearney<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1f497d">Huntsville, Alabama, USA<u></u><u></u></span></p></div><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b>From:</b> MOIMS-DAI [mailto:<a href="mailto:moims-dai-bounces@mailman.ccsds.org" target="_blank">moims-dai-bounces@<wbr>mailman.ccsds.org</a>] <b>On Behalf Of </b>David Giaretta<br><b>Sent:</b> Tuesday, September 13, 2016 4:31 PM<br><b>To:</b> 'MOIMS-Data Archive Ingestion' <<a href="mailto:moims-dai@mailman.ccsds.org" target="_blank">moims-dai@mailman.ccsds.org</a>><br><b>Subject:</b> [Moims-dai] Draft responses to MOSSG<u></u><u></u></p></div></div><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><span lang="EN-GB">As discussed at the DAI webex today, here is a collection of comments on the MOSSG paper. Any last updates?<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB">..David<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p><p><u></u><span lang="EN-GB"><span>1)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB">Although the paper states “Archive ingestion is not considered part of the IOAG interoperability goals.”, nevertheless as is recognised in “However, the assumption is that there are mechanisms for archive ingestion implemented”, it will not be possible to get data out of an archive unless data is ingested into it. MOIMS-DAI covers data ingest and should be mentioned in the document, for example CCSDS 651.1-B-1, Producer-Archive Interface Specification (PAIS). Blue Book. Issue 1. February 2014.<u></u><u></u></span></p><p><u></u><span lang="EN-GB"><span>2)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB">The use of the word archive is misleading. What is discussed in most of the document is what might be termed “short-term storage”. For example, the Service Description of the kind “Archive of Agency Y is accessed by Agency X to…”, which implies simple access to the bits which have been stored. Interoperability normally means being able to use the bits. <u></u><u></u></span></p><p><span lang="EN-GB">The MOIMS-DAI work on archives is about maintaining the usability of the bits. <u></u><u></u></span></p><p><span lang="EN-GB">If agencies X and Y use the same format and semantics for the bits then there is no problem. If one the other hand they do not then agency X will need additional information. This may be relevant if there is a long time between the creation of the data by Agency Y and the use by Agency X. It may also be relevant if there is very little time between creation and use, for example if the agencies use different systems. <u></u><u></u></span></p><p><span lang="EN-GB">This is recognised in slide 29 in the PowerPoint presentation which has, at the top level:<u></u><u></u></span></p><p><span lang="EN-GB"><u></u> <u></u></span></p><table border="0" cellspacing="0" cellpadding="0" width="784" style="width:588.25pt;margin-left:35.2pt;border-collapse:collapse"><tbody><tr><td width="432" valign="top" style="width:323.7pt;border:solid windowtext 1.0pt;background:red;padding:0in 5.4pt 0in 5.4pt"><p class="MsoNormal"><b><span lang="EN-CA" style="font-size:12.0pt">Integration levels<u></u><u></u></span></b></p><p class="MsoNormal"><b><span lang="EN-CA" style="font-size:12.0pt">Archiving<u></u><u></u></span></b></p></td><td width="353" valign="top" style="width:264.55pt;border:solid windowtext 1.0pt;border-left:none;background:#acb9ca;padding:0in 5.4pt 0in 5.4pt"><p class="MsoNormal"><b><span lang="EN-CA" style="font-size:12.0pt">Degree<u></u><u></u></span></b></p><p class="MsoNormal"><b><span lang="EN-CA" style="font-size:12.0pt">of Interoperability<u></u><u></u></span></b></p></td></tr><tr style="height:31.25pt"><td width="432" valign="top" style="width:323.7pt;border:solid windowtext 1.0pt;border-top:none;background:#f2f2f2;padding:0in 5.4pt 0in 5.4pt;height:31.25pt"><p style="margin-left:0in"><span lang="EN-CA" style="font-size:10.0pt">Ops and engineering teams from various space agencies need to integrate their data in a common archive and update/retrieve from it<u></u><u></u></span></p></td><td width="353" valign="top" style="width:264.55pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;background:#f2f2f2;padding:0in 5.4pt 0in 5.4pt;height:31.25pt"><p class="MsoNormal"><span lang="EN-CA" style="font-size:10.0pt">Agreed common data formats (data standard), agreements on metadata content, central archive server and clients<u></u><u></u></span></p></td></tr></tbody></table><p><span lang="EN-GB"><u></u> <u></u></span></p><p><span lang="EN-GB">There are several problems with the right hand side:<u></u><u></u></span></p><p style="margin-left:.75in"><u></u><span lang="EN-GB"><span>a)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB">Agreeing formats is not adequate. For example the agencies could agree to use CSV – but what do the elements mean? what are the units? Is agency X going to combine something measured in meters with something measured in feet? In other words what metadata content is needed? This is what DAI is concerned with.<u></u><u></u></span></p><p style="margin-left:.75in"><u></u><span lang="EN-GB"><span>b)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB">If Agency X wants the data from Agency Y after Y’s project has ended, can one be sure that the right metadata has been collected? MOIMS-DAI is working on “INFORMATION PREPARATION TO ENABLE LONG TERM USE” to create a checklist to help ensure that enough of the right kinds of metadata is collected. Of course ensuring the data continues to be usable despite the inevitable changes over time in software, systems, semantics etc., is covered by CCSDS 650.0-M-2, Reference Model for an Open Archival Information System (OAIS). Magenta Book. Issue 2. June 2012.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p></div></div><br>______________________________<wbr>_________________<br>
MOIMS-DAI mailing list<br>
<a href="mailto:MOIMS-DAI@mailman.ccsds.org">MOIMS-DAI@mailman.ccsds.org</a><br>
<a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai" rel="noreferrer" target="_blank">https://mailman.ccsds.org/cgi-<wbr>bin/mailman/listinfo/moims-dai</a><br>
<br></blockquote></div><br></div>