Skip to end of metadata
Go to start of metadata

This wireframe is...



Fix for


Still to do: pagination



On this page

Buttons to include in each roles page


Buttons to include

Create new role page

Cancel and Save

View only page

Delete, Duplicate, and Edit

Edit page

Delete, Duplicate, Cancel, and Save

Editing a role

Creating a new role


  1. Hi Erin, Joe King and I just reviewed these wireframes together and we have a few comments for you.  First off, they look great and were pretty simple to understand.  All of our comments are about the Roles/Permissions wireframes. 

    1. Delete?  We need a delete permission for those cases where a mistake is made such as a duplicate record is entered.  This brings up the larger issue of where things go when they are deleted.  Joe and I agree that we want there to be some type of holding tank for deleted records so that they can part of the audit trail (i.e., part of the history of the record).  This also brings up the idea of Hidden, Active, Inactive records.  Examples of these include records for objects that have been deaccessioned.  We won't delete the record because we need to know that the object was deaccessioned, however, we don't want to see it on a daily basis and may want to restrict who sees it. 

    2. Screen 5.  We found it difficult to distinguish the permission 'layers' as they opened up (Example: Object Entry: Cataloguing: Object Identification: Titles).  Is there a way to make them more visually distinct from one another?  

    3. Screen 5.  Can you clarify the purpose of the radio buttons at the highest level (procedure).  If our understanding is correct and that button assigns the same permission to all children items, what is the purpose of it when all three types of permissions exist at the child levels?  To show that all 3 permission types are in use for that procedure?  Again, just checking to make sure that we understand how this works. 

  2. I forgot to mention that we agree with whomever made the comment about the need for multiple profiles per user.

  3. Walkthrough with Joe King, the Walker


    • Question about the categories: for example, summer intern. What does that mean? (A: the categories shown are just examplary. You can set it however you want.) There's no meaning to the heading.
    • By selecting write, you can read and write, right? (A: Yes) I get it.
    • Can you delete one role? (A: Yes)

    General Comments

    • Really easy to use.
    • (When shown that you can click on an item on the list and see the schema at the bottom) wow, that's fantastic.
    • If you delete a group, "would expect to delete all the roles inside."
    • Duplicating a role is useful. For example, if Media and Cataloging intern have one thing that's different, I would just dulpicate and change that one thing.
  4. Walkthrough with SMK

    It is clear to the users (both the Walker and SMK) what each of the four permission levels mean.

    "We can really follow you. This is much better than what we have today."
    At SMK, there are 6 different groups of different permissions, and this will come in handy. Very good.