...

• 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 

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

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

...

1. Announcements:
   1. Future of Technology Info Gathering Sessions
      
      1. Encourage your institutions to come and participate - https://fedora.lyrasis.org/fedora-technology-needs-you/
2. Pop-up/Other Topics:
   
   1. Hyrax Valkyrization Community Meeting (April 10 @ 1pm Eastern) - https://groups.google.com/g/samvera-community/c/mh5rSk8EuXU/m/Fg62-5zwAgAJ
   2. Documentation process for new releases review
3. Migration Updates:

4. Updates on:

   1. Open Tickets (but assigned in some cases):

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3883

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3882

      3. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3881

      4. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3879

      5. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3875

      6. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3844

   2.  In Progress and older but still relevant open tickets:

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3878

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3876

      3. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3871

      4. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3868

   3. In Review:

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3880

          

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3867

          

      3. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3834

          

      4. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3830

          

5. New tickets:

   1. 1. OAI-PMH tickets?

6. Backlog Tickets to consider working: NA at present
7. Next Meeting Chair:
   1. Chair: Doron Shalvi
   2. Note Taker: Dan Field
   3. See Rotating Schedule here 

Notes

Announcements:

...

• Ben hoping to attend Hyrax
• Agreement that the wiki is confusing at times. Several tables like Documentation exist already. Take the discussion to the larger tech group to see about reducing further duplication of effort between wiki and github documentation.

Pop-up/Other Topics:

Migration Updates:

• Doron still ongoing 3 to 6 migration (smaller repo). On prem. Moving UI elements of the stack to cloud. Migration validator output is a bit hard to search or use. It might be nice to have a RDBMS output option
• NLW testing atomic migration alongside archival group and archival group head only

Updates on:

1. Open Tickets (but assigned in some cases):
   
   

   1. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3883

      - came out of discussion in tech meeting last week with Quinn Hart.  Nothing done yet.  Bring behavior of archive groups in line with OCFL?  Needs design discussion?  

   2. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3882

      - same as 3883

   3. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3881

      - same as 3883
2. OAI-PMH design meeting
   Open question: start on base of an exisitng OAI-PMH implementation for Fedora 4, 5 or 6
   next step: start to create tickets to actually plan work
3. Future of Technology Info Gathering Sessions
   Registration open: https://fedora.lyrasis.org/fedora-technology-needs-you/
   2 groups: new/future users, existing Fedora 6 implementers. Registration is necessary!
   Open for core administrators as well as people working with Fedora.
4. RDF fixity
   2. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-

   2253Problem: checksum depends on serialization format
   What canonical representation to use to compute the checksum? Proposed by Quinn Hart: https://www.w3.org/community/reports/credentials/CG-FINAL-rdf-dataset-canonicalization-20221009/
   What should be included in the checksum? Only user-added triples? Server-managed triples as well?
5. Meaning of deletions (of a resource? of a tombstone? deletion of archive groups?) in Fedora 6
   Deleting a resource → data is only marked as deleted in OCFL
   Deleting the tombstone → the OCFL object is actually deleted (except if it's part of a archival group, then it would still be available in a older version of the archival group).
   Quinn proposes some changes to how deletion within archival groups works.
   Discussion: Recover a deleted object from a tombstone by adding a special header to a PUT request to tombstone?
   Next steps: Jared Whiklo  will create 3 tickets to track the discussion
   Would it be a breaking change to introduce this behaviour? Do we have to wait for Fedora 7?

Migration Updates: skipped

Updates on:

1. 1. 3879

      - waiting on third party release

   2. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3875

      - would be good to do, need to schedule doc update, maybe after 3883 discussion

   3. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3844

      - no new update since October, wait for Demian
2. In Progress and older but still relevant open tickets:
   
   

   1. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3878

      - PR created, Mike to review

   2. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3876

      - PR created by Mike, needs review.  Dan could take a look, could use another reviewer, Doron

   3. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3871

      - no update, something similar added in slack last week. Sanity check also fails locally for Mike, UTF-8 related.

   4. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3868

      - no update. Still shipping with Java 11, but want to test on 17 and ensure everything works, be prepared for 17.
3. In Review:
   
   

   1. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3880

      - PR ready, needs review.  Mike may test.
   Open Tickets (but assigned in some cases):
   Additional ticket:
   2. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-

   3864 seems like something that can be solved.
4. In Progress and older but still relevant open tickets:
   Only some tickets were discussed briefly

5. 1. 3867

      - can be closed

   2. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3834

      - ready for test - James
   In Review:
   2. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-

   3839

   1. 3830

   waiting for feedback from government group
   1. - waiting on Jared to test

6. New tickets:

   1. 1. OAI-PMH tickets?

      2. Dan started some OAI-PMH work within Java 17