Release 0.1 Documentation

Main Page > Documentation > Release 0.1 Documentation

UC1 Ingest

Use Case	Implementation	Notes
UC1.1 Receipt of SIP
UC1.1 Step 1. Producer (or Administration>Archival Information Update) transfers SIP to Receive Submission (OAIS Page 4-5, Section 4.1.1.2)	Producer places the SIP in the ingest folder: /home/qubituser/ingest/.	The LiveDVD has a SIP consisting of test files in this folder.
UC1.1 Step 2. Receive Submission provides the appropriate storage capability or devices to receive a SIP (OAIS Page 4-5, Section 4.1.1.2)	Currently this is a directory: /home/qubituser/ingest/.
UC1.1 Step 3. Receive Submission sends confirmation of receipt to Producer (OAIS Page 4-5, Section 4.1.1.2)
UC1.1 Step 4. Receive Submission transmits SIP to Generate AIP (OAIS Page 4-5, Section 4.1.1.2)		In the simplified LiveDVD environment, this use case step is not implemented. The objects remain in /home/qubituser/ingest/.
Use Case	Implementation	Notes
UC1.2 Quality Assurance
UC1.2 Step 1. Quality Assurance validates the transfer of the SIP to Receive Submission (OAIS Page 4-5)	Archivist uses md5sum to compare checksums of transferred objects.	In a real digital archives implementation, this would require that the producer use md5sum prior to transfer and include the checksum.md5 report in the SIP. In the LiveDVD environment the archivist does this instead. Note that currently md5sum is not capable of handling folders.
UC1.2 Step 2. Quality Assurance sends QA results to Receive Submission (OAIS Page 4-5)		We can't do this currently because md5sum does not allow the archivist to save the checkMD5 report.
Use Case	Implementation	Notes
UC1.3 Generation of AIP
UC1.3 Step 1. Generate AIP receives SIP from Receive Submission (diagram only)		In the simplified LiveDVD environment, this use case step is not implemented. The objects remain in /home/qubituser/ingest/.
UC1.3 Step 2. Generate AIP extracts content information from SIP (diagram only)	Archivist uses DROID, JHOVE and/or the NLNZ Metadata Extraction Tool to extract Content Information from the objects, saving the xml reports to the ingest folder.
UC1.3 Step 3. Generate AIP extracts Preservation Description Information (PDI) from SIP (diagram only)	See step 2, above.
UC1.3 Step 4. Administrator adds or modifies PDI if necessary (OAIS Page 4-50)		At this point that would require modification of the xml reports, which is not practical.
UC1.3 Step 5. Generate AIP requests report from Data Management>Generate Report on information required to assemble the AIP (OAIS Page 4-6)
UC1.3 Step 6. Generate AIP receives report from Data Management>Generate Report (implied by OAIS 4-6)
UC1.3 Step 7. Generate AIP assembles AIP (OAIS Page 4-6)
UC1.3 Step 8. Generate AIP provides AIP to Generate Descriptive Information for extraction of Descriptive Information (diagram only)
UC1.3 Step 9. Generate AIP provides AIP to Administration>Audit Report for validation (OAIS Page 4-6)
UC1.3 Step 10. Generate AIP receives AIP audit report from Administration>Audit Report (OAIS Page 4-11, 4-12)
UC1.3 Step 11. Generate AIP sends AIP to Coordinate Updates (diagram only)
Use Case	Implementation	Notes
UC1.4 Generation of Descriptive Information
UC1.4 Step 1. Generate Descriptive Information extracts Descriptive Information from AIP (OAIS Page 4-6)
UC1.4 Step 2. Administrator provides additional Descriptive Information for AIP (OAIS Page 4-6)
UC1.4 Step 3. Generate Descriptive Information sends Descriptive Information to Coordinate Updates (OAIS Page 4-6)
Use Case	Implementation	Notes
UC1.5 Transfer of AIP to Archival Storage
UC1.5 Step 1. Coordinate Updates submits AIP storage request to Archival Storage>Receive Data (OAIS Page 4-6)
UC1.5 Step 2. Coordinate Updates sends AIP to Archival Storage>Receive Data (OAIS Page 4-6)	Archivist copies SIP to /home/qubituser/archivalstorage/.
UC1.5 Step 3. Coordinate Updates receives storage confirmation (including storage identification information) from Archival Storage>Receive Data (OAIS Page 4-6)
Use Case	Implementation	Notes
UC1.6 Transfer of Descriptive Information to Data Management
UC1.6 Step 1. If AIP exists, Coordinate Updates adds storage identification information to the Descriptive Information (OAIS Page 4-6)
UC1.6 Step 2. Coordinate Updates submits Descriptive Information to Data Management>Receive Database Updates along with a database update request (OAIS Page 4-6)
UC1.6 Step 3. Coordinate Updates receives a response from Data Management>Receive Database Updates (OAIS Page 4-6)

UC2 Archival Storage

Use Case	Implementation	Notes
UC2.1 Receipt of AIP
UC2.1 Step 1. Receive Data receives storage request from Ingest>Coordinate Updates (OAIS page 4-7)
UC2.1 Step 2. Receive Data receives AIP from Ingest>Coordinate Updates (OAIS page 4-7)	Archivist copies SIP to /home/qubituser/archivalstorage/.	At this point the Archivist should run md5sum on the copied SIP ("checkMD5"). If md5sum confirms that the transfer was successful, the Archivist can delete the copies from the ingest folder.
UC2.1 Step 3. Receive Data selects the appropriate storage device or media (OAIS page 4-7)
UC2.1 Step 4. Receive Data prepares the storage devices or volumes (OAIS page 4-7)
UC2.1 Step 5. Receive Data transfers the AIP to the archival storage volumes (OAIS page 4-7)
UC2.1 Step 6. Receive Data sends a storage confirmation message to Ingest>Coordinate Updates which includes the storage identification of the AIP (OAIS page 4-7)
Use Case	Implementation	Notes
UC2.2 Manage Archival Storage
UC2.1 Step 1. Manage Storage Hierarchy receives storage management policies from Administration>Establish Standards and Policies (OAIS page 4-7, diagram)
UC2.1 Step 2. Manage Storage Hierarchy ensures the appropriate level of protection for the AIP based on storage management policies (OAIS page 4-7)
UC2.1 Step 3. Manage Storage Hierarchy assigns AIP to appropriate storage media based on storage management policies (OAIS page 4-7)