http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7911
Ian Walls <koha.sek...@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |In Discussion See Also| |http://bugs.koha-community. | |org/bugzilla3/show_bug.cgi? | |id=7676 --- Comment #1 from Ian Walls <koha.sek...@gmail.com> --- Having more barcode options is definitely a good thing. I would recommend, however, we abstract this another level, and create barcode namespaces. These namespaces would live in their own database table, with a unique code, and the user could create as many as they need. Each namespace would be composed of several kinds of tokens: - plain text: universal constants across the entire namespace. Easy stuff. - items.*: meta token to retrieve the code from any of the items database fields. Most useful for core data like homebranch, itype, ccode, stocknumber, etc - alternate branch code: a new field to the branches table that let's libraries specify another identifier code. This would satisfy bug 7676. - auto-increment numbers: token for an integer that auto-increases by a specified value (default 1) for each new material in the namespace. A length limiter would also need to be applied, as well as whether to zero-pad or not. - date: token for the date acquired, formatted using standard d,D,m,M,y,Y syntax - checksum: a token to calculate a checksum of the rest of the namespace. the type of checksum calculation would need to be specified (and a plugin for that calculation added to the codebase) Other tokens as required, but I think this would cover most of our cases. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org 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/