Samvera Tech Call 2024-05-22

Owned by Bradley Watson
Last updated: May 22, 2024 by Rebekah Kati
3 min read

Meeting Logistics:

Meeting ID: 773 959 1625

One tap mobile

  • +13017158592,,7739591625# US (Washington DC)

  • +13126266799,,7739591625# US (Chicago)

Dial by your location

  • +1 301 715 8592 US (Washington DC)

  • +1 312 626 6799 US (Chicago)

  • +1 646 558 8656 US (New York)

  • +1 253 215 8782 US (Tacoma)

  • +1 346 248 7799 US (Houston)

  • +1 669 900 6833 US (San Jose)

  • 888 788 0099 US Toll-free

  • 877 853 5247 US Toll-free



Meeting ID: 773 959 1625

Find your local number: https://princeton.zoom.us/u/abfeKpHD7T

Join by SIP 7739591625@zoomcrc.com

Join by H.323

  • 162.255.37.11 (US West)

  • 162.255.36.11 (US East)

  • 115.114.131.7 (India Mumbai)

  • 115.114.115.7 (India Hyderabad)

  • 213.19.144.110 (Amsterdam Netherlands)

  • 213.244.140.110 (Germany)

  • 103.122.166.55 (Australia Sydney)

  • 103.122.167.55 (Australia Melbourne)

  • 64.211.144.160 (Brazil)

  • 69.174.57.160 (Canada Toronto)

  • 65.39.152.160 (Canada Vancouver)

  • 207.226.132.110 (Japan Tokyo)

  • 149.137.24.110 (Japan Osaka)


Meeting ID: 773 959 1625

Agenda (meeting notes below)

  • Dev Congress Report @Daniel Pierce

  • Freyja/Frigg migration adapter status report @Daniel Pierce

  • google analytics 4 progress @Rob Kaufman



Moderator: @Daniel Pierce

Notetaker: @Rebekah Kati

Attendees:

  • @Thomas Scherz

  • @Rob Kaufman

  • @Bradley Watson



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 2023-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: 2023

      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. Dev Congress Report

    1. Randall worked on getting pair-tree support into Hyrax and Valkyrie. Trey has looked at the PR for Valkyrie. Hyrax PR is in progress

    2. Chris looked at changing ordered_aggregation

    3. Daniel and Randall looked at slashes in fedora IDs, but just brainstorming so far

    4. Daniel worked on Frejya/Frigg (see below)

    5. Rebekah and Julie looked at accessibility.

      1. Accessibility audit is finished, Rebekah is currently ticketing issues

      2. Comparison of EU and WCAG guidelines was completed. No additional actions needed for audit, but we need an accessibility statement for nurax compliance. Rebekah wrote recommendations for new Web Accessibility Interest Group to consider

    6. Julie looked at Samvera documentation

      1. Providing links on the Samvera wiki to component documentation on the Github wiki. Julie drafted recommendations for further work for new Documentation Interest Group to take over

    7. Is there a better name for the Developer Congress that could help with attendance?

      1. “Developer Congress” works for in-person, when we’re trying to get travel funds, but maybe not as important for virtual

      2. emphasize upskilling for developers

  2. Freyja/Frigg migration adapter status report

    1. Daniel and LaRita have been working on this

    2. There is a branch where Dassie is configured like Hyku (dassie-combo). When trying to edit work from main branch (which uses ActiveFedora), filesets get saved and re-indexed but file metadata gets routed to Wings. Daniel is currently troubleshooting

      1. Rob suggests that this behavior could be a misconfiguration. LaRita is also doing derivative work which may have affected this. Rob will look at the branch.

    3. Work on Frigg will happen soon

  3. Google Analytics 4

    1. Haven’t been recording events in GA4 in a way that we can report on them. This component broke sometime last year.

    2. Work page and fileset analytics page, user report page are loading properly.

    3. Still need aggregate report to work

    4. Using Google-shipped gem, no more Legato. Google gem doesn’t support alpine binaries. Rob has figured out a work-around. Main drawback is slowness

  4. Github Actions and Hyrax

    1. Daniel needs to get this working for Dassie, but it is working for Koppie