800-222-9711

PA - Quick Requests - Exceptions Report for Quick Requests

More
9 years 9 months ago #54 by joel.henderson
Currently, as you're entering quick requests, if an exception comes up (the patron already has the book on request, you entered a retro RC number as a DB request but there is no DB version yet, too many digits in the book number, etc) you have to deal with the exception before being able to move on entering requests. Some people are not always looking at their screens when they are entering requests, and so they may go on without noticing the requests are not being logged. Also, removing the exception notice requires a tab then enter, or a click on the mouse, moving your hands all over the place instead of keeping them at the keypad. And, after you click OK to get past the exception, the entire contents of the input field is highlighted so if you first hit backspace you end up getting rid of anything, which defeats the purpose of having a prefix set.
All these little things put together make the process of entering requests less quick and more frustrating. Can you develop instead an exceptions list that pops up when you finish entering all the requests that lists the ones that could not go through. It'd be kinda like the alerts in the new OPAC, but instead of each one popping up in the middle of the process they all pop up in the end. That way you can deal with them all at once, and they don't break the flow of requests entered correctly. This feature would be especially helpful when entering requests from phone messages, since the person keeps talking but staff have to stop and deal with the exception notice.

Please Log in to join the conversation.

More
9 years 5 months ago #74 by Mitake
The main problem is that the error situation is being presented because a record cannot be created, so there would be nothing to "report" on when the entry is done. The issues like not being able to dismiss the message without an additional keystroke, that you mention are specific controls to ensure that the error is seen and not just passed by without acknowledgement. When an error is displayed, the system should be playing the error sound so that someone who is not looking at the screen will know that an error has occurred. Is the error sound not playing?

The other approach that could be taken with this function is to allow a text file to be loaded, with a "report" at the end of the load for any entries in the text file that could not be processed.

Please Log in to join the conversation.

More
9 years 5 months ago #76 by joel.henderson
Hmmm, that is an interesting idea. I'm assuming that is similar to the way the OPAC processes requests. Is there a way we can meld the two ideas into one, much like the Quick Requests feature on the OPAC, only as a feature of the Patron Module in KLAS? That way staff can type in all the requests at once, hit submit once, then see a "report" of what requests fail and for what reason.

Please Log in to join the conversation.

More
9 years 5 months ago #78 by joel.henderson
Oh, I forgot to answer your question, Mitake. Yes, the error sound is playing, but several of us don't have speakers or we turn the sound on our computers off because system sounds can be distracting. But that's a matter of personal preference, not a KLAS performance issue.

Please Log in to join the conversation.

Time to create page: 0.166 seconds

KLAS Users - Keystone Systems, Inc. logo

Keystone Systems, Inc.
8016 Glenwood Ave., Suite 200
Raleigh, NC 27612
800-222-9711