[OPEN-ILS-DEV] Circulation Menu in the Staff Client
Cynthia Williamson
crwbookgirl at gmail.com
Sat Jun 20 06:39:49 EDT 2009
I think my "lack of regard" for the retrieve patron option on the circ menu
probably has to do with the fact our circ desk is not that busy (relatively
speaking in comparison to a lot of public libraries) - no doubt people come
in *with* their cards to do things other than check out books, but really,
not so much in our library.
If the retrieve barcode function is useful to most folks I guess I'm happy
to leave it where it is, but it'd be nice to have that replace barcode
function buried a bit for sure.
Laura - I think we'll probably have a mix of function key and menu users on
staff - once we're live, I promise to send lots of feed back - you'll have
to take it with a grain "from a not so busy circ desk" salt.
Cynthia
On Fri, Jun 19, 2009 at 8:41 PM, <
open-ils-dev-request at list.georgialibraries.org> wrote:
> Send Open-ils-dev mailing list submissions to
> open-ils-dev at list.georgialibraries.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://libmail.georgialibraries.org/mailman/listinfo/open-ils-dev
> or, via email, send a message with subject or body 'help' to
> open-ils-dev-request at list.georgialibraries.org
>
> You can reach the person managing the list at
> open-ils-dev-owner at list.georgialibraries.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Open-ils-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Circulation Menu in the Staff Client (Nathan Eady)
> 2. Re: Export to RefWorks in Evergreen (Bill Erickson)
> 3. Re: Export to RefWorks in Evergreen (Mike Rylander)
> 4. Re: Export to RefWorks in Evergreen (Mike Rylander)
> 5. Re: Export to RefWorks in Evergreen (David Fiander)
> 6. Re: Export to RefWorks in Evergreen (Warren Layton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 19 Jun 2009 13:06:14 -0400
> From: Nathan Eady <eady at galion.lib.oh.us>
> Subject: Re: [OPEN-ILS-DEV] Circulation Menu in the Staff Client
> To: Evergreen Development Discussion List
> <open-ils-dev at list.georgialibraries.org>
> Message-ID: <87skhw17cp.fsf at donalbain.galion.lib.oh.us>
> Content-Type: text/plain; charset=utf-8
>
> Cynthia Williamson <crwbookgirl at gmail.com> writes:
>
> > I also agree that [patron lookup by barcode] isn't really needed on
> > the circ menu because if you have barcode you're probably going to
> > be checking out books and you would indeed just use the check out
> > function - as William R pointed out. ?
>
> Actually, this exact line of reasong is one of the key things I am
> dissatisfied with in our current ILS. I don't know about other
> libraries, but where I work, not having this is a real problem. There
> are a LOT of reasons to scan a patron's card and look at their record.
> It's one of the most frequent things we do. Not having a quick and
> easy way to get there is a real pain.
>
> > Another argument for removing the retrieve patron by barcode
> > function is that it is right above the "replace barcode function"
> > .... we are a couple of weeks from going live and starting to worry
> > about newbies accidently replacing barcodes
>
> I would argue that the "replace barcode" function is the more
> dangerous function of the two, and also it's used a great deal less
> often, and so that's the one that should be tucked away behind some
> longer workflow.
>
> Pulling up a patron's record by barcode is safer and needs to be done
> much more frequently, so that one should be quick and easy.
>
> --
> Nathan Eady
> Galion Public Library
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 19 Jun 2009 17:11:13 -0400
> From: Bill Erickson <erickson at esilibrary.com>
> Subject: Re: [OPEN-ILS-DEV] Export to RefWorks in Evergreen
> To: Evergreen Development Discussion List
> <open-ils-dev at list.georgialibraries.org>
> Message-ID:
> <284aac600906191411t5be6ef7clecb02870e1659d05 at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Thu, Jun 18, 2009 at 7:39 AM, Warren Layton <warren.layton at gmail.com
> >wrote:
>
> > On Wed, Jun 17, 2009 at 11:50 PM, Mike Rylander <mrylander at gmail.com
> >wrote:
> >
> >>
> >> Hrm ... is the purpose of <VENDOR> to tell RefWorks what sort of
> >> system the data is coming from, or to tell them which of their clients
> >> is using the service?
> >>
> >
> > I believe it's the latter (for instance, see the link to RefWorks at
> > http://mirlyn2-beta.lib.umich.edu/Record/001376273 ).
> >
> > I've attached a slightly modified patch that doesn't append "+Evergreen"
> to
> > <VENDOR> and just uses the org's fullname (with spaces replaced with '+'
> > chars). That is likely more appropriate, at least from RefWorks' point of
> > view.
> >
>
>
> Couple comments... We need to turn "Export to RefWorks" into a DTD entity
> for i18n purposes (says the lazy i18n-er). We also need to consider
> displaying (or suppressing display) of the link by org unit setting or some
> other easily toggled switch in the javascript.
>
> Other than that, the patch looks great to me.
>
> wlayton++
>
> -b
>
>
> --
> Bill Erickson
> | VP, Software Development & Integration
> | Equinox Software, Inc. / The Evergreen Experts
> | phone: 877-OPEN-ILS (673-6457)
> | email: erickson at esilibrary.com
> | web: http://esilibrary.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20090619/5cdfbdf1/attachment-0001.htm
>
> ------------------------------
>
> Message: 3
> Date: Fri, 19 Jun 2009 17:14:24 -0400
> From: Mike Rylander <mrylander at gmail.com>
> Subject: Re: [OPEN-ILS-DEV] Export to RefWorks in Evergreen
> To: Evergreen Development Discussion List
> <open-ils-dev at list.georgialibraries.org>
> Message-ID:
> <b918cf3d0906191414ia5005b0n6f7164e47946f50b at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Fri, Jun 19, 2009 at 5:11 PM, Bill Erickson<erickson at esilibrary.com>
> wrote:
> >
> >
> > On Thu, Jun 18, 2009 at 7:39 AM, Warren Layton <warren.layton at gmail.com>
> > wrote:
> >>
> >> On Wed, Jun 17, 2009 at 11:50 PM, Mike Rylander <mrylander at gmail.com>
> >> wrote:
> >>>
> >>> Hrm ... is the purpose of <VENDOR> to tell RefWorks what sort of
> >>> system the data is coming from, or to tell them which of their clients
> >>> is using the service?
> >>
> >> I believe it's the latter (for instance, see the link to RefWorks at
> >> http://mirlyn2-beta.lib.umich.edu/Record/001376273 ).
> >>
> >> I've attached a slightly modified patch that doesn't append "+Evergreen"
> >> to <VENDOR> and just uses the org's fullname (with spaces replaced with
> '+'
> >> chars). That is likely more appropriate, at least from RefWorks' point
> of
> >> view.
> >
> > Couple comments... We need to turn "Export to RefWorks" into a DTD entity
> > for i18n purposes (says the lazy i18n-er).
>
> Done while integrating the patch.
>
> >? We also need to consider
> > displaying (or suppressing display) of the link by org unit setting or
> some
> > other easily toggled switch in the javascript.
> >
>
> Not done ... but I'm inclined to leave it in, rather than out, by
> default for now. Thoughts, anyone?
>
> > Other than that, the patch looks great to me.
> >
>
> I also wrapped the code that does the actual attribute setting in a
> test to make sure the element's there, which it won't be in craftsman,
> for now.
>
> > wlayton++
>
> Indeed.
>
> Not committed yet. Waiting on an updated xslt.
>
> --
> Mike Rylander
> | VP, Research and Design
> | Equinox Software, Inc. / The Evergreen Experts
> | phone: 1-877-OPEN-ILS (673-6457)
> | email: miker at esilibrary.com
> | web: http://www.esilibrary.com
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 19 Jun 2009 17:28:35 -0400
> From: Mike Rylander <mrylander at gmail.com>
> Subject: Re: [OPEN-ILS-DEV] Export to RefWorks in Evergreen
> To: Evergreen Development Discussion List
> <open-ils-dev at list.georgialibraries.org>
> Message-ID:
> <b918cf3d0906191428j235078a4t49fa8c2750cb3b29 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Fri, Jun 19, 2009 at 5:14 PM, Mike Rylander<mrylander at gmail.com> wrote:
> > On Fri, Jun 19, 2009 at 5:11 PM, Bill Erickson<erickson at esilibrary.com>
> wrote:
> >>
> >>
> >> On Thu, Jun 18, 2009 at 7:39 AM, Warren Layton <warren.layton at gmail.com
> >
> >> wrote:
> >>>
> >>> On Wed, Jun 17, 2009 at 11:50 PM, Mike Rylander <mrylander at gmail.com>
> >>> wrote:
> >>>>
> >>>> Hrm ... is the purpose of <VENDOR> to tell RefWorks what sort of
> >>>> system the data is coming from, or to tell them which of their clients
> >>>> is using the service?
> >>>
> >>> I believe it's the latter (for instance, see the link to RefWorks at
> >>> http://mirlyn2-beta.lib.umich.edu/Record/001376273 ).
> >>>
> >>> I've attached a slightly modified patch that doesn't append
> "+Evergreen"
> >>> to <VENDOR> and just uses the org's fullname (with spaces replaced with
> '+'
> >>> chars). That is likely more appropriate, at least from RefWorks' point
> of
> >>> view.
> >>
> >> Couple comments... We need to turn "Export to RefWorks" into a DTD
> entity
> >> for i18n purposes (says the lazy i18n-er).
> >
> > Done while integrating the patch.
> >
> >>? We also need to consider
> >> displaying (or suppressing display) of the link by org unit setting or
> some
> >> other easily toggled switch in the javascript.
> >>
> >
> > Not done ... but I'm inclined to leave it in, rather than out, by
> > default for now. ?Thoughts, anyone?
> >
> >> Other than that, the patch looks great to me.
> >>
> >
> > I also wrapped the code that does the actual attribute setting in a
> > test to make sure the element's there, which it won't be in craftsman,
> > for now.
> >
> >> wlayton++
> >
> > Indeed.
> >
> > Not committed yet. ?Waiting on an updated xslt.
> >
>
> Now ... it's committed. Thanks a ton, Warren. Very nice work.
>
> I'm not going to backport this from trunk to 1.6 just yet so we can
> have some discussion on the ability to turn it on or off, and what the
> default should be.
>
> --
> Mike Rylander
> | VP, Research and Design
> | Equinox Software, Inc. / The Evergreen Experts
> | phone: 1-877-OPEN-ILS (673-6457)
> | email: miker at esilibrary.com
> | web: http://www.esilibrary.com
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 19 Jun 2009 19:40:04 -0400
> From: David Fiander <david at fiander.info>
> Subject: Re: [OPEN-ILS-DEV] Export to RefWorks in Evergreen
> To: Evergreen Development Discussion List
> <open-ils-dev at list.georgialibraries.org>
> Message-ID:
> <a8d66ee70906191640n3a9d6943te2d47ce60b8e6608 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> You definitely need to be able to turn it off and on. The default
> should probably be "off".
>
> You also need to be able to set the refworks server name, since most
> Canadian universities don't go to the refworks.com server, but use the
> Canadian server, refworks.scholarsportal.info.
>
> In the perfect world, individual users would have a personal
> configuration option, but that's easily handled by some of the other
> ways of integrating refworks.
>
> - David
>
> On Fri, Jun 19, 2009 at 5:28 PM, Mike Rylander<mrylander at gmail.com> wrote:
> > On Fri, Jun 19, 2009 at 5:14 PM, Mike Rylander<mrylander at gmail.com>
> wrote:
> >> On Fri, Jun 19, 2009 at 5:11 PM, Bill Erickson<erickson at esilibrary.com>
> wrote:
> >>>
> >>>
> >>> On Thu, Jun 18, 2009 at 7:39 AM, Warren Layton <
> warren.layton at gmail.com>
> >>> wrote:
> >>>>
> >>>> On Wed, Jun 17, 2009 at 11:50 PM, Mike Rylander <mrylander at gmail.com>
> >>>> wrote:
> >>>>>
> >>>>> Hrm ... is the purpose of <VENDOR> to tell RefWorks what sort of
> >>>>> system the data is coming from, or to tell them which of their
> clients
> >>>>> is using the service?
> >>>>
> >>>> I believe it's the latter (for instance, see the link to RefWorks at
> >>>> http://mirlyn2-beta.lib.umich.edu/Record/001376273 ).
> >>>>
> >>>> I've attached a slightly modified patch that doesn't append
> "+Evergreen"
> >>>> to <VENDOR> and just uses the org's fullname (with spaces replaced
> with '+'
> >>>> chars). That is likely more appropriate, at least from RefWorks' point
> of
> >>>> view.
> >>>
> >>> Couple comments... We need to turn "Export to RefWorks" into a DTD
> entity
> >>> for i18n purposes (says the lazy i18n-er).
> >>
> >> Done while integrating the patch.
> >>
> >>>? We also need to consider
> >>> displaying (or suppressing display) of the link by org unit setting or
> some
> >>> other easily toggled switch in the javascript.
> >>>
> >>
> >> Not done ... but I'm inclined to leave it in, rather than out, by
> >> default for now. ?Thoughts, anyone?
> >>
> >>> Other than that, the patch looks great to me.
> >>>
> >>
> >> I also wrapped the code that does the actual attribute setting in a
> >> test to make sure the element's there, which it won't be in craftsman,
> >> for now.
> >>
> >>> wlayton++
> >>
> >> Indeed.
> >>
> >> Not committed yet. ?Waiting on an updated xslt.
> >>
> >
> > Now ... it's committed. ?Thanks a ton, Warren. ?Very nice work.
> >
> > I'm not going to backport this from trunk to 1.6 just yet so we can
> > have some discussion on the ability to turn it on or off, and what the
> > default should be.
> >
> > --
> > Mike Rylander
> > ?| VP, Research and Design
> > ?| Equinox Software, Inc. / The Evergreen Experts
> > ?| phone: ?1-877-OPEN-ILS (673-6457)
> > ?| email: ?miker at esilibrary.com
> > ?| web: ?http://www.esilibrary.com
> >
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 19 Jun 2009 20:41:19 -0400
> From: Warren Layton <warren.layton at gmail.com>
> Subject: Re: [OPEN-ILS-DEV] Export to RefWorks in Evergreen
> To: Evergreen Development Discussion List
> <open-ils-dev at list.georgialibraries.org>
> Message-ID:
> <65b8a83b0906191741u5795bb97we3d45f8e0bc5e0f5 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Fri, Jun 19, 2009 at 5:28 PM, Mike Rylander <mrylander at gmail.com>
> wrote:
>
> > Now ... it's committed. Thanks a ton, Warren. Very nice work.
> >
> > I'm not going to backport this from trunk to 1.6 just yet so we can
> > have some discussion on the ability to turn it on or off, and what the
> > default should be.
>
>
> Thanks for including it -- and thanks for keeping it in trunk only. As you
> and David Fiander have noted, it probably needs a bit more thought to make
> sure that it will work for other types of RefWorks users.
>
> One possible option would be to include the SuperCat feed in 1.6 (if the
> feed is deemed stable, of course) but leave out the changes to rdetail.js
> and page_rdetail.xml until a good solution is found for the default
> settings.
>
> Thanks again!
> Warren
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20090619/0f640dff/attachment.htm
>
> End of Open-ils-dev Digest, Vol 39, Issue 33
> ********************************************
>
--
Afoot and light-hearted I take to the open road,
Healthy, free, the world before me,
The long brown path before me leading wherever I choose.
Henceforth I ask not good-fortune, I myself am good-fortune,
Henceforth I whimper no more, postpone no more, need nothing,
Done with indoor complaints, libraries, querulous criticisms,
Strong and content I travel the open road.
Walt Whitman, Song of the Open Road
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20090620/2434201f/attachment-0001.htm
More information about the Open-ils-dev
mailing list