Samvera Tech Call 2022-08-03

Owned by Bradley Watson
Last updated: Aug 03, 2022 by Juliet Hardesty
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: @Chris Colvard

Notetaker: @Juliet Hardesty

Attendees:

  • @Heather Greer Klein (Samvera)

  • Collin Brittle (Emory)

  • @James Griffin (Princeton)



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

      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

  • In-person developer’s congress (Chris)

    • with Samvera Connect going virtual there’s no opportunity there for in-person dev congress

    • is there some way to have in-person dev congress this fall or winter?

    • talking to Heather, thought it could work

    • Heather polling Partners about fall Partner meeting now, seems like it is possible it might not happen in-person until spring because it is too late to plan for fall but not sure yet

    • might also want to plan on dev congress in-person in spring to go along with that

    • would dev congress be in addition to partner meeting or concurrent? Heather: thinking in addition (after) partner meeting; Esme coming on as Board Chair in January and might want to be able to participate in both and others might also be interested in doing both

    • would need “enough interest” (not sure what that means - 10 people??) and would still need host for fall dev congress

      • Emory suggested and possibly in November right after Samvera Connect (which is happening virtually)

    • 10-20 is critical mass to have dev congress; 2-3 days is good amount for dev congress, 1 day is not enough time to gather people together in-person

    • Julie and James both think spring would be better for planning in-person dev congress

    • What needs to happen to plan for spring?

      • Nabeela proposed Events WG be chartered to help plan things like this - call will go out for this soon

      • by end of this month, frame up in-person spring events (partner meeting, dev congress, maybe even Connect)

      • WG would also be charged with finding host locations, consider if in-person Connects should happen in same place every year?

  • Rails 6.1 support update

    • timeframe that is achievable for this with Hyrax - does it fit into 4.0 or would it need to be 4.1?

    • Chris tried this and everything but hydra-editor seems work with Rails 6.1, so not that much to update

    • Rails 6.0 EOL is probably June 2023

    • might have to figure out how Hyrax-Valkyrie work lines up and is prioritized with Rails 6.1 upgrade

  • Hyrax-Valkyrization Community Effort – September 6th - 16th (Heather)

    • just scheduled and notice going out today

    • using HMWG sprint time for this work

    • calling for participation to get to MVP release

    • preparing by updating nurax-pg with Hyrax 4.0 and reviewing open issues from feature spreadsheet testing

    • mark your calendars!

  • Next Scheduled Samvera Tech Call (08/10/22)

    • Moderator: Chris Colvard

    • Notetaker:

  • Support Requests (Slack)

    • #hyrax from end of last week (LaRita and Brad)

    • LaRita - Docker build for Hyrax 3.4.1 not working; need to post comment in #hyrax channel that 3.4.2 release in the works to update tiny-mce gem version (Julie will ask Daniel to do that)

    • Brad - Bulkrax issue - errors with locks, Chris will respond and tag someone from Bulkrax team if help needed

      • should there be a bulkrax channel? maybe continue in #dev and #hyrax for now

      • Collin: Brad found info on how to increase the timeout on the locks and seeing if that will work; working with CSV bulkrax parser for multiple files, Brad has PR that might be ready to go?

  • Pull Request Review

    •