Thanks for everyone's feedback and information so far. It is important to note the differences between the codes and the descriptions found in the permissions table.
the codes such as: "CREATE_ORG_TYPE" are used by the system and not just labels and thus would require developer involvement (for computer and human consumption) and outside the scope of the DIG. For adjusting those, the discussion should be taken to the dev list or dev meeting or by making an enhancement request in launchpad for a permission code reorganization. Or perhaps Joseph may be reviewing or could review that as part of his project? The descriptions are more human informative so we can adjust these to make them useful without effecting the system and thus I think could be in the scope of the DIG to improve these. Some good points were made about having documentation on traditional library roles or staff groups (cataloguer, circulator) and required permissions to carry out those roles. Perhaps the improved admin interface work will include some automatic permission assignments for particular library roles/groups to make that easier? Regards, Robert Robert Soulliere, BA (Hons), MLIS Systems Librarian Mohawk College Library [email protected] Telephone: 905 575 1212 x3936 Fax: 905 575 2011 ________________________________________ From: [email protected] [[email protected]] On Behalf Of Anoop Atre [[email protected]] Sent: May 12, 2011 5:52 PM To: Documentation discussion for Evergreen software Cc: Joseph Lewis Subject: Re: [OPEN-ILS-DOCUMENTATION] Evergreen Permissions descriptions/map/matrix documentation? 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: [email protected] > [mailto:[email protected]] 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<[email protected]> 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 >> [email protected] >> _______________________________________________ >> OPEN-ILS-DOCUMENTATION mailing list >> [email protected] >> 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 _______________________________________________ OPEN-ILS-DOCUMENTATION mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation This E-mail contains privileged and confidential information intended only for the individual or entity named in the message. If the reader of this message is not the intended recipient, or the agent responsible to deliver it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is prohibited. If this communication was received in error, please notify the sender by reply E-mail immediately, and delete and destroy the original message. _______________________________________________ OPEN-ILS-DOCUMENTATION mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
