Hi,
On 08/15/2012 09:01 AM, Nicole Engard wrote:
Does anyone know what reserves.constrainttype is? It has an 'o' or an
'a' in my database but I'm not sure what causes what value or what
each stands for.
Chris or Paul may know the history, but I think what constrainttype is
_supposed_ to do is allow one to distinguish between a copy-level (or
biblioitem-level?) hold (type 'o') and a title-level hold (type 'a').
Or was it meant to be "metabib" (type 'a') versus biblioitem (type 'o')?
However, as near as I can tell, at present 'a' and 'o' holds currently
behave identically, and the only code that creates holds with a type
other than 'a' is the serial routing list. In other words, I'm 99% sure
that the reservecontraints mechanism doesn't work at all, and is a
carry-over from 2.x that it may be better to drop.
I would be grateful if anybody with knowledge of the original intent of
the hold constraint feature could share what they know.
Regards,
Galen
--
Galen Charlton
Director of Support and Implementation
Equinox Software, Inc. / The Open Source Experts
email: [email protected]
direct: +1 770-709-5581
cell: +1 404-984-4366
skype: gmcharlt
web: http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org &
http://evergreen-ils.org
_______________________________________________
Koha mailing list http://koha-community.org
[email protected]
http://lists.katipo.co.nz/mailman/listinfo/koha
