[OPEN-ILS-DEV] [OPEN-ILS-GENERAL] Possible Development Idea
Tim Spindler
tjspindler at gmail.com
Wed Jan 16 08:08:34 EST 2013
I have further use case from one of our libraries on this topic:
---
The Westfield Library has a status of "Ask your librarian" for items that
go to a location that is short term storage and the physical location of
the copy is rather fluid. However, the general location assigned is Adult
Fiction. The spine label has the label of "Adult Fic Corn." There is a
location in public areas and short term storage that is adult fiction and
the copy status is a reminder to staff to check both locations but also an
alert to patrons that if they don't find it on the shelves to check with a
librarian. The short term storage is readily accessible for librarians but
not for patrons. If the library has to change the location every time then
spine labels and copy locations need to be updated regularly where as if a
status like "Ask Your Librarian" that is sticky were available the copy
location could be static with the public adult fiction stacks or short term
storage depending on the immediate needs of the library and the status of
Ask Your Librarian could be used to alert both patrons and staff to check
both locations.
Tim
On Tue, Jan 15, 2013 at 10:38 AM, Thomas Berezansky <tsbere at mvlc.org> wrote:
> My personal view is that the status should still go to Available, period.
>
> However, I could see assigning a field that overrides for display purposes
> in the OPAC. A table of such values could include a "Always or just when
> Available" flag, and doing something like %s in the name could inject the
> real status name when always replacing.
>
> Thus you could end up with "Available" replaced by "Walk In Loan" or have
> the status say "Walk In Loan - %s" to get things like "Walk In Loan -
> Available" and "Walk In Loan - Checked Out".
>
> This also removes the need for fighting with overrides on the status at
> checkout, as the real status isn't a custom one, and prevents us from
> having to change reshelving code because it would still be pushing things
> to "Available".
>
> Thomas Berezansky
> Merrimack Valley Library Consortium
>
>
> Quoting Tim Spindler <tspindler at cwmars.org>:
>
> I'm not sure but I think there are two ways the interface could work (and
>> I could envision both options being available).
>>
>>
>> - A flag in the copy record that indicates the status is essentially
>>
>> "sticky" and return after reshelving to the status once it is checked
>> in.
>> - Another field where the status itself is marked as sticky.
>>
>>
>> In other case, if status is meant to be temporary as you suggest, it
>> wouldn't retain that status. The cases below are how some of our
>> libraries want to use it now. I think the best example may be where a
>> library is using Walkin Loan to clearly identify to their patrons that the
>> item is non-holdable but there as a courtesy for those patrons who come to
>> the library to get an item rather than using the holds system.
>>
>>
>> Tim
>>
>> On Tue, Jan 15, 2013 at 10:24 AM, Hardy, Elaine <
>> ehardy at georgialibraries.org
>>
>>> wrote:
>>>
>>
>> Under use case #2, how would you then configure the system so that you
>>> could easily remove the item from storage to available in a case where
>>> storage is a temporary status?****
>>>
>>> ** **
>>>
>>> *Elaine*****
>>> ------------------------------
>>>
>>>
>>>
>>> J. Elaine Hardy
>>> PINES Bibliographic Projects & Metadata Manager
>>> Georgia Public Library Service
>>> 1800 Century Place, Ste 150
>>> Atlanta, Ga. 30345-4304
>>>
>>> 404.235-7128
>>> 404.235-7201, fax
>>> ehardy at georgialibraries.org
>>> www.georgialibraries.org
>>> www.georgialibraries.org/pines
>>>
>>>
>>> ****
>>>
>>> *From:* open-ils-general-bounces at list.**georgialibraries.org<open-ils-general-bounces at list.georgialibraries.org>[mailto:
>>> open-ils-general-bounces at list.**georgialibraries.org<open-ils-general-bounces at list.georgialibraries.org>]
>>> *On Behalf Of *Tim
>>> Spindler
>>> *Sent:* Friday, January 11, 2013 2:52 PM
>>> *To:* Evergreen Development Discussion List; Evergreen Discussion Group
>>> *Subject:* [OPEN-ILS-GENERAL] Possible Development Idea****
>>>
>>> ** **
>>>
>>>
>>> We are in the process at prioritizing some development projects for C/W
>>> MARS. I have started to write some specs for one project and wanted to
>>> check with the community to see how others felt. A number of our
>>> libraries liked this functionality coming from an Innovative system. Tom
>>> Berezansky questioned it because it is counter to the purpose of status
>>> and
>>> he was arguing (and correct me where I am wrong) that a library should be
>>> using shelf location and not a status for this purpose. However, I can
>>> imagine instances where you might want different statuses for the same
>>> shelf location.****
>>>
>>> *Restore Original Status of Item after Checkin*****
>>>
>>> *Idea:* Restore proper status when an item is checked in (Reference
>>> Development Ideas #30)****
>>>
>>> *Description: *Copies checked out in Evergreen have the status changed to
>>>
>>> Checked Out. There is no mechanism to retain the status of the item
>>> prior
>>> to checkout. When the item is returned, the checkout status defaults to
>>> Available. ****
>>>
>>> *Expected Functionality*****
>>>
>>> · An item is checked out and the status changes to "Checked Out"
>>> as it does in the current system (2.3.1)****
>>>
>>> · The item is checked in and returns to the status prior to the
>>> above checkout while still using the interim status of reshelving.****
>>>
>>> · Some statuses such as "lost", "repair" and "missing" should be
>>> allowed to be permanently removed.****
>>>
>>> *Use Case 1*****
>>>
>>>
>>> Joe Circulation has a student who brings to the desk an item that was on
>>> course reserves with the status of course reserves. The item is checked
>>> out and the status of the item changes to "Checked Out" with a a loan
>>> period of 3 hours. The student returns the item and it is checked in
>>> and
>>> the status returns to "Reshelving" and then"Reserves".****
>>>
>>> *Use Case 2*****
>>>
>>>
>>> We have many books with the status of storage. When the book gets checked
>>> out, we are asked if we want to force the action, which is to check it
>>> out.
>>> Of course, when it is returned, the status of storage is gone. When
>>> checked
>>> back in, the status would return to "Reshelving" and then "Storage."****
>>>
>>>
>>> -- ****
>>>
>>> Tim Spindler****
>>>
>>> Manager of Library Applications****
>>>
>>> tspindler at cwmars.org****
>>>
>>> 508-755-3323 x20
>>> ****
>>>
>>> C/W MARS, Inc.****
>>>
>>> 67 Millbrook St, Suite 201****
>>>
>>> Worcester, MA 01606
>>> http://www.cwmars.org****
>>>
>>> ****
>>>
>>> *P** Go Green - **Save a tree! Please don't print this e-mail unless
>>> it's really necessary.*****
>>>
>>> ****
>>>
>>>
>>
>>
>> --
>>
>> Tim Spindler
>>
>> Manager of Library Applications
>>
>> tspindler at cwmars.org
>>
>> 508-755-3323 x20
>>
>>
>> C/W MARS, Inc.
>>
>> 67 Millbrook St, Suite 201
>>
>> Worcester, MA 01606
>> http://www.cwmars.org
>>
>>
>>
>> *P** Go Green - **Save a tree! Please don't print this e-mail unless
>> it's
>> really necessary.*
>>
>>
>
--
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://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20130116/6e901301/attachment.htm>
More information about the Open-ils-dev
mailing list