...

1. Announcements
   1. Next sprint on Jan 27th – currently 6 participants
      1. Andrew and Daniel Danny will be available!
   2. Fedora 6 docs are up – please capture updates and changes
      1. There's a lot that's no longer relevant – a lot of changes needed
      2. When you make software changes – update the docs
2. Fedora 6 Demo
   1. Demo build is tagged and available
   2. Double-click doesn't work but you can run it with java -jar
      1. Not a priority to fix right now (might just be related to the version of Java that the OS is trying to use to launch it)
      2. Works on Andrew's machine
   3. Jared just added functionality to save state but not in tagged demo. Should the tagged be moved?
      1. Yes, will move tag
3. Next Demo Target
   1. Create/read binaries
   2. Mohammed has an outstanding PR for replacing binaries (link?)
      1. At the time RDF and binary persisters were the same – no longer the case
      2. Should this PR be updated or start over?
         1. Andrew thinks it could be brought into alignment if it was still useful
         2. Jared thinks there is valueable work in it
         3. Danny: Changes in the PR are above the persister layer. Get create & read working first? Hard to test if you can't create.
         4. Bethany: Does it take into account some of the other changes that were made at the kernel layer? Might need to be refactored.
         5. Action: Andrew and Danny figure out where things stand
         6. Andrew: Features should be end to end going forward
4. Sprint planning
   1. Create and read binaries
   2. Containment index
      1. Peter E: A lot of the code exists but not hooked up to Fedora
      2. JDBC fairly agnostic and not hooked up to a DB yet – used H2 for testing
   3. Update migration utils to use the same on disk representation as the current direction in Fedora 6 (Doc)
      1. Need something to iterate over an existing OCFL repo and init Fedora
      2. Andrew: Should Fedora do this on startup or should there be an external tool that creates everything Fedora needs?
      3. Jared: Long term the index should be in a db. Need to know how object ids are mapped to location on disk. Should we support a lazy-load of the index?
      4. Danny doesn't see much value in the lazy-load.
      5. Andrew: Potential use case for iteratively migrating objects?
      6. Ben: Wants incremental migrations. Would like Fedora to be able to handle objects that aren't in the index. Would be nice to not have to run a reindex/rebuild.

Actions

•  Clarify in in documentation that multiple simultaneous writes to OCFL are not supported

...