Bug 29584 - autoBarcode generates a fifteen-digit number in the unit catalog instead of EAN13
Summary: autoBarcode generates a fifteen-digit number in the unit catalog instead of E...
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 21.05
Hardware: All All
: P5 - low minor
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-28 11:28 UTC by Pavel Bédi
Modified: 2022-12-12 21:23 UTC (History)
1 user (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Bédi 2021-11-28 11:28:21 UTC
I have Koha 21.05.05.003. I have autoBarcode in Administration set to Barcodes are incremental EAN-13 barcodes. Previously, this generated a EAN13 number correctly for my units. Now I get a number like, for example: 977233613400114 - There are extra zeros I guess.
Comment 1 Katrin Fischer 2022-02-26 22:55:47 UTC
Hi Pavel, the autobarcode feature always looks at what is already in your database in terms of the highest used number so far.

So for example if someone added a barcode manually that is odd/very long, this could set off the calculation. Maybe check if there is anything unusual with your existing barcodes.
Comment 2 Pavel Bédi 2022-02-27 08:52:42 UTC
(In reply to Katrin Fischer from comment #1)
> Hi Pavel, the autobarcode feature always looks at what is already in your
> database in terms of the highest used number so far.
> 
> So for example if someone added a barcode manually that is odd/very long,
> this could set off the calculation. Maybe check if there is anything unusual
> with your existing barcodes.

Yes. You are right. Sorry.
Comment 3 Katrin Fischer 2022-02-27 10:31:43 UTC
No need to be sorry! Glad we could resolve this.