Metadata syncing

From Archivematica
Revision as of 13:08, 22 March 2011 by Evelyn McLellan (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Main Page > Development > Development documentation > Metadata syncing

For 0.8 we need to be able to update the AIP metadata with metadata added to the DIP in the access system.


Archivematica and Bagit

Archivematica is already using Bagit to package Archival Information Packages (AIP). We are now considering whether to standardize on using Bagit to package and transmit SIPs and DIPs as well. This diagram illustrates the SIP, AIP and DIP interfaces that we expect to be functional in the 0.8-beta release (scheduled for December 2011) Archivematica-0.8-beta-architecture.png

The Archivematica use cases for a Bagit REST API assume:

  1. SIPs, AIPs and DIPs are all Bags packaged in compliance with the Bagit specification
  2. Archivematica implements the Bagit REST API
  3. The archival storage, backup, and access components as well as any SIP posting systems/tools have a corresponding REST APIs (at the least the subset required for that particular use case)

Archivematica RESTful Bagit API Use Cases

  1. Archivematica responds to a POST SIP request from (a) Archivematica pre-ingest tools or (b) external system/service
  2. Archivematica responds (success/error) to a GET request for a SIP receipt/integrity check
  3. Archivematica sends a POST AIP request to primary archival storage
  4. Archival storage responds (success/error) to an Archivematica GET request for AIP receipt/integrity check
  5. Archival storage or Archivematica sends a POST AIP request to one or more backup storage locations
  6. Backup storage responds (success/error) to an Archivematica GET request for AIP receipt/integrity check
  7. Archival storage and backup respond to a (periodic) Archivematica GET request for AIPs integrity check information
  8. Archival storage responds to a GET AIP request from Archivematica (e.g. a 'read' action)
  9. Archivematica sends a PUT AIP request to archival storage (e.g. after Archivematica performs an 'update' action)
 10. Archivematica sends a POST DIP request to an access system
 11. Access system responds (success/error) to an Archivematica GET request for DIP receipt/integrity check
 12. Archivematica sends a PUT DIP request to an access system (e.g. after Archivematica updates AIP metadata or generates a new access copy)
 13. Archivematica responds to a a PUT AIP request from an access system (e.g. after an access system updates metadata which should be synced in the AIP)

NOTE: There is likely some overlap/duplication in these use cases. A Bag does not care if it is being used as SIP, AIP or DIP, i.e the Bag REST API response may be identical if it is responding to a SIP or AIP receipt/integrity check request.

NOTE: Each use case may in fact have more than one request/response transaction. Further analysis is required.