[Koha-bugs] [Bug 9921] Make it possible to force 001 = biblionumber

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Wed Jul 18 20:41:37 CEST 2018


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9921

--- Comment #63 from emjhet at pa.net ---
(In reply to Katrin Fischer from comment #62)
> I understand, just trying to prevent you from doing something that might
> break stuff (because people have gone there before). I can't tell you why
> for Koha 999c was chosen in the beginning, but it's one of the things that
> will need quite a bit of thinking if we wanted to change it now.
> 
> I think here are patches around to make a plugin to set 001 individually. I
> am using a variation of the stocknumberAV plugin in one of our libraries to
> create numbers, but you have to trigger it and it doesn't move the number to
> 035 as they only do original cataloguing. A catalouging plugin might be a
> route to explore.

Katrin -- Thank you so much for responding. I'm a cataloger among
non-catalogers and I am just trying to make things as easy as possible for my
co-workers while following standard guidelines for minimum level cataloging. 

Unless I have a plug-in for the 001 and permit it to be filled in with a click
of the mouse, I will not be able to convince anyone to spend the time on it.
Some of our libraries are completely one-"man" operations.

Koha deviates in several significant ways from the ILS that I am accustom to,
including not having a good way to run reports requesting specific MARC fields.
Am I correct that I can run a report and find out how many records have a
specific MARC field, but the only way to find out the content of the field in a
report is to have the MARC field mapped to an authorized value?

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


More information about the Koha-bugs mailing list