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:
- Join Zoom Meeting: https://lyrasis.zoom.us/j/81195576163?pwd=MkIvektGQVhYdGpkZndNOE1DbG5UZz09
- Meeting ID: 811 9557 6163
- Passcode: 408241
Attendees
- Arran Griffith
- Michael Ritter - Chair
- Jared Whiklo
- Ben Pennell
- Doron Shalvi
- Dan Field
- James Alexander
- Demian Katz
- Thomas Bernhart
**Each week a meeting chair will be assigned based on a rotating schedule.**
- denotes note taker
Agenda
- Announcements:
- Fedora Open Office Hours recap - Community Q&A Doc has some conversation-type questions in it
- New Fedora 6 with a testing instance - Archaeological Map of Czech Republic ( https://digiarchiv.aiscr.cz/)
- Pop-up/Other Topics:
- OAI-PMH design meeting
- Future of Technology Info Gathering Sessions
- Encourage your institutions to come and participate - https://fedora.lyrasis.org/fedora-technology-needs-you/
- Migration Updates:
Updates on:
- Open Tickets (but assigned in some cases):
- FCREPO-3879 - Getting issue details... STATUS
- FCREPO-3875 - Getting issue details... STATUS
- FCREPO-3850 - Getting issue details... STATUS
- FCREPO-3849 - Getting issue details... STATUS
- In Progress and older but still relevant open tickets:
- FCREPO-3878 - Getting issue details... STATUS
- FCREPO-3876 - Getting issue details... STATUS
- FCREPO-3874 - Getting issue details... STATUS
- FCREPO-3873 - Getting issue details... STATUS
- FCREPO-3871 - Getting issue details... STATUS
- FCREPO-3868 - Getting issue details... STATUS
- FCREPO-3840 - Getting issue details... STATUS
- In Review:
- FCREPO-3867 - Getting issue details... STATUS
- FCREPO-3839 - Getting issue details... STATUS
- FCREPO-3834 - Getting issue details... STATUS
- FCREPO-3830 - Getting issue details... STATUS
- FCREPO-3880 - Getting issue details... STATUS
- Open Tickets (but assigned in some cases):
New tickets:
NA at present
- Backlog Tickets to consider working: NA at present
- Next Meeting Chair:
- Chair: Doron Shalvi
- Note Taker: Dan Field
- See Rotating Schedule here
Notes
Announcements:
- Fedora Open Office Hours recap:
Good conversation. Samvera/Hyrax compatability with Fedora 6 / migration to Fedora 6 - New Fedora 6 with a testing instance - Archaeological Map of Czech Republic ( https://digiarchiv.aiscr.cz/)
Binary data and metadata in Fedora 6; index in Solr; fresh Fedora 6 setup
Pop-up/Other Topics:
- OAI-PMH design meeting
Open question: start on base of an exisitng OAI-PMH implementation for Fedora 4, 5 or 6
next step: start to create tickets to actually plan work - Future of Technology Info Gathering Sessions
Registration open: https://fedora.lyrasis.org/fedora-technology-needs-you/
2 groups: new/future users, existing Fedora 6 implementers. Registration is necessary!
Open for core administrators as well as people working with Fedora. - RDF fixity
FCREPO-2253 - Getting issue details... STATUS
Problem: checksum depends on serialization format
What canonical representation to use to compute the checksum? Proposed by Quinn Hart: https://www.w3.org/community/reports/credentials/CG-FINAL-rdf-dataset-canonicalization-20221009/
What should be included in the checksum? Only user-added triples? Server-managed triples as well? - Meaning of deletions (of a resource? of a tombstone? deletion of archive groups?) in Fedora 6
Deleting a resource → data is only marked as deleted in OCFL
Deleting the tombstone → the OCFL object is actually deleted (except if it's part of a archival group, then it would still be available in a older version of the archival group).
Quinn proposes some changes to how deletion within archival groups works.
Discussion: Recover a deleted object from a tombstone by adding a special header to a PUT request to tombstone?
Next steps: Jared Whiklo will create 3 tickets to track the discussion
Would it be a breaking change to introduce this behaviour? Do we have to wait for Fedora 7?
Migration Updates: skipped
Updates on:
- Open Tickets (but assigned in some cases):
Additional ticket: FCREPO-3864 - Getting issue details... STATUS seems like something that can be solved. - In Progress and older but still relevant open tickets:
Only some tickets were discussed briefly - In Review:
FCREPO-3839 - Getting issue details... STATUS waiting for feedback from government group