Please be aware, last night we countered another abnormal ADUText report, which handles our daily record maintenance and processing. This previously occurred last Wednesday, 6/23/2021.
We may encounter record issues throughout the day until SirsiDynix is able to repair the affected records. These issues will most likely impact records that were added/deleted/updated yesterday and are typically in the form of “heading keys need to be indexed” errors in WorkFlows. You may see these errors when searching, modifying, or checking in/out the impacted records. You also may not be able to search certain records via WorkFlows. A workaround for the record searching issue is posted below.
We’ve escalated this issue to SirsiDynix Support. If you come across affected records, please email a list to help@swanlibraries.net and we’ll forward them to SirsiDynix for further investigation and temporary correction.
We'll post additional updates to this Known Issue as new information becomes available.
Temporary Workaround
We have found a workaround for those of you who are receiving “Heading not found” or “Heading keys need to be indexed”. Records with this error are searchable by Title Control Number. You can retrieve the Title Control Number with the following steps. It seems many of you are searching by item barcode, so these steps use that as an example:
- Perform a keyword search in Enterprise for the item barcode. (Or search by title, author, etc.)
- Click on the title in the search result to see the detail view.
-
In the URL of your browser, look for the portion that says "SD_ILS:" and a number. This is the catalog key of the record.
- The Title Control Number is simply an 'a' followed by this number. In this example: a2954604
- Perform a Title Control Number search in WorkFlows, and the record should come up.
Once you have retrieved the record in WorkFlows, making any change to the bibliographic record or any attached call number or item should push the record through dynamic indexing so it will be searchable by normal means for you and other SWAN members.
Of course this method only works for records that have had time to be indexed by Enterprise. We cannot guarantee it will work for every item.
