March 2010 Archives
This morning, we experienced problems with the Millennium server. We'll be working to determine the full extent of the problems, but right now we know that:
1) There were problems checking items in before around 8:40 AM. We recommend re-checking in any items that were checked in prior to 8:40 AM. If you continue to experience problems checking these items in, please contact Patty at the OWLS office.
2) The notices were delayed. The final notices were not sent until 8 AM. If you checked the notices page prior to this, we'd recommend checking it again to make sure that you've seen all of today's notices.
-Gerri
1) There were problems checking items in before around 8:40 AM. We recommend re-checking in any items that were checked in prior to 8:40 AM. If you continue to experience problems checking these items in, please contact Patty at the OWLS office.
2) The notices were delayed. The final notices were not sent until 8 AM. If you checked the notices page prior to this, we'd recommend checking it again to make sure that you've seen all of today's notices.
-Gerri
*** UPDATE*** As of 11 AM, all of the notices have now been posted, and are available from the notice website. ***
This morning, some notices failed to be posted to the notice website. We're working on fixing the problem. Once all of the notices have been posted, I'll update this message.
-Gerri
This morning, some notices failed to be posted to the notice website. We're working on fixing the problem. Once all of the notices have been posted, I'll update this message.
-Gerri
If you're printing out the OWLSnet Directory, the following page has
changed and should be updated:
*Page 17 NIA Niagara Branch Public Library no longer has a fax number.
*Page 17 NIA Niagara Branch Public Library no longer has a fax number.
As of this afternoon (Tuesday, March 9), the slowness issue in Millennium circulation appears to be resolved.
Thanks to everyone who sent in examples of slowness in Millennium circulation. We received lots of good examples from OWLSnet librarians, listing exactly what happened, with what patron, and when. This was very helpful in troubleshooting the problem. After we provided this information to Innovative, they were able to make a change that fixed the problem.
The problem appeared to be closely related to the holds database. When checking out or adding holds to patron accounts with more than a few holds, the system would pause for several seconds, sometimes as many as 15.
If you have any questions or comments about the issue, or if you continue to experience the problem, please let me know.
-Gerri
Thanks to everyone who sent in examples of slowness in Millennium circulation. We received lots of good examples from OWLSnet librarians, listing exactly what happened, with what patron, and when. This was very helpful in troubleshooting the problem. After we provided this information to Innovative, they were able to make a change that fixed the problem.
The problem appeared to be closely related to the holds database. When checking out or adding holds to patron accounts with more than a few holds, the system would pause for several seconds, sometimes as many as 15.
If you have any questions or comments about the issue, or if you continue to experience the problem, please let me know.
-Gerri
***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
