Difference between revisions of "Ingest (0.5)"

From Archivematica
Jump to navigation Jump to search
Line 1: Line 1:
−
[[Main Page]] > [[Documentation]] > [[Release 0.3 Documentation]] > Ingest (0.3)
+
[[Main Page]] > [[Documentation]] > [[Release 0.5 Documentation]] > Ingest (0.5)
  
  
Line 162: Line 162:
 
|-
 
|-
 
|- style="background-color:#cccccc;"
 
|- style="background-color:#cccccc;"
−
!style="width:20%"|'''Step'''
+
!style="width:20%"|'''Workflow step'''
−
!style="width:40%"|'''Implementation'''
+
!style="width:40%"|'''Description'''
−
!style="width:40%"|'''Notes'''
+
!style="width:40%"|'''UML diagram references'''
−
|-
 
−
|'''5.1''' Request storage of AIP ([[UC-1.5]])
 
−
|
 
−
|
 
 
|-
 
|-
−
|'''5.2''' Transfer AIP to Archival storage ([[UC-1.5]])
+
|Archivist moves AIP to archival storage folder
−
|
 
−
*Right click on folder /home/demo/ingest/2009_01.
 
−
*Click ''Scripts > BagIt''.
 
−
*A bag will be created and stored automatically in /home/demo/mybags/.
 
−
*Copy AIP to /home/ingest/archivalstorage/.
 
−
|
 
−
*In archivematica 0.4 maybe configure BagIt script to drop the bag directly into /home/demo/ingest/archivalstorage/.
 
−
*The BagIt script can also be edited manually if desired: open demo/.gnome2/nautilus-scripts/Bagit and change "mybags" to "archivalstorage".
 
−
|-
 
−
|'''5.3''' Confirm receipt and storage of AIP ([[UC-1.5]])
 
−
|
 
−
|
 
−
|-
 
−
|'''5.4''' Add AIP storage location to descriptive information ([[UC-1.6]])
 
−
|In the ''physical storage'' area in Qubit, add the storage location.
 
−
|
 
−
|-
 
−
|'''5.5''' Add Descriptive Information to Data Management ([[UC-1.6]])
 
−
|This was done in AD4, step 4.6. In OAIS, generating descriptive information and adding them to data management are two different steps; however, in Archivematica this is done in one step in Qubit, which is used to upload images to a web interface, generate derivatives for searching and browsing and record descriptive information.
 
−
|
 
−
|-
 
−
|'''5.6''' Confirm update of Data Management
 
−
|
 
−
|
 
−
|-
 
−
|'''5.7''' Destroy SIP and AIP copies
 
−
|Destroy /home/demo/ingest/2009_01 and /home/demo/mybags/2009_01.
 
−
|
 
 
|-
 
|-
 
|}
 
|}

Revision as of 13:44, 19 November 2009

Main Page > Documentation > Release 0.5 Documentation > Ingest (0.5)


AD1 Receive SIP

File:Archivematica AD1 ReceiveSIP v1.pdf


Workflow diagram step Description UML diagram references
Producer places SIP in shared folder on host machine
  • The purpose of shared folders is to allow the Producer to drop SIPs into a folder on their host machine or network and have the SIPs automatically appear in a folder in Archivematica.
    • For instructions on setting up shared folders, please go to Virtual appliance instructions.
    • Neither the folder name nor any of the filenames should include spaces or special characters. Underscores are ok.
    • Make the shared folder in Archivematica /home/demoreceiveSIP/.
  • For testing purposes you can avoid setting up shared folders and simply use the test files found in /home/demo/testFiles/.
SIP appears in shared folder in Archivematica
  • SIP will appear in /home/demo/receiveSIP/.
  • If using files from /home/demo/testFiles/, copy a folder from /testFiles/ into /home/demo/receiveSIP/.
Archivist copies SIP from shared folder to SIP backup folder
  • Copy the SIP in /home/demo/receiveSIP/ and paste it into /home/demo/receiveSIPbackup/. If anything goes wrong during the ingest process, this backup copy can be retrieved and processed.

AD2 Audit SIP

File:Archivematica AD2 AuditSIP v5.pdf


Workflow diagram step Description UML diagram references
Archivist moves SIP from shared folder into quarantine
  • Drag the SIP from /home/demo/receiveSIP/ to /home/demo/quarantine.
SIP is quarantined for 2 minutes
  • In a production system, SIPs would normally be quarantined for a set period of time (for example, four weeks), to allow anti-virus software to be updated with the latest virus profiles.
  • A lock should appear on the SIP folder in quarantine. The archivist will not be able to read or modify the files during this time.
SIP is scanned for malware
  • At the end of the quarantine period, ClamAV will automatically scan the files for viruses and other malware.
Infected files are sent to possiblevirii folder
  • Infected files will appear in /home/demo/possiblevirii/. If this occurs, do not take any further steps in the ingest process. Inform the Producer that infected files have been found. It is recommended at this point to delete all SIP copies and request that the Producer take steps to review the causes of the problem and eventually resubmit a malware-free SIP.

AD3 Accept SIP for Ingest

File:Archivematica AD3 AcceptSIPforIngest v4.pdf


Workflow diagram step Description UML diagram references
SIP contents are identified and validated using FITS
  • FITS (File Information Tool Set) is automatically launched once the quarantine period has ended and the files have been scanned for viruses.
  • FITS incorporates format identification and validation tools such as DROID. JHOVE and the New Zealand Metadata Extractor, comparing the results of each tool and extracting a set of identification, validation and technical metadata. For more information on the FITS tool, see File Information Tool Set (FITS) [http://code.google.com/p/fits/ File Information Tool Set (FITS)
Identification/validation reports are sent to accessions folder
  • The FITS report will appear in /home/demo/accessionreports/. The report appears as a folder with a 10-digit number; inside the folder is a report for each file in the SIP.
  • Note that each report contains an MD5 checksum for the file.
Virus-checker report is sent to accessions folder
  • A report on ClamAV's virus scan will appear automatically: home/demo/accessionreports/virus.log.
Accession log is sent to accessions folder
  • A report on the accession process will appear automatically: home/demo/accessionreports/accession.log.
  • For each file in the SIP, the accession log will state "Accession of /tmp/accession-[FITS folder number]/[SIP number]/filename] completed successfully."

AD4 Generate AIP

File:Archivematica AD4 GenerateAIP v2.pdf


Workflow diagram step Description UML diagram references
SIP is moved to AIP preparation folder
Archivist normalizes files
Normalized files are saved to AIP preparation folder
Normalization log is saved to accessions folder
Archivist moves PDI in accessions folder to SIP in AIP preparation folder
Archivist moves SIP to AIP generation folder
SIP content and PDI are zipped into AIP
AIP is moved to AIP receipt folder

AD5 Transfer AIP to Archival Storage

File:Archivematica AD5 TransferAIPtoArchivalStorage v2.pdf


Workflow step Description UML diagram references
Archivist moves AIP to archival storage folder
Retrieved from "https://wiki.archivematica.org/index.php?title=Ingest_(0.5)&oldid=620"