...

1. Danny Bernstein
2. Jared Whiklo  
3. Andrew Woods  
4. Peter Winckles  
5. Ben Pennell  
6. Ben Cail  
7. Ben Cail
9. David Wilcox
10. Thomas Bernhart
11. Daniel LambJon Roby

Agenda

1. Announcements

2. June 1-5 Sprint 
   1. Post suite wrap-up 
   2. Reflections
   3. Next Demo
   4. Fedora 6 Feature Tracking
   5. Fedora Test Suite Results
3. Renaming of 'master' branch?
4. Defining Fedora ID limits
5. Search
   1. escapes within condition params
6. 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?
      2. Ralf Claussnitzer Message headers are useful for filtering (Camel and Nifi) → No need to parse message JSON body.
7. Community-raised bugHousekeeping: 

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

   3306

   3339

8. Your Topic Here

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

   
   

...

1. In Review

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

3. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

4. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

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. sprint
   1. accomplished quite a bit
   2. 1 pending ticket
   3. not a ticket, but progress made on documenting fedora-ocfl structure and header file structure
      1. Fedora Header Files
      2. Fedora OCFL Object Structure
   4. reflections
      1. lots of PRs on Friday => fedoraful weekend
      2. contingencies come up
      3. fairly smooth
   5. next demo
      1. search? Danny & David will work on it.
      2. database work?
   6. mark features that should be done
   7. test suite - someone run it after each spring & track results over time
      1. performance tests - run existing jmeter tests and/or modify them. Add to next sprint.
6. renaming of master branch
   1. sooner or later it'll change
   2. how to handle with existing PRs? can retarget all PRs in GitHub.
7. fedora id limits
   1. OCFL persistence - archival group parts, because of mapping logical paths to content paths
      1. translate between logical path and content path?
   2. limitations based on how to persist fedora-specific data (eg. reserving .fcrepo, ...)
   3. DB - eg. varchar in mysql limit - could be avoided
   4. discuss later
   Open questions: 
   1. JMS: Remove Fedora-related JMS messaging headers? 2018-04-26 - Fedora Tech MeetingACTION: 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-11 - Fedora Tech Meeting)
•  Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-06-11 - Fedora Tech Meeting)
•  Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported
•  Jared Whiklo to investigate impact of removing JMS Headers on camel tooling.