Bug 7012 - Limit to available does not exclude in-transit items
Summary: Limit to available does not exclude in-transit items
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching (show other bugs)
Version: master
Hardware: All All
: P5 - low normal with 30 votes (vote)
Assignee: Galen Charlton
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-12 13:43 UTC by Nicole C. Engard
Modified: 2024-01-11 09:54 UTC (History)
10 users (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 Nicole C. Engard 2011-10-12 13:43:46 UTC
When I limit to only available items in the OPAC it doesn't appear to be limiting anymore.
Comment 1 Nicole C. Engard 2011-10-12 14:17:45 UTC
Actually it does work, but 'in transit' is considered 'available' why is that? should it be? I would think available is on the shelf.

Nicole
Comment 2 Owen Leonard 2011-10-12 14:44:48 UTC
(In reply to comment #1)
> Actually it does work, but 'in transit' is considered 'available' why is that?

Especially since the staff client considers "in transit" to be /unavailable/ with regard to placing holds from the search results page.
Comment 3 Karl Holten 2015-12-10 20:50:54 UTC
(In reply to Owen Leonard from comment #2)
> (In reply to comment #1)
> > Actually it does work, but 'in transit' is considered 'available' why is that?
> 
> Especially since the staff client considers "in transit" to be /unavailable/
> with regard to placing holds from the search results page.

This is the main reason we reported it as a bug- so that students at our univerities wouldn't get confused when they tried either placing a hold or finding the material on the shelves and it wasn't available.
Comment 4 Daniel Gaghan 2019-04-09 15:49:47 UTC
We at PCCLD are seeing this error on 18.05 and it's causing some headaches amongst our staff.
Comment 5 Daniel Gaghan 2019-12-02 18:30:31 UTC
It looks like this issue is also listing items that are on hold as available in addition to in-transit. Does anyone know if this was a recent change or did it originally include on hold items?
Comment 6 Carolyn Hughesman 2022-11-28 17:27:34 UTC
Hoping to revive this bug.  On the search results page in the staff interface, items are still counted as available both when they are in transit and sitting on the holds shelf.

This is confusing to our staff.  Items should only be listed as available if they are physically on the shelf.
Comment 7 Katrin Fischer 2022-11-28 20:16:56 UTC
Just to explain why this is not as easy of a fix as it might sound:

The information if an item is on hold or in transfer is only found in the reserves table right now. it's not part of the item records. 

In order to be able to exclude these from the availability search, the information needs to be made available to the search engines. 

This means: The information needs to be added to the records, for example into otherwise unused MARC fields at the time of indexing. And every time a hold changed status, we'd need to automatically trigger reindexing of the record.

At the moment the filter only looks at information in the item record already.
Comment 8 Benjamin Daeuber 2022-11-30 14:00:05 UTC
(In reply to Katrin Fischer from comment #7)

> At the moment the filter only looks at information in the item record
> already.

Is performance the reason Koha can't also check the reserves table? Is this something that can (or has?) been addressed with elastic search? 

We're willing to pitch in funds if a solution is possible.
Comment 9 Katrin Fischer 2022-11-30 18:54:23 UTC
(In reply to Benjamin Daeuber from comment #8)
> (In reply to Katrin Fischer from comment #7)
> 
> > At the moment the filter only looks at information in the item record
> > already.
> 
> Is performance the reason Koha can't also check the reserves table? Is this
> something that can (or has?) been addressed with elastic search? 
> 
> We're willing to pitch in funds if a solution is possible.

Elasticsearch and Zebra both index MARC. So bibliographic records and items.

Information from reserves is not part of the data that we push to the search engines for indexing at the moment.

So we would need to do that AND then make sure everytime a hold changes in any way, the record gets reindexed with updated information.

I was just trying to explain why this isn't just about changing the search query used. The data is currently not available for searching in the first place.
Comment 10 Katrin Fischer 2022-11-30 18:56:45 UTC
you could change to "Seeking cosponsors" if you wanted - also people from bug 5463 could be interested. It's mostly the same issue.

Hm, actually it depends. transfers can also be in branchtransfers... so maybe we'd need both info from reserves and branchtransfers.
Comment 11 Christopher Brannon 2023-03-22 19:11:13 UTC
I am hoping this feature will get some much needed attention.  It has been unreliable for way too long.