Re: [Koha] transfers to receive- checking in books: more info
Hello again, I have more info. Just now, when canceling transfers as described below, I saw that the fields for "home library" and "holding library" were slightly different. One says "Cary" and the other says "CARY". I should mention that only the books that I checked in that have the lower case "Cary" as home library end up in the 'transfers to receive' queue. When I look at these records in the OPAC I don't see differences between them - they all have thefull name of our institution (Cary Institute Library) listed as home and current holding library. I just looked in global sys preferences > libraries and see that there is only one library, Cary Institute Library, code CARY indicated here. So I am not sure where lower case 'Cary' is coming from, or how to merge or get rid of it without really messing things up. Any help or advice would be appreciated. Thanks again! a On Wed, Jul 29, 2015 at 12:00 PM, Amy Schuler <schulera@caryinstitute.org> wrote:
Hi, if this message looks familiar it's because I posted it originally back in 2013, but got no response. I am still having the same problem.
An annoying thing is occurring when I check in an item in the circulation module. After I check in as usual, the status becomes "In transit from Cary Institute Library, to , since . " Then I have to go into Transfers to Receive and cancel the transfer for that item before it will display as available for loan in the OPAC record.
Any tips or advice? I searched bugs and didn't find anything about this.
We use Koha 3.18.06.000 (Linux ubuntu).
Hope you can help. thanks!
Amy Schuler schulera@caryinstitute.org
Amy Schuler schreef op wo 29-07-2015 om 12:44 [-0400]:
I just looked in global sys preferences > libraries and see that there is only one library, Cary Institute Library, code CARY indicated here. So I am not sure where lower case 'Cary' is coming from, or how to merge or get rid of it without really messing things up.
The quick way to check is to look directly in the database, that way you know you're seeing things without being filtered by Koha first. For example, see what distinct home library codes your items actually have: SELECT distinct(homebranch) FROM items; (replace with holdingbranch to get the current location.) If you have more than one result here, then somehow you've ended up with strange data in there somehow, and you can go from there to work out what items are affected. In the results, pay attention to case (it should be case sensitive, so any difference in capitalisation is a different result), and the possibility of leading/trailing spaces, which will also count as a different result. If this doesn't give you a place to start, do some experiments, for example pick on an item and get all its fields: SELECT * FROM items WHERE itemnumber=<<itemnumber>>; do the things that cause it to change, and compare what the results are afterwards. If you do this, rigorously document everything otherwise it's probably going to not be useful. Also, have a look in the branches table: SELECT * FROM branches; to see what's actually defined there. In theory, you shouldn't be able to have an item that has a home/holdingbranch that isn't in there, but in practice there are ways that can cause the rules to get broken. One thing your email didn't say was whether this occurs all the time, or whether it's only on certain items. This should let you see where the funky data might be coming from, once you can see what the incorrect case is, fixing it should be a lot easier. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
participants (2)
-
Amy Schuler -
Robin Sheat