[OPEN-ILS-GENERAL] Reshelving status?

Thu Jan 8 13:11:33 EST 2015

Good to know!

I copied the srfsh file and modified it, then ran it.

I just heard from Jennifer that the command line tests I ran worked.  Now I
need to go figure out why the cron isn't running right.  But that's
something I can debug.

Patrick

On Thu, Jan 8, 2015 at 11:22 AM, Ben Shum <bshum at biblio.org> wrote:

> Hi Patrick,
>
> Out of curiosity, where are you changing the interval for reshelving
> to 1 hour?  There's a place in the reshelving_complete.srfsh for the
> argument (by default it's set to "24h"), but that is overwritten by
> whatever is contained in your library settings for the given org
> units.  I would double check to see what value you have the library
> setting configured to.  Quoting my reply to Janice a couple months
> back:  "For reference, the library setting in question is in group
> "Library" named "Change reshelving status interval"."  Note, because
> it is a library setting, it is possible to have different intervals
> for each library org unit in Evergreen.  For us, we set ours for the
> entire consortium to share a single value.
>
> -- Ben
>
> On Thu, Jan 8, 2015 at 10:52 AM, Patrick Gardella
> <patrick.gardella at asburyseminary.edu> wrote:
> > Hi, Ben (and everyone!),
> >
> > I'm now helping Jennifer with this reshelving issue and Janice whom you
> > helped a few months ago. (This is the same evergreen installation, just
> two
> > different libraries.)
> >
> > I ran the script manually last night, and then again today.  I also
> dropped
> > it to 1h to test one of your previous notes. The script completed in
> about
> > 30 seconds last night, and now in less than a second.  It returned 88
> > records reshelved today, and now 0 every time I run it. So it's doing its
> > job, but Jennifer still sees the status as Reshelving.  Is there another
> > step beyond running reshelving_complete.srfsh
> >
> > Any suggestions before opening a ticket?
> >
> > Patrick
> >
> > On Wed, Jan 7, 2015 at 12:06 PM, Ben Shum <bshum at biblio.org> wrote:
> >>
> >> Ideally, if the script is running properly, then you should not have
> >> to manually change anything.  Manually changing statuses seems tedious
> >> and annoying to me; that's why the script exists.  That said, I
> >> believe it is possible to use item status to change the status of
> >> items manually to Available all at once.
> >>
> >> If you really want the interval to be applied at the rate set, then
> >> yes, you do need to run the reshelving script more frequently.  That
> >> said, it is currently not advised to do this *too* frequently due to
> >> potential bugs arising from having items go back to Available even as
> >> they are being checked out again to new patrons.  i.e. the item was
> >> selected to be moved from reshelving to available, but is checked out
> >> while the reshelving script is being run.  This Evergreen bug refers
> >> to the problem (for other curious eyes):
> >> https://bugs.launchpad.net/evergreen/+bug/1018011
> >>
> >> -- Ben
> >>
> >> On Wed, Jan 7, 2015 at 11:53 AM, Walz, Jennifer <jlwalz at asbury.edu>
> wrote:
> >> > Thanks!
> >> >
> >> >  I did find a mention of this script that is supposed to be running on
> >> > our server.  I believe it is NOT running and we are looking into that.
> >> >
> >> >   I'll pass along the info about setting the interval shorter.   But
> >> > then it seems from your instructions that the script ALSO needs to be
> >> > running on the server at the same interval yes?
> >> >
> >> >   To answer your question about items in the reshelving status.  We
> have
> >> > items that are STILL in the reshelving status after one month!   So,
> it
> >> > seems like the script is not running as it should on the server.
> >> >
> >> >   Is there  a way to MANUALLY change an item / items from reshelving
> to
> >> > available??     Or do we always have to wait for that script to run?
> >> >
> >> > Thanks!
> >> >
> >> > Jennifer
> >> > --------------------------------------------------
> >> > Jennifer Walz, MLS - Head of ILS stuff
> >> > Kinlaw Library -  Asbury University
> >> > One Macklem Drive, Wilmore, KY 40390
> >> > 859-858-3511 ext. 2269
> >> > jlwalz at asbury.edu
> >> >
> >> > -----Original Message-----
> >> > From: open-ils-general-bounces at list.georgialibraries.org
> >> > [mailto:open-ils-general-bounces at list.georgialibraries.org] On
> Behalf Of Ben
> >> > Shum
> >> > Sent: Wednesday, January 07, 2015 11:48 AM
> >> > To: Evergreen Discussion Group
> >> > Subject: Re: [OPEN-ILS-GENERAL] Reshelving status?
> >> >
> >> > Hi Jennifer,
> >> >
> >> > In a reply I made a couple months ago, I described in a little more
> >> > detail how the reshelving interval might be processed (see
> >> > http://georgialibraries.markmail.org/thread/skib7pmbyu6v3cwz)  You
> may
> >> > find that you need to set it to less than "1 day" exactly, and more
> like "1
> >> > hour" to definitely catch up and move things back to Available when
> the
> >> > reshelving_complete.srfsh cron job runs daily.  Also, are you saying
> that
> >> > nothing is changing after one day, exactly?  Or that nothing is
> changing at
> >> > all?  Maybe you should verify that the right script is running on your
> >> > Evergreen system.
> >> >
> >> > To my knowledge, there is no easy way to bypass the reshelving status,
> >> > but you can consider other options.  Like renaming the copy status to
> >> > "available" (lowercase, instead of init capitalized, making it
> different,
> >> > but conceptually the same).
> >> >
> >> > As for making a second checkin change the status definitely to
> >> > available, that's a nice idea, but I could see it being trouble on
> >> > situations like double-scanning or other mis-scans in live use.  That
> said,
> >> > if you were to sponsor development in this area, perhaps other
> libraries may
> >> > be interested.
> >> >
> >> > Cheers,
> >> >
> >> > -- Ben
> >> >
> >> > On Wed, Jan 7, 2015 at 11:35 AM, Walz, Jennifer <jlwalz at asbury.edu>
> >> > wrote:
> >> >> All –
> >> >>
> >> >>
> >> >>
> >> >>   We are very annoyed by the reshelving status and it is NOT going
> >> >> away in the time interval it is supposed to.  We have set our library
> >> >> settings to 1
> >> >> day.   But nothing is changing over after one day.    Is there a
> >> >> trigger or
> >> >> action that needs to be taken to make it occur?   How do we get it to
> >> >> NOT
> >> >> ever go into that status, or to do it for a very short time?    Is
> >> >> there any
> >> >> way to make all items never go into that status on checkin?
> >> >>
> >> >>
> >> >>
> >> >> What we would LIKE is to have it switch from that status on a SECOND
> >> >> checkin at the circ desk just before putting those items out on the
> >> >> shelves.  Is
> >> >> that possible?    We have always done a double checkin to make sure
> all
> >> >> items are checked in before shelving.
> >> >>
> >> >>
> >> >>
> >> >> Thanks for all your input!
> >> >>
> >> >>
> >> >>
> >> >> Jennifer
> >> >>
> >> >> --------------------------------------------------
> >> >> Jennifer Walz, MLS - Head of ILS stuff Kinlaw Library -  Asbury
> >> >> University One Macklem Drive, Wilmore, KY 40390
> >> >> 859-858-3511 ext. 2269
> >> >> jlwalz at asbury.edu
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Benjamin Shum
> >> > Evergreen Systems Manager
> >> > Bibliomation, Inc.
> >> > 24 Wooster Ave.
> >> > Waterbury, CT 06708
> >> > 203-577-4070, ext. 113
> >>
> >>
> >>
> >> --
> >> Benjamin Shum
> >> Evergreen Systems Manager
> >> Bibliomation, Inc.
> >> 24 Wooster Ave.
> >> Waterbury, CT 06708
> >> 203-577-4070, ext. 113
> >
> >
>
>
>
> --
> Benjamin Shum
> Evergreen Systems Manager
> Bibliomation, Inc.
> 24 Wooster Ave.
> Waterbury, CT 06708
> 203-577-4070, ext. 113
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20150108/09e5b26d/attachment.htm>