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

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Wed Jun 19 16:57:26 CEST 2013


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

M. de Rooy <m.de.rooy at rijksmuseum.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Needs Signoff               |Failed QA

--- Comment #33 from M. de Rooy <m.de.rooy at rijksmuseum.nl> ---
Still some comments, but we are coming further :) Thanks for your patience..

When editing an existing record, I would prefer not to change the biblionumber
in the 001 by a string again when receiving focus. Currently, you overwrite and
save the string in the record.
Since you only changed AddBiblio and not ModBiblio, this is permanent.
Same for incremental.
Please combine your code for AddBiblio and ModBiblio.

Also when I would incidentally change biblionumber by deleting a char or so, I
would loose my biblionumber or incremental.
Consider adding the focus action to Blur?
Consider blocking edit in this input field via your javascript?

I am not yet fully sure if your incremental update will hold under concurrent
use.
If between your fetch with preference and the next execute, someone else does
an earlier execute, you could have double numbers? 
Need some way of locking or transaction?

Updatedatabase
Need a print statement if someone already has a plugin for 001? Maybe they can
consider your new plugin?
I am wondering if it is dangerous to set the plugin for one framework and not
for another (could be the case)?

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


More information about the Koha-bugs mailing list