Page History

...

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?
   3. Dependency updates - Fedora 7 considerations
3. Migration Updates:

4. Updates on:

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

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

      
      

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

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

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

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

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

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

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

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

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

      Jira

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

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

   3. In Review:
      

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

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

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

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

   
   

5. New tickets:

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

...