https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27981
Nick Clemens <n...@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off --- Comment #15 from Nick Clemens <n...@bywatersolutions.com> --- (In reply to Marcel de Rooy from comment #14) > + unless($record->field('001')){ > + $record->insert_fields_ordered(MARC::Field->new('001', > $biblionumber)); > + }elsif($record->field('001')->data() eq 'biblionumber'){ > + $record->field('001')->update($biblionumber); > + } > > Please explain. > Why do you test eq 'biblionumber' ?? > Why not always overwrite 001 with $biblionumber if the pref is set ? Similar to autobarcode or automembernum - we will default, but if you force a new value we let it stand - I think allowing the librarian to force a different number allows for collections that fall outside the norm. It could be useful for an OAI set for instance -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://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/