History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SAK-11025
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Unassigned
Reporter: Jim Eng
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Sakai

Error in library search does not allow user to recover

Created: 06-Aug-2007 14:59   Updated: 23-Oct-2008 07:48
Component/s: Citations Helper
Affects Version/s: 2.4.0, 2.4.x, 2.4.1
Fix Version/s: 2.5.0

Time Tracking:
Not Specified

2.4.x Status: None
2.5.x Status: None
2.6.x Status: None


 Description  « Hide
If an error occurs while the user is attempting a library search, the UI shows these messages:

Alert: Unable to search at this time. Please try again.
There was an error.
Please click the "done" button to close this window.

The screen has a "done" button, but that seems to do nothing.

The error message should allow the user to cancel out of the search attempt back to the screen with the options for creating citations (library search, google search, and manual entry).

This can be reproduced with the xserver impl by changing the config.xml file to supply an invalid value for metasearch-baseurl (or probably the username and/or password). Probably the same with web2bridge impl.


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Jim Eng - 06-Aug-2007 15:00
Assigning to Steve temporarily so we can talk it over.

Steve Smail - 07-Aug-2007 13:25
It looks like this happens when the OSID throws an exception; I think it should happen at the same "mis-configuration" points when you're using the Web2Bridge OSID.

Your suggestions on how the UI should act seem perfect.

I'll add a new wrinkle as well. We've been testing all of the available Sirsi databases here at IU, and a couple behave so badly that the OSID throws a SearchException when trying to make sense of the results.

This exception takes place after we've gotten past the potential configuration problems, and it doesn't cause the UI to present the "error display". Instead, the UI "resets" to the inital search screen - no error text is displayed.

For a "basic search", this "reset screen" seems fully functional - you can select other databases and search again, with success.

Should this be opend as a separate issue?

Steve Smail - 07-Aug-2007 13:27
Hi Jim - I added some comments and am re-assigning this per your request.

Jim Eng - 27-Aug-2007 09:01
This needs to be merged into 2.4.x and post-2.4

Jon Dunn - 15-Nov-2007 14:45
Steve, can you verify and close?

Filter Maintainer - 08-Aug-2008 06:02
2.5.0 QA has been completed. Unfortunately, there were not resources available to specifically test this issue. If you find this to still be a problem in the latest release (at this point 2.5.2), please reopen the JIRA and add the latest affects version.