Samvera Tech Call 2017-08-16

Time: 9:00am PDT / Noon EDT

Call-In Info: 1-641-715-3660, access code 651025

Moderator: Adam Wead

Notetaker: Andrew Myers

Attendees:

• LaRita Robinson (Notre Dame)
  
• Michael Joseph Giarlo
• Steve Van Tuyl (oregon state uni)
• Josh Gum (oregon state unicorn)
• Jim Coble (Duke)
• Esmé Cowles (Princeton)
• Andrew Myers (WGBH)
• justin (Stanford)
• cam156 (PSU)
• Lynette Rayle (Cornell)
• tlw72 (Cornell)
• Collin Brittle (Emory)
• Glen Horton (Cincinnati)
• whunter (Virginia Tech)
• Bill Dueber (U. Michigan)
• Jose Blanco (U. Michigan)
• Fritz Freiheit (U. Michigan)
• Michael Klein (Northwestern)

Agenda

1. Roll call by timezone per following order - ensure notetaker is present (moderator)

   1. folks outside North and South America

   2. Eastern timezone

   3. Central timezone

   4. Mountain timezone

   5. Pacific timezone

   6. folks who were missed or who dialed in during roll call

   7. Welcome all newcomers!
2. Agenda (moderator)
   1. Call for other agenda items (moderator)
   2. LaRita Robinson and Jeremy Friesen An initial review of analysis and proposal regarding roles, permissions, and groups in Hyrax (document to review and comment on)

      1. Seeking feedback over the next 2 weeks.

      2. The doc describes a non-trivial refactor with the aims of:

         1. identify a more unified direction for how to handle roles, permissions, and groups.

         2. bring code together, rather than having the logic spread throughout the code base

      3. easily answer:

         1. "What can a given user do on a given entity?”

         2. "Who all can perform a given action on a given entity"

      4. Please add feedback and discussions within the Google Doc itself.

      5. Feedback and next steps will be discussed in 2 weeks.

      6. Lynette Rayle thoughts:

         1. suggests reading the glossary to get a feeling for the terms

         2. concerned about potential proliferation of Workflows

      7. Jeremy Friesen thoughts:

         1. Workflow code will have to be refactored to be less tightly coupled with Admin Sets

         2. CanCan may still be used as a convenient interface, and for backward compatibility, but may end up delegating most authorization logic to whatever new system we come up with.

   3. Need additional guidance on https://github.com/samvera/hyrax/issues/1376, in particular where should we be storing the banner image for a collection? If there is not agreement, then we'll need to propose some semblance of an adaptive solution.

      1. Follow-up discussion from last week's call, and on the Samvera-tech list regarding how to attach files to Collections, specifically banner images and logos.

      2. Previous idea thought we may use FileSet objects, but currently that's not allowed in PCDM.

      3. justin thoughts:

         1. Web assets like banner images typcially undergo changes due to design concerns (scaling, cropping, etc).

         2. The optional preservation of a banner image could, and probably should, occur as a separate process.

      4. Lynette Rayle thoughts:

         1. a likely first iteration is to store relationships between the collection_uri and the path_to_image in the application database

         2. further summary of today's discussion can be seen on this Samvera-tech list thread:

            1. https://groups.google.com/forum/#!searchin/samvera-tech/banner$20image%7Csort:relevance/samvera-tech/DU_jlwZ8CyY/kU8dRgG-BQAJ

3. Moderator/notetaker for next time (moderator)
   1. Moderator: Steve Van Tuyl
   2. Notetaker: cam156
4. After call, this week's notetaker should create the agenda for the next call.