As I've been going through the process of creating roles and assigning permissions in preparation for the PAHMA launch, I've noticed a problematic aspect of the current permissions with respect to authority terms.

With dynamic term lists, people who can select terms from term lists do not necessarily need to be able to edit those term lists.  That's the kind of behavior PAHMA wants to have—to be able to allow general use of a vocabulary, but restrict the editing of the list to only a few qualified individuals.

With authorities, however, it appears that if I give someone the ability to choose a term from an authority, they are also given the power to edit that authority.  I had hoped that by setting the permissions for an authority to "read," I'd be able to grant access to select items from an authority but not modify that authority.  Instead, "read" not only prevents a user from modifying the authority, it also prevents the user from selecting terms from that authority (although they can view terms selected by others with "write" privileges).

Am I doing something wrong, or is this the expected behavior?

Are there plans to allow term-list-like permissions on authorities?  If so, what is the approximate time table for their implementation?

Hi Patrick, Megan, As I've been going through the process of creating roles and assigning permissions in preparation for the PAHMA launch, I've noticed a problematic aspect of the current permissions with respect to authority terms. With dynamic term lists, people who can select terms from term lists do not necessarily need to be able to edit those term lists. That's the kind of behavior PAHMA wants to have—to be able to allow general use of a vocabulary, but restrict the editing of the list to only a few qualified individuals. With authorities, however, it appears that if I give someone the ability to choose a term from an authority, they are also given the power to edit that authority. I had hoped that by setting the permissions for an authority to "read," I'd be able to grant access to select items from an authority but not modify that authority. Instead, "read" not only prevents a user from modifying the authority, it also prevents the user from selecting terms from that authority (although they can view terms selected by others with "write" privileges). Am I doing something wrong, or is this the expected behavior? Are there plans to allow term-list-like permissions on authorities? If so, what is the approximate time table for their implementation? Thanks, Michael

    As I've been going through the process of creating roles and

    With dynamic term lists, people who can select terms from term

    With authorities, however, it appears that if I give someone the

    Am I doing something wrong, or is this the expected behavior?

    Are there plans to allow term-list-like permissions on authorities?

Michael, First, stop reading this email because you are on vacation. Second, I did an analysis of the current behavior of roles/permissions/vocabs, and you are correct that it's not working properly. I have filed a Jira ( http://issues.collectionspace.org/browse/CSPACE-5323 ) with a description of the issues as I understand them, and a workflow document that shows how the system should behave. I'll ask the engineers to take a look at the Jira and comment on the scope of the fix, and then we will see what future release this work can fit into. Thanks for bringing this up. I might also take a look at the r+p test plans to see if there's a better way to break them up so that it doesn't take 2 hours to complete one test! Thanks, Megan On Sun, Jun 10, 2012 at 12:21 PM, Michael T. Black <mtblack@berkeley.edu>wrote: > Hi Patrick, Megan, > > As I've been going through the process of creating roles and > assigning permissions in preparation for the PAHMA launch, I've noticed a > problematic aspect of the current permissions with respect to authority > terms. > > With dynamic term lists, people who can select terms from term > lists do not necessarily need to be able to edit those term lists. That's > the kind of behavior PAHMA wants to have—to be able to allow general use of > a vocabulary, but restrict the editing of the list to only a few qualified > individuals. > > With authorities, however, it appears that if I give someone the > ability to choose a term from an authority, they are also given the power > to edit that authority. I had hoped that by setting the permissions for an > authority to "read," I'd be able to grant access to select items from an > authority but not modify that authority. Instead, "read" not only prevents > a user from modifying the authority, it also prevents the user from > selecting terms from that authority (although they can view terms selected > by others with "write" privileges). > > Am I doing something wrong, or is this the expected behavior? > > Are there plans to allow term-list-like permissions on authorities? > If so, what is the approximate time table for their implementation? > > Thanks, > > Michael -- Megan Forbes Collection Manager Museum of the Moving Image 36-01 35 Avenue Astoria, NY 11106 movingimage.us 718 777 6800 Direct 718 777 6834