When making a request from the ARS using a web browser and the III Snoopy Interface, errors may occur. Perhaps someone else made a request for the same item you were looking to request? Maybe the item is being reviewed by another patron, but not checked out? Perhaps the item was recently checked back in, but has not been returned to the ARS for storage? Many errors are possible. Known errors are documented here.
If you would like to see the kinds of errors that may come up, and understand what they mean, try reading below. Numbers on the left correspond to the error number often printed in the Snoopy web session when there is a problem.
Error Number: |
Notice sent to patron: |
HK Systems Message: |
Mike's Description: |
000 |
No errors (000) [users should never see this message] |
000-request completion (no errors) |
When programmers design functions, algorithms, or programs which share information or communicate, they often include some way to have them also show they were able to complete their task without error. This is just the most common and simple error message even though this is not a true error for the non-programmer. |
001 |
Item has already been requested. Please check at the Circulation Desk on the first floor to see if it is available. (001) |
001-item has been committed to a request |
The ARS uses a modified FIFO based que to order requests. (FIFO just means, First In, First Out.) Many requests may be made to the ARS every minute. Requests can be placed in the que faster than they can be picked from the system and sent via the ETV. If an item is requested to be picked by one person, and the item has not yet been picked from the ARS, and a new request for the same item is attempted before the first request is picked, then this is the resulting error message for the second, third and future requests for the item while the item has not yet been picked for the first pick request.
This error message can be duplicated by placing a request for an ARS stored item, and then very quickly attempting to place a second request for the same item before library employees are able to pick the item from the ARS. |
002 |
Item has already been requested. Please check at the Circulation Desk on the first floor to see if it is available. (002) |
002-item has been checked out |
After a pick request is completed in the ARS chamber, the status of the item in the ARS database is set to be checked out of the ARS system, but this says nothing about being checked out with the library system by a patron. This message will appear when an item is requested from the ARS, and then picked and then a new attempt is made for the same item to be picked from the ARS.
To duplicate this, make a pick request from the ARS, and after it arrives at the circulation desk for pickup, try to make another ARS request for the same exact item before you check it out with your borrowing/lending/library card. |
003 |
This item is not in the ARS. Please check the shelves or ask for assistance at the Circulation Desk on the first floor. (003) |
003-item is not in the ASRS database |
This is a book keeping and database synchronization problem, and should not come up. However, it eventually will come up as humans can make mistakes. We have 2 separate databases running on two separate machines. One runs on the III or Snoopy system and the other one runs on the ARS Manager. The III or Snoopy system keeps track of all library items. The ARS Manager only keeps track of items that should be stored in the ARS for the long term. If the III or Snoopy system thinks an item is stored in the ARS, it will allow the patron to place a pick request for that item from the ARS. When the III or Snoopy system tries to request an item that is not in the ARS Database, but shows up in the III or Snoopy system as belonging to the ARS, this is the error message.
To duplicate this error, change the location field of a record to be an ARS stored item, and then delete the item record in the the ARS Manager if it exists in the ARS Manager. |
004 |
This item is not available. You may request it through Interlibrary Loan. (004) |
004-item is missing |
The ARS Manager keeps track of items by Aisle, Row, Bay, and Tier for each bin, and also uses a sector location for each bin. During slower periods, library employees may incrementally audit parts of the ARS bin by bin. During an audit, the employee scans each item in each sector sector by sector until all of the items in all of the sectors are scanned. If the ARS Manager notices that an item in a particular sector is not scanned when the library employee claims to be done with a sector, then the employee has another chance to find the item. The ARS Manager will at this point tell the employee the name of the item to find and the bar code. If the employee is still unable to find the item, then the employee may mark the item in the ARS Manager as "Missing". When a pick request is made for such an item, then this error message will result.
To duplicate this error, force an item to be missing in the ARS Manager, and then place a pick request for that item from the III or Snoopy system.
|
005 |
Item has already been requested. Please check at the Circulation Desk on the first floor to see if it is available. (005) |
005-item has not been returned |
When a patron makes a pick request for an item from the ARS, and then checks it out, the III system notes this. When the item is checked back into the III System at circulation, then the III system notices the item should be stored in the ARS and lets the ARS Manager know that this item is to be "EXPECTED". However, while the item is in a kind of limbo (stuck between being checked back in, but not quite in the ARS) this error message will appear when a pick request is made from the III or Snoopy system for the item while in this "EXPECTED" limbo state.
To duplicate this error, place a pick request for an item from the ARS, pick up the item, check it out, check it back in and then try to make a pick request for the item from the ARS before it is stored in the ARS.
|
006 |
This item is not available. You may request it through Interlibrary Loan. (006) |
006-item has bad item code |
*** (Will need to verify this) If a request for an item with a bar code that is the incorrect length, or a bar code that does not pass the bar code CRC value, then this error message is returned. As long as all bar coded items stored in the ARS use the same bar code system and length as is currently in use, this error message should never come up.
You should not need to duplicate this error message. Contact the Systems Department if a test for this is really needed. |
007 |
This item is available. (007) [users should never see this message] |
007-item is available |
As items are stored in the ARS, the ARS notifies the III or Snoopy system on the availability of the item. Presently, I think the III system does nothing with this value for ARS reported items. However, the III or Snoopy system may ask if an item is available when the user clicks to make a pick request for an item from the ARS.
You should not need to see this error message. Contact the library systems department if it is really needed.
|
010 |
This item is not in the ARS. Please check the shelves or ask for assistance at the Circulation Desk on the first floor. (010) |
010-item has been deleted from ASRS database |
*** (Will need to verify this) When an item is deleted from the ARS, the ARS notifies the III System that the item was deleted so the III Server may change the location status seen by patrons. I think the III System does not allow the ARS to change the location status in the III Database with this notice, so the III System just ignores this.
To generate this message, ask the ARS Manager to delete an item. The III Communications log will show the message come through.
|
011 |
This item is not available. You may request it through Interlibrary Loan. (011) |
011-item has bad item status |
*** (Will need to verify this) If the ARS Item Status does not jive with other information in the ARS database, or the III Server offers the ARS Manager a bad status message, this is the result.
You should not need to duplicate this message. If you need to see it, please contact the systems department.
|
012 |
Please ask for assistance at the Circulation Desk on the first floor. (012) |
012-item is in Locked location |
In some cases, we may encounter a problem with a bin being damaged, or the crane may have serious difficulties in requesting a bin from a specific location. In these cases, we may choose to lock a bin location. Presently, the only locked bins are locks for administrative reasons and are either empty or have special non-circulation or non-public documents. (These include system manuals and other parts that nobody should ever request. |
013 |
The system is having difficulty retrieving this item. Please ask for assistance at the Circulation Desk. (013) |
013-item is stored in a bad location |
Every item has a location field that references a bin coordinate that includes Aisle, Row, Bay, Tier and sector. If for some reason, an impossible location is specified i the ARS Manager, then this error is the result. (This should never happen unless there is serious database corruption, or manual editing of the ARS Manager database leads to bad locations being used.
You should not need to duplicate this message. Contact the systems department if you have questions. |
014 |
Item has already been requested. Please check at the Circulation Desk on the first floor to see if it is available. (014) |
014-item has a duplicate pick request |
*** (Will need to verify this) I am not sure how this will work. I think this might be a case where an item is request again with the same sequence number. This would be a sign of a problem in the III Server or Snoopy system.
You should not need to duplicate this. If you need to duplicate this, contact the Systems Department. |
015 |
Please check the shelves or ask for assistance at the Circulation Desk on the first floor. (015) |
015-item is delete pending |
*** (Will need to verify this) The III Server may choose to add or delete items from the ARS Manager. If the III System is asked to delete an item from the ARS Manager, then the ARS Manager cannot just delete the item from its database. If it did, the item would be forever lost in an unknown bin! Instead, a delete request is translated into a pick request. However, when the pick request is completed, then the ARS Manager then deletes the item from its database. Between the time that the item is picked after a delete is requested and the time the delete request was actually made, the item is marked as "deleted" so it cannot be picked from the ARS by a patron. |
999 |
Your request cannot be processed at this time. Please ask a library
staff member for help. Or try again later. (999) |
999-item status unknown |
*** (Will need to verify this) |
BAD- |
Your request cannot be processed at this time. Please ask a library staff member for help. Or try again later. (BAD) |
BAD- |
*** (Will need to verify this) This is likely to be an error that the III System cannot figure out. |