...

1. Announcements

   1. PRs closed this last week:
      1. (no JIRA): https://github.com/fcrepo4/fcrepo4/pull/1662 Ben Pennell
      2. (no JIRA): https://github.com/fcrepo4/fcrepo4/pull/1663 Peter Winckles
      3. (no JIRA): https://github.com/fcrepo4/fcrepo4/pull/1665 Peter Winckles

      4. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3278

          Jared Whiklo
   2. New tickets/bugs: 

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3280

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3281

2. Committers leaders call upshot (5 mins)
   1. Follow-on meeting next Wed @11am ET - 2020-04-29 - Fedora Leaders - Committers Meeting
   Containment IndexHow to handle SQL differences (H2, MySQL, PostgreSQL) - pluggable connectors?
3. fcrepo4-docker and fcrepo-docker status update
4. Pre-Sprint focus:
   1. simple search plan
      1. What do we plan to support in 6.0.0? 
      2. 2019-02 Fedora Design Summary
      3. Query Service Specification
      4. Samvera / Valkyrie Queries
5. Fedora 6 testing
6. Containment Index
   1. How to handle SQL differences (H2, MySQL, PostgreSQL) - pluggable connectors?
   fcrepo4-docker and fcrepo-docker status update
7. Housekeeping PRs
   1. https://github.com/fcrepo4-labs/fcrepo4-docker/pull/38
   2. https://github.com/fcrepo4/fcrepo4/pull/1628 
8. Fedora 6 Roadmap?

9. <Add your topic here>

   Expand
   title Tickets resolved this week...
   Jira server DuraSpace JIRA jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

...

1. Lots of good work happening this week
2. New bug tickets

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3280

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3281

      1. Andrew used git-bisect to pin down the error
      2. Getting the build to work with IntelliJ

Leaders/Committers Call

1. Follow-up meeting scheduled for next Wednesday
2. Setting context for vanilla-rebuild functionality
   1. Supporting both plain OCFL and Fedora-specific OCFL for read/write, rebuild, etc. would be challenging
   2. If Fedora leaves Fedora-specific data in OCFL directories this might be unexpected/unwanted behaviour
      1. However, this extra data could be stored in a .fcrepo directory which would be fairly easy to remove if desired
      2. The .fcrepo directory may actually be useful for providing context of the previous state of the resources within a Fedora repository
      3. Reaction from OCFL editors: why now use the extensions directory?
         1. Put .fcrepo inside extensions outside the context of the OCFL Object
         2. Risks complexity, splitting metadata in different locations
   3. Fedora should be able to import and read vanilla OCFL without adding specific Fedora data
      1. Fedora would add Fedora-specific data in order to manage/write to the content on disk
      2. Documentation should be clear about what operations on vanilla OCFL objects do and do not add Fedora-specific data
3. Fedora makes assumptions in the absence of specified details based on the platform needs. It seems like there are multiple categories of info that are relevant to different purposes, such as:
   1. common to ocfl objects (timestamps, a checksum, etc),
   2. useful for a linked data platform (interaction models, containment),
   3. fedora specific (external binary location, binary details, creator/modifier details),
   4. user provided RDF/binary content.
4. In the last design document, all of those details were going into .fcrepo except for the last one. Some can be derivable, some only matter in some contexts
5. Proposal: Fedora doesn't know how to upgrade from read-only vanilla OCFL. Upgrading to read/write would require a migration utility
   1. In this case the repository would be in read-only mode - can't create new resources without running the migration utility
   2. Migration would be in-place - adding new versions with Fedora-data
6. Two different concerns: software maintainability vs. long-term preservation

Actions

•  Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-04-23 - Fedora Tech Meeting)
•  Ben Pennell to create ticket to use OCFL optimistic locking in transactions (see: 2020-04-23 - Fedora Tech Meeting)
•  Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-04-23 - Fedora Tech Meeting)
•  Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported
•   Who:  After team has a chance to comment, send Ghost Node idea to general community for feedback
•   Who: Decide who works on what in the next sprint
  

...