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/my/fedora
  
  • Dial-in: 
    +1 408 638 0968
    +1 646 876 9923
    +1 669 900 6833
    Meeting ID:
    812 835 3771

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

Attendees

Part 1: 

1. Danny Bernstein 
2. Peter Winckles
3. Jared Whiklo 
4. Bethany Seeger 
5. Thomas Bernhart 
6. Aaron Birkland
7. Andrew Woods  
8. Ben Pennell 
9. Ben Cail
10. David Wilcox
11. Peter Eichman

Agenda

1. Announcements 
   1. Sprint 2
   2. ?
2. See if we can get a unified vision for how we want Fedora to interact with OCFL, so that we can propose one of the following to the leadership group:
   1. Recommend pushing for changes to the OCFL spec (i.e. a mutable head), so that both versioned and un-versioned content can be "in" OCFL
   2. Accept the immutability of object versions in OCFL, and recommend one of the following
      1. Fedora shall store un-versioned content outside of OCFL in a fedora-specific layout
      2. Fedora shall disallow un-versioned content entirely
   3. Recommend Fedora use something other than OCFL for Fedora's persistence layer, and create external tools for exporting/publishing to OCFL when desired.
3. This document describes the core issues and outlines the pros and cons of the implementation possibilities described in the preceding agenda item. Recommending a particular implementation is beyond the scope of the document; it simply seeks to provide an objective (to the degree possible) analysis to serve as a baseline for an informed discussion. Comments and suggestions are welcome, but please respect the scope of the document.
4. Other questions to be answered
   1. > “When making a request during a transaction, should the ACL of the HEAD version of the resource be evaluated, or the ACL of the version of the resource that exists in the transaction?”
      1. Related to https://github.com/fcrepo4/fcrepo4/pull/1559
      2. from Decisions and Open Questions
   2. What is the approach we want to take for adding digests to external binaries?
      1. Reference: 2019-09-26 - Fedora Tech Meeting (Notes: 3.a.)
   3. What do we want our approach to be for loading Fedora6 resources? lazy or eager?
      1. Related to https://github.com/fcrepo4/fcrepo4/pull/1557 
5. <add topics here>

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

Actions

• Aaron Birkland  to look explore notion of OCFL client with database as authoritative metadata source + asynchronous writing of the inventory.json file
• David Wilcox will review the NDSA matrix and pull out the concrete technical requirements that could be considered during the Fedora 6 development.