Title (Goal) | As a data management specialist, I want to see the provenance stream of an object in order to be assured of the integrity and authenticity of an object. |
Primary Actor | Data management specialist |
Scope | |
Level | |
Author | Elliot Metsger |
Story (A paragraph or two describing what happens) | In order to meet preservation goals, I should be able to ask the repository for provenance information for an object. |
As a data management specialist, I want to see the provenance stream of an object in order to be assured of the integrity and authenticity of an object. As a data management specialist, I am comfortable with using URIs to identify objects, and interpreting XML or JSON documents. Knowing the identifier or URI of an object in the repository, I would like to request the the provenance stream that is associated with the object.
Events in the provenance stream may have been generated by the repository itself, or the events may have been generated by external processes that have operated on the object (e.g. a service that performed a format migration). I would expect the provenance stream (especially the events generated by the repository) to conform to a known standard such as Prov-O or PREMIS. The kinds of events I would expect in the provenance stream include (but aren't limited to):
- fixity verification (e.g. a service (internal or external to the repository) successfully verified the checksum of a file)
- model validation (e.g. a service validated the conformance of the object to some model)
- virus checking (e.g. a service scanned the contents of a file for known viruses)
- accession information (who deposited the object, when, by what method, etc.)
- preservation actions (e.g. a service which targets the object for a preservation action)
- object modifications (e.g. correcting descriptive metadata of the object)
