...

1. Announcements
   
   1. Fedora 6.1.1
2. FYI: Fixity Service Design Document
3. Breaking change alert: https://github.com/fcrepo/fcrepo/pull/1956
4. OCFL Version Squash Tool?
5. 5.x Release Status
6. Demo videos
7. Fun tickets

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

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

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

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

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

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

8. ?

...

• In Review

  Expand
  Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

  
  

• 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

  
  

• 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

  
  

• 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

1. Announcements
   1. Danny was part of a roundtable for Phaidracon. Phaidra is a digital management system out of University of Vienna. 3 day conference.
   2. Demian did a demo video for the camel-toolbox http forwarding service. May not have been released yet.
   3. End of the month a Fedora workshop for Squib coming up at the end of the month.
2. Not a huge response to the survey. Lots of interest in a scheduled fixity service.  How do we move this idea forward?
   1. Call a meeting with those interested to flesh out the proposal.
   2. Do you check only HEAD state or all past versions?
   3. For large repositories this would need to be a continous running process. But for smaller repositories we would not to perform too many checks in a small timeframe.
   4. What data do we track for a check? Is this sort of an audit service?
   5. Make use of the camel-toolbox's existing fixity service?
   6. Do we store fixity output on the resource? Do we send an email or call an external service?
      1. Storing the fixity result on the resource would generate an OCFL version which could cause OCFL bloat.
   7. Side discussion about OCFL version squashing and how it might work.
3. PR in fcrepo-camel-toolbox that Danny needs for the release.
4. :
   
   1. Fedora 6.1.1 and camel toolbox released
5. Fixity service design underway: https://wiki.lyrasis.org/display/FF/Design+-+Fixity+Service
6. Changing content-disposition from "attachment" to "inline" (https://github.com/fcrepo/fcrepo/pull/1956)
   1. "inline" causes the binary to be loaded in the browser without a dialog popup
   2. Support for leaving current behavior and introducing a query param to control output
   3. Some content-disposition headers are deprecated, but we'll continue to use them for now
7. OCFL squash?
   1. There is some interest in having this feature
   2. Does it need to be a feature in Fedora or can it be an external tool?
   3. This is not currently possible in Fedora because you cannot currently reindex single resources that already exist. (https://fedora-repository.atlassian.net/browse/FCREPO-3553)
   4. The squash could be done either inplace or by cloning the object, modifying it, deleting the original, and moving the clone into place (could be quite slow for large objects on slow storage)
   5. What is community interest?
   6. What does the OCFL community think of squash?
8. 5.x release
   1. modeshaped released
   2. outstanding pr to update fedora to use the new modeshape version
   3. get Eli to test
   PR for modeshape S3 issues need to create release of it.