...

1. Announcements:
   1. Fedora Open Office Hours recap - Community Q&A Doc has some conversation-type questions in it
   2. New Fedora 6 with a testing instance - Archaeological Map of Czech Republic (https://digiarchiv.aiscr.cz/)
2. Pop-up/Other Topics:
   1. OAI-PMH design meeting
   2. Future of Technology Info Gathering Sessions
      
      1. Encourage your institutions to come and participate - https://fedora.lyrasis.org/fedora-technology-needs-you/
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-3879

          

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

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

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

   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-3874

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

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

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

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

   3. In Review:

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

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

      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. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3880

5. New tickets:

   1. 1. NA at present

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:

1. Fedora Open Office Hours recap:
   Good conversation. Samvera/Hyrax compatability with Fedora 6 / migration to Fedora 6
2. New Fedora 6 with a testing instance - Archaeological Map of Czech Republic (https://digiarchiv.aiscr.cz/)
   Binary data and metadata in Fedora 6; index in Solr; fresh Fedora 6 setup

Pop-up/Other Topics:

1. 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
2. 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.
3. RDF fixity
   

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

   
   Problem: 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?
4. 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. Open Tickets (but assigned in some cases):
   Additional ticket:

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

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

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

   waiting for feedback from government group