Comment 4 for bug 596988

Sorry to open this one up again!

We have a sneaking suspicion that some reels are getting the wrong diagnosis. This is the scenario we are concerned about:

1. A reel gets uploaded
2. The processing person comes back to that computer and looks at the uploader
3. At that precise moment the contents of the reel uploaded in step one are being deleted and presents a "no frames" error
4. The processing person deletes this item, causes a redrow, and files a bug, requesting that the item be rescanned
5. Hank comes along and see this redrow. Since the necessary files have been uploaded, he asks the processing person to delete the directory (it's already gone) so he can push the reel along
6. The second upload fails due to "Item already online" message

I think this could be avoided by moving "busy" up on the filter order.
Is there any problem with moving "busy" above "no frames" and under "item (bibliographics) not found on cluster"?