Time/Place

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

Attendees

• David Wilcox
• Andrew Woods
• Nick Ruest
• Mark Jordan
• John Doyle
• Doron Shalvi
• John Rees
• Susan Lafferty
• Eric James
• Michael Friscia
• Unknown User (escowles@ucsd.edu)
• Bria Parker
• Peter Eichman
• David Chandek-Stark
• Matt Critchlow
• Dr. Arif Shaon
• Charles Schoppet

Agenda

1. Introduction and topic summary
   1. Proposed Plan
      1. Establish common understanding of function of Audit Service
      2. Brainstorm use-cases
      3. Compile initial requirements
      4. Summarize and Post use-cases and requirements
         • Iterative meetings, as required
         • Set deadline for feedback
      5. Create strawman design
         • Set deadline for feedback
      6. Confirm commitments
         • developer and stakeholders (verification)
      7. Sprint (Mar 23, Apr 13)
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