You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Time/Place

  • Time: 3:00pm Atlantic Standard Time US (UTC-4)
  • Call-in: DuraSpace conference line
    • 1-209-647-1600, 117433#

Attendees

Agenda

  1. Introduction and topic summary
  2. Use case discussion
    1. Audit service should automatically record who updated which resource when and with which action.
    2. Audit service should be able to include/import events that were performed external to the repository.
    3. Audit service should be able to purge events.
    4. Audit service should be RDF-based, and use PATCH semantics for updates.
    5. PROV-O ontology may be better suited than PREMIS.
    6. Audit service would ideally support map-reduce-style analytics.
    7. Evidence of fixity checking on a "routine basis", and with logs "stored separately or protected separately from the AIPs themselves" should be available.
    8. Fedora 4 REST API should support dissemination of event/audit information.
  3. Workplan and timelines
  4. Testing and validation
  5. Questions

Minutes

 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.