<div dir="ltr">See comments <font color="#ff0000">below.</font><br><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Mark Conrad<br>NARA Information Services</div>
<div>Systems Engineering Division (IT)<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></div></div>
<br><div class="gmail_quote">On Mon, Jun 11, 2018 at 5:26 AM, david <span dir="ltr"><<a href="mailto:david@giaretta.org" target="_blank">david@giaretta.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-m_-6784099864281630584WordSection1"><p class="MsoNormal">Action from <span class="gmail-m_-6784099864281630584SpellE">Webex</span> 20180605<u></u><u></u></p><ol style="margin-top:0cm" start="1" type="1"><li class="MsoNormal"><span>David to write an example of the application of OAIS preservation concepts to components of PDI including illustration of Ingest and recursion.<u></u><u></u></span></li></ol><p class="MsoNormal"><span><u></u> <u></u></span></p><p class="MsoNormal"><span><u></u> <u></u></span></p><p class="MsoNormal">A Producer – in this case outside the OAIS <font color="#ff0000">A Producer is a role that can be played by an internal or external source. However the role is always outside the OAIS. See Figure 2-1 and Section 2-1 "Outside the OAIS are Producers, Consumers, and Management."</font> – wishes to submit information to be preserved by the OAIS. Agreement has been reached on the procedures to be followed. The Producer prepares one or more SIPs which are transferred to the OAIS.</p><p class="MsoNormal"><u></u></p><ul style="margin-top:0cm" type="disc"><li class="MsoNormal">A Receive Submission function receives the <span class="gmail-m_-6784099864281630584GramE">SIP, and</span> acknowledges the receipt or requests a re-submission if there is an error, for example as reported by Quality Assurance.<u></u><u></u></li><li class="MsoNormal">The SIP (or the collection of SIPs together) contains the Content Information (Data Object and Representation Information), plus PDI and may also provide Information Property Descriptions of Information Properties. <font color="#ff0000">According to the current definition, Information Properties (Description?) is part of the Content Information.</font><u></u><u></u></li><li class="MsoNormal">The AIP is generated by a Generate AIP function from the SIP(s)<font color="#ff0000"> This is not specific enough to evaluate your proposal. What is in the SIPs? How are they transformed/mapped to produce the AIP?</font> with any additional Representation Information required <font color="#ff0000">Isn't the additional Representation Information part of the AIP?</font>. I think that logically we can say that it may also produce Fixity Information<font color="#ff0000"> If you are forming an AIP this is required.</font>, as part of verifying the transfer or if some file format conversions have taken place. Additional Provenance should be created to record the fact that the information has been taken into the OAIS <font color="#ff0000">Required if you are creating an AIP</font>. Some additional Context may be <span class="gmail-m_-6784099864281630584GramE">created <font color="#ff0000">Required if you are making an AIP/</font></span> and Reference Information will also be created to allow the Content Information to be found. The Packaging Information will be determined by the structure of the AIP which the OAIS has decided to use. Note that an AIP is defined as a logical container.<u></u><u></u></li><li class="MsoNormal">The associated Descriptive Information is created by Generate Descriptive Information.<u></u><u></u></li><li class="MsoNormal">Coordinate Updates transfers the AIP to Archival Storage and the Descriptive Information to Data Management. <u></u><u></u></li></ul><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">The OAIS will need to preserve the PDI. Let us see how the each of the components of PDI is preserved. Let us say that the Fixity is encoded as a hash code <font color="#ff0000">Are you assuming all of the PDI is in a single file?</font>, <font color="#ff0000">f</font>or example the Data for which is a sequence of bits which encode ASCII characters. <u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">The following runs through a likely process, mapping it to the Ingest Functional Entity.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">A Producer – in this case inside the OAIS <font color="#ff0000">No. </font><span style="color:rgb(255,0,0);font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">A Producer is a role that can be played by an internal or external source. However the role is always outside the OAIS. See Figure 2-1 and Section 2-1 "Outside the OAIS are Producers, Consumers, and Management."</span>
– wishes to submit information to be preserved by the OAIS. Agreement has been reached on the internal procedures to be followed. The Producer prepares one or more SIPs which are transferred to the OAIS - in this case this is an internal transfer. <font color="#ff0000">No. Producers are outside the OAIS so their submissions come from outside the OAIS.</font><u></u><u></u></p><ul style="margin-top:0cm" type="disc"><li class="MsoNormal">In this case the SIP would contain the hash code. <u></u><u></u></li></ul><ul style="margin-top:0cm" type="disc"><li class="MsoNormal" style="margin-left:18pt">The Representation Information will probably be the same for many examples of Fixity if the OAIS uses the same method for many pieces of data; for <span class="gmail-m_-6784099864281630584GramE">example</span> the RepInfo could be (1) Structure: ASCII code to go from bits (2) Semantic: SHA256 was used to create the hash. <span class="gmail-m_-6784099864281630584GramE">Therefore</span> there needs only to be a pointer to the RepInfo for the hash. <u></u><u></u></li><li class="MsoNormal" style="margin-left:18pt">The Provenance would be that this was created at a <span class="gmail-m_-6784099864281630584GramE">particular time, <font color="#ff0000">who created it as part of what business proccess and what file the hash is associated with. </font></span>. The hash would have been created either by the external Producer or the OAIS. In the latter case one would only need to point to a single statement that the OAIS created the hash. <font color="#ff0000">No. You also need to know when it was created and what business process included the generation of the hash value, what file it was generated from, etc.</font><u></u><u></u></li><li class="MsoNormal" style="margin-left:18pt">The Reference Information provides the location where the hash may be retrieved – unique for each hash – surely each hash will have such a reference otherwise how can it be retrieved?<u></u><u></u></li><li class="MsoNormal" style="margin-left:18pt">The Access Rights would again be the same for things that are being preserved – no-one <span class="gmail-m_-6784099864281630584GramE">is allowed to</span> alter the hash. <u></u><u></u></li><li class="MsoNormal" style="margin-left:18pt">The Context would be that the hash is created as part of the OAIS preservation functionality.<u></u><u></u></li></ul><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">All the things (RepInfo, Provenance creator, Access Rights, Context) which are the same for all, or lots of similar, things, could be contained in the documentation about the process. <font color="#ff0000">What does this mean?</font><u></u><u></u></p><p class="MsoNormal"><span> </span><u></u><u></u></p><ul style="margin-top:0cm" type="disc"><li class="MsoNormal">The Receive Submission (possibly different from the one used for SIPs from the external Producer) function receives the SIP, and acknowledges the receipt or requests a re-submission if there is an error, for example as reported by Quality Assurance. One might expect these may be taken care of by the normal computing infrastructure since it is an internal transfer. <font color="#ff0000">No. All submissions are treated as external submissions. See Section 2.1.</font><u></u></li><li class="MsoNormal">The SIP(s) contains the Content Information (Data Object and Representation Information), plus PDI and may also provide Information Property Descriptions of Information Properties. <u></u><u></u></li><li class="MsoNormal">The AIP is generated by a Generate AIP function from the SIP(s) with any additional Representation Information required.<font color="#ff0000">You are not providing sufficient detail to evaluate your proposal. </font> Again the Generate AIP function may be different from the one used for information from n external Producer. It should also produce Fixity Information, as part of verifying the transfer or if some file format conversions have taken place. Additional Provenance should be created to record the fact that the information has been taken into the OAIS. Some additional Context may be <span class="gmail-m_-6784099864281630584GramE">created</span> and Reference Information will also be created to allow the Content Information to be found. <font color="#ff0000">All the elements you have identified in the previous sentences are mandatory if you are generating an AIP.</font> The Packaging Information will be determined by the structure of the AIP which the OAIS has decided to use. Note that an AIP is defined as a logical container.<u></u><u></u></li><ul style="margin-top:0cm" type="circle"><li class="MsoNormal">As noted above, many of the components of the AIP would be common to many things and could be covered by a procedures document <font color="#ff0000">What is this procedures document in OAIS terminology? </font>. The Packaging Information could be contained in a procedures document which essentially just has to say where all the components of the AIP are to be found.<u></u><u></u></li></ul><li class="MsoNormal">The associated Descriptive Information is created by Generate Descriptive Information.<u></u><u></u></li><ul style="margin-top:0cm" type="circle"><li class="MsoNormal">This again could be covered by a procedures document.<u></u><u></u></li></ul><li class="MsoNormal">Coordinate Updates transfers the AIP to Archival Storage and the Descriptive Information to Data Management. <u></u><u></u></li></ul><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">As the next level of <span class="gmail-m_-6784099864281630584GramE">iteration</span> one can work through the RepInfo or PDI of the procedures documents mentioned above – for example a Word file, written in English, written by a member of the OAIS staff and finalised at a specified time.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">I hope it can be understood that the view that I take, re-using OAIS Information concepts repeatedly, does not lead to a plethora of confusing AIPs <font color="#ff0000">See my questions below.</font> but instead allows us to be logically coherent in our approach to preservation by simply mapping what I would imagine any good repository would normally be doing, or, alternatively, to check that a repository _<i>is</i>_ doing the right things. To confirm this all you <span class="gmail-m_-6784099864281630584GramE">have to</span> do is to go through the above steps and ask yourself whether any steps (or some equivalent steps since we are implementation agnostic) can be missed out.</p></div></div></blockquote><div><br></div><div><font color="#ff0000">How do you map the AIPs created by the OAIS in the role of the Producer to the components of the first AIP generated from the original Content Information? For example, if the the Fixity Information in the second AIP generated is the Fixity Information for one or more components of the original AIP, how is that reflected in the original AIP? How is this mapping created for each of the subsequent iterations of AIP generation? </font></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-m_-6784099864281630584WordSection1"><p class="MsoNormal">Regards</p><span class="gmail-HOEnZb"><font color="#888888"><p class="MsoNormal">David</p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p></font></span></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></div>