Samvera Community Wiki
Samvera Tech Call 2018-10-03
How to connect: https://psu.zoom.us/j/613720745 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)
Time: 9:00am PDT / Noon EDT
Moderator: @tamsin woo
Notetaker: @James Griffin
Attendees:
@Collin Brittle (Emory)
@Gordon Leacock (University of Michigan)
@Jose Blanco (University of Michigan)
@Chris Colvard (Deactivated) (Indiana University)
@LaRita Robinson (Notre Dame)
@Julie Allinson(CoSector - University of London)
@Jim Coble (Duke)
@tamsin woo (DCE)
@James Griffin (Princeton University Library)
Agenda
Roll call by timezone per following order - ensure notetaker is present (moderator)
folks outside North and South America
Eastern timezone
Central timezone
Mountain timezone
Pacific timezone
folks who were missed or who dialed in during roll call
Remind everyone to sign in on agenda.
Welcome all newcomers!
Agenda (moderator)
Call for new agenda items (moderator)
What to do about Blacklight::Access::Controls (@Chris Colvard (Deactivated) )
Moderator & notetaker for next time
Moderator: @LaRita Robinson
Notetaker: @Julie Allinson
After call, this week's notetaker should create the agenda for the next call:
Open template agenda titled "Samvera Tech Call 2018-xx-xx"
Click on ... in the top right corner, and select copy.
Popup will open for location. It should contain:
Space: Samvera
Parent page: 2018
Select copy. New page should be created.
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
Blacklight Access Controls (Colvard)
Johnson raised this issue within hydra-head (https://github.com/samvera/hydra-head)
Depends on blacklight-access-controls (https://github.com/projectblacklight/blacklight-access_controls)
Split out from hydra-access-controls (https://github.com/samvera/hydra-head/tree/master/hydra-access-controls)
Used to have similar read/discovery access controls
Within the Blacklight context, this Gem hasn’t had activity since January
Not under Samvera, hence it cannot be considered a Core Component
It is sitting with some breaking changes in the master branch
How to we insulate ourselves from potential changes in that Gem?
How do we ensure stability in hydra-head?
Perhaps we can fold it into samvera-labs?
Questions?
Does this fit into the scope of the permissioning WG? (Samvera Permissioning Analysis and Design Working Group)
LaRita Robinson
It should be, but Blacklight hasn't been explored too thoroughly
The WG just undertook requirements gathering
The intent would be to have the permissioning work would feed through a single interface
There should be one source to manage the permissions within the Samvera application stack
Colvard
hydra-access-controls
Does not depend upon the release candidate for blacklight-access-controls
Perhaps we should wait to take action until the Permissioning WG proceeds with their work
Leacock
Is Blacklight a core component?
Johnson
No, Blacklight itself has maintainers outside of the community and its own governance structure
Arguably, this should also be the case for blacklight-access-controls, but it is not receiving any maintenance
Colvard
Does the Samvera community need to own it under the Blacklight GitHub organization?
Can we try and ensure that hydra-head is maintained without duplicating work between communities?
Robinson
Try and keep track of information, but permissions management is likely going to require some significant changes
Maintenance should still be addressed, but the simplest changes should be the goal
Ultimately the access controls for hydra should ultimately be deprecated
Colvard
If actions are taken, updates will be discussed on the samvera-tech mailing list
Moderator and Notetaker
Moderator for Next Meeting
(Not going to be held next week due to Samvera Connect, but for 10/17/18)
LaRita Robinson shall serve as the moderator
Notetaker
Julie Allinson will serve as the notetaker
Call concluded at 12:22EDT