David Everly wrote:
> On 8/11/05, Barry Callahan <barryc@xxxxxxxxxxxxxx> wrote:
>
>>A more permanent solution would be to add an option to the user profile that
>>toggles whether the YAZ/Zebra errors are displayed or not.
>
>
> Most folks understand that if you go to a web site and the network, or
> that site's server is down, the browser will show an appropriate
> error.
>
> This seems to be a similar situation: when Emilda is configured to
> look for and retrieve a record in another library's server so as to
> minimize data entry effort.
>
> If that server (or the network between Emilda and that server) is
> down, one would expect to see an error to explain why some book you
> might think would be easily found in that library is not retrieved.
>
> While we might want "more meaningful" errors, IMHO it would be a
> disservice to the user to suppress the error, just as it would be a
> disservice to suppress browser errors when the network/web site is
> down.
YAZ errors will have better handling in v1.3, it will probably be
possible to suppress the errors if need be.
Currently we get similar errors for eg. queries without hits and
connection failures although they represent different error levels.
Failing connections might be interesting for system admins while failed
queries are normally only interesting for the user performing them.
Regards,
--
Erik Berglund
Chairman of the Board
Oy Realnode Ab
berglund@xxxxxxxxxxxx
www.realnode.com
|
