[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

emjhet at pa.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |emjhet at pa.net

--- Comment #57 from emjhet at pa.net ---
Like the 2013 thread starter and initial commentator, I believe MARC designates
the 001 field (Control Number) for use to uniquely identify a bibliographic
record. IME the ILS does this automatically with both created and imported
records. (Imported records with data in the 001 field would have that data
automatically transferred into a newly created 035 field.) These unique,
sequential Control Numbers were automatically generated system-wide despite
multiple locations and input from multiple users.
Koha appears to be able to create a unique, auto-generated, sequential
identifier for each bibliographic record despite input from multiple users
through the Koha field 'biblio.biblionumber;' however, it is mapped to the MARC
field 999 subfield 'c.'
It would be preferable to have this unique identifier in the MARC 001 field.
Does the sequence number engine need to be fixed when the biblio.biblionumber
auto-generates a unique sequential identifier already? Is it a matter of
setting up the two fields alike (created upon the record being saved, and being
visible after saving and during editing) so that a unique identifier could
safely be generated in that field? With all the sequential auto-generated
fields used currently by Koha (999$c, 999$d, 952$p), surely there is a way to
auto populate the 001 field. 
If Koha requires that the 999$c field contain a unique identifier, I would find
it preferable if the same identifier be used in the 001 rather than multiple
unique identifiers.

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