...
The Audit Service provides a mechanism for tracking repository events, preserving recording critical details about them for auditingusing predicates from the PREMIS ontology:
- Who What 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 ontologyIn addition to browsing events, the events can be queried by date range, event type, or agent (username or client software).
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
Event-driven audit events provide a lightweight audit system, with minimal impact on the repository. All information for processing is included in the events that Fedora 4 sends, so the Camel processing does not need to retrieve any extra information from the repository, and can accurately process multiple update and deletion events. The external triplestore provides full-featured query functionality for working with audit event records using SPARQL.
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.
Internal audit events provide a way to store audit event information without having to setup an external triplestore, and provides a more robust event store that can take advantage of Fedora's replication, backup, and other preservation features.
When used together, the event-driven and internal audit events provide robust audit storage and full-featured query functionality.