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/my/fedora
- Dial-in:
+1 408 638 0968
+1 646 876 9923
+1 669 900 6833
Meeting ID:
812 835 3771
- Dial-in:
Join fedora-project.slack.com on the "tech" channel
Attendees
Part 1:
- Danny Bernstein
- Peter Winckles
- Andrew Woods (out)
- David Wilcox (out)
- Peter Eichman
- Joshua Westgard
- Ben Pennell
- Jared Whiklo
- Bethany Seeger
- Paul Cummins
- Youn Noh
Part 2:
Agenda
- Announcements
- Sprint Planning
- 6.0 Architecture Review
- Coming to consensus on unversioned/staged content
- what shall we call it: staged or unversioned
- Multi-object transaction implementation ideas
- Transaction Sidecar Spec Update
- Status on organizing a Fedora documentation review
- Update on Fedora 6 Pilots
- Status
- API Test Suite PRs
- Minimal 4 →5 migration needs testing and code review:
- API Test Suite PRs
- Your topic here...
Tickets
In Review
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Notes
PART 1
OCFL Java Client - let's get Peter Winckles and Aaron Birklandtogether for a discussion about a common java ocfl client interface / interaction model - hopefully we can discuss in part two of today's meeting.
Designed outcome: a java interface that will support both the java client and a JNI-wrapped Go Client.
Bethany Seeger : will take a look at Greg Jansen 's PR.
Danny Bernstein to add a discussion point around API Test Suite modifications and overall spec compliance discussion.
Joshua Westgard to look into fcrepo-upgrade-utils PR the next week.
Danny Bernstein to run upgrade routine on sample (e.g. plant patents ) datasets
Paul Cummins raising the concern about bloat with respect automated versions. His Fedora 3 application performs frequent updates to binary content. In a world of version on change, he would quickly experience bloat. "Copy into new OCFL object + Delete old OCFL object" mechanism for removing unwanted object history is an acceptable solution.
There was shared on the understanding of the new versioning proposal and its implications.
PART 2
Ben Pennell , Peter Winckles and Danny Bernstein continued the discussion of the new versioning proposal.
Everyone seemed concerned that this would represent a significant departure from the current interaction model of Fedora.
Also storing "significant version" files in OCFL seems a bit convoluted. In order to restore a previous version, clients would need to indicate whether or not to make the restored version "significant". Fedora or possibly the client would then need to remove or keep that marker file accordingly.
Question: What is the standard for rebuildability from OCFL? Are we still in agreement that you should be able to take an OCFL layout, copy it to a new location, stand up a new fedora instance against it, and have the state of Fedora be exactly what it was before the move? Can any non-derivative state live outside OCFL?
The meeting was adjourned early due to the low turnout.
Actions
- Aaron Birkland to look explore notion of OCFL client with database as authoritative metadata source + asynchronous writing of the inventory.json file
- Peter Eichman and maybe Ben Pennell to make recommendations re transaction side car specification.
- Andrew Woods will look into java 11 transition
