Skip to content

2018.09.12 Community Meeting

Andrew Woods edited this page Sep 13, 2018 · 10 revisions

Call-in Details

Attendees

  • Andrew Woods
  • Andrew Hankinson
  • Rosalyn Metz
  • Neil Jefferies
  • Simeon Warner
  • Josh Westgard
  • David Wilcox
  • Doron Shalvi
  • Don Brower
  • Jonathan Green

Regrets

  • ...

Agenda

  1. Community updates / points of discussion?
  2. Review Face-to-Face meeting
  3. Review Roadmap (Simeon)
    • Alpha
      • October community call we will release (OCFL Editors and PASIG Discuss)
      • Review feedback in the November community call
      • Then determine release date based on the amount of feedback
    • Beta
      • Experimental validation tool
      • Determine who else to push this out to
    • Release 1.0
      • One production ready validator
      • Test suite and fixture objects
      • Two institutions committed to backing the initiative (should define that)
  4. Review upcoming meetings/presentation proposals (Rosy)
    • CNI Fall 2018
    • JISC
    • PASIG
    • Publication
    • Others?

Action Items

Notes

Audio recording

General comments

  • Univ of Maryland has implemented fixity checking process
    • Interested in whether OCFL represents an opportunity for more efficient/performant processing
    • Noted that OCFL is specifically designed to support independent process to act against OCFL content
  • Notre Dame is particularly interested in:
    • Immutable versions
    • Permanently remove content - purge
      • OCFL editors' recommendation to delete object, then create a new one
  • NLM interested in scale and application-independence
    • Application code will be required... can the OCFL model be implemented in a scalable way?

OCFL Specification walk-through

  • Have split out outputs into two documents:
  • Will be publishing versioned releases of both documents
    • In-progress drafts published under /draft/ version
  • Basic structure of specification has been defined
    • Terminology
    • OCFL Object
      • Have established versioning approach to OCFL Objects
      • Noting that digests are primarily used for content addressability
      • OCFL specifically does not require renaming of persisted files
      • Inventory
        • Inventory is a JSON-LD document describing structure and state of an OCFL Object
        • OCFL inventory identifies files via their digest
        • Inventory includes Manifest and Versions blocks
      • Inventory digest: ensures integrity of inventory file
      • Logs directory: location for administrative information related to the OCFL Object
    • OCFL Storage Root
  • Comments on the specfication can be submitted via github issues

Roadmap

  • Goal: have "alpha" version of specification by Oct community call
    • Will be looking for community feedback
  • What is criteria for release 1.0?
    • Validator
    • Test suite/fixtures
    • Two or more committed institutions

Upcoming meetings

  • CNI
  • JISC
  • PASIG
  • Samvera connect
  • ..also, we plan on publishing an OCFL article
    • Noting that one of the reasons Moab has been successful is that it was published
Clone this wiki locally