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:   
  • Join Zoom Meeting: https://lyrasis.zoom.us/j/81195576163?pwd=MkIvektGQVhYdGpkZndNOE1DbG5UZz09
  • Meeting ID: 811 9557 6163
  • Passcode: 408241

Attendees 

• Danny Bernstein 
• Arran Griffith 
• Michael Ritter
• Jared Whiklo 
• Ben Pennell
• Doron Shalvi
• Dan Field - Chair 
• James Alexander 
• Demian Katz
•  Thomas Bernhart 

**Each week a meeting chair will be assigned based on a rotating schedule.**

 - denotes note taker

Agenda

1. Announcements:
2. Pop-up/Other Topics:
   1. Questions from the Open Office Hours 
3. Migration Updates:

4. Updates on:

   1. Open Tickets (but assigned in some cases):
      1. FCREPO-3873 - Getting issue details... STATUS
      2. FCREPO-3866 - Getting issue details... STATUS
      3. FCREPO-3864 - Getting issue details... STATUS
   2.  In Progress and older but still relevant open tickets:
      1. FCREPO-3840 - Getting issue details... STATUS
      2. FCREPO-3874 - Getting issue details... STATUS
   3. In Review:
      1. FCREPO-3834 - Getting issue details... STATUS
      2. FCREPO-3830 - Getting issue details... STATUS

5. New tickets:

   1. 1. None

6. Backlog Tickets to consider working:
7. Next Meeting Chair:
   1. Chair: Arran Griffith
   2. Note Taker: Mike Ritter
   3. See Rotating Schedule here 

Notes

1. Announcements:
   1. none
2. Pop-up/Other Topics:
   1. Questions from the Open Office Hours 
      1. First office hours had about 10 people
      2. Next one will be last Wednesday of the Month at 5pm GMT
      3. will need to check if S3 client is doing any checksumming on transmission
      4. When migrating objects into an F6 repo and the files are being written to OCFL, are they written in a flat structure by default?
         1. Within OCFL, it is sorted in a flat structure within OCFL objects by checksum, except for Archival Groups which can have hierarchy within the AG.
      5.  How are the old Fedora 3 pathways maintained in Fedora 6.x?
         1. The PID is in the URL of the new fedora 6 object. On disk, the paths are very different.
      6. Some renewed interest in OAI-PMH support, some offer of support to help develop it.
3. Migration Updates:
   1. Doron gearing up for working on a migration for one of their smaller repositories
   2. Damian - things are going fine, although metrics managed to fill up the disk even though nothing was happening (related to Performance Co-Pilot, not clear if fedora, Prometheus, or other system turned this on)
      
      1. Add a ticket for checking on low level metrics files being written

4. Updates on:

   1. Open Tickets (but assigned in some cases):
      1. FCREPO-3873 - Mike will look at this more soon
      2. FCREPO-3866 - Will be creating new tickets
      3. FCREPO-3864 - Could make for inconsistency in what can be returned between direct addressing of versions versus timestamp negiotation. Will need to be sure that we don't become out of compliance with memento spec.
   2.  In Progress and older but still relevant open tickets:
      1. FCREPO-3840 - Two PRs in, one for API, one for UI. Will show unless a config variable is set
      2. FCREPO-3874 - Not started, just assigned
   3. In Review:
      1. FCREPO-3834 - Confirming that there is test coverage
      2. FCREPO-3830 - A lot of work to understand how things fit together

5. New tickets:

   1. None

6. Backlog Tickets to consider working:
   1. None