...

1. Announcements:
2. Pop-up/Other Topics:
   1. Slack Questions
      1. https://fedora-project.slack.com/archives/C8B5TSR4J/p1711558664660589 - rehashing Fedora ID's to replicate object ID's in S3 (I think this was answered, but I think Emily was thinking a documentation update to include what Scott suggested would be helpful)
      2. https://fedora-project.slack.com/archives/C8B5TSR4J/p1711995943026199 - Doron's question about how to find out what's already in an index (again, I think this is resolved, but is there any follow up needed on this?)
      3. https://fedora-project.slack.com/archives/C8B5TSR4J/p1712220464339919 - Tom's questions....resolved?
   2. User from University of Zagreb looking for examples using the API requests integrated with PHP? Or Laravel specifically. Thoughts?
   Dependency updates - Fedora 7 considerations
   3. Use Jira filters to get ticket lists for agenda? Thomas Bernhart 
   4. Permissions to share Jira ticket filters with other users and publicly Thomas Bernhart 
   5. Default container type for migration utils. Archival Group (current) vs Atomic Resource 
3. Migration Updates:

4. Updates on:
   

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

      Jira
      created >= -1W AND statusCategory = "To Do" ORDER BY updated DESC, created DESC server Fedora JIRA columnIds issuekey,summary,issuetype,created,assignee,reporter,priority,status,created,updated columns key,summary,type,created,assignee,reporter,priority,status,created,updated maximumIssues 20 jqlQuery filter=10022 serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4

      
      
      

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

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

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

      3931

      4. 3932

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

      -3929

      6. -3931

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

      Jira
      server Fedora JIRA columnIds issuekey,summary,issuetype,assignee,reporter,priority,status,created,updated columns key,summary,type,assignee,reporter,priority,status,created,updated maximumIssues 20 jqlQuery filter=10023 serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4

      
      
      

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

   3928

   3. 1. 3918

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

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

   3924

   4. 1. 3923

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

   3923

   5. 1. 3924

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

   3918

   6. 1. 3922

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

   7. In Review:3932 In Progress and older but still relevant open tickets:
       
      

      Jira

      server Fedora JIRA columnIds issuekey,summary,issuetype,created,updated,assignee,reporter,priority,status,created,updated columns key,summary,type,created,updated,assignee,reporter,priority,status,created,updated maximumIssues 20 jqlQuery (created <= -1W AND statusCategory = "To Do") or (statusCategory = "In Progress") and updated >= -90d order by updated DESC filter=10024 serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4

      
      
      

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

      In Review:

      1. 3919

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

      3919

      3. 3917

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

      3917

      5. 3912

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

      3912

      7. 3897

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

      3897
   New tickets:

   1. 1. 3834

5. Backlog Tickets to consider working:
6. Next Meeting Chair: 
   1. Chair: Dan Field 
   2. Note Taker: James Alexander 
      

See Rotating Schedule here 

Notes

1. Announcements
   1. User group gathering at Open Repositories, starting some planning for Sweden.
   2. Fedora will be at TCDL Texas Conference on Digital Libraries, second day at 7:00 AM!!!
2. Pop-up topics: Emily and Ayoub from Emory University.
   1. Working with Hyrax 5, Valkyrie, Fedora 6 and AWS for storage. Issue upgrading from the 6.4.0 docker container to the 6.5.0. Tomcat will not accept encoded slashes anymore.
   2. Also need to update the base Tomcat tag. 
   3. Feature request to add in to the HTML UI the hash path to the object in the OCFL root.
   4. Files persisted to S3 are not getting a mime-type in their AWS metadata. Seems like this is how Hyrax persists. The mime-type is stored in a separate container and not on the actual binary, so it becomes application/octet-stream.
3. Slack topics
   1. Fedora to OCFL hash ids - new ticket generated
   2. Doron's question about how we track objects in the index. Would it be faster to hold that list in memory? Would we run out of memory?
4. David Wilcox is the keymaster and we are asking if he can give some keys to Arran to perhaps make some changes to make Jira a little more user friendly. Also to open sharing of filters. View tickets without logging in.
5. Discussion of use of Archival Groups in migration utils, should we change the default to Atomic. 
   1. Which you use is really dependant on your particular use case and data model.
   2. Arran is going to set up a community call to discuss why people might choose one over the other.