[OPEN-ILS-DOCUMENTATION] OPEN-ILS-DOCUMENTATION Digest, Vol 37, Issue 9
Shae Tetterton
shae at esilibrary.com
Thu May 12 15:50:31 EDT 2011
In response to a couple help spot tickets and some recent implementations, I
started working on a set of permissions to be delivered during new installs.
We are still testing these groups out but I'm attaching the proposed list in
case you would find it useful in this discussion. I'd also welcome any
advice some of you have given your experience with permissions.
Shae Tetterton
On Thu, May 12, 2011 at 3:40 PM, <
open-ils-documentation-request at list.georgialibraries.org> wrote:
> Send OPEN-ILS-DOCUMENTATION mailing list submissions to
> open-ils-documentation at list.georgialibraries.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
>
> or, via email, send a message with subject or body 'help' to
> open-ils-documentation-request at list.georgialibraries.org
>
> You can reach the person managing the list at
> open-ils-documentation-owner at list.georgialibraries.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OPEN-ILS-DOCUMENTATION digest..."
>
>
> Today's Topics:
>
> 1. Re: Evergreen Permissions descriptions/map/matrix
> documentation? (Tim Spindler)
> 2. Re: Evergreen Permissions descriptions/map/matrix
> documentation? (Lori Bowen Ayre)
> 3. Re: Evergreen Permissions descriptions/map/matrix
> documentation? (Turner, Jennifer M)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 12 May 2011 12:34:00 -0400
> From: Tim Spindler <tjspindler at gmail.com>
> Subject: Re: [OPEN-ILS-DOCUMENTATION] Evergreen Permissions
> descriptions/map/matrix documentation?
> To: Documentation discussion for Evergreen software
> <open-ils-documentation at list.georgialibraries.org>
> Message-ID: <BANLkTimL=ChLcy6Y5xVhtn7iBgoy=M5pTQ at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I think I would generally agree with what you are suggesting. For one, I
> don't think repeating the code description does anything and I personally
> would find it an enormous help to have more meaningful descriptions. I
> also
> think it would be very helpful to have the required for language in there
> and in the appropriate sections of the documentation. In working on our
> system, I have had to do a bit of sleuth work to identify what permissions
> are need for a given function and I'm still very uncertain if I'm
> understanding some of these correctly. Therefore, proceeding as you
> suggest
> would be a big help.
>
> Tim Spindler
> Manager of Library Applications
> C/W MARS
>
> On Thu, May 12, 2011 at 10:57 AM, Soulliere, Robert <
> robert.soulliere at mohawkcollege.ca> wrote:
>
> > Hi All,
> >
> > One of the most challenging aspects of Evergreen is working with the
> > complex permissions matrix. In order to alleviate some of the challenges
> > associated with giving the appropriate permissions for groups/users to
> carry
> > out various tasks. I was thinking about 2 strategies for improving
> > documentation in this area:
> >
> > 1) Update the descriptions located in the permission.prm_list table in
> the
> > Evergreen database . Then, create a script to generate a docbook table
> with
> > the updated descriptions. I would really like some feedback for the best
> > approach for this in regards to the wording of the descriptions.
> Currently,
> > some of the descriptions repeat the code field (e.g."DELETE_BIB_LEVEL")
> and
> > in other cases they have descriptions with. "Allow a user to..." or
> "Enables
> > the user to..." etc... I wonder if it would be useful for these
> permission
> > descriptions to include "required for ..." with a list of functions
> actions
> > where the permission is required. Does that sound like a plausible or
> useful
> > bit on info in the descriptions themselves or would it create a complex
> > situation as permissions are added and the permission structure is
> adjusted
> > in the future?
> >
> > 2) At the DIG meeting in Decatur someone mentioned creating a list of
> > required permissions fat the beginning of various procedures/sections in
> the
> > documentation. I thought this was an excellent idea and I think someone
> > might have suggested that they have begun work on a permission matrix.
> Would
> > anyone be able to share with this DIG list any permission matrix/mapping
> > work they have started or is anyone able to provide some permission
> > information for specific procedures in the documentation?
> >
> >
> > Thanks,
> > Robert
> >
> >
> >
> > Robert Soulliere, BA (Hons), MLIS
> > Systems Librarian
> > Mohawk College Library
> > robert.soulliere at mohawkcollege.ca
> > Telephone: 905 575 1212 x3936
> > Fax: 905 575 2011
> >
> > 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
> > OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> > http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
> >
>
>
>
> --
> Tim Spindler
> tjspindler at gmail.com
>
> *P** Go Green - **Save a tree! Please don't print this e-mail unless it's
> really necessary.*
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://list.georgialibraries.org/pipermail/open-ils-documentation/attachments/20110512/a292f46a/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Thu, 12 May 2011 12:10:59 -0700
> From: Lori Bowen Ayre <lori.ayre at galecia.com>
> Subject: Re: [OPEN-ILS-DOCUMENTATION] Evergreen Permissions
> descriptions/map/matrix documentation?
> To: Documentation discussion for Evergreen software
> <open-ils-documentation at list.georgialibraries.org>
> Message-ID: <BANLkTikXym7kvNxKp5yBoEnSBwZ=r6KA3A at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Strongly agree. And just FYI, this problem is true for Koha as well. Just
> restating the code description doesn't help anyone. There needs to be
> context (what is needed upstream and what does it affect downstream). Even
> if it isn't filled in completely, creating a workflow that asks for that
> kind of info would be most useful.
>
> Lori Ayre
>
> On Thu, May 12, 2011 at 9:34 AM, Tim Spindler <tjspindler at gmail.com>
> wrote:
>
> > I think I would generally agree with what you are suggesting. For one, I
> > don't think repeating the code description does anything and I personally
> > would find it an enormous help to have more meaningful descriptions. I
> also
> > think it would be very helpful to have the required for language in there
> > and in the appropriate sections of the documentation. In working on our
> > system, I have had to do a bit of sleuth work to identify what
> permissions
> > are need for a given function and I'm still very uncertain if I'm
> > understanding some of these correctly. Therefore, proceeding as you
> suggest
> > would be a big help.
> >
> > Tim Spindler
> > Manager of Library Applications
> > C/W MARS
> >
> >
> > On Thu, May 12, 2011 at 10:57 AM, Soulliere, Robert <
> > robert.soulliere at mohawkcollege.ca> wrote:
> >
> >> Hi All,
> >>
> >> One of the most challenging aspects of Evergreen is working with the
> >> complex permissions matrix. In order to alleviate some of the challenges
> >> associated with giving the appropriate permissions for groups/users to
> carry
> >> out various tasks. I was thinking about 2 strategies for improving
> >> documentation in this area:
> >>
> >> 1) Update the descriptions located in the permission.prm_list table in
> the
> >> Evergreen database . Then, create a script to generate a docbook table
> with
> >> the updated descriptions. I would really like some feedback for the
> best
> >> approach for this in regards to the wording of the descriptions.
> Currently,
> >> some of the descriptions repeat the code field (e.g."DELETE_BIB_LEVEL")
> and
> >> in other cases they have descriptions with. "Allow a user to..." or
> "Enables
> >> the user to..." etc... I wonder if it would be useful for these
> permission
> >> descriptions to include "required for ..." with a list of functions
> actions
> >> where the permission is required. Does that sound like a plausible or
> useful
> >> bit on info in the descriptions themselves or would it create a complex
> >> situation as permissions are added and the permission structure is
> adjusted
> >> in the future?
> >>
> >> 2) At the DIG meeting in Decatur someone mentioned creating a list of
> >> required permissions fat the beginning of various procedures/sections in
> the
> >> documentation. I thought this was an excellent idea and I think someone
> >> might have suggested that they have begun work on a permission matrix.
> Would
> >> anyone be able to share with this DIG list any permission matrix/mapping
> >> work they have started or is anyone able to provide some permission
> >> information for specific procedures in the documentation?
> >>
> >>
> >> Thanks,
> >> Robert
> >>
> >>
> >>
> >> Robert Soulliere, BA (Hons), MLIS
> >> Systems Librarian
> >> Mohawk College Library
> >> robert.soulliere at mohawkcollege.ca
> >> Telephone: 905 575 1212 x3936
> >> Fax: 905 575 2011
> >>
> >> 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
> >> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> >>
> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
> >>
> >
> >
> >
> > --
> > Tim Spindler
> > tjspindler at gmail.com
> >
> > *P** Go Green - **Save a tree! Please don't print this e-mail unless
> > it's really necessary.*
> >
> >
> >
> >
> > _______________________________________________
> > OPEN-ILS-DOCUMENTATION mailing list
> > OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> > http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
> >
> >
>
>
> --
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=
> Lori Bowen Ayre // Library Technology Consultant
> The Galecia Group // www.galecia.com
> (707) 763-6869 // Lori.Ayre at galecia.com
>
> <Lori.Ayre at galecia.com>Specializing in open source ILS solutions, RFID,
> filtering,
> workflow optimization, and materials handling
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://list.georgialibraries.org/pipermail/open-ils-documentation/attachments/20110512/1deaa8f2/attachment-0001.htm
>
> ------------------------------
>
> Message: 3
> Date: Thu, 12 May 2011 19:35:23 +0000
> From: "Turner, Jennifer M" <jennifer.turner at mnsu.edu>
> Subject: Re: [OPEN-ILS-DOCUMENTATION] Evergreen Permissions
> descriptions/map/matrix documentation?
> To: Documentation discussion for Evergreen software
> <open-ils-documentation at list.georgialibraries.org>
> Message-ID:
> <A2C42DB72B6692469E4A92BB3ABB62A8195293AD at EX10DB4.Campus.mnsu.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> I also strongly agree with all of Robert's suggestions. Getting
> permissions ironed out was one of our biggest issues when we went live on
> Evergreen - and we still have questions.
>
> A list of "recommended permissions" for the various Evergreen modules
> and/or library employees (circ, cataloging, acq, serials, branch managers,
> etc...) could be useful, too. I tried to start something like this WAY back
> when we were setting our libraries up, but I didn't get very far, since
> permissions like "CREATE_LASSO_MAP" kept me in a continually perplexed
> state, since I had - and have - no idea what that permission might be used
> for!
>
> Although getting a comprehensive list of permissions and
> definitions/descriptions will be a challenge, once a list is assembled, it
> *shouldn't* be too difficult to maintain...ideally developers could/would
> release descriptions of what permissions do when they are added to the code.
>
> Jenny (PALS)
>
> 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 2:11 PM
> To: Documentation discussion for Evergreen software
> Subject: Re: [OPEN-ILS-DOCUMENTATION] Evergreen Permissions
> descriptions/map/matrix documentation?
>
> Strongly agree. And just FYI, this problem is true for Koha as well. Just
> restating the code description doesn't help anyone. There needs to be
> context (what is needed upstream and what does it affect downstream). Even
> if it isn't filled in completely, creating a workflow that asks for that
> kind of info would be most useful.
>
> Lori Ayre
> On Thu, May 12, 2011 at 9:34 AM, Tim Spindler <tjspindler at gmail.com
> <mailto:tjspindler at gmail.com>> wrote:
> I think I would generally agree with what you are suggesting. For one, I
> don't think repeating the code description does anything and I personally
> would find it an enormous help to have more meaningful descriptions. I also
> think it would be very helpful to have the required for language in there
> and in the appropriate sections of the documentation. In working on our
> system, I have had to do a bit of sleuth work to identify what permissions
> are need for a given function and I'm still very uncertain if I'm
> understanding some of these correctly. Therefore, proceeding as you suggest
> would be a big help.
>
> Tim Spindler
> Manager of Library Applications
> C/W MARS
>
> On Thu, May 12, 2011 at 10:57 AM, Soulliere, Robert <
> robert.soulliere at mohawkcollege.ca<mailto:robert.soulliere at mohawkcollege.ca>>
> wrote:
> Hi All,
>
> One of the most challenging aspects of Evergreen is working with the
> complex permissions matrix. In order to alleviate some of the challenges
> associated with giving the appropriate permissions for groups/users to carry
> out various tasks. I was thinking about 2 strategies for improving
> documentation in this area:
>
> 1) Update the descriptions located in the permission.prm_list table in the
> Evergreen database . Then, create a script to generate a docbook table with
> the updated descriptions. I would really like some feedback for the best
> approach for this in regards to the wording of the descriptions. Currently,
> some of the descriptions repeat the code field (e.g."DELETE_BIB_LEVEL") and
> in other cases they have descriptions with. "Allow a user to..." or "Enables
> the user to..." etc... I wonder if it would be useful for these permission
> descriptions to include "required for ..." with a list of functions actions
> where the permission is required. Does that sound like a plausible or useful
> bit on info in the descriptions themselves or would it create a complex
> situation as permissions are added and the permission structure is adjusted
> in the future?
>
> 2) At the DIG meeting in Decatur someone mentioned creating a list of
> required permissions fat the beginning of various procedures/sections in the
> documentation. I thought this was an excellent idea and I think someone
> might have suggested that they have begun work on a permission matrix. Would
> anyone be able to share with this DIG list any permission matrix/mapping
> work they have started or is anyone able to provide some permission
> information for specific procedures in the documentation?
>
>
> Thanks,
> Robert
>
>
>
> Robert Soulliere, BA (Hons), MLIS
> Systems Librarian
> Mohawk College Library
> robert.soulliere at mohawkcollege.ca<mailto:robert.soulliere at mohawkcollege.ca
> >
> Telephone: 905 575 1212<tel:905%20575%201212> x3936
> Fax: 905 575 2011<tel:905%20575%202011>
>
> 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
> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org<mailto:
> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org>
> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
>
>
> --
> Tim Spindler
> tjspindler at gmail.com<mailto:tjspindler at gmail.com>
>
>
> P Go Green - Save a tree! Please don't print this e-mail unless it's
> really necessary.
>
>
>
>
> _______________________________________________
> OPEN-ILS-DOCUMENTATION mailing list
> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org<mailto:
> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org>
> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
>
>
>
> --
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=
> Lori Bowen Ayre // Library Technology Consultant
> The Galecia Group // www.galecia.com<http://www.galecia.com/>
> (707) 763-6869 // Lori.Ayre at galecia.com<mailto:Lori.Ayre at galecia.com>
>
> Specializing in open source ILS solutions, RFID, filtering,
> workflow optimization, and materials handling
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://list.georgialibraries.org/pipermail/open-ils-documentation/attachments/20110512/c10f63c1/attachment.htm
>
> ------------------------------
>
> _______________________________________________
> OPEN-ILS-DOCUMENTATION mailing list
> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
>
>
> End of OPEN-ILS-DOCUMENTATION Digest, Vol 37, Issue 9
> *****************************************************
>
--
Shae Tetterton
Project Manager
Equinox Software, Inc. / Your Library's Guide to Open Source
email: shae at esilibrary.com
direct: +1 678-431-5808 or 770-709-5573
web: http://www.esilibrary.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.georgialibraries.org/pipermail/open-ils-documentation/attachments/20110512/14dcbc99/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Proposed_Permissions.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 47592 bytes
Desc: not available
Url : http://list.georgialibraries.org/pipermail/open-ils-documentation/attachments/20110512/14dcbc99/attachment-0001.bin
More information about the OPEN-ILS-DOCUMENTATION
mailing list