Samvera Tech Call 2024-12-04

Owned by Bradley Watson
Last updated: Dec 04, 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)



Moderator: @Daniel Pierce

Notetaker: @Chris Colvard

Attendees:

  • @dmoles

  • @Bradley Watson

  • you!



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. Updates

    1. David is digging into Workflows as part of working towards production with Comet

      1. Implicit behavior in WorkflowImporter leads to confusing errors in testing · Issue #6977 · samvera/hyrax

        1. Could just be test setup issues

        2. Daniel is open to any suggestions of refactoring

    2. Daniel is working on fixing sirenia failing tests

    3. Randall Floyd is working on Rails/Ruby upgrade PR

    4. Pushing to Hyrax 5.1

    5. Fedora 6.5.1 RC with fixes for encoded slashes

      1. valkyrie still has one failing test with that fedora image

      2. part of Hyrax 5.1 work

    6. Avalon

      1. working on getting 8.0 release by end of year

      2. working through test migration to fedora 6 with snapshot of IU production data

        1. Able to use latest version of fedora import-export tool because Avalon doesn’t use versions or fedora ACLs

        2. Had flakiness which killed the export

        3. Latest version of import-export allows for resuming export

        4. Migrating exported data to Fedora 5 then 6 using fcrepo-upgrade-utils worked fine

        5. Starting up fresh Fedora 6 on migrated data had issues

          1. On startup Fedora 6 indexed into DB for cache which took hours

          2. While reindexing Fedora unavailable (responds with 503)

          3. Membership indexing failed (worked on second startup?)

            1. Discussing in fedora slack with others who had same issue

  2. Browse-everything

    1. Needs a lot of love - particularly JS

    2. What to do about all of the forks

    3. Chris will make a call in early 2025 to figure out plan

    4. Daniel had looked at it during attempt to upgrade Hyrax to Bootstrap 5

      1. Ran into issues

      2. Could it be dropped from Hyrax?

    5. Could B-E be deprecated in favor of a 3rd party tool like Uppy?

  3. Next meeting: 12/11/2024

    1. Moderator: @Daniel Pierce

    2. Notetaker: @Bradley Watson