UC-1.1

From Archivematica
Jump to: navigation, search


Main Page > Requirements > OAIS Use Cases > UC-1 Ingest > UC-1.1 Receipt of SIP

[edit] UC-1.1 Receipt of SIP

Summary
Number UC-1.1
Name Receipt of SIP
Context UC-1 Ingest
Sub-Use Cases None
Overview Producer or Administration>Archival Information Update transfers Submission Information Package (SIP) to Receive Submission. Receive Submission provides the appropriate storage capability or devices to receive a SIP.
Actors
  • Producer
  • Receive Submission
  • Administration>Archival Information Update
Description
Preconditions Establish a Submission Agreement with the Producer. Create a virtual Submission Agreement if necessary. (see OAIS, page 2-9, section 2.3.2)
Trigger A Data Submission Session is started by the Producer, OAIS or Management. (see OAIS, page 2-9, section 2.3.2)
Successful outcome Receive Submission sends SIP to Quality Assurance
Steps
  1. Producer (or Administration>Archival Information Update) transfers SIP to Receive Submission (OAIS Page 4-5, Section 4.1.1.2)
  2. Receive Submission provides the appropriate storage capability or devices to receive a SIP from Producer (OAIS Page 4-5, Section 4.1.1.2)
  3. Receive Submission transmits SIP to Quality Assurance (OAIS Figure 4-2:Functions of Ingest Page 4-5)
Exceptions
Documentation
Citations OAIS
  • Page 2-9, section 2.3.2: "The first contact between the OAIS and the Producer is a request that the OAIS reserve 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. Within the Submission Agreement, one or more Data Submission Sessions are specified. There may be significant time gaps between the Data Submission Sessions. A Data Submission Session will contain one or more SIPs and may be a delivered set of media or a single telecommunications session. The Data Submission Session content is based on a data model negotiated between the OAIS and the Producer in the Submission Agreement. This data model identifies the logical components of the SIP (e.g., the Content Information, PDI, Packaging Information, and Descriptive Information) that are to be provided and how (and whether) they are represented in each Data Submission Session. All data deliveries within a Submission Agreement are recognized as belonging to that Submission Agreement and will generally have a consistent data model, which is specified in the Submission Agreement. For example, a Data Submission Session may consist of a set of Content Information corresponding to a set of observations, which are carried by a set of files on a CD-ROM. The Preservation Description Information is split between two other files. All of these files need Representation Information which must be provided in some way. The CD-ROM and its directory/file structure are the Packaging Information, which provides encapsulation and identification of the Content Information and PDI in the Data Submission Session. The Submission Agreement indicates how the Representation Information for each file is to be provided, how the CD-ROM is to be recognized, how the Packaging Information will be used to identify and encapsulate the SIP Content Information and PDI, and how frequently Data Submission Sessions (e.g., one per month for two years) will occur. It also gives other needed information such as access restrictions to the data. Each SIP in a Data Submission Session is expected to meet minimum OAIS requirements for completeness. However, in some cases multiple SIPs may need to be received before an acceptable AIP can be formed and fully ingested within the OAIS. In other cases, a single SIP may contain data to be included in many AIPs. A Submission Agreement also includes, or references, the procedures and protocols by which an OAIS will either verify the arrival and completeness of a Data Submission Session with the Producer or question the Producer on the contents of the Data Submission Session."
  • Page 4-5, Section 4.1.1.2: "The Receive Submission function provides the appropriate storage capability or devices to receive a SIP from the Producer (or from Administration). Digital SIPs may be delivered via electronic transfer (e.g., FTP), loaded from media submitted to the archive, or simply mounted (e.g., CD-ROM) on the archive file system for access. ... The Receive Submission function may represent a legal transfer of custody for the Content Information in the SIP, and may require that special access controls be placed on the contents. This function provides a confirmation of receipt of a SIP to the Producer, which may include a request to resubmit a SIP in the case of errors resulting from the SIP submission."
Diagrams
Notes
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox