Samvera Tech Call 2022-03-02


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: @Anna Headley

Notetaker: @James Griffin

Attendees:

  • @Heather Greer Klein (Samvera Community)

  • @Chris Colvard (Indiana University)

  • Eddie Rubeiz (Science Heritage Institute)

  • @jrochkind (Science Heritage Institute)

  • @Thomas Scherz (Cincinnati)

  • @Lynette Rayle (Cornell)

  • @Daniel Pierce (Indiana University)

  • @Juliet Hardesty (Indiana University)

  • @Max Kadel (UNC Chapel Hill)

  • @Michael Johnson (Indiana University)




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

  • Bixby Upgrade for Rubocop

    • Chris is continuing from the last release, rubocop 1.x upgrade

    • This will maintain bixby as much as possible, and this will be the easiest path forward for the Gem

    • Hyrax was run against this, and there were 86 offenses

      • There was a second PR for corrections which weren’t autocorrectable

    • Request for feedback

      • There are modifications for the bixby configuration

      • These can be ported into a bixby PR

      • Most of the changes are autocorrectable

    • Feedback on the Call:

      • Some did not mind continuing to use bixby for now

      • Do we want a Working Group for further decisions regarding style guidelines and standards?

        • This is definitely desirable once rubocop 1.x is supported

    • Best Practices

    • Chris will push the changes from Hyrax into the bixby PR

  • BE gem work

    • questions about how BE is being used in community - cloud vs file system

    • survey shows that there is use of forked adaptors, Amazon S3, and IU has Google Drive interest (Julie: this is moving to OneDrive, or at least away from Google)

    • Thomas would like to join group, use BE 1.0 with Box, Dropbox, Google, and localhost - aspiring to OneDrive

      • BE great for large file ingest (towards TB sized)

    • came up from pledged hours (1 week’s worth) for BE work

    • There are many issues with reconciliation for the browse-everything

      • Organizations are going to need to continue using various branches, and forks of various branches

    • Science History Institute aims to address Rails 7.0 support

      • JavaScript support for sprockets, and, ideally, support for Webpack, Import Maps, and other Rails 7 solutions

      • There is not enough time for contributing a refactoring of the JavaScript, but this is desirable (preferably dropping jQuery)

    • Science History Institute needs review for PRs

      • James can commit to this

  • ActiveFedora and RDF

    • Release of RDF which broke some internals

      • This is due to a monkey-patch to support Fedora 4, which needed to be addressed

      • This led to a new release for the active_fedora Gem

    • This may have triggered test failures for Hyrax (there are three failures)

    • Chris please requests some assistance for inspecting the failing tests

    • Lynette confirmed that the failing tests are related to the failing tests

      • RDF Gem needed a PR, Lynette did offer a PR and corresponded with Greg Kellogg (maintainer)

    • Chris and Lynette can collaborate on this

    • Should this release be yanked from RubyGems?

      • Another patch release can be issued as an alternative

      • Some do lean towards to pinning rdf, as the level of precision for specifying DateTime values might impact the code base

        • This would require the yanking the release from RubyGems

        • Yanking the release was determined to be the best path forward

        • Contributors can also provide guidance for pinning releases within the documentation perhaps?

  • Infrastructure for Seeding Release Dates

  • QA

    • call for outstanding work on QA gem - are there issues to prioritize for pledged hours from Science Institute folks?

    • Contact James with these issues

  • Next Samvera Tech. Call

    • Moderator

      • Heather

    • Notetaker

      • James

  • Requests for Support

    • Hyku support request from Eric Phetteplace

    • @Kevin Kochanski will be contacted for a requested for assistance