Samvera Tech Call 2025-05-21

Samvera Tech Call 2025-05-21


Meeting Logistics:

Agenda (meeting notes below)

  • Hyrax

    • Community sprint - more user facing/feature focused

    • Investigating Hyrax to interpret WCAG 2.x requirements

    • Looking to upgrade to Solr 9

  • Question: how do we determine key values for all languages we have locales for?

 

Moderator: @Randall Floyd

Notetaker: @Bradley Watson

Attendees:

  • @Daniel Pierce

  • @Mark Bussey

  • David Moles

  • @Tracy McCormick

  • @Nic Don Stanton-Roark

  • Nick from Notch8




Meeting Process

  1. Standing pre-agenda items (moderator)

    1. Welcome

      • "Welcome everyone, please add your name to the Attendees list.  If you are unable to do so, please let us know, and someone will add you. To any newcomers, Welcome, and please feel free to ask questions. Likewise for all attendees. We strive for an open and accessible conversation around Samvera technology."

    2. Call for new agenda items

  2. Follow Agenda from above (facilitated by moderator) and record notes in Notes section below (note taker)

  3. Standing post-agenda items (moderator)

    1. call for next moderator and note taker (moderator)

      1. Moderator:

      2. Notetaker:

    2. Samvera help follow-up (moderator)

    3. Pull request review (moderator)

      1. Recent Samvera PR list

  4. Post-meeting action (note taker)

    1. After call, this week's notetaker should create the agenda for the next call:

      1. Open template agenda titled "Samvera Tech Call XXXX-XX-XX"

      2. Click on ... in the top right corner, and select copy.

      3. Popup will open for location. It should contain:

        1. Space: Samvera

        2. Parent page: (Verify value is current year)

      4. Select copy. New page should be created.

      5. Modify the title to remove "copy of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish. 




Notes

  1. @Mark Bussey: Upgraded v5.0.4 to Hyrax v5.1 and was surprised to find that he had to jump from Rails 6 to 7.

    1. Can that be better documented or include compatibility for Rails 6?

    2. Maybe it should have been a major release.

    3. More consideration should be given to advise less seasoned Hyrax implementers of possible breaking changes and resolutions.

    4. @Randall Floyd will own the expanding of the documentation on both versions.

  2. Question: how do we determine key values for all languages we have locales for?

    1. Previously, YAMLs were put through Google Translate tools and then passed to language experts for approval/remediation.

    2. There may be more nuanced AI tools now available for future translations.

  3. Next week’s Moderator: @Randall Floyd

  4. Next week’s Notetaker: David Moles