Woodruff Library MARKING - SpineOMatic weirdness and how to fix it
I encountered some weirdness with SpineOMatic on 6 June 2016. It was discovered that 240 barcodes were scanned into SpineOMatic (in batch print mode), and they all show as being in the batch, but only 202 labels actually printed. The printing stopped at a record that was missing a call number. The record was fully cataloged, except for not having a call number in the Holding record, so SpineOMatic was able to find the record in Alma by searching the barcode number, but no call number was found.
This missing call number appears as a gap in the batch log that you can scroll through. Any call numbers that were scanned after the item that does not have a call number do not appear in the Preview/print window.
There is a solution. Each batch used in SpineOMatic is saved a .txt file on the computer's hard drive. To correct this problem, you will need to edit the text file of the SpineOMatic batch to remove the problem lines of text; save the text file and then the entire batch will print correctly. The sets of double lines plus the gap where the call number should be act as stop characters in SpineOMatic and something in the coding won't allow anything after that to appear.
The latest pdf version of this can be found at: F:\Tech Services\New - Teams and WGs\ABM\Marking\marking documentation files
Original Problem
This item was cataloged, but a call number was not entered into the Holding record.
- The problem record shows in the list of items in the batch as a gap between two sets of double lines.
- You can see that there are currently 240 items in this batch.
- Take note of the batch # that you are using.
When you view the Preview/print screen, none of the items scanned after the problem book appear on the screen, even though they show in the list of items on the batch.
Close SpineOMatic.
- Click on Start
- Click on This PC.
How to fix the problem - Option 2
- In the left sidebar, under This PC, click on OS Disk (C:)
- Double click to open the SpineOMatic folder.
- Find the text file for the batch that you are using (Batch #3 translates to labelbatch3.txt). Double click to open the file in Notepad.
All of the items scanned will appear, with a double dashed line between each item.
Scroll down to find where the problem book is located.
- Delete the empty lines and one set of the double lines. There should be no blank lines between the double line and the next call number.
- Click on File
- Navigate to Save.
When you are finished, close the batch using the x in the upper right corner.
Now, return to SpineOMatic to look at the batch, you will see that
- There are now 239 entries (instead of 240)
- The problem book is no longer visible in the list. If the number of Entries in the batch still chows the original number, try changing to one of the other batches and then returning to the batch that had the problem, to see if it shows the new number of entries.
When you look at the Preview/print screen, all of the items scanned (before and after the problem book), will now appear, and you can print the new batch as normal.
The problem book would need to be pulled from the cart, to be sent back to the cataloger for corrections, and you would want to make a note of the barcode number so that it can deleted from the txt file that will be generated to run the API that removes the work orders from the items.
20 May 2020 version
0 Comments
Add your comment