300 likes | 432 Views
The EVIE Project. Derek Sergeant Leeds University Library. Presentation overview. Overview of the 10 WPs User requirements analysis Document visualization Digital preservation. The 10 work-packages. WP1 Ensure the project runs smoothly WP2 User requirements analysis
E N D
The EVIE Project Derek Sergeant Leeds University Library
Presentation overview • Overview of the 10 WPs • User requirements analysis • Document visualization • Digital preservation
The 10 work-packages • WP1 Ensure the project runs smoothly • WP2 User requirements analysis • WP3 Systems scoping/design • WP4 Digital preservation requirements • WP5 Resource discovery and document visualisation • WP6 Taxonomy • WP7 Simplified-sign-on, channel development • WP8 Implementation and deployment • WP9 Evaluation and dissemination • WP10 Collaborative tools
The 10 work-packages WP2 User Req WP3 Sys Req (WP5) Res Disc (Doc Viz) WP7 SSO Dev WP8 Implement (WP10) Collab
User Requirements Analysis • 1 – 1 interviews • Focus groups • Online questionnaire
Peer activities (publishing) Research-Teaching Links Consultancy Research Lifecycle Resource Discovery Research Outputs Project Management Obtain Funding Collaboration with Partners
User Requirements - Results Arts Business Biological Sciences Education, Social Science and Law Environment Engineering Mathematical & Physical Sciences Medicine and Health Performance, Visual Arts and Communications Joint Honours Other Faculty not stated
User Requirements - Results Professor, Reader, Senior Lecturer, Senior Research Fellow Lecturer, Research Fellow Graduate Student, Post-doctoral Researcher Other Research role not stated
User Requirements - Results essential 1 very important 2 aspect ID important 3 somewhat important 4 not important 5 0 20 40 60 80 100 120 140 number of times rated 1: Resource Discovery 2: Obtain Funding 3: Collaboration with Partners 4: Research Outputs 5: Other
Document Visualization • 10 week summer project • Uses the Google API • Alternative user interface to sort and conceptualise a web search
Document Visualization • User types in Search Term • GoogleAPI called with ST • Cached copy obtained for top 10 • HTML parsed and analysed to extract keywords • GoogleAPI called with ST+keyword • Results analysed to allocate relationship strengths between URLs and keywords • Modified TouchGraph presents this
Document Visualization • User types in Search Term • GoogleAPI called with ST • Cached copy obtained for top 10 • HTML parsed and analysed to extract keywords • GoogleAPI called with ST+keyword • Results analysed to allocate relationship strengths between URLs and keywords • Modified TouchGraph presents this • 20 calls • 10 calls • 15*10 • ~20 = ~200 calls to GoogleAPI
Traditional textual outputs (published papers, articles, books, chapters, tech reports, …) + Types of research outputs • Community knowledge • Processed data • Raw data • Sound / dialogue recording • Audio • Video • Consultancy reports
Case Study One : Kia Ng • Outputs for a project that has just started • In the beginning… email is important • Use Wiki to share docs • Contracts, Budgets, Diarys (EU proprietary) • Year financial statement • Kia sends 30GB a day to EC • Consortium agreement (physical signature)
Case Study One : Kia Ng • Website, public (mainly static) • Private view • Partner profile • Workpackage manager • UML diagrams • Test cases (arbitrary formats) • Upload/download area (CMS), with metadata • Stats on usage • Forum • Newsletter
Case Study One : Kia Ng • Deadlines + deliverables need to go to EU • Source code (a subversion repository) • JavaDoc • User docs (latex, bibtex, pdf, word, endnote) • Conferences attended (text paper, pdf, ppt) • Conferences run • Info for next conference • Proceedings (IEEE) • Website (photos, links)
Case Study One : Kia Ng • Deliverables • Reports • Software • Docs • Websites • Fliers / dissemination material • CD/DVD • T-shirts/pens/bags (photo in report) • Marketing video
Case Study Two : Mark Priestley • Based on ESSL “Support for your Research” • My research plan (reviewed yearly) (PDP) • Building a research culture • ULPD keywords used to indicate expertise • Communication strategy • Finding funding • Notes on conversation with resource mentor
Case Study Two : Mark Priestley • Write research proposal • Want: My applications, past and present • Work out realistic budget • Submitting a proposal (JeS) • Letters, referee’s comments, etc. • Approval • Costing, ethical, HoS • COSTA schedule • Case for support • Application form
Case Study Two : Mark Priestley Start project • Accept the award • Open a research account • Appoint new staff, sub-contractors • Communications, job description, advert Manage project • Track expenditure, manage time + workload
Case Study Two : Mark Priestley Finish project • Delivering promised output • End of project report • Annual reports • Working papers • Publications • (details of events, external publications) • Publicise outputs • Dissemination
Case Study Two : Mark Priestley Doing the research • Data • RA digitally records interview • Transcription service • Store (CD with .wmf + transcript) • Use analysis software (NVivo), coded by staff • Photo, Video, Stats datasets, Spreadsheets
3rd VRE Programme Meeting Monday, January 16th 2006