Samvera Tech Call 2021-03-31

Owned by Jeremy Friesen
Last updated: Mar 31, 2021 by Chris Colvard (Deactivated)
3 min read

Meeting Logistics:

Agenda

(meeting notes below)


Moderator: Lynette Rayle

Notetaker: Heather Greer Klein

Attendees:


Meeting Process

 Moderator and Note Taker - click to see 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 2021-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: 2021
      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

  • Hydra Access Controls behavior change in 11.0.5
    • Had a release about 2 weeks ago, 11.x line was throwing deprecation warnings. Ubiquity and DCU folks found a behavior change where email addresses and usernames with %20 are being treated as spaces. Looking for advice and suggestions on how to unravel this. Concern that data is getting stored differently now than it should and collisions could cause security concerns.
    • Dependency for user email addresses. Hydra access control is the source of the issue.
    • Should yank the release and go back to the drawing board on the deprecation issues.
    • Concerns for those who have deployed and saved info records, how to revert those to behave the same as previous. Yank first and then address this issue to prevent further problems.
    • Any advice? Document expected behavior. Will see the community response. 
    • Will cut a new release to reverse the change, yank the old one, send an email explaining the behavior change and info about the data in case others have bad data. If anyone needs help healing that can be a dev congress topic potentially. If it can't wait others will likely be able to step up. 
  • Hot topic of the Mind Magic issue in dev chat. Should bump the Hyrax README to suggest the correct Rails release. 5.2.5 is the right version, Julie will follow up.
  • https://github.com/samvera/hydra-head/pull/529
  • Hydra Head doesn't need to solve Rails version issue for downstream users.
  • CircleCI builds need to be looked into – will be done in the Hyrax Maintenance standup today
  • Moderator for next time: tamsin
  • Notetaker: Julie