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

More documents

Recommendations

Info

DICE Final Report Figure 11. Saving returned results by list name Figure 12. Results saved message 24
DICE Final Report Figures 11 illustrates the exemplar result list named ‘john maynard keynes’ being saved and Figure 12 shows that a web page is displayed indicating that the results were saved successfully. An error message is displayed if the account details can’t be authenticated. Returning to the COSE interface, shown in Figure 13 we can see that a new resource list named ‘john maynard keynes’ (c.f. Figure 6) appears in the top level folder with a timestamp indicating when it was generated. Figure 13. New resource list saved the Resource Discovery interface Clicking twice on the named list, as in Figure 14, we can see the results displayed in a similar format to the results returned in D+, with additional header information indicating the source of the search (target) and the query term. This requires further work to fully capture and present result descriptions (metadata). Whereas D+ renders results by XSL transformations of the results data (in SRW xml format), results presented in COSE depend on parsing the results data and presenting this as HTML using the D+ style sheet, avoiding the overhead of building the transform engine into COSE. Though resource lists have their own COSE icon, there is a lot more work to render them as a fullblown COSE (learning) objects 10 . However, because they are associated with an HTML component generated in parallel, they can in effect be retrieved as text components using COSE. 10 This requires updating COSE code to accommodate them as a (page set) component in browsing, editing, publication, sharing, export, searching, use in various other tools etc., and so is beyond the remit of the project. 25
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 and 16: DICE Final Report 1) Several target
Page 17 and 18: DICE Final Report Figure 2. Transfo
Page 19 and 20: DICE Final Report The figures show
Page 21 and 22: DICE Final Report The D+ toolkit (/
Page 23: DICE Final Report Figure 9. Modific
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

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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?