The CREW system - PowerPoint Web2.0 - Release 5 April 2009 Improved Faceted Searching
Development of a Virtual Research Environment to support Collaborative Research Events Meik Poschen, Michael Daw, Rob Proc...
Outline <ul><li>What is CREW? </li></ul><ul><ul><li>Project, Context & Technical System </li></ul></ul><ul><li>Practice an...
The CREW Team <ul><li>CREW: one of four funded projects under the JISC Virtual Research Environment (VRE) phase 2 Programm...
VRE <ul><li>JISC defines a Virtual Research Environment (VRE) as to </li></ul><ul><li>“ help researchers in all discipline...
Project Aim <ul><li>“ The aim of CREW is to develop and deploy user-centred software to support research resources (includ...
Project Roots <ul><li>Successor of two JISC VRE phase 1 projects, integrating their functionalities: </li></ul><ul><li>Mem...
 
 
Functionalities of the System <ul><li>CREW provides an environment and support material, with four main features: </li></u...
CREW Architecture
Unique selling point <ul><li>CREW’s unique selling point is to be able to  record events , have all gathered data  fully s...
User Engagement <ul><li>The VRE programme phase 2 focuses strongly on user engagement </li></ul><ul><li>Lesson’s indicated...
Approach <ul><li>The user engagement and user-centred design process in CREW is grounded in the concept of  co-realisation...
User Groups <ul><li>Three user groups have been integrated from the proposal phase on and each is also a use case: </li></...
User Groups: Integration  <ul><li>A very important asset of CREW is to take into account the different research settings a...
Engagement activities <ul><li>Users are integrated into the  core activities of the project: </li></ul><ul><li>Users can p...
User Requirements Gathering <ul><li>What do users need and how do we find out?  </li></ul><ul><li>So called User Days in t...
 
Supported User Events <ul><li>Workshop: making good applications to the research for patient benefit programme - September...
Case Study <ul><li>Monthly ACM SIGGRAPH Manchester Professional Chapter seminars - end 2007 onwards (Scientific Visualizat...
Case Study <ul><li>Monthly ACM SIGGRAPH Manchester Professional Chapter seminars - end 2007 onwards (Scientific Visualizat...
Challenges for User Engagement <ul><li>1. Are the activities run in CREW sufficient to provide continuous maximum user eng...
1. Are the activities run in CREW sufficient to provide continuous maximum user engagement? <ul><li>Successful so far in t...
2. How do the elicited requirements from different use cases translate into design decisions appropriate for all, across d...
3. Lesson learned on a  practical, technical issue <ul><li>Recorded by CREW on location in a lecture room it turned out, t...
CREW in Action <ul><li>CREW – if you have an Access Grid node </li></ul>
CREW in Action <ul><li>CREW-Kit – Without an Access Grid node </li></ul>
CREW in Action
 
 
 
Initial Screen – allowing searches and browsing of recorded/annotated events
Selecting an Event – lists all sessions within the event plus event metadata
Selecting a Session – individual recorded parts are listed and described
Selecting a Recording – allows automatic cross-selection and post annotations
Playing a Recording – starts Flash integrated ppt and videos with slide notes …
Playing a Recording – … and automated annotation timelines. All selectable.
Search and Browsing – in this case authors and presenters, over many events. Extra items included Google Mash-ups for loca...
Live Demo
Software Outcome: Caboto <ul><li>An RDF-based annotation system. </li></ul><ul><li>Provides a RESTful
interface for submit...
Caboto in CREW and STARS http://caboto.org
User Requests – new needs <ul><li>Security Model – VOs, authentication (eg NGS) etc. </li></ul><ul><li>IP Performance Righ...
Further Steps <ul><li>Ongoing cycles of requirements gathering </li></ul><ul><li>Supported user events will continue, test...
Thank You <ul><li>From the CREW team: </li></ul><ul><li>http://www.crew-vre.net </li></ul>
Upcoming SlideShare
Loading in …5
×

CREW VRE Release 5 - 2009 May

1,038 views

Published on

CREW (Collaborative Research Events on the Web) aims to improve access to research event content by capturing and publishing the scholarly communication that occurs at events like conferences and workshops. This is a Virtual Research Environment funded by JISC within the UK.

This slide show describes release 5 of the development. See site: http://www.crew-vre.net/

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,038
On SlideShare
0
From Embeds
0
Number of Embeds
62
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • CREW VRE Release 5 - 2009 May

    1. 1. The CREW system - PowerPoint Web2.0 - Release 5 April 2009 Improved Faceted Searching
    2. 2. Development of a Virtual Research Environment to support Collaborative Research Events Meik Poschen, Michael Daw, Rob Procter, Martin Turner, Terry Hanley, Roger Slack, Andy Hall, Mike Jones, Rebecca Jones, Anja Le Blanc, Emma Place, Nikki Rogers, Andrew Rowley, Tobias Schiebeck, Damian Steer, Caroline Williams The CREW Project
    3. 3. Outline <ul><li>What is CREW? </li></ul><ul><ul><li>Project, Context & Technical System </li></ul></ul><ul><li>Practice and User Engagement </li></ul><ul><ul><li>Approach, User Groups, Activities </li></ul></ul><ul><li>System Demo </li></ul><ul><li>Future Release and Users </li></ul>
    4. 4. The CREW Team <ul><li>CREW: one of four funded projects under the JISC Virtual Research Environment (VRE) phase 2 Programme </li></ul><ul><li>2 year project: ends March 2009 </li></ul><ul><li>Overall aim: “Support the research process” </li></ul><ul><li>Focus strongly on user engagement </li></ul>
    5. 5. VRE <ul><li>JISC defines a Virtual Research Environment (VRE) as to </li></ul><ul><li>“ help researchers in all disciplines manage the increasingly complex range of tasks involved in carrying out research. A VRE will provide a framework of resources to support the underlying processes of research on both small and large scales, particularly for those disciplines which are not well catered for by the current infrastructure.” </li></ul>
    6. 6. Project Aim <ul><li>“ The aim of CREW is to develop and deploy user-centred software to support research resources (including audio-visual recordings) that arise from collaborative research events such as conferences, workshops and seminars to be discoverable in context.” </li></ul>
    7. 7. Project Roots <ul><li>Successor of two JISC VRE phase 1 projects, integrating their functionalities: </li></ul><ul><li>Memetic (Meeting Memory Technology Informing Collaboration), University of Manchester, Open University, University of Southampton, University of Edinburgh </li></ul><ul><li>Iugo , Institute for Learning and Research Technology (ILRT), University of Bristol </li></ul>
    8. 10. Functionalities of the System <ul><li>CREW provides an environment and support material, with four main features: </li></ul><ul><li>Recording: Users can record events audio-visually, incorporating presentation slides and similar material, building on Memetic and AG technology. </li></ul><ul><li>Replaying of the recorded events and choosing the interface layout. </li></ul><ul><li>Annotating and editing: CREW supports the addition of tags during recordings, e.g. to annotate slides or link to related blog discussions. </li></ul><ul><li>Searching: The search and browse application will connect and cross-link all the relevant content and metadata in the VRE portal, presenting detailed information. </li></ul>
    9. 11. CREW Architecture
    10. 12. Unique selling point <ul><li>CREW’s unique selling point is to be able to record events , have all gathered data fully searchable , be it annotated audio-visual content or other internal or external resources like papers, conference information and researchers’ profiles etc., which are harvested and cross-linked, integrated in a web environment . </li></ul>
    11. 13. User Engagement <ul><li>The VRE programme phase 2 focuses strongly on user engagement </li></ul><ul><li>Lesson’s indicated from Iugo and Memetic: </li></ul><ul><ul><li>Despite engaging users wherever possible, this engagement was limited to occasional and informal participation in requirement gathering activities and the use of the tools </li></ul></ul><ul><ul><li>User needs should be the driver and focus for requirements gathering, development and evaluation, and underpin the whole methodological approach </li></ul></ul>
    12. 14. Approach <ul><li>The user engagement and user-centred design process in CREW is grounded in the concept of co-realisation (Hartswood et al., 2007), drawing on ethnomethodologically informed workplace studies </li></ul><ul><li>Bridging the gap between users and developers </li></ul><ul><li>Formalising user involvement within the core activities of the project </li></ul><ul><li>Active and long-term user participation </li></ul><ul><li>Being minimally invasive in development and evaluation techniques, focusing on the user groups’ work practices </li></ul><ul><li>Creating a shared user-driven design-in-use process </li></ul>
    13. 15. User Groups <ul><li>Three user groups have been integrated from the proposal phase on and each is also a use case: </li></ul><ul><li>Intute: national JISC service providing access to web resources for research to UK higher education institutions (Bristol & Manchester) </li></ul><ul><li>Institute of Health Sciences (IHS): promotes health sciences research in Manchester </li></ul><ul><li>Manchester scientific visualization research groups (UK Professional SIGGRAPH Chapter & Eurographics UK Chapter): using the AG for seminars and workshops. </li></ul>
    14. 16. User Groups: Integration <ul><li>A very important asset of CREW is to take into account the different research settings and requirements of the users themselves. </li></ul><ul><li>The members of the three user groups are actively and formally participating in the project during its complete lifecycle to help achieve these goals. </li></ul><ul><li>Project funds are used to remunerate users for their time and effort in project activities </li></ul>
    15. 17. Engagement activities <ul><li>Users are integrated into the core activities of the project: </li></ul><ul><li>Users can participate in the monthly project meeting </li></ul><ul><li>A Project User Management Group (PUMG) has been set up, meeting bi-monthly </li></ul><ul><li>Users can contribute to the project website and Wiki (and BSCW) </li></ul><ul><li>Two mailing lists are used: </li></ul><ul><ul><li>Project mailing list including all users </li></ul></ul><ul><ul><li>Technical development mailing list including users who want to </li></ul></ul>
    16. 18. User Requirements Gathering <ul><li>What do users need and how do we find out? </li></ul><ul><li>So called User Days in the first phase of the project </li></ul><ul><ul><li>One day with each user group </li></ul></ul><ul><ul><li>Introduction what we plan to do (in development) </li></ul></ul><ul><ul><li>Discussion in focus groups </li></ul></ul><ul><ul><li>Document findings and feed those back to the users (User Requirements Report) </li></ul></ul><ul><ul><li>Challenge: find a path for development recognising the different needs of different user groups and domains </li></ul></ul><ul><li>All User Day </li></ul><ul><ul><li>Bring together all users on one day and repeat the above process </li></ul></ul>
    17. 20. Supported User Events <ul><li>Workshop: making good applications to the research for patient benefit programme - September 2007 (Institute of Health Sciences) </li></ul><ul><li>Monthly ACM SIGGRAPH Manchester Professional Chapter seminars - end 2007 onwards (Scientific Visualization Groups) </li></ul><ul><li>UK Chapter of the Eurographics Association - TP.CG (Theory and Practice of Computer Graphics) Annual Conference - June 2008 (Scientific Visualization Groups) </li></ul><ul><li>ESRC Research Methods Festival, Oxford - 30 June to 3 July 2008: Recording of “What is?” sessions (special) </li></ul><ul><li>HP Hosted Event: SWIG UK - A Semantic Web Community Event – 11 November 2008 </li></ul><ul><li>Health Postgraduate Workshop Seminars – 9 December 2008 </li></ul><ul><li>Major training event/harvesting – 2009 (Intute) </li></ul>
    18. 21. Case Study <ul><li>Monthly ACM SIGGRAPH Manchester Professional Chapter seminars - end 2007 onwards (Scientific Visualization Groups) </li></ul><ul><li>50 Research Events over three years: from seminars, to specialist software/hardware roadmaps and tutorials. </li></ul>
    19. 22. Case Study <ul><li>Monthly ACM SIGGRAPH Manchester Professional Chapter seminars - end 2007 onwards (Scientific Visualization Groups) </li></ul>
    20. 23. Challenges for User Engagement <ul><li>1. Are the activities run in CREW sufficient to provide continuous maximum user engagement? </li></ul><ul><li>2. How do the elicited requirements from different use cases translate into design decisions appropriate for all, across disciplinary boundaries and different work practices? </li></ul><ul><li>3. Lessons learned on a practical, technical issue </li></ul>
    21. 24. 1. Are the activities run in CREW sufficient to provide continuous maximum user engagement? <ul><li>Successful so far in the first year in collaborating well with highly motivated users </li></ul><ul><li>Gaining valuable information about user needs and their work practice </li></ul><ul><li>Regular participation of user representatives in all project meetings </li></ul><ul><li>Project team gets frequent feedback on the respective activities of the project </li></ul><ul><li>Idea of last requirements session was brought in by the user groups </li></ul><ul><li>Maximum user engagement means staying flexible and responsive to users’ advice, whenever possible </li></ul>
    22. 25. 2. How do the elicited requirements from different use cases translate into design decisions appropriate for all, across disciplinary boundaries and different work practices? <ul><li>Found a lot of common requirements.. </li></ul><ul><li>..but also some rather specific ones </li></ul><ul><li>The success of their integration will be determined by users’ feedback and finding a compromise </li></ul><ul><ul><li>Access rights and confidential data issues </li></ul></ul><ul><ul><li>Different metadata schemes and categories </li></ul></ul><ul><li>Definition of terms and common vocabulary is needed </li></ul>
    23. 26. 3. Lesson learned on a practical, technical issue <ul><li>Recorded by CREW on location in a lecture room it turned out, that microphone and projector’s light bulb were defective, resulting in substandard sound and picture quality. These circumstances affected the user feedback slightly to the negative, although it was made clear, that this was no fault of the CREW software itself. </li></ul>
    24. 27. CREW in Action <ul><li>CREW – if you have an Access Grid node </li></ul>
    25. 28. CREW in Action <ul><li>CREW-Kit – Without an Access Grid node </li></ul>
    26. 29. CREW in Action
    27. 33. Initial Screen – allowing searches and browsing of recorded/annotated events
    28. 34. Selecting an Event – lists all sessions within the event plus event metadata
    29. 35. Selecting a Session – individual recorded parts are listed and described
    30. 36. Selecting a Recording – allows automatic cross-selection and post annotations
    31. 37. Playing a Recording – starts Flash integrated ppt and videos with slide notes …
    32. 38. Playing a Recording – … and automated annotation timelines. All selectable.
    33. 39. Search and Browsing – in this case authors and presenters, over many events. Extra items included Google Mash-ups for location checking.
    34. 40. Live Demo
    35. 41. Software Outcome: Caboto <ul><li>An RDF-based annotation system. </li></ul><ul><li>Provides a RESTful
interface for submitting
and receiving annotations. </li></ul><ul><li>Allows P u blic and P r ivate annotations. </li></ul><ul><li>A work in progress! </li></ul>CIP
    36. 42. Caboto in CREW and STARS http://caboto.org
    37. 43. User Requests – new needs <ul><li>Security Model – VOs, authentication (eg NGS) etc. </li></ul><ul><li>IP Performance Rights Issues: Personalisation Permissions </li></ul><ul><li>Server “Hardening” – Repository Integration Institutional Repository and SUE Direct links </li></ul><ul><li>Speed – Performance Test: Load Testing and Evaluation </li></ul><ul><li>Full Interface – skin – rewrite (c word) </li></ul>
    38. 44. Further Steps <ul><li>Ongoing cycles of requirements gathering </li></ul><ul><li>Supported user events will continue, testing the software releases in use in the user groups’ workplace settings </li></ul><ul><li>Further gathering of user feedback through surveys and/or interviews after release 3 and 4 </li></ul><ul><li>Usability testing sessions will be conducted with the next releases </li></ul>
    39. 45. Thank You <ul><li>From the CREW team: </li></ul><ul><li>http://www.crew-vre.net </li></ul>

    ×