...

1. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

3. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

Minutes

API Spec Outstanding Issues

• #82 about ordering issues, which was largely not an API issue
• #81, a little bit of langage in the spec should clear up confusion here
  • change a "may" to a "must" if a preference is applied, the fedora implementation should say so
• #80, there's some disagreement about whether fedora should redirect or proxy to external content, and once a clear consensus is achieved, the spec should reflect it
  • Benjamin Armintor is the only one who has articulated a need for proxying, while presumably other stakeholders are content with redirects
    • Feedback at LDCX suggested that other stakeholders minimally preferred proxied content, and in some cases required it.
  • A new issue was opened for this Proxy vs. Redirect requirement in the spec.

Committer's needed to close PRs

• S3 Configuration ticket needs to be merged, but someone with S3 storage should test them
  • no one on the call volunteered as having S3 storage
  • Esmé Cowles will contact Andrew Woods about this

A PR from Danny Bernstein to address performance of items with lots of properties

• This is almost done, but maybe a test failure is holding it back

In-Flight tickets (none?) and Bugs

• no questions or comments about current outstanding bugs.