Fedora Camp Atlanta
- May 20-22 at Emory
- Andrew, Danny, Jared as instructors
Open Repositories events
- Fedora user group on Friday
- Dinner earlier in the week
FMP Grant survey
- Survey went out yesterday
- Open to anyone to complete. About 10 minutes.

Updates from Slack

#tech
- Some questions about using JSON-LD
- Questions around scale, ingest performance, etc.
#ocfl
- Conversation around locking
  - Some suggestion that implementation notes should mention different approaches to contention in object updates, uncoordinated applications adding revisions to the same object. Maybe out of scope?
  - Some commenters thinking of scenarios analogous to those we will deal with in Fedora (e.g. many writers making simultaneous changes to an object).
  - How to build up and commit changes to an OCFL object safely. This could go in the implementation notes.
  - Dealing with locking: Fedora will need to answer this question. Less about OCFL and more about the applications built on top of OCFL.
  - Fedora design includes caching changes until committing to an OCFL object.
    - Changes are maintained in a deposit space until a version is explicitly created.
  - OCFL in S3: filesystems can make certain guarantees that are impossible in S3. File paths are not really directories, no true renaming. S3 may only be safe if every client uses a single application that mediates access.
  - Can locking be cast a a general HTTP issue rather than a Fedora-specific issue?
    - Stateless HTTP requests will need to be managed by a higher-level application
    - It would be useful to have concrete use cases
- Oxford experimenting with Aaron Birkland's OCFL client
  - Created 250K objects and were pleased with performance

Ready for Review

Peter Eichman is planning to work on documenting UMD's fixity check system on the Fedora in Production: Case Studies wiki page.
Danny Bernstein will pull together some use cases for object locking in OCFL