...

1. Danny Bernstein
2. Jared Whiklo 
3. Andrew Woods 
4. Peter Winckles  
5. David Wilcox  
6. Ben Cail 
7. Thomas Bernhart 
8. Daniel Lamb
9. Ben Pennell
10. Rosie Le Faive

Agenda

1. Announcements?

2. May 4-8 Sprint
   1.  Updates
      1. Simple Search - 
   - Updates
   1. Simple Search - Fedora 6 Search Service API proposal
   2. Migration tooling
   3. WebAC
   4. Testing
3. Alignment on "Fedora OCFL Storage" proposal
4. Remove Fedora-related JMS messaging headers? 2018-04-26 - Fedora Tech Meeting

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

      2. Migration tooling - 

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

      3. WebAC - 

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

      4. Testing
   2. In-Review

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

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

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

   Naming conflicts from files generated by Fedora
   1. 2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-

      3139

      1. 3297

6. Alignment on "Fedora OCFL Storage" proposal
7. Remove Fedora-related JMS messaging headers? 2018-04-26 - Fedora Tech Meeting
8. Containment Index
   1. How to handle SQL differences (H2, MySQL, PostgreSQL) - pluggable connectors?
9. Change versioning default to opt-out of auto-versioning?

10. <Add 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

Announcements

David Wilcox : Summarizing current work regarding community interactions:

• Online Fedora 
• Building training materials for Fedora 6 → who would/can contribute?
• One online user group meetings/trainings in US
• probably another in European timezone
• Announcements will follow
• Goal keep up community interactions
• fcrepo-terraform project –> can it be made public?

Sprint updates:

Danny Bernstein : Summarizing progress of current sprint:

• All in all: good progress
• Open questions/remarks regarding simple search?
• Simple search:
  • Searching for containment relationships use case? → might make ACL implementation easier
  • include Google Doc (https://docs.google.com/document/d/1nFmvIRmMkGx93hqJUp9unw0RWwqb_DBx8-dvGSSP4iY/edit#) into wiki
• WebAC progress:
  • Jared Whiklo: currently slow
• Testing:
  • API test suite reactivated by Andrew Woods
  • a lot of tests are already passing
• Tickets in review:

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

    should be ready

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

    probably depends on FCREPO-3297, documentation on wiki needs review

Alignment on "Fedora OCFL Storage"

Peter Winckles : summarizing proposal from https://pad.disroot.org/p/874NsxcjLLAAwgIRg2kh

• OCFL objects should be transparent → files on disk match expectations of users what should be in that object
• handle conflicting filenames in OCFL storage, 3 approaches:
  • adding a reserved prefix/suffix → users would be unable to create resources with that prefix/suffix
    • certain files created by fedora will have that prefix/suffix
  • store system generated files in separate directory
    • not outlined in document
    • downside: more directories
    • resource is never in the OCFL object root directory → might be unexpected by users
  • no expectation where a ressource is stored
    • Fedora would have to check the resource headers to find conflicts
    • conflicts are resolved by adding a mapping to the resource headers (if a file needs to be stored under a different name)
    • most of the time, files are exactly where they should be, unless there is a collision
• approaches should be discussed in separate meeting
• main question: transparency of ocfl vs. easier to handle implementation
• Ben Cail favors solution with separate directories
• discussion related to handling Vanilla OCFL –> one approach here is to treat all files Vanilla OCFL objects as binaries
• proposal by Andrew Woods : don't replicate the fedora id into the filename, but use fixed names
  • Jared Whiklo: might lead to conflicts with binaries

Remove Fedora-related JMS messaging headers

Not discussed this week.

Containment Index

Not discussed this week.

Change versioning default to opt-out of auto-versioning?

Not discussed this week.

Actions

•  Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-05-07 - Fedora Tech Meeting)
•  Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-05-07 - 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
  
•  Thomas Bernhart Update some of documentation pages for Fedora 6 (with findings from building the docker container)