2024-03-28 Hyrax Fedora 6 Working Group

\uD83D\uDDD3 Date

28 Mar 2024@9am Eastern

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

Updates
Establish next steps for Sirena/Nurax

\uD83D\uDDE3 Discussion topics

Time	Item	Notes
10:00am-10:05am	Welcome	Volunteer Note taker? Julie
10:05am - 10:30am	Updates Updated Scope & Objectives Published Outstanding Sirenia work? Migration News Emory?	new deliverables and timeframes are in place on wiki; old ones are archived on a separate page so they still exist Fedora 6.5 release is out HMWG sprint hasn’t focused on Sirenia - this will be Hyrax 5.1 release; to get there we need CI testing set up completed (switch over to Github Actions); add Sirenia tests to that and away we go Hyrax 5.1 will be fixing significant bugs for Sirenia and fix pair-tree change from Fedora update no timeframe for 5.1 yet, analytics work happening first/in parallel (if we have resources available) before Daniel’s tech lead time is done (July 1) Next HMWG sprint starts April 15 migration and Emory - Emily reports building out prod instance of Hyrax 5 with Fedora 6; setting up work type and configs and bring over local customization for pres metadata (fixity checking, virus scanning); using S3 storage with Fedora 6; migrating collection from Fedora 3, doing export using Fedora tools then bring in to Hyrax through Bulkrax; testing Bulkrax soon; found new bugs and reported with tickets (Circle CI with Fedora 6 on Samvera-orb) next thing for Fedora - next major release but not feature-heavy; updating dependencies; no timeline yet performance testing with Fedora 6 happening now in high perf computing environment (cloud storage) - Texas Advanced doing this, testing with research data (many children, deeply nested; also Lidar files, super-large)
10:30am - 10:50am	Nurax set up Performance Testing	nurax-stable will get Fedora 6 (and maybe get a rename) performance testing use cases - Emory has added some and others need to add to this list! question from Ben Pennell - are there other benchmarks for Hyrax (with Postgres or other setups) - performance testing use cases lists setups we want to try in addition to Hyrax 5/Fedora 6 Randall Floyd and Randall Embry at IU load balance testing with Fedora 4 - anything to factor in for performance testing? have to think about it; not sure what exactly is happening to cause slow responses but once we know something, we can report here; external factors that can impact Fedora performance (in general) - something to keep in mind for performance testing
10:50am - 11:00am	Wrap Up Next meeting proposal: April 26th @ 9am Eastern Establish regular meetings 4th Friday of each month at 9 am Eastern?	Emory/Emily proposing lightning talk about H5 F6 work for SVC Arran doing working group update at SVC (thank you!!) meeting times - 4th Friday of month at 9am Eastern next meeting Friday, April 26 at 9am Eastern

Notes

Welcome
- Hyrax/Fedora working group will present at Samvera Connect
Updates
- Working on migration tooling primarily worked on by Softserv for Hyku. Updating the Dassie app to make use of it.
- Freya - adapter for postgres
- Frigg - adapter for fedora 6 - commented out waiting on other work
- Required for support of Fedora 6
  - Issue with admin set default IDs which contain a slash, may work on in the developer congress
    - admin_set/default is the default admin set
    - Causes an error in Fedora 6 even when options are set that supposed to allow the / to be encoded
    - Colin - recommends changing name of default admin set to not contain URL unsafe character
      - Concern is that users may have other encoded slashes or characters in non-hyrax standard IDs, so we would not be able to address that in hyrax
    - Fedora Jira issue for the problem https://fedora-repository.atlassian.net/jira/software/c/projects/FCREPO/issues/FCREPO-3933?jql=project%20%3D%20%22FCREPO%22%20ORDER%20BY%20created%20DESC
      - Currently believe it is a tomcat issue, since the version of tomcat in docker went up between versions of Fedora.
    - Valkyrie needs to be updated to work with pair trees
    - Files in filesets, or filesets themselves (can’t remember which) attached to do not get put into pair trees at the moment
    - To enable pair trees, have to pass in docker configuration options
- Emory update
  - When persisting binaries to S3 through fedora 6, the binaries are not persisted with any mimetype or filename. So files are only interpretable through hyrax/fedora, since there is no info about what they are in S3. Not sure if its a fedora or hyrax issue
    - Tom - can set the filename via setting Slug, and mimetype with header.
      - They use hyrax 2.6 with a custom fedora 6 adapter https://github.com/bodleian/fedora6_client/blob/develop/lib/fedora6/client.rb
      - Not sure if doing this in valkyrie would be a problem or not, would need to investigate
        Looks like there is support for content-type in valkyrie, but the more recent versioned object type does not currently support it, so that will need to be added in.
    - It looks like ocfl-java does allow content-types to be supplied when uploading files:
      - https://github.com/OCFL/ocfl-java/blob/05aa875d50a8f8e9fc58bba825c9ffce43dc3699/ocfl-java-aws/src/main/java/io/ocfl/aws/OcflS3Client.java#L182
    - Sirenia issue: https://github.com/samvera/hyrax/issues/6521
      - Most likely resolved now by other PRs that were taking place - Emily will add comments to the ticket, and maintenance working group will re-test.
Nurax setup / Performance testing
- Next steps are to outline what we want to test

Updates:

✅ Action items

⤴ Decisions