This page lays out the considerations and activities surrounding the Fedora 4 Audit Service.
Table of Contents |
---|
Guiding Principles
- Any Fedora4 feature should be available through an API which is an implementation of LDP or an optional extension (ideally an existing standard)
- Fedora4 features should favor existing tools over custom code
- Fedora4 features should establish integration patterns where an implementation is not a part of the core code
Actions
Action | Owner | |
---|---|---|
1 | Define required Audit Service queries | Dr. Arif Shaon |
2 | Perform comparative analysis of PROV-O vs. PREMIS-RDF (Reference: http://dcpapers.dublincore.org/pubs/article/view/3709) | Nick Ruest |
3 | Define repository events and event agents that should be recorded and supported by the Audit Service | Unknown User (escowles@ucsd.edu) |
4 | Define capability of the Audit Service REST-API |
Unresolved Questions
Note |
---|
Click here to discuss and provide answers to these 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?
- 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?
Excerpt | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Proposed RequirementsLegend: - Needs refinement, consensus, or removal Functional - Write/Import
| ||||||||||||||||||||
Excerpt | ||||||||||||||||||||
Proposed Requirements
Functional - Read/Export
Non-Functional
|
Role Commitments
Development
Stakeholder
Supplementary Documentation
...