CREE Project (Contextual Resource Evaluation Environment)

Size: px

Start display at page:

Download "CREE Project (Contextual Resource Evaluation Environment)"

Barrie Richardson
5 years ago
Views:

1 CREE Project (Contextual Resource Evaluation Environment) Matthew J. Dovey University of Oxford ZING Meeting 22/23 June 2005, Chicago

2 Introduction The CREE Project Part of the JISC Portals Programme <url> User evaluation How do users want to search? Technical development Portlet development using JSR 168 and WSR

3 CREE - Partnership Lead: e-sig, e University of Hull OUCS, University of Oxford EDINA, University of Edinburgh Archaeology Data Service, University of York Newark & Sherwood College instructional media + magic, inc

4 CREE A JISC Project Joint Information Systems Committee UK Government Agency supporting post-16 education Network (SuperJANET( SuperJANET) Content Advice Development $1.4 million per year on portals

5 JISC Portals Programme A range of portal development projects Each supports: Resource discovery across distributed multiple resources Presentation Use of open standards e.g., Z39.50, SRW/U, OAI, RSS Each has its own discrete website

6 Where does CREE fit in? Contextual Resource Evaluation Environment Context in that there are different portal environments Institutional National/International Library Virtual Learning Environments Virtual Research Environments Etc. Portals have assumed user will come to them Better taking the portals, or portal functionality, to the user Embedding in institutional contexts CREE Investigating whether users find this valuable Testing portal technologies to enable embedding

7 User evaluation How do users want to search? How do they currently search? What requirements do users have for searching? How might different contexts affect searching?

8 CREE Survey National survey carried out September - October 2004 >4500 responses 2500 of them came from Oxford! CREE Focus groups 13 groups held: 6 staff and 7 student >60 people from across disciplines University of Hull and University of Oxford, Newark and Sherwood College

9 What did the survey find? 85% used Internet search tools daily 61% used them daily for learning, teaching or research 67% used subject-specific specific resources 68% used the local library catalogue at least weekly 54% used other library catalogues at least monthly

10 What search tools are used? Google! Used frequently by over 90% Usually as first choice and starting point Sometimes as last resort! Yahoo!,Ask Jeeves,Altavista also used Nationally maintained subject-specific specific resources Second in popularity to Google But users are aware of and use more specific search tools (especially electronic journals) Choice of tool is according to need

11 Simultaneous Searching

12 Displaying search results

13 Technical development Test out how users wish to interact with portal search tools in different contexts Institutional portal Learning Management Systems Virtual Research Environments Outside of formal framework Creation of interactive search interface demonstrators for users to view

14 Testing portal standards For testing in portals and related frameworks Developing portlets using open standards JSR 168 WSRP Examine the relationship between these

15 Potted History of JSR-168/WSRP Apache JetSpeed Portal JCP - Java Portlet API JSR 168 JSR WebServices Web Service User Interface OASIS TC Web Service for Remote Portals OASIS TC Web Service for Interactive Applications WSRP Implementations: Java,.Net, Perl, Python WSRP 2.0, JSR OASIS TC WSIA Family WSRP (initial spec) OASIS TC WSRP 1.0 (WSIA dropped) Very rough timeline

16 Re-purposing existing tools JAFER OpenSource Z39.50/SRW engine for searching library catalogues (and other) Oxford jafer.org GetRef - Metasearch engine for searching bibliographic databases EDINA Including GetCopy - OpenURL resolver EDINA edina.ac..ac.uk/getref/ Archaeology Data Service Z39.50 search ahds.ac..ac.uk/index.html XSLT based Google Portlet developed by im&m

17 Development path All project partners concluded that JSR 168 was the simpler development route JSR 168 portlets developed for all so far JSR 168 portlet is basis for WSRP portlet JAFER the first example of this ADS now working via this route as well Google being developed

18 uportal at Hull

19 The usual stuff

20 Workflow for SRW Searches User Portal Portlet WebService Catalogue HTML Post HTML Search Form Rendered Portal HTML Rendered portal HTML Form Fragment (Portal CSS) HTML fragment (portlet CSS styles ) ZeeRex WSRP getmarkupreq uest WSRP sendblockingi nteraction XSLT Transform SRW Response getexplain SRW Request

Portal Technology. State University of New York Albany, New York 26 October Jim Farmer. i n s t r u c t i o n a l m e d i a + m a g i c, i n c.

Portal Technology. State University of New York Albany, New York 26 October Jim Farmer. i n s t r u c t i o n a l m e d i a + m a g i c, i n c. i n s t r u c t i o n a l m e d i a + m a g i c, i n c. Portal Technology State University of New York Albany, New York 26 October 2005 Jim Farmer instructional media + magic, inc. Overview Use of portals