Agenda: Wrap-up for Developer Congress January 22-26, 2024

Owned by Heather Greer Klein
Last updated: Jan 26, 2024 by Randall Floyd

DATE AND TIME

Required roles: Host, note-takerĀ 

  • Host will use the list of topics in the wiki to call on each facilitator. Facilitators should summarize:
    • The focus of the group
    • What the group accomplished
    • Whether there are next steps or follow-up steps and how those have been captured
  • Host will lead a retrospective
    • proposed format: plus/delta
    • Give 3 minutes at the beginning to allow people to take notes on what they want to say
    • Host invites people to "raise hand" to contribute to the retro
    • Participants can speak to both categories at once to reduce the time spent calling on people.
    • Ensure the notes are open so people can add things later



Move Hyrax development testing from Circle CI to GitHib Actions

adapt SoftServ's approach for Hyku to Hyrax:

  • SoftServ's approach works, but Hyrax's approach is complex. We may need an approach that's more custom to Hyrax
  • stuck on feature tests, which needs investigation.Ā 

convert CircleCI config directly to GitHub: unable to connect to solr container


Fold hyrax-iiif-av gem into Hyrax core

  • no updates


Update core components to latest ruby and rails

Created issues in maintenance repo

QA and browse_everything have PRs that have been merged, thanks Jonathan Rochkind

Chris will continue to work on noid_rails

active fedora and hydra head are passing tests


Hyrax Fedora 6 testing

We looked at 6 failing tests in sirenia this week

Effort to update fedora being used w/sirenia to fedora 6.5

Update from Randall Floyd:

Looking at how pairtree IDs work on both the Hyrax and Fedora sides to support the upcoming release of Fedora 6 that will support pairtrees

  • Related to the issue discovered where IDs with encoded slashes breaks sirenia when using Fedora 6.5.0-SNAPSHOT

Trying to find the right way to address issue 6521: "error when approving or requesting changes on a 1 step workflow deposit"

  • I've uncovered a deeper problem in the way certain attributes are handled that can translate IDs that should have no value into non-existent locations in Fedora
  • There are two issues, one on the Hyrax side which then exposes a separate anomaly on the Valkyrie side:
    • When a work is in an admin set with a one-step workflow, it incorrectly changes certain IDs from nil to blank strings
    • But on the Valkyrie side, when IDs are blank strings and not nil, it expands them into locations in Fedora instead of considering them to have no value
  • The existence of these incorrectly translated IDs trigger method calls that result in: FCREPO_URL/fcrepo/rest/development/development: 404, "Ldp::NotFound" etc.
  • The potential for this to occur is broader than 6521, and could even be at the root of other things reported as failing (maybe)

Hyrax Accessibility Testing

Looked at tickets marked accessibility-concern:Ā https://github.com/samvera/hyrax/issues?q=is%3Aissue+is%3Aopen+label%3Aaccessibility-concern

  • Closed 3 issues
  • some were not testable, as they deal with analytics, or file versioning which is not working currently on dev.nurax
  • Most tickets have been partially addressed. We updated these tickets to list current accessibility issues

Rebekah will draft an email to the community asking about Site Improve for nurax, and if anyone needs to meet a standard other than WCAG 2 or EU Accessibility. She will aim to send this to the community and tech lists next week


Hyrax 2.9.8 ā†’ 3.6 Upgrade Path

Thomas is working on documentation:Ā https://github.com/samvera/hyrax/wiki/Upgrade-Hyrax-2.x-to-Hyrax-3

plus

IU group met in person, which was nice

Randall and Dan Field's collaboration was very helpful and the dev congress provided the connection to folks outside the community

Contributions from folks not at dev congress in slack were helpful

delta

Check in times were not convenient and an earlier time might have worked for the attendees, since no West Coast folks attended. Next time, perhaps do a poll for preferred check in times.