[Koha-bugs] [Bug 12632] Hold limits ignored for record level holds with item level itemtypes

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Sun Sep 14 22:16:15 CEST 2014


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12632

Katrin Fischer <katrin.fischer at bsz-bw.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |katrin.fischer at bsz-bw.de

--- Comment #5 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
I have been thinking about this change and I think there are some use cases
where this approach will or might create problems.

Right now, we use items for circulation conditions (with item-level_itypes at
least) and the record is separate from those. With this patch, that will
change.

There is currently no option to preserve a single field when overwriting a
record using one of our import scripts or tool or the Z39.50 search. So one has
to be very careful to not overwrite 942$c accidentally. It is mandatory by
default if you edit it manually, but the mandatory fields are not enforced,
when using scripts or staged import.

In fact, this is the reason the feature would not be usable for most of our
libraries, as the databases are kept in sync with the union catalog and 942$c
would be overwritten on a regular basis when importing the newer record from
the union catalog. :(

That's why I'd prefer 4) in 'comment 0', but it reads like the patch implements
1)?

What happens if there is no itemtype on record level?
How will this work for consortia were libraries might be using different sets
of itemtypes?

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list