This page will lay out a design for an Audit Service in Fedora 4.
Proposed Use Cases
...
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 | |
4 | Define capability of the Audit Service REST-API |
Excerpt |
---|
Proposed RequirementsLegend: - Needs refinement, consensus, or removal Functional - Write/Import
|
...
|
...
Functional - Read/Export
Non-Functional
|
Role Commitments
Development
Stakeholder
Supplementary Documentation
UCSD
Document |
---|
DAMS-Events-Agents-Final Version--20120106.docx |
Event type controlled value list.pdf |
Event Class and Properties |
user-stories.pdf |
...