UC-1

From Archivematica
Revision as of 17:58, 3 September 2009 by Evelyn McLellan (talk | contribs) (Created page with '__NOTOC__ Main Page > Requirements Analysis > UC-1 Ingest {| border="1" cellpadding="10" cellspacing="0" width=90% | colspan="4" style="background-color:silver;"| ===…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


Main Page > Requirements Analysis > UC-1 Ingest


UC-1 Ingest

Summary
Number UC-1
Name Ingest
Context N/A
Sub-Use Cases
Overview Producer sends Submission Information Package (SIP) to Receive Submission; Quality Assurance validates transfer of SIP to Receive Submission; Generate AIP prepares Archival Information Package (AIP); Generate Descriptive Infomation generates Descriptive Information; Co-ordinate Updates sends AIP to Archival Storage>Receive Data and Descriptive Information to Data Management>Receive Database Updates.
Actors
  • Coordinate Updates
  • Generate AIP
  • Generate Descriptive Information
  • Receive Submission
  • Quality Assurance
  • Administration>Archival Information Update
  • Administration>Audit Submission
  • Administrator
  • Archival Storage>Receive Data
  • Data Management>Generate Report
  • Data Management>Receive Database Updates
  • Producer
Description
Preconditions
  • Establish a Submission Agreement with the Producer. Create a virtual Submission Agreement if necessary. (OAIS, Page 2-9, section 2.3.2)
  • Establish a Data Submission Schedule with the Producer. (OAIS, Page 4-10, section 4.1.1.5)
Trigger A Data Submission Session is started by the Producer, OAIS or Management. (OAIS, Page 2-9, section 2.3.2)
Successful outcome Coordinate Updates submits Descriptive Information to Data Management>Receive Database Updates, sends AIP to Archival Storage>Receive Data and sends AIP to Archival Storage>Receive Data.
Steps
  1. Producer (or Administration>Archival Information Update) transfers SIP to Receive Submission
  2. Receive Submission transmits SIP to Generate AIP
  3. Quality Assurance validates the transfer of the SIP to Receive Submission
  4. Generate AIP extracts Content Information from SIP
  5. Generate AIP extracts Preservation Description Information (PDI) from SIP
  6. Generate AIP assembles AIP
  7. Generate AIP sends AIP to Coordinate Updates
  8. Generate AIP sends AIP to Generate Descriptive Information
  9. Generate Descriptive Information extracts Descriptive Information from AIP
  10. Generate Descriptive Information sends Descriptive Information to Coordinate Updates
  11. Coordinate Updates adds storage identification information to the Descriptive Information
  12. Coordinate Updates submits Descriptive Information to Data Management>Receive Database Updates along with a database update request
  13. Coordinate Updates sends AIP to Archival Storage>Receive Data
  14. Coordinate Updates submits Descriptive Information to Data Management>Receive Database Updates
Exceptions
  • Validation of SIP fails
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 preserve the data products created by the Producer. This contact may be initiated by the OAIS, the Producer or Management."
  • OAIS, page 4-1, section 4.1: "This entity provides the services and functions to accept Submission Information Packages (SIPs) from Producers (or from internal elements under Administration control) and prepare the contents for storage and management within the archive. Ingest functions include receiving SIPs, performing quality assurance on SIPs, generating an Archival Information Package (AIP) which complies with the archive’s data formatting and documentation standards, extracting Descriptive Information from the AIPs for inclusion in the archive database, and coordinating updates to Archival Storage and Data Management."
  • OAIS, page 4-10, section 4.1.1.5: "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 ngestion."
Diagrams
  • OAIS figure 4-2 (section 4.1.1.2)
OAIS fig. 4-2
Notes