Bug 23439 - Barcode number with serveral users
Summary: Barcode number with serveral users
Status: RESOLVED DUPLICATE of bug 32896
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 19.05
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-08 13:01 UTC by lmr
Modified: 2023-10-08 12:11 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
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 lmr 2019-08-08 13:01:36 UTC
Hello, everybody,

When two or more users are trying to add a new item, the barcode field get the same numnber, so when they save the item and with have an error.

This is happing since 19.05.

Now only just one user can add item.

Any help?
Comment 1 Katrin Fischer 2019-08-10 20:35:10 UTC
I am not sure if this is really a regression. As far as I know the barcode with AutoBarcode is filled into the input field looking up the highest existing value in the database. So if multiple people open an item form they will get the same number and the first one to save will 'win'.

If you get the duplicate barcode message... can you empty out the barcode and generate the next one clicking on the ... next to the field? I think this should work and allow saving.
Comment 2 George Veranis 2022-08-31 10:42:46 UTC
Would be helpful if you have a notice message that also someone else also edit that item ?
Comment 3 Katrin Fischer 2022-09-07 17:52:07 UTC
(In reply to George Veranis from comment #2)
> Would be helpful if you have a notice message that also someone else also
> edit that item ?

You get a message that the barcode is already used in the case described here. This bug is about multiple users adding new items, I think yours would be a different bug about locking item editing when someone already edits it. Unfortunately, that's not so easy to do. If you want, you could file a separate bug.
Comment 4 Katrin Fischer 2023-10-08 12:11:01 UTC

*** This bug has been marked as a duplicate of bug 32896 ***