https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9921
--- Comment #60 from Katrin Fischer <[email protected]> --- > 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. 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 strongly advise against trying to change the configuration to use 001 instead, because the indexing won't match and you will get a lot of hard to fix problems. Indexing relies on the biblionumber to be in 999$c and you can't map 2 fields at the time (so duplicating won't work). -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
