Join meeting: https://notredame.zoom.us/j/789935621

Attendees:

Jeremy Friesen, LaRita Robinson, jrudder, Emily Porter, Maria Whitaker, Jon Cameron, Noah Botimer

Agenda:

Roll call
Call for additional agenda items
Review previous action items

2018-06-01 Meeting
Huzzah we completed all of them!

Groups requirement
1. Discussed that group is a bunch of users, and a group is analogue to a user
Clarify IP Authenticated User Use case
1. We need to revisit and clarify this use case
2. These are assigning IP ranges to groups (e.g. because you are in the On Campus group you can see this)
3. IP Ranges have similarities to users, or may be an overlay of an authenticated user
Adding an Owner user as a use case?
1. How does this differ from acting on your own item?
2. Is there a conflation of Depositor and Proxy?
3. You are a collection owner and delegated deposit to a student, the student leaves and were the owners of the object. Does that make sense?
4. What does "owner" of an object mean in relation to our emerging use cases?
5. Do we need an "owner" concept and use case? Are these subsumed in the varying permission methods?
Bulk actions - how do these fit?
1. Maria Whitaker - Under the works section in the Permission Matrix, there is Batch Edit. Is this Bulk edit? Yes (LaRita Robinson)
2. Discussion about limiting bulk actions
  1. Not everyone may have a bulk edit action, even though they might have permission to update more than one item
  2. Bulk actions we see are Update Permissions, Update Metadata, Export Metadata
Design questions from Slack channel (attn Anna Headley)
1. Discussed preliminary design objectives
  1. This is not just for Hyrax
  2. Desire to define a well-formed plugin interface
  3. How is this different from CanCan?
  4. Expunge the concept of using is_admin? or is_superadmin?
Discussion concerning permission to view different formats (attn Anna Headley)
1. Just because I can see the HTML representation does not mean I can see the RDF Turtle representation, nor the IIIF
2. There is an implication in this requirement that we are really looking at attribute level permissions and not necessarily format permissioning
Establish next steps and action items

Action Items:

LaRita Robinson will add lines to the Permission Matrix reflecting actions on groups; Verify that those lines are reflected in the Coordinated Permissioning Use Cases document.
LaRita Robinson will update notes to further clarify the IP Authenticated User column and notify Emily Porter and Maria Whitaker of updates.
jrudder will work through the Owner Use case, reaching out to the community to better understand its usage and limitations and tag LaRita Robinson in those conversations.
Maria Whitaker will coordinate with Emily Porter to write use cases (in Coordinated Permissioning Use Cases document.) related to bulk actions and notify LaRita Robinson when those use cases can be mapped into the Permission Matrix
Jeremy Friesen will create a Design Objective document to share (team editable, world commentable), adding a link to the document in the Wiki. Then LaRita Robinson will sift through Slack and add other considerations for discussion - https://docs.google.com/document/d/1OdacxmL2FfAKgbY6Z5eM4fCaXXB2AqhSJMqJaJynkD4/edit#heading=h.4mklo57wve4b
Emily Porter and Maria Whitaker will send the use case of non-HTML formats through the Coordinated Permissioning Use Cases document and notify LaRita Robinson to update the Permission Matrix.
Jeremy Friesen will schedule a different timed conference call - Monday July 9th at 3pm EDT
LaRita Robinson add team member editing rights to Permission Matrix

Browser not supported