[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Hi Gayle,

I think the system behavior makes sense. As described on manual page #100729, the two separate 'Access' and 'Create' lists authorizations behave similarly to the way the separate 'View' and 'Edit' for the individual record types, and is consistent with how the system behaves in general. This is definitely a good thing.

On the other hand, it doesn't *all* make sense. If you're editing the records in the list, and not the list itself, then maybe it makes sense to only need permission to edit that record type. There are some exceptions, for example when you delete records from a review file, the file gets zeroed.

Have you looked into utilizing the 'Setting Review File Initials' function (see manual page #100682)? 

It might help you dole out authority over specific lists to specific individuals. To keep people from creating additional lists or accidentally editing the wrong lists, you'd have to put initials on all the other lists as well, but this might be more managable if you assign at least one staff at each member library the 'Review file list administrator' authorization. 

It's definitely not a perfect solution, and I'm sure you have more than enoughauthorizations to keep track of already, but if you're worried about giving Create Lists access to staff, it might be a place to start.

Caleb T-R
Golden Gate University


>>> gsimundza@xxxxxxxxxx 03/17/03 08:08AM >>>
We are a library consortium that is fairly new to Innovative, and we have
been happy with a feature, permission 181, that has allowed staff in our
member libraries to edit records contained in a review file without needing
permission to Create Files themselves. We create them centrally with a
limited number of key people at member libraries also
creating their own review files. We give additional member library staff
permission 181 to access review files to edit item records as needed.
We have found this an easy and convenient way for staff to access item
records for post migration clean up.

We currently are on Release 2002 Phase 1.  However, we are testing Release
2002 Phase 2 on our training server, and
have found that permission 181 no longer acts the same way, and that the
only way users can edit records from a review file is by giving them full
Create List permission as well.  When I reported this to the Help Desk, I
was told that the way we are using it is unintended, and that users must
have Create Lists permissions (Permission 18) in order to have any access to
Review Files.

Does anyone else on the list find this to be a problem?

Gayle Simundza
System Manager
CLAMS (Cape Libraries Automated Materials Sharing)
270 Communication Way, Unit 4E
Hyannis, MA 02601
(508) 790-4399 x19
Email:  gsimundza@xxxxxxxxxx 


--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies:  INNOPAC@xxxxxxxxxx 
Update your subscription options: http://innopacusers.org/list/listinfo/innopac