This page lays out the considerations and activities surrounding the Fedora 4 Audit Service.
Unresolved Questions
- Should there be support for adding external events to the Audit Service?
- If yes, what restrictions, if any, should be enforced on this capability? (e.g. only when migrating from Fedora3? only by administrators?)
- If yes, what should the import format be?
- What is the scope of the Audit Service: the Repository? or the Resource?
- What is the most appropriate ontology? PROV-O, PREMIS, combination? other?
- How should the Audit Service support different users? administrators, users?
- For event tracking, where is the user principal expected to come from? servlet-request#getUserPrincipal?
- How will user principals be mapped to persistent user identifiers?
Actions
- Define required Audit Service queries
- Perform comparative analysis of PROV-O vs. PREMIS-RDF
- Define repository events that should be recorded by the Audit Service
- Define event agents that should be supported by the Audit Service
- Define capability of the Audit Service REST-API
Proposed Requirements