Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Audio/Video Conference Link: https://lyrasis.zoom.us/j/396037251
  
  • Meeting ID: 396 037 251
  • Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia

• Join fedora-project.slack.com on the "tech" channel

  • Self-register at: http://slack.fcrepo.org/

Attendees 

1. Danny Bernstein
2. Jared Whiklo  
3. Andrew Woods  
4. Peter Winckles  
5. Ben Pennell 
6. Ben Cail
7. Jon Roby

Agenda

1. Announcements

2. June 1-5 Sprint 
   1. Fedora 6 Feature Tracking
   2. Fedora Test Suite Results
3. Changing the default OCFL encapsulation directory from fedora-ID to fedora-ID-hash
   1. There be dragons in keeping fedora-ID
4. Search:
   1. Any interest in a depth setting when recursively retrieving descendants?
   2. What are the community use cases for WebAC and Search?
5. Open questions: 
   1. JMS: Remove Fedora-related JMS messaging headers? 2018-04-26 - Fedora Tech Meeting
      1. ACTION: Jared to investigate potential impact on Camel tooling - updates?
6. Housekeeping: 
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

7. Your Topic Here

   Tickets resolved this week...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Tickets

1. In Review

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Please squash a bug!

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

3. Tickets resolved this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

4. Tickets created this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

1. Announcements

   1. None
2. June 1-5 Sprint 
   1. Fixity:
      1. Ben: disappointed that the OCFL digest options are only sha512 and sha256.
      2. Fedora stores all digests in the headers, but only pushes the digest that matches the content addressing digest algorithm to the OCFL client
      3. Do we want the other digests to be pushed into OCFL? This would incur additional computational costs.
         1. Decided to not push the other digests into OCFL at this time.
   2. Database
      1. MySQL has a limit of 503 characters for Fedora ID length
         1. Could support different limits for different DBs
         2. Could use a pid instead of the Fedora ID to support any length of Fedora ID
         3. Decided to postpone decision for now
   3. Jared's work:
      1. Identified a lot of things that Fedora still isn't doing when he renenabled the Ldp ITests
      2. Andrew identified a lot of problems while testing the tombstone ticket – not related to the PR
      3. Should we remove support of PUT/POST for updating SPARQL?
         1. Yes. 409 if not a binary.
   4. Daniel is making progress on his ticket and expects to have it wrapped up soon
3. Changing the default OCFL encapsulation directory from fedora-ID to fedora-ID-hash
   1. 255 character cap on the length of file names, so if we use the ocfl id as the encapsulation directory then there can never be ids longer than 255 characters
   2. Possible solution, use a hash of the id as the encapsulation directory. This reduces readability, but will allow for any length of id.
   3. Ben C: Maybe use a mix of the ocfl id and a hash, include a hash when id length is longer than X number of characters
   4. No decision – something to think about
4. Search:
   1. Any interest in a depth setting when recursively retrieving descendants?
      1. Ben P: People might be expecting immediate children rather than all children
   2. What are the community use cases for WebAC and Search?
      1. Initial impl: Just allow admins to search
      2. Get ACs in DB?
   3. Plan: Get a first pass and then collect additional use cases
5. Open questions: 
   1. JMS: Remove Fedora-related JMS messaging headers? 2018-04-26 - Fedora Tech Meeting
      1. ACTION: Jared to investigate potential impact on Camel tooling - updates?

Actions

• Andrew Woods to reply to leaders side-loading thread with proposal
• Andrew Woods / Peter Winckles / Team to review and refine F6/OCFL ID mapping proposal
• Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-06-04 - Fedora Tech Meeting)
• Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-06-04 - Fedora Tech Meeting)
• Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported