Bug 24307 - Allow loose item matching for on-order items
Summary: Allow loose item matching for on-order items
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-26 15:25 UTC by Andrew Fuerste-Henry
Modified: 2023-09-16 13:40 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 Andrew Fuerste-Henry 2019-12-26 15:25:30 UTC
We run into this issue with libraries who are not using EDI, get their items pre-processed by a vendor, and want on-order items to show in the catalog:
- MARC records are imported for on-order titles
- On-order items are created
- Vendor sends final MARC records including 952 tags with barcode, ccode, location, etc
- Final records match to existing records at the bib level, but cannot match at the item level
- Item records need to be manually touched either to add final details to on-order items or to delete on-order items in favor of newly-created final items

The vendor cannot give a barcode number when supplying on-order records and (without EDI) Koha doesn't have a way to send the on-order item numbers to the vendor to be included in the final item info.

I'm imagining something like a syspref that lets us say "if an item has notforloan of [X], then allow item overlay without matching an itemnumber or barcode." But as I type that I suspect there are a lot of ways it could go bad.
Comment 1 Katrin Fischer 2019-12-29 14:14:59 UTC
I think this is worth thinking it over some more. Maybe it could work like this:
- match not-for-loan = on order
- match home or holding branch if possible
- match itemtype if possible...

So it tries to find the best match and falls back to the next best?
Comment 2 Sara Brown 2022-01-27 21:58:04 UTC
Maybe there could be 'Item matching rules' similar to what exists for bibs - a notforloan status picker could be built in, plus options to set whatever other criteria a library wanted to use.