Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We are working through PAWG - Use Cases to Permissions Matrix Followups to ensure we've fully captured and understand our initial round of use cases.

Introduction to the Permission Matrix

The PAWG has gathered the permissioning needs of various Samvera-based implementations. We are presenting the Permission Matrix as our attempt at synthesizing and normalizing these actions, action levels, and possible user types.

The Permission Matrix introduces some new concepts, which are also explained in notes attached to the spreadsheet cells:

  • action levels (column B) - "Levels" are based on two concepts:
    • There is a hierarchy of objects with site being the top level: A collection type is added within a site. A collection is added within a collection type.
    • Abilities are object-based: Users may have the ability to create a work, but not create a collection.

  • actions (column D) - 
    • a list of ALL available (or desired) site actions at each of the levels
    • broken down to the point where the ability to access the action needs to be conferred to the users independently of other actions
  • user types (row 8, columns G-AA) - users grouped into three categories
    • authority users - documenting the permissions are conferred solely by signing into site
    • repository users - documenting the permissions which are currently predefined in the Hyrax system
    • institutional users - documenting the use cases identified by various institutions

Questions

  • What can we clarify to help you better understand the Permission Matrix?
  • What actions (column D), action levels (column B), or user types (row 8, columns G-AA) are we missing?
  • Are the actions and their target objects granular enough?
  • Are we missing conceptual item levels?
  • What other things can we clarify regarding our Permission Analysis work?

...