Samvera Tech Call 2024-11-06

Owned by Daniel Pierce
Last updated: Nov 06, 2024 by Chris Colvard
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: Video Conferencing, Web Conferencing, Webinars, Screen Sharing

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)

  • Hyrax Fedora 6 support progress and issues @Daniel Pierce

  •  



Moderator: @Daniel Pierce

Notetaker: @Chris Colvard

Attendees:

  • @Randall Floyd

  • @Daniel Pierce

  • @Rebekah Kati

  • @dmoles

  • @Heather Greer Klein



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

      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 Fedora 6 support update

    1. ~24 failing tests

      1. inserting into frozen array (not happening in postgres adapter?)

      2. Spec change: Date objects not handled correctly (lease or embargo) (also not causing error in postgres adapter)

      3. hydra-works state attribute not being stored in fedora (working in postgres)

        1. Conflict with server managed triples? (https://wiki.lyrasis.org/display/FEDORA6x/Server+Managed+Triples )

    2. Hoping to get this out by end of year

      1. Will Rails 7.2 support be included in this release?

        1. Not too many failing tests but some may take longer

        2. Still would need to do manual QA testing

  2. Hyrax accessibility sprint going on right now

  3. Fedora 6 autoversioning

    1. On by default

    2. Fedora documentation notes that many versions in OCFL can have performance issues

      1. Is this inherent in the spec or an implementation issue?

    3. Avalon is turning it off because Avalon isn’t a preservation system and may have more edits than other repositories

      1. Could use version audit trail for visibility / permission granting but these are separate resources (at least in hydra-access-controls) so versioning wouldn’t help

    4. Will Hyrax have any guidance on this?

  4. Slack

    1. Hyrax 3 → 4 → 5 upgrade dependency issues; Has anyone blazed this path?

      1. Hyku?

      2. IU and other may be taking the path of rewriting on Hyrax 5 instead of upgrading

  5. Next Meeting: 11/13/2024

    1. Moderator: @Daniel Pierce

    2. Notetaker: @Heather Greer Klein