2025-04-25 Hyrax Fedora 6 Working Group

 Date

Apr 25, 2025@9am Eastern

 Participants

  • @Arran Griffith

  • @Ben Pennell

  • @Bradley Watson

  • @Collin Brittle

  • @Dan Field - regrets

  • @Daniel Pierce

  • @Emily Porter

  • @Heather Greer Klein

  • @Jon Dunn

  • @Juliet Hardesty

  • @Kate Dohe

  • @Nicholas Mark Homenda

  • @Scott Prater

  • @Randall Floyd

  • @Rebekah Kati

  • @Tom Wrobel

indicates note taker

 Discussion topics

Item

Item

Welcome

Updates:

  • General updates

  • Hyrax Release

    • 5.1.0 Released!

  • F6 Nurax Testing instance for Performance Work now available

    • Performance Testing

      • Do we want to make a public version of this now that F6 Nurax is available and begin asking for community input?

  • Migration updates

What work remains?

  • Capture Performance Testing (Final WG Deliverable)

    • How much? What do we want to do with it once we have “enough”?

Wrap Up

Next meeting:

  • May 23rd @ 9am Eastern

Next note taker: Dan Field

Notes 

Hyrax 5.1.0 release

  • Had been testing sirenia locally, two weeks ago were able to stand up the f6 nurax instance, redid testing

  • Some notes related to Wings and Activefedora issues still present

  • Collections are slow to view, but Daniel has a PR

  • Still making configuration fixes to nurax

  • Probably a 5.1.1 release soon for collections fix and maybe migration tooling

  • After this, will be looking at rails 8 and newer ruby versions, but also want to do some feature development

  • For migration testing, need a reliable way of setting up old style works so that they can be migrated

  • Reach out to Nicholas for additional permissions in nurax

Performance testing

  • Some of the tests would be good to have anyone try, while some of the larger tests should be more restricted

  • Nick suggesting reordering tests to put easier ones first. Also, there is no bulkrax on nurax.

  • We will duplicate testing doc and clean up the columns, will share out the performance testing spreadsheet in the next week or so. Should add a column to say who is testing so we can followup. Plus add instructions.

  • Might be difficult to set up 5000 works. Maybe could use some other automated system for adding works, or "Seeds" test data.

  • If people want to see extra parts of the application (like fedora, ocfl), we will wait for people to ask

  • Considering having a short period for scale testing to limit costs

Looking for labels? They can now be found in the details panel on the floating action bar.