Preservation Core requires three kinds of information about its objects to be collected and maintained for operational and reporting purposes.
A basic object inventory with a set of information per-object (per-druid) about the current state of the object in Preservation Core wrt to ingest and replication. (#2)
A "Trusted Checksum Repository" containing the fixity information required to support the audit and recover functions of Preservation Core. (#3)
Provenance, a complete list of events/actions relating to the object -- from ingest, through each replication, every audit check and finding or recovery action taken. As the name implies, this constitutes the object's provenance. (#4)
These may exist as separate datastores using appropriate technologies, but each should be Web Service addressable so that an authorized agent (Argo in this case) can request each type of information to display.
Preservation Core requires three kinds of information about its objects to be collected and maintained for operational and reporting purposes.
These may exist as separate datastores using appropriate technologies, but each should be Web Service addressable so that an authorized agent (Argo in this case) can request each type of information to display.