Using Archivematica 0.8 for Digitized Content
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


Using Archivematica 0.8 for Digitized Content



Shows production workflow currently in use for a bare-metal installation of Archivematica 0.8, without direct access to AIPstore or DIPstore. Screenshots show different Archivematica configurations ...

Shows production workflow currently in use for a bare-metal installation of Archivematica 0.8, without direct access to AIPstore or DIPstore. Screenshots show different Archivematica configurations available.



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds


Upload Details

Uploaded via

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Using Archivematica 0.8 for Digitized Content Presentation Transcript

  • 1. Transfers go in, not SIPs
  • 2. Transfers go in, not SIPs• Verify transfer compliance• Rename with transfer UUID• Assign file UUIDs to objects• Assign checksums and file sizes to objects• Verify metadata directory checksums• Generate METS.xml document• Extract packages• Scan for viruses• Sanitize objects file and directory names• Sanitize transfer name• Characterize and extract metadata• Create SIP(s)
  • 3. Transfer directory structure (0.8) Transfer_Name /logs (only for logs created by Archivematica) /metadata checksum.md5 (must have this name) /submissionDocumentation (optional) info_about_digitization.xls /objects example.MKV transfer_name.csv /access (optional) example.MP4 (must have same name) transfer_name.csv processingMCP.xml
  • 4. Digitization metadata: excerpt
  • 5. Ingest Planning: organization• Decide how to organize transfer contents : logical or arbitrary groupings?• Don’t make AIP too big!• Organize files into single transfers – we did this on a network drive
  • 6. Ingest Planning: organizationTIFFs: arbitrary blocks of ~ 1,000 Audio & video: fewer files, fewer errors,for migration; prob. logical groups easier to organize by fonds or series
  • 7. Ingest Planning: Quality• Need time for quality control of digital objects and metadata before ingest• Set aside problem or “do later” files, such as those requiring rescanning
  • 8. Ingest Planning: Quality• Check metadata completeness & accuracy, image quality: no garbage in!• Started with export from current db: current workflow is to only ingest items already described to item level• One item #, one file (and no more)• Filenames have to agree with item # and with csv ingested: spaces, capitalization, etc, including extensions
  • 9. Ingest Planning: Quality• Using custom MS Access form, volunteers inspected master & derivative images next to their descriptions to ensure correct image• Image sizes double-checked in case any too small
  • 10. Ingest Planning: TIFFs• Separate files not to be ingested and those to be ingested as sub-items• Not for ingest: not owned by us, should never have been digitized; or need descriptions• Sub-items: multi-page, need a procedure first
  • 11. Assemble transfer objects: no access files
  • 12. Assemble transfer objects: have access files
  • 13. Tracking transfers
  • 14. Configure Archivematica• Workflow (s): configure for each transfer unless using default• AIP compression: will be the same for all transfers processing at the same time• Normalization choices
  • 15. Workflow: processingMCP.xml• Overrides default processing xml files used to process born-digital materials• Can customize to make the processing faster• Must always have exactly this name, even if contents vary
  • 16. Workflow: processingMCP.xml Location Transfer_Name /logs /metadata /objects processingMCP.xml
  • 17. Workflow: processingMCP.xml Example
  • 18. Workflow: processingMCP.xml Example
  • 19. Workflow: processingMCP.xml Example
  • 20. Workflow: processingMCP.xml Example
  • 21. Workflow: processingMCP.xml Example
  • 22. Workflow: processingMCP.xml Example. No normalization
  • 23. Workflow: processingMCP.xmlExample. Access normalization
  • 24. Workflow: processingMCP.xml Example
  • 25. Setting AIP compression
  • 26. Setting AIP compression
  • 27. Normalization:Preservation planning tab
  • 28. Normalization: TIFconvert "%fileFullName%" -sampling-factor 4:4:4 -quality 60 %outputDirectory %%prefix%%fileName%%postfix%.jpg"
  • 29. Load Transfers
  • 30. Structured directory on server
  • 31. Staging area for transfers
  • 32. Launching transfers
  • 33. Monitoring using htop
  • 34. Transfer failed: X marks it
  • 35. Failed microservice: what went wrong?
  • 36. Failed microservice message
  • 37. Reporting: microservices
  • 38. Reporting: Compress AIP Greenwich Mean Time
  • 39. Upload DIP directory• As they are created, DIPs appear here
  • 40. Upload DIP directory• DIP objects in “objects” folder
  • 41. Upload DIP directory• Inside objects folder, each DIP object with new UUID
  • 42. Completed AIPs
  • 43. Inside the AIP directory
  • 44. Open Terminal to checksum AIP bag
  • 45. Checksum AIP bag
  • 46. Copyto external drive and then to AIPstore
  • 47. Exception: service copies
  • 48. Exceptions: service directory Transfer_Name /logs /metadata /objects /access /service processingMCP.xml
  • 49. Bare-metal Workflow: lots of copying! Network Network storage – storage -Digitized QA AIPstore External drive External drive
  • 50. VM Workflow: less manual copying automated Network storage – Digitized QA Network storage - AIPstore External drive