Bug 35886 - FindDuplicate only checks first ISBN
Summary: FindDuplicate only checks first ISBN
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-23 20:56 UTC by Caroline Cyr La Rose
Modified: 2024-03-05 17:52 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Caroline Cyr La Rose 2024-01-23 20:56:53 UTC
When ordering a title via z39.50, the duplicate match is only done on the first ISBN. This can lead to duplicates being ordered and created.

To recreate:
1. Have a record that you can find via z39.50
2. Copy the ISBN
3. In Acquisitions, create a basket
4. Add to basket from an external source
5. Using the copied ISBN, search a z39.50 source
6. Click the result and click Order
--> It should warn for a duplicate

7. Click Cancel
8. Edit the record, add a second ISBN
9. Redo steps 4-6
--> It should warn for a duplicate

10. Click Cancel
11. Edit the record, place the second ISBN in first position
12. Redo steps 4-6
--> No duplicate warning!

Note: if you cancel after step 12, the duplicate record will have been created. You will need to search your catalog and delete the record to redo the tests.

I don't know if that is only in the case of z39.50 or if other types of orders also have that same problem.
Comment 1 Caroline Cyr La Rose 2024-01-23 20:58:22 UTC
I don't know if this is the same problem as bug 27278
Comment 2 Katrin Fischer 2024-01-28 14:28:19 UTC
Hi Caroline,

I am wondering about this one, because I thought we had taken care of it with:
Bug 31471 - Duplicate check in cataloguing fails with Elasticsearch for records with multiple ISBN

Could you verify the version and search engine you are seeing this with?