[Bug 12348] New: unique barcodes should be mandatory
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12348 Bug ID: 12348 Summary: unique barcodes should be mandatory Change sponsored?: --- Product: Koha Version: 3.14 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs@lists.koha-community.org Reporter: barton@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle.m.hall@gmail.com Partner has an item that shows 'check-in failed' in the 'Check-in' column in circulation.pl. When the item is brought up in holdings, there is no link to click on to allow editing. All library interaction with items (check-in, check-out, item edit) require bar codes, but there are no integrity checks in Koha (in the database or perl code) to ensure that all items must have barcodes. This leads to support issues when partners create items that do not have barcodes, then cannot do anything with them. Ideally, I would think that items.barcode should be defined as `barcode` varchar(20) NOT NULL If this isn't possible for historical reasons, then an effort should be made to deprecate the practice of allowing NULL barcodes by emitting obnoxious warning messages stating that NULL bar codes will not be allowed in future versions of Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12348 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hi Barton, I disagree here. I think the bug here is not that the item has no barcode, but that it seems to cause problems for you. We use items without barcodes when there is not really an item, like when the library wants to add items for electronic resources or 'bound with' items, where only one item exists, but other items on other records link to the real one. There are also libraries that have no barcodes on migration and add barcodes as the items are checked out for the first time. We also have introduced a new feature just one version ago to make it possible to check out items without barcodes: itemBarcodeFallbackSearch If you want to prevent libraries from adding items without barcodes, an option could be to make the subfield mandatory in all frameworks. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12348 Magnus Enger <magnus@enger.priv.no> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED CC| |magnus@enger.priv.no --- Comment #2 from Magnus Enger <magnus@enger.priv.no> --- I agree with Katrin. Because of itemBarcodeFallbackSearch, we cannot force barcodes to be NOT NULL. This should be ficed in the frameworks instead. Marking as RECOLVED WONTFIX. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org