...
Michael Ritter - Chair
Doron Shalvi
James Alexander (notes)
Arran Griffith
Demian Katz
Jared Whiklo
Dan Field
Announcements:
TCDL recap from Aran - Texas universities, UT testing with F6 and migrating/considering migration from F4, maybe something to show by the fall
Good opportunity to meet Fedora folk, including TACC
Fedora Open Office Hours - May 31st @ 12pm Eastern (https://bit.ly/3pffGEV) https://wiki.lyrasis.org/display/FF/2023-05-25+-+Fedora+Tech+Meeting
Governance meeting next week, Friday
Pop-up/Other Topics:
Linked Data Notifications - Oliver Schöner from Berlin State Library wants to bring up this topic at the June 12th Tech Info Session for Fedora 6 users (see also Slack channel for recent conversation)
Confederation of Open Access Repositories -
https://www.coar-repositories.org/
Should Fedora have representation here? Question for Governance
Pop-up topics
Doron - migration x2 F3s. Test migrating smaller (c 4million citations), tried migration in cloud - faster than on-prem (which took x5 days) - still to validate.
...
OCFL has released a new version today. The Group ID changes will require a PR.
Upcoming performance improvements are deferred.
Updates on:
https://fedora-repository.atlassian.net/jira/software/c/projects/FCREPO/issues
Open Tickets (but assigned in some cases):
FCREPO-3881 - Disallow DELETE of tombstone of objects in an Archival Group OPEN
FCREPO-3882 - Allow access to the timemap and versions from a tombstone. OPEN
FCREPO-3883 - Allow PUT over a tombstone OPEN
Above will be discussed at GoverneanceGovernance
FCREPO-3851 - Catalina session error on start OPEN
Session deserialization - problem does not break anything.
Mike will standup docker. Jared will try and reporiduce reproduce the error
In Progress and older but still relevant open tickets:
...
FCREPO-3834 - Enable Camel toolbox to send xml records to Solr indexing service IN REVIEW
Jaren Jared will review
FCREPO-3802 - Specify Stats API IN REVIEW
In June documentation was written and appears to be complete. Fixed versions in Sept. This is Is this complete. ? Explanation of the aim for API (standardized storage metrics) could be added.
New tickets:
https://github.com/fcrepo/fcrepo/issues/2040
Transaction Id could usefully be added to the log (but it would be a possible threat risk). Jared will respond to Tom in the ticket. This could be a configurable toggle. Backlog Tickets to consider working: NA at present
GitHub & Jira
We have GitHub and Jira but do we need both? Could we transition to just GitHub? for most people its convenient and improving but has some stability issues (Demian).
Jira is Altassian (so it may not be here to stay after Lyrasis upgrades from the current Confluence). You need to register to use Jira. Also transitioning and assigning state can be quite complex and enterprise-orientated and we haven't taken time for onboarding with this (as well as using GitHub).
We could shut down Jira for new tickets and archive them.
Possible issue with documentation that would need to be updated?
...
A discussion to be continued another time.
Next Meeting
Apologies for next week - James Alexander
Next Meeting Chair:
Chair: Ben Pennell (for Mike Ritter)?? or Doron Shalvi
Note Taker: Thomas Bernhart