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 Events
The event-driven audit service is a Camel component that processes the JMS events emitted by Fedora 4, and creates audit event records in an external triplestore. As with other RDF metadata, an external triplestore provides full-featured query functionality for working with audit event records.
Internal Audit Events
The internal audit service is an optional module which can be used to have audit event records automatically created in the repository when updates happen.
