[OPEN-ILS-DEV] [OPEN-ILS-GENERAL] Possible Development Idea

[Mike Rylander]

ISTM == it seems to me.

And, no, it's morally equivalent what you're talking about.   Think of
Available as the implicit, default base status.  The status to which a copy
wants to settle when not checked out or otherwise occupied -- its "ground
state".  You're suggesting a way to configure an alternate base status,
something other than Available to which it will settle once it is no longer
involved in any type of transaction.


On Mon, Jan 14, 2013 at 9:39 AM, Tim Spindler <tspindler at cwmars.org> wrote:

> Mike,
>
> I'm not sure what ISTM is and when you are talking about a per-copy base
> status does this mean something different to you than what we are looking
> at?
>
> Tim
>
>
> On Mon, Jan 14, 2013 at 9:34 AM, Mike Rylander <mrylander at gmail.com>wrote:
>
>> I may be missing some nuance, but ISTM that using the on-copy holdable
>> flag, perhaps in combination with a copy stat cat value or copy bucket to
>> facilitate finding, would cover this use case.  That aside, the general
>> idea of having a per-copy "base status" seems interesting.
>>
>>
>> On Fri, Jan 11, 2013 at 3:20 PM, Tim Spindler <tspindler at cwmars.org>wrote:
>>
>>> Kathy Lussier suggested I add another use case that might provide
>>> additional insight into why this would be useful.
>>>
>>> *Use Case 3*
>>>
>>> We have many books with the status of walkin loan.  These are extra
>>> copies that are non-holdable so are only available to patrons who come into
>>> the library but are spread throughout the collection intermingled with
>>> holdable copies.  When checked back in, the status would return to
>>> “Reshelving” and then “Walk in Loan.”
>>>
>>>
>>> On Fri, Jan 11, 2013 at 2:52 PM, Tim Spindler <tspindler at cwmars.org>wrote:
>>>
>>>> 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.*
>>>
>>>
>>>
>>
>>
>>
>> --
>> Mike Rylander
>>  | Director of Research and Development
>>  | Equinox Software, Inc. / Your Library's Guide to Open Source
>>  | phone:  1-877-OPEN-ILS (673-6457)
>>  | email:  miker at esilibrary.com
>>  | web:  http://www.esilibrary.com
>>
>
>
>
> --
>
> 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.*
>
>
>



-- 
Mike Rylander
 | Director of Research and Development
 | Equinox Software, Inc. / Your Library's Guide to Open Source
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20130114/49db80ec/attachment.htm>