Difference between revisions of "Ingest (0.5)"
Line 6: | Line 6: | ||
[[File:Archivematica_AD1_ReceiveSIP_v1.pdf|Archivematica UML Activity diagram AD1 Receive SIP]] | [[File:Archivematica_AD1_ReceiveSIP_v1.pdf|Archivematica UML Activity diagram AD1 Receive SIP]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 49: | Line 36: | ||
| | | | ||
|- | |- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
Line 76: | Line 41: | ||
[[File:Archivematica_AD2_AuditSIP_v5.pdf|Archivematica UML Activity diagram AD2 Audit SIP]] | [[File:Archivematica_AD2_AuditSIP_v5.pdf|Archivematica UML Activity diagram AD2 Audit SIP]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 88: | Line 46: | ||
|- | |- | ||
|- style="background-color:#cccccc;" | |- style="background-color:#cccccc;" | ||
− | !style="width:20%"|''' | + | !style="width:20%"|'''Workflow diagram step''' |
− | !style="width:40%"|''' | + | !style="width:40%"|'''Description''' |
− | !style="width:40%"|''' | + | !style="width:40%"|'''UML diagram references''' |
|- | |- | ||
− | |''' | + | |'''Archivist moves SIP from shared folder into quarantine''' |
| | | | ||
+ | *Drag the SIP from /home/demo/receiveSIP/ to /home/demo/quarantine. | ||
| | | | ||
|- | |- | ||
− | |'''2 | + | |'''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. | |
− | |||
− | * | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| | | | ||
|- | |- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
Revision as of 12:57, 19 November 2009
Main Page > Documentation > Release 0.3 Documentation > Ingest (0.3)
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 |
|
|
SIP appears in shared folder in Archivematica |
|
|
Archivist copies SIP from shared folder to SIP backup folder. |
|
AD2 Audit SIP
File:Archivematica AD2 AuditSIP v5.pdf
Workflow diagram step | Description | UML diagram references |
---|---|---|
Archivist moves SIP from shared folder into quarantine |
|
|
SIP is quarantined for 2 minutes |
|
|
SIP is scanned for malware |
|
|
Infected files are sent to possiblevirii folder |
|
AD3 Accept SIP for Ingest
File:Archivematica AD3 AcceptSIPforIngest v4.pdf
Expected Procedure
[3.1] --> [3.2] --> [3.3] --> [3.4] --> [3.5] --> [3.6] --> [3.9] --> [3.10]
Exceptions
- Producer notification required following [3.6]
- Appraisal decision appealed following [3.7]
Step | Implementation | Notes |
---|---|---|
General procedures | ||
3.1 Unpack SIP (UC-1.3) |
Create folders for the SIP contents
Go to: 3.2 - Modify/Provide additional PDI |
|
3.2 Modify / provide additional PDI (UC-1.3) |
Go to: 3.3 - Identify Formats |
|
3.3 Identify format | Use DROID and NLNZ Metadata extractor to identify objects in the SIP. Save the reports to /home/demo/ingest/2009_01/PDI/.
Go to: 3.4 - Validate formats |
|
3.4 Validate format | Use JHOVE to validate the objects in the SIP. Save the report to /home/demo/ingest/2009_01/PDI/.
Go to: 3.5 - Extract metadata |
|
3.5 Extract metadata |
Extract preservation metadata from content objects in the SIP Go to: - 3.6 Audit submission and select for preservation |
|
3.6 Audit submission and select for preservation (UC-4.6) |
Based on the results of steps 3.2, 3.3, and 3.4, apply Archives policies and determine which (if any) content objects in the SIP should not be included in the AIP Document which content objects will not be included and why. If all SIP content is to be included in the AIP, go to: 3.10 - Accept selected SIP components for ingest
|
Possible reasons for exclusion:
|
3.7 Notify Producer about appraisal decision(s) | Provide the Producer with copies of the appraisal report or other documentation as required by the submisssion agreement identifying SIP components to be destroyed.
If the Producer appeals the appraisal decision, go to: 3.8 - Evaluate appeals Else, go to: 3.9 - Destroy unselected SIP components |
|
3.8 Evaluate appeals |
Go to: 3.9 - Destroy unselected SIP components |
|
3.9 - Destroy unselected SIP components |
|
|
3.10 Accept selected SIP components for ingest |
AD4 Generate AIP
File:Archivematica AD4 GenerateAIP v2.pdf
Step | Implementation | Notes |
---|---|---|
4.1 Create AIP containers | If 1 SIP = 1 AIP this step is not necessary. It is only necessary if the SIP is being divided into multiple AIPs. | |
4.2 Add Content Information to AIP | See note for step 4.1, above | |
4.3 Transform Content Information |
|
|
4.4 Add Transformed Content Information to AIP | See step 4.3, above. | |
4.5 Add PDI to AIP | Create a plain text report containing provenance and other PDI elements (including arrangement information) and save it to the AIP. | |
4.6 Generate Descriptive Information (UC-1.4) |
|
AD5 Transfer AIP to Archival Storage
File:Archivematica AD5 TransferAIPtoArchivalStorage v2.pdf
Step | Implementation | Notes |
---|---|---|
5.1 Request storage of AIP (UC-1.5) | ||
5.2 Transfer AIP to Archival storage (UC-1.5) |
|
|
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. |