UC-4.1

Main Page > Vancouver Digital Archives > Requirements Analysis > UC-4 Administration

{| border="1" cellpadding="10" cellspacing="0" width=90%
 * colspan="4" style="background-color:silver;"|

UC-4.1 Negotiating Submission Agreement
Negotiating Submission Agreement UC-4 Administration None Producer and Negotiate Submission Agreement negotiate requirements for submitting SIPs; SIP is designed and sent to Audit Submission. Not triggered by an internal step. This use case is initiated the by the first contact between the OAIS and the Producer, the request that the OAIS preserve the data products created by the Producer (OAIS Page 2-9, s. 2.3.2). This contact may be initiated by the OAIS, the Producer or Management.
 * colspan="2" style="background-color:#E0FFFF;"|Summary
 * Number
 * UC-4.1
 * Name
 * UC-4.1
 * Name
 * Name
 * Context
 * Context
 * Sub-Use Cases
 * Sub-Use Cases
 * Overview
 * Overview
 * Actors
 * Audit Submission
 * Negotiate Submission Agreement
 * Producer
 * Preservation Planning>Develop Packaging Design and Migration Plans
 * colspan="2" style="background-color:#E0FFFF;"|Description
 * Preconditions
 * Data submission policies exist (UC-4.5 Step ??)
 * "The data submission formats and procedures must be clearly documented in the archive’s data submission policies, and the deliverables must be identified by the Producer in the Submission Agreement." [OAIS 4.1.1.5, Page 4-10]
 * Trigger
 * Preconditions
 * Data submission policies exist (UC-4.5 Step ??)
 * "The data submission formats and procedures must be clearly documented in the archive’s data submission policies, and the deliverables must be identified by the Producer in the Submission Agreement." [OAIS 4.1.1.5, Page 4-10]
 * Trigger
 * Trigger
 * Trigger
 * Successful outcome
 * SIP designed and agreed on by Producer and Negotiate Submission Agreement
 * Submission schedule agreed on by Producer and OAIS
 * Steps
 * 1) Negotiate Submission Agreement sends Submission Agreement(s) to Producer (OAIS Figure 4-5: Functions of Administration, Page 4-10)
 * 2) Negotiate Submission Agreement receives Submission Agreement(s) from Producer (OAIS Figure 4-5: Functions of Administration, Page 4-10)
 * 3) Negotiate Submission Agreement sends data submission schedule(s) to Producer (OAIS Figure 4-5: Functions of Administration, Page 4-10)
 * 4) Negotiate Submission Agreement receives data submission schedule(s) from Producer (OAIS Figure 4-5: Functions of Administration, Page 4-10)
 * 5) Negotiate Submission Agreement negotiates Submission Agreement(s) and data submission schedule(s) with Producer (OAIS Page 4-10)
 * 6) Negotiate Submission Agreement maintains a calendar of expected Data Submission Sessions that will be needed to transfer one or more SIPs to the OAIS and the resource requirements to support their ingestion (OAIS Page 4-10)
 * 7) Negotiate Submission Agreement receives AIP/SIP templates and customization advice from Preservation Planning>Develop Packaging & Migration Plans (OAIS Page 4-10)
 * 8) Negotiate Submission Agreement designs SIP (inferred from OAIS Page 4-10)
 * 9) Negotiate Submission Agreement sends SIP design(s) to Audit Submission as part of the submission approval process (OAIS Page 4-10)
 * 10) Negotiate Submission Agreement sends SIPs to Audit Submission as part of the submission approval process (OAIS Page 4-10)
 * 11) Negotiate Submission Agreement receives final ingest report from Audit Submission (OAIS Figure 4-5:Functions of Administration Page 4-10)
 * 1) Negotiate Submission Agreement designs SIP (inferred from OAIS Page 4-10)
 * 2) Negotiate Submission Agreement sends SIP design(s) to Audit Submission as part of the submission approval process (OAIS Page 4-10)
 * 3) Negotiate Submission Agreement sends SIPs to Audit Submission as part of the submission approval process (OAIS Page 4-10)
 * 4) Negotiate Submission Agreement receives final ingest report from Audit Submission (OAIS Figure 4-5:Functions of Administration Page 4-10)


 * Exceptions
 * colspan="2" style="background-color:#E0FFFF;"|Documentation
 * Citations
 * OAIS 4.1.1.5 (Page 4-10, 4-11) The Negotiate Submission Agreement function solicits desirable archival information for the OAIS and negotiates Submission Agreements with Producers. This function also negotiates a data submission schedule with the Producer. It maintains a calendar of expected Data Submission Sessions that will be needed to transfer one or more SIPs to the OAIS and the resource requirements to support their ingestion. This function receives AIP/SIP templates and customization advise from Preservation Planning and sends SIP designs and SIPs to the Audit Submission function as part of the submission approval process. The data submission formats and procedures must be clearly documented in the archive’s data submission policies, and the deliverables must be identified by the Producer in the Submission Agreement.
 * colspan="2" style="background-color:#E0FFFF;"|Documentation
 * Citations
 * OAIS 4.1.1.5 (Page 4-10, 4-11) The Negotiate Submission Agreement function solicits desirable archival information for the OAIS and negotiates Submission Agreements with Producers. This function also negotiates a data submission schedule with the Producer. It maintains a calendar of expected Data Submission Sessions that will be needed to transfer one or more SIPs to the OAIS and the resource requirements to support their ingestion. This function receives AIP/SIP templates and customization advise from Preservation Planning and sends SIP designs and SIPs to the Audit Submission function as part of the submission approval process. The data submission formats and procedures must be clearly documented in the archive’s data submission policies, and the deliverables must be identified by the Producer in the Submission Agreement.
 * OAIS 4.1.1.5 (Page 4-10, 4-11) The Negotiate Submission Agreement function solicits desirable archival information for the OAIS and negotiates Submission Agreements with Producers. This function also negotiates a data submission schedule with the Producer. It maintains a calendar of expected Data Submission Sessions that will be needed to transfer one or more SIPs to the OAIS and the resource requirements to support their ingestion. This function receives AIP/SIP templates and customization advise from Preservation Planning and sends SIP designs and SIPs to the Audit Submission function as part of the submission approval process. The data submission formats and procedures must be clearly documented in the archive’s data submission policies, and the deliverables must be identified by the Producer in the Submission Agreement.
 * OAIS 4.1.1.5 (Page 4-10, 4-11) The Negotiate Submission Agreement function solicits desirable archival information for the OAIS and negotiates Submission Agreements with Producers. This function also negotiates a data submission schedule with the Producer. It maintains a calendar of expected Data Submission Sessions that will be needed to transfer one or more SIPs to the OAIS and the resource requirements to support their ingestion. This function receives AIP/SIP templates and customization advise from Preservation Planning and sends SIP designs and SIPs to the Audit Submission function as part of the submission approval process. The data submission formats and procedures must be clearly documented in the archive’s data submission policies, and the deliverables must be identified by the Producer in the Submission Agreement.


 * OAIS 2.3.2 (Page 2-9) "The first contact between the OAIS and the Producer is a request that the OAIS preserve the data products created by the Producer. This contact may be initiated by the OAIS, the Producer or Management. The Producer establishes a Submission Agreement with the OAIS, which identifies the SIPs to be submitted and may span any length of time for this submission. Some Submission Agreements will reflect a mandatory requirement to provide information to the OAIS, while others will reflect a voluntary offering of information. Even in the case where no formal Submission Agreement exists, such as a World Wide Web (WWW) site, a virtual Submission Agreement may exist specifying the file formats and the general subject matter the site will accept."
 * Diagrams
 * colspan="2" style="background-color:#E0FFFF;"|Notes
 * Where does the SIP that Negotiate Submission Agreement sends to Audit Submission come from? *Negotiate Submission Agreement "maintains a calendar of . . . the resource requirements to support their ingestion". This information should be acted upon in some way in case additional resources need to be found for ingestion but that is not in the model.
 * It appears this function must design the SIP based on the templates and customization advice received from Preservation Planning>Develop Packaging & Migration Plans but this is not explicitly stated.
 * Preservation Planning>Develop Packaging & Migration Plans is responsible for developing "new IP designs." SIPs are a subset of these. from a functional perspective, I don't think (and I don't think it is the intent of the OAIS standard) that administration should be responsible for designing SIPs
 * }
 * Where does the SIP that Negotiate Submission Agreement sends to Audit Submission come from? *Negotiate Submission Agreement "maintains a calendar of . . . the resource requirements to support their ingestion". This information should be acted upon in some way in case additional resources need to be found for ingestion but that is not in the model.
 * It appears this function must design the SIP based on the templates and customization advice received from Preservation Planning>Develop Packaging & Migration Plans but this is not explicitly stated.
 * Preservation Planning>Develop Packaging & Migration Plans is responsible for developing "new IP designs." SIPs are a subset of these. from a functional perspective, I don't think (and I don't think it is the intent of the OAIS standard) that administration should be responsible for designing SIPs
 * }
 * Preservation Planning>Develop Packaging & Migration Plans is responsible for developing "new IP designs." SIPs are a subset of these. from a functional perspective, I don't think (and I don't think it is the intent of the OAIS standard) that administration should be responsible for designing SIPs
 * }