Display of circulation status in catalog searches

I have noticed a difference in the circulation status displays that occur when user searches catalog as a general user versus logged in as a system administrator. The “Missing” status does not display for general users when they view search results. The display is “Available”. The same record viewed when logged in as a system administrator correctly shows the status “Missing” in search results. Is there a setting we need to change to show “Missing” or “ In repair” status for general users’ search results?

Thanks for the note! A couple of questions so I can dig further into this, please:

1. Are you logged in as the main admin (GHA.Library user) in TinyCat, when you're seeing the "Missing" status, or as a staff admin user? If the latter, please private message me at kristilabrie and let me know which user you're logged in as.

2. Can you link me to 2-3 records where you're seeing this issue of "Missing" as admin and "Available" as non-admin? If you're seeing certain titles on search pages, please click through to view those detail/book pages and give me a direct link to the record in question, along with your search page URL, so I can look at those records specifically.

Okay, I've verified this, but after testing over a dozen titles, I'm only seeing this issue on one record: An American Beauty ( https://www.librarycat.org/lib/GHA.Library/item/258310979 ).

>1 GHA.Library: Are you seeing this issue on any other record in your library?

I noticed the difference with “in repair” book Herblock right after I changed the status and with American Beauty right after I changed its status. My bad - I did not verify display was different for all the other books with these statuses Now I see that Herblock book shows in repair status as well as the others with these statuses. Is there a delay factor for general users seeing status after it has been changed??

>3 kristilabrie: I see 'Missing' on that link. Almost certainly a delay issue.

>4 GHA.Library: Looks like one of our databases was behind, causing this issue for non-logged in users. We're making some tweaks that should minimize this in the future, but let me know if it crops up again! Thanks for your patience.