Samvera Tech Call 2024-02-07

Owned by Chris Colvard
Last updated: Feb 07, 2024 by Daniel Pierce
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)



Moderator: @Jeremy Friesen

Notetaker: @Bradley Watson

Attendees:

  • @Jeremy Friesen

  • @Shana Moore

  • @LaRita Robinson

  • @Heather Greer Klein

  • @Chris Colvard

  • @Daniel Pierce

  • Kirk Wang

  • @Bradley Watson

  • @Rebekah Kati



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)

  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. Hyrax 5.0.0.rc3:

    1. Double combo is not blocking 5.0.0 and is looking like it can be a minor version release; many PRs have been submitted to main regarding bugs discovered during the Hyku upgrade to Hyrax 5 (by way of the Double Combo PR)

    2. Release candidate is the goal.

  2. Jeremy found some things in Hyrax that didn’t work with Valkyrie. PRs are upcoming.

  3. Hyku work is producing more errors locally versus Circle CI; SoftServ is working through these as part of the upgrades.

  4. Jeremy has been documenting the upgrade of Hyrax in Hyku, found here: https://github.com/samvera/hyku/wiki/Updating-Hyku-6-with-Hyrax-5-Developer-Notes#access-control-list-acl-considerations

  5. App generation has been ongoing to provide new Hyrax users a proper valkyrie environment to work with by Daniel:

    1. Now using Lando for providing backend services (see Lando https://github.com/lando/lando ).

    2. Zeitwerk fixes are also ongoing.

    3. Lando spins up a Postgres environment and should work with Fedora as well (not tested yet).

  6. double_combo:

    1. What context do others need to help understand the PR?

    2. This work could wait for future releases or RCs.

    3. One discovered bug is that the creation of an admin set is hard-coded to use the Valkyrie model, ignoring the configuration. You could still create by hand an AdminSet object but the service does not provide that native support. SoftServ’s exploring what steps we can take regarding that.

      1. Unable to create a non- Hyrax::AdminSet via the service class; configuration implies this should work but there’s hard-coded logic that’s proving hard to disentangle.

  7. Next week’s Moderator: @Daniel Pierce

  8. Next week’s Notetaker: @Jeremy Friesen