[OPEN-ILS-DOCUMENTATION] Evergreen Permissions descriptions/map/matrix documentation?

[Anoop Atre]

I'd like to mention that life might indeed be getting easier for 
configuration, we just got ourselves a smart student developer (Joseph 
Lewis) as part of our Google Summer of Code involvement.

http://evergreen-ils.org/blog/?p=513

His project for the summer will be to: "Bring sanity to the Evergreen 
configuration interface"

He has some great ideas and should probably sign up to the DIG list if 
he hasn't yet so he can follow your discussions.

Cheers

On 05/12/2011 04:26 PM, Turner, Jennifer M wrote:
> YES!  It would be much easier to set permissions if related items were grouped in such a fashion.
>
> -----Original Message-----
> From: open-ils-documentation-bounces at list.georgialibraries.org [mailto:open-ils-documentation-bounces at list.georgialibraries.org] On Behalf Of Lori Bowen Ayre
> Sent: Thursday, May 12, 2011 4:15 PM
> To: Documentation discussion for Evergreen software
> Subject: Re: [OPEN-ILS-DOCUMENTATION] Evergreen Permissions descriptions/map/matrix documentation?
>
> Deborah,
>
> Absolutely agree with you too!
>
> ORG_TYPE_CREATE
> ORG_TYPE_DELETE
> ORG_TYPE_UPDATE
>
> Much better!  Sounds like you should be the DIG Style Coordinator!
>
>
> On Thu, May 12, 2011 at 2:03 PM, Deborah Hensler<hensler at hslc.org>  wrote:
>> Hi, Robert,
>>
>> 1) I would love to see the copied permissions become actual
>> descriptions! I also don't like the varied terms used. Terminology
>> (allow or enable) should be consistent as well as plural or singular.
>>
>> 2) I was the person at the conference DIG meeting who brought up
>> listing the applicable permission(s) in the official documentation.
>> It's a project I'm in the very early stages of as we move toward
>> working with our first library. I volunteered at the meeting to take
>> that on and will share as soon as I'm further along.
>>
>> Also, I have created a permission matrix, still to be tested, but I'm
>> not sure it's what you're looking for here. We have developed specific
>> permission groups and the matrix lists those groups (Circ Clerk, Circ
>> Staff, Circ Supervisor, etc.) and their permissions. If that is what
>> you're thinking of and would like to see it I'd be happy to share.
>> Right now it's untested and I'm guessing on some, like those with no
>> description.
>>
>> On a different topic, I wonder if anyone else wonders about usability
>> of the current format of permissions, e.g,:
>> CREATE_ORG_TYPE
>> DELETE_ORG_TYPE
>> UPDATE_ORG_TYPE
>>
>> Speaking as an old indexer, I would find it more helpful if they were
>> listed as:
>> ORG_TYPE_CREATE
>> ORG_TYPE_DELETE
>> ORG_TYPE_UPDATE
>>
>> That would keep all of the permissions relating to one function
>> together instead of having to go through the list to find them. I
>> realize that's a bit beyond the scope of this discussion, but wanted
>> to put it out there to see if I'm the only one thinking this way.
>>
>> Debbie
>>
>> --
>> Deborah Hensler
>> HSLC ILS Trainer
>> Office: 412-517-8388
>> Mobile: 412-258-0372
>> HSLC office: 215-222-1532
>> hensler at hslc.org
>> _______________________________________________
>> OPEN-ILS-DOCUMENTATION mailing list
>> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
>> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentati
>> on
>>
>
>
>


-- 

Anoop Atre
IS Developer & Integrator, MnPALS
PH: 507.389.5060
OF: 3022 Memorial Library (Office-ML 3022)
-- 
"Mit der Dummheit kämpfen Götter selbst vergebens"
  ~ Johann Christoph Friedrich von Schiller