Reports of slowness in circulation - update
***March 9, 2010 update*** Thanks to everyone who has been sending in examples of slowness. We're pretty sure that the problem is related to patron holds, and we'll be working with Innovative to see if we can resolve this problem. No need to send in further examples, unless they seem to be related to patrons without holds.
Over the past week, we've had several reports of slowness in Circulation. The slowness doesn't seem to be happening at any particular time of day, and it doesn't seem to be consistent. We've called Innovative several times, but they've not seen any problems with server functions.
One library has reported that it seems to be more of a problem when patrons have higher holds, and we've seen this happening too. So we're asking Innovative to do an intensive data integrity check tonight. We should know by Monday if this finds any problems. If not, we'll keep working on it.
In the meantime, if you are experiencing slowness, please let us know as soon as possible. It would be helpful to know exactly when it happened, what you were doing, and the patron barcode.
-Gerri
Over the past week, we've had several reports of slowness in Circulation. The slowness doesn't seem to be happening at any particular time of day, and it doesn't seem to be consistent. We've called Innovative several times, but they've not seen any problems with server functions.
One library has reported that it seems to be more of a problem when patrons have higher holds, and we've seen this happening too. So we're asking Innovative to do an intensive data integrity check tonight. We should know by Monday if this finds any problems. If not, we'll keep working on it.
In the meantime, if you are experiencing slowness, please let us know as soon as possible. It would be helpful to know exactly when it happened, what you were doing, and the patron barcode.
-Gerri
