DICE Project Final Report Resource Discovery Tools Evaluation and ...

More documents

Recommendations

Info

DICE Final Report The Google target worked after moving the googleapi.jar file to a location (common\lib) other than that specified. The Amazon target returned results that couldn’t be rendered (ClassCast exception). The British Library target had changed (Z39.50) configuration parameters after release (this remains unresolved on our part, pro tem). The ADLIB and COLIS targets wee configured to run from the Edinburgh server (tweed.lib.ed.ac.uk) in release 1. 2) Features which worked in release 1, namely RLI and CP save formats haven't been maintained in release 2. Release 1 is deprecated, but in that version these and other features ran from the Edinburgh server after the service was launched locally. 3) Notes relating to the configuration (addition) of new targets are incomplete. Edits to searchfield.jsp and searchfield.xsl and additional index-newtarget.txt files are also required. These edits are easily made and additional index files were copied from what looked like similar targets and renamed, but without better instruction and explanation in the guide, we could not be sure of unintended side effects. Errors are thrown from the tomcat console where new targets might be mis-configured but this does not seem to impact unduly on performance. 4) There is no instruction regarding the configuration.jsp file (default variable for server is set as tweed.lib.ed.ac.uk). • Exception handling As noted in the User evaluation, the toolkit is prone to throw unhandled exception messages which are might be due to various causes. These include problems with the network (timeout) and server availability (connection failure), unsupported protocols or metadata, transformation, configuration, and other errors. A selection of these error messages are illustrated below. Figure 1. ePrints target (localhost), ‘encoding too long’ error 16
DICE Final Report Figure 2. Transformation error (‘middot entity’), Google target (localhost) Figure 3 Transformation error (‘text/html not text/xml’), Google target (localhost) 17
Page 1 and 2: DICE Final Report DICE Project Fina
Page 3 and 4: DICE Final Report Contents Summary
Page 5 and 6: DICE Final Report Alternative disco
Page 7 and 8: DICE Final Report retrospect this w
Page 9 and 10: DICE Final Report First, it did not
Page 11 and 12: User Evaluation DICE Final Report T
Page 13 and 14: DICE Final Report • Metadata retu
Page 15: DICE Final Report 1) Several target
Page 19 and 20: DICE Final Report The figures show
Page 21 and 22: DICE Final Report The D+ toolkit (/
Page 23 and 24: DICE Final Report Figure 9. Modific
Page 25 and 26: DICE Final Report Figures 11 illust
Page 27 and 28: DICE Final Report Figure 15. Resour
Page 29 and 30: DICE Final Report Figure 19. Resour
Page 31 and 32: Acknowledgements DICE Final Report
Page 33 and 34: Different kinds of RD tool DICE Fin
Page 35 and 36: DICE Final Report other RD tools ho
Page 37 and 38: DICE Final Report Other significant
Page 39 and 40: DICE Final Report Figure 3. Results
Page 41 and 42: DICE Final Report Figure 6. Search
Page 43 and 44: DICE Final Report Figure 10. Start
Page 45 and 46: There’s a link to Google Scholar
Page 47 and 48: DICE Final Report The figures and l
Page 49 and 50: DICE Final Report Figure 18. Using
Page 51 and 52: • On other standards and protocol
Page 53 and 54: DICE Final Report 7. **Do you have
Page 55 and 56: Appendix B: User Evaluation DICE Fi
Page 57 and 58: 3. **Would you actually use any of
Page 59 and 60: DICE Final Report ACADEM2: This is
Page 61 and 62: DICE Final Report EDTECH2: A lot of
Page 63 and 64: DICE Final Report STU3: The DEVIL h
Page 65 and 66: EDTECH3: EDTECH4: (see Q 14) DICE F
Page 67 and 68:
13. **Do you have comments to make
Page 69 and 70:
Appendix C: Demonstrating D plus in
Page 71:
DICE Final Report D. Resource Disco
show all

DICE Project Final Report Resource Discovery Tools Evaluation and ...

Create successful ePaper yourself

Delete template?

Save as template?