Time/Place
This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Audio/Video Conference Link: https://lyrasis.zoom.us/j/88068382811
- Meeting ID: 880 6838 2811
- Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia
Join fedora-project.slack.com on the "tech" channel
- Self-register at: http://slack.fcrepo.org/
Attendees
- Danny Bernstein
- Arran Griffith (out)
- Jared Whiklo
- Peter Winckles
- Ben Pennell
- Calvin Xu
- Michael Ritter
- Demian Katz (out)
- Geoff Scholl
Agenda
- Announcements
- Camel toolbox update - release is in progress
- Survey Results (Part 2)
- Scheduled fixity service
- New Issue:
- FCREPO-3792 - Getting issue details... STATUS
- 5.x Release Status
- Modeshape fork PR: https://github.com/fcrepo-exts/modeshape/pull/12
- PRs
- Progress on Tickets
- FCREPO-3790 - Getting issue details... STATUS
- FCREPO-3768 - Getting issue details... STATUS
- FCREPO-3751 - Getting issue details... STATUS
- FCREPO-3673 - Getting issue details... STATUS
- FCREPO-3719 - Getting issue details... STATUS
- FCREPO-3635 - Getting issue details... STATUS
- ?
Tickets
In Review
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
- Announcements
- Danny was part of a roundtable for Phaidracon. Phaidra is a digital management system out of University of Vienna. 3 day conference.
- Demian did a demo video for the camel-toolbox http forwarding service. May not have been released yet.
- End of the month a Fedora workshop for Squib coming up at the end of the month.
- Not a huge response to the survey. Lots of interest in a scheduled fixity service. How do we move this idea forward?
- Call a meeting with those interested to flesh out the proposal.
- Do you check only HEAD state or all past versions?
- 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.
- What data do we track for a check? Is this sort of an audit service?
- Make use of the camel-toolbox's existing fixity service?
- Do we store fixity output on the resource? Do we send an email or call an external service?
- Storing the fixity result on the resource would generate an OCFL version which could cause OCFL bloat.
- Side discussion about OCFL version squashing and how it might work.
- PR in fcrepo-camel-toolbox that Danny needs for the release.
- PR for modeshape S3 issues need to create release of it.