http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7676
--- Comment #8 from Ian Walls <[email protected]> --- Having this toggle between branches would be a huge pain, since so many different workflows and contexts involve barcode scanning. It would also place the burden on the librarian to know a) this book is from another library and b) there could be a conflict. What needs to happen, I think, is a kind of "did you mean" screen for when barcode scans come back with more than one result (or perhaps even in no results cases...). This would include the full barcode, with the scanned value highlighted some how (to explain why this is in the list), the branch, and the title/author/callnumber (some kind of distinguishing feature). Chances are, the two conflicting barcodes are not going to belong to the same title, unless we're in an even more convoluted situation than originally imagined. What I'd like to see, though, is more than just item and patron barcode prefixes and lengths, a full Barcode Namespace setup, where multiple parts can be identified. This way, whatever barcoding schema is in use, be it prefixed, length controlled, check digited, or otherwise delineated, Koha could handle it. -- 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/
