Samvera Tech Call 2022-04-27

Owned by James Griffin
Last updated: Apr 27, 2022
2 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)

  • Component Maintenance Interest Group meetings (@James Griffin)

  • (To be added)

 

Moderator: @Chris Colvard (Indiana University)

Notetaker: @James Griffin (Princeton University Library)

Attendees:

  • @Heather Greer Klein (Samvera Community)

  • @Thomas Scherz (University of Cincinnati)

  • Brad Watson (Emory University)

  • Julie Hardesty (Indiana University)

  • (To be added)

 

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

  • Component Maintenance Interest Group meetings (@James Griffin)

    • Scheduled time for Component Maintenance group

    • anyone interested in components (what is happening, PR reviews, issues or questions)

    • might be different than how component maintenance has been handled previously

    • providing updated at SVC and will talk about more specific goals with onboarding and establishing procedures

  • Nurax Dev Deployment (Julie)

    • There was reports of there being data being cleaned out due to issues affecting the Fedora deployment

    • This seems to have broken derivative generation and IIIF image viewer, as well as some unexpected data loss

    • Chris: Perhaps there are permissions issues affecting derivative file storage within the server environment?

    • Who is the primary person of contact for the Nurax project? (Data Curation Experts? Mark Bussey?)

      • Due to these breaking features, this is problematic for users to test newer Hyrax features

 

  • Support Requests

    • bl7bootstrap4 branch Rails Routing Error was reported in #hyrax

      • Daniel Pierce did find a solution for this, and this shall be tested

    • fedora4 binary storage reported in #dev

      • Deleted files are not going to be moved into the fcrepo4 trash

      • Perhaps seeking out support from #fcrepo?

      • Is this somehow related to the creation of tombstone resources within fcrepo4?

        • This moves the location of a resource, but does not consider it fully removed from the system

https://samvera.slack.com/archives/CA8ANGLEL/p1650549422053629
https://samvera.slack.com/archives/C0F9JQJDQ/p1651073671141179

 

  • Next Scheduled Samvera Tech Call (this shall be 05/11/22 due to the conflict with Virtual Connect)

    • Moderator: @Thomas Scherz

    • Notetaker: @James Griffin

 

Call adjourned at 09:19 PDT/12:19 EDT