Archived

If you are looking for the last documentation in the 4.x series, see 4.7.5. Looking for another version? See all documentation.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview

The Audit Service provides a mechanism for tracking repository events, preserving critical details about them for auditing:

  • Who performed the event, and using what software
  • What kind of action was taken (creating objects, deleting files, etc.)
  • When was the action performed
  • What repository resource was changed

These properties are recorded using predicates from the PREMIS ontology.

 

Event-Driven Audit Service

asdf

Internal Audit Service

asdf

Use Cases

  • Detailed use case from Yale
  • UCSD Preservation Transfer Use Case
  • SFU external events
  • Yale external events
  • No labels