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

[bugzilla-daemon at bugs.koha-community.org]

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

--- Comment #61 from emjhet at pa.net ---
(In reply to Katrin Fischer from comment #60)

> The biblionumber is not a sequentially created number of the application,
> but it's the primary key assigned by the database. That's why it will only
> be set after saving a record for the first time - before it doesn't exist.
> 

I understand the purpose of the biblionumber. It is what MARC says the field
001 is for. I am trying to understand why Koha chose to use the 999$c for this
information instead of the 001, and the implications this decision has on our
library.

Although it is not good cataloging practice, Koha recommends importing a
"close" record if you can not find a matching record in your Z39.50 search.
Then simply alter the record as needed. This has happened at the library where
I work. However, the 001 field was not changed. Often these records were
imported from our state union catalog. Because Koha does not create a unique
001, these records would be for different items but have the same 001, and our
holdings would likely be attached to the wrong record. Thus we could receive
requests for items that we do not, in fact, own.

Thus this matter is not merely academic for us.

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