[Koha-bugs] [Bug 20070] autoBarcode Increment Value

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20070

Jonathan Druart <jonathan.druart at bugs.koha-community.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #3 from Jonathan Druart <jonathan.druart at bugs.koha-community.org> ---
Confirmed, it certainly comes from that line:

108     $head =~ s/\d{4}$//; # else strip the old yymm
in C4::Barcodes::hbyymmincr::process_head

This value of autoBarcode is deprecated and should not be used.

Take a look at the notice in the bottom of the file:

"""
This format is deprecated and SHOULD NOT BE USED.

It is fairly clear the originator of the format did not intend to accommodate
multiple branch libraries, given that the format caps the available namespace
to
10,000 barcodes per year TOTAL...

Also, the question of what to do with an item that changes branch is
unsettled...
Nothing prevents the barcode from working fine, but it will look out of place
with the old branchcode in it.  Rebarcoding a single item is trivial, but if
you
consider the scenario of branches being consolidated, it is an unnecessary.
burden to force the rebarcoding of thousands of items, especially when the
format
will limit you to under 10,000 on the year!

The main purpose of the format seems to be to get the branch code into the
barcode.
This is wholly unnecessary, since the barcodes can be printed with the
branchcode
directly on it, without it being part of the barcode itself...

The API for this module should exist almost exclusively through C4::Barcodes...
One novel aspect of this format is the fact that the barcode is tied to a
branch...
"""

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