[ 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]
I also agree with Gayle that these should be different authorization 
checkpoints.  This doesn't happen to be an issue for us because tend to 
give the authorization to create lists to practically everyone, but I 
can certainly see that creating a list, and editing records within a 
list, are really different things that need separate authorizations.

Unfortunately, these individual enhancement requests for authorization 
changes tend not to do well in the enhancements process.  I'm the FE for 
Database/Cataloging Enhancements, and to be honest, Nancy's enhancement 
request about the authorization to preserve the sort order might not 
even make the ballot-- not because I don't totally agree with her that 
this should be a separate authorization, but because it might affect 
fewer sites than some of the dozens of enhancement requests that I've 
received.  And if I saw either of these enhancement requests on the 
ballot, I would be disinclined to vote for them because they don't 
happen to affect our system at the moment, and there are other things 
that we'd be likely to want more.  But this doesn't mean that I don't 
totally agree that these authorizations should be separate.

What I would really like to see Innovative do is go through all the 
authorizations and make all the enhancements that have been suggested 
over the years, and more.  We want the authorizations to be a 
fine-grained as possible.  Even though that means more administrative 
overhead in understanding and maintaining them, it would give us-- every 
system-- much more control over how we implement them locally, and much 
more flexibility to change things over time.

Nancy Helmick wrote:
> Dear Gayle,
> 
> I absolutely agree with you.  It is not uncommon for us to want to have 
> a student assistant do some updating in a review file; being able to 
> give them access to review files without giving them create lists 
> permission is the perfect solution. 
> 
> We have a similar problem with giving out "edit an item record" -- it 
> also allows anyone who has that to preserve a sort in Millennium.  
> That's a problem because our serials are sorted first in copy order and 
> then in reverse chronological order.  Lots of people need to have edit 
> an item record, but if they preserve the changed sort, we can't get our 
> serials back into the correct order except by moving each individual 
> volume one-by-one.  The problem is compounded by the fact that 
> Millennium uses a computer sort, not a smart sort, so even trying to 
> resort in reverse order results in vol.200, 20, 2, 100, 10, 1.  So far 
> we've had to fix 6 serials, some of which had 3,000 attached items.  
> Drives us nuts.
> 
> We submitted an enhancement to require separate authorization for 
> "preserve the sort" and hope it makes it through.
> 
> Nancy Helmick
> Ohio State University Libraries
> 
>  >>> gsimundza@xxxxxxxxxx 03/17/03 08:08AM >>>
> 
> 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
> 


-- 

Elizabeth Thomsen, Member Services Manager
NOBLE: North of Boston Library Exchange
Danvers MA 01923
et@xxxxxxxxxx