DICE Project Final Report Resource Discovery Tools Evaluation and ...
DICE Project Final Report Resource Discovery Tools Evaluation and ...
DICE Project Final Report Resource Discovery Tools Evaluation and ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>DICE</strong> <strong>Final</strong> <strong>Report</strong><br />
The Google target worked after moving the googleapi.jar file to a location (common\lib)<br />
other than that specified. The Amazon target returned results that couldn’t be rendered<br />
(ClassCast exception). The British Library target had changed (Z39.50) configuration<br />
parameters after release (this remains unresolved on our part, pro tem). The ADLIB <strong>and</strong><br />
COLIS targets wee configured to run from the Edinburgh server (tweed.lib.ed.ac.uk) in<br />
release 1.<br />
2) Features which worked in release 1, namely RLI <strong>and</strong> CP save formats haven't been<br />
maintained in release 2. Release 1 is deprecated, but in that version these <strong>and</strong> other<br />
features ran from the Edinburgh server after the service was launched locally.<br />
3) Notes relating to the configuration (addition) of new targets are incomplete. Edits to<br />
searchfield.jsp <strong>and</strong> searchfield.xsl <strong>and</strong> additional index-newtarget.txt files are also<br />
required. These edits are easily made <strong>and</strong> additional index files were copied from what<br />
looked like similar targets <strong>and</strong> renamed, but without better instruction <strong>and</strong> explanation in<br />
the guide, we could not be sure of unintended side effects. Errors are thrown from the<br />
tomcat console where new targets might be mis-configured but this does not seem to<br />
impact unduly on performance.<br />
4) There is no instruction regarding the configuration.jsp file (default variable for server is set<br />
as tweed.lib.ed.ac.uk).<br />
• Exception h<strong>and</strong>ling As noted in the User evaluation, the toolkit is prone to throw unh<strong>and</strong>led<br />
exception messages which are might be due to various causes. These include problems with the<br />
network (timeout) <strong>and</strong> server availability (connection failure), unsupported protocols or metadata,<br />
transformation, configuration, <strong>and</strong> other errors. A selection of these error messages are illustrated<br />
below.<br />
Figure 1. ePrints target (localhost), ‘encoding too long’ error<br />
16
Change language