[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 #59 from emjhet at pa.net ---
(In reply to paxed from comment #58)
> 
> 001 alone does not guarantee uniqueness. 001 and 003 together should be
> globally unique. If 001 is changed, then 003 should be changed to match the
> org code of the system.

Indeed. That is why I referred to the original post. But as Koha has a plugin
that can be used in the 003, this field does not present a hurdle for use of
that MARC field as designed. 

The other Integrated Library Systems I have worked with did not overlay data in
the 003 field. Usually, information in that field was also automatically
transferred to the 035. Also automatically, a new number that was relevant to
our system was generated for the 001 and our institutional code was put into
the 003 field. 

Indeed, there is TRULY nothing globally unique to the 999$c. If a Koha system
permitted another Koha system to import a record in which the 999$c overlays,
there is no "003" field to designate which institution the "unique identifier"
belongs. 

This came up because I am trying to create Frameworks for my co-workers that
are not trained in cataloging but yet have to catalog. It didn't make sense
that some of our records did not have anything in the 001 field, as I was
taught that this field was essential. So I am simply trying to understand
how/why Koha differs so much from the other ILS I have used in the past and
from MARC 21 in general.

Thus, I am wondering what it is about the 999$c that permits an auto-generated
unique identifier to be created when it can not be created in the 001, and if
anything can be done to either duplicate the 999$c into the 001 or use the 001
instead of the 999$c.

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