Projects within Projects DELIVER and ANGEL

1. Projects within ProjectsDELIVER and ANGEL John PaschoudLSE LibraryJISC Projects ANGEL and DELIVER COLIS: e-Libraries:e-Learning London, 28-Feb-2003

2. Where do VLE and Library domains really overlap? This is the general question posed in the JISC 7/02 programme • VLE classifies resources by purpose • course, lecture, date (of use), topic • some resources created for a teaching purpose • LMS classifies resources by content • author, title, subject, date (of creation) • Reading lists! This is the focus of Project DELIVER COLIS: e-Libraries:e-Learning London, 28-Feb-2003

3. Digital Electronic Library Integration within Virtual EnviRonments • A broader interpretation than ‘traditional’ reading lists: any citeable resource • Library back-office staff (acquisitions, etc) are an important group of users • Organisational engineering (as well as the technical sort) • Solutions to be implemented by LSE and De Montfort University • Open standards inter-operability between components (not limited to particular VLE/LMS) • Experience to be documented for use by the wider community COLIS: e-Libraries:e-Learning London, 28-Feb-2003

4. Course compilers VLE (WebCT) LMS (Sirsi, Talis) RLM (???) ‘appropriate copy’ links, access-controlled external content:e-journals Library staff (Acquisitions, Course Support) locally-held content:e-course-packs Structure of DELIVER COLIS: e-Libraries:e-Learning London, 28-Feb-2003

5. DELIVER Project Structure • User Needs Analysis • Academic staff (including surrogate course-compilers) • Students • Library liaison & acquisitions staff • VLE support staff • Requirements Spec • Core Resource List Management • Interface (listing, retrieving, content-management) to e-resources • Organisational changes • Build, Integrate • Deploy, Disseminate, Promote • Institutional decisions • Evaluation (Exit strategy, sort of) COLIS: e-Libraries:e-Learning London, 28-Feb-2003

6. Reading List Management products • Bookworm • Open Source from Loughborough Uni • bookworm.lboro.ac.uk/distribution.html • ReadingListDirect • online managed service • www.readinglistdirect.co.uk/info • TalisList • commercial s/w; works with non-Talis LMSs • www.talis.co.uk/products/lms/talislist.htm COLIS: e-Libraries:e-Learning London, 28-Feb-2003

7. Content Management problems • ‘Appropriate Copy’ • the version the tutor finds isn’t always the version to direct the students to • Access Management • password proliferation • user role definition • Local content needs librarianship • re-usability • scaleable management COLIS: e-Libraries:e-Learning London, 28-Feb-2003

8. ANGEL-inside • The ‘smart-link-finder’ • helps course compilers find/copy/paste a URL for a resource • Links are ‘indirect’ • they point to the ANGEL metadata for a resource; not some actual location of the resource itself • Actual links are resolved when used • to ‘appropriate copy’ for user and location • with all use logged consistently • to resources without a ‘natural URL’ COLIS: e-Libraries:e-Learning London, 28-Feb-2003

9. How to give users what they want Most users don’t want a single ‘interface-to-everything’ • When they are following a directed course of learning, a VLE is appropriate • When they are researching (whether formally, or not) a LMS (or another sort of Find/Browse portal) is better They would like better integration between the two, when they need it COLIS: e-Libraries:e-Learning London, 28-Feb-2003

10. user interface user interface user interface VLE LMS MIS content manager content manager content manager Lots of Interfaces to Separate Things COLIS: e-Libraries:e-Learning London, 28-Feb-2003

11. user interface user interface user interface VLE LMS MIS content manager content manager content manager One Interface-to-Everything universalportal COLIS: e-Libraries:e-Learning London, 28-Feb-2003

12. learning portal libraryportal adminportal user interface user interface user interface VLE LMS MIS content manager content manager content manager Lots of Interfaces to Most Things …users get a choice of purpose-specific interfaces, but also access to (some) content from other purpose-specific systems COLIS: e-Libraries:e-Learning London, 28-Feb-2003

13. user interface user interface user interface VLE LMS MIS content manager content manager content manager …but …all those 1-to-1 interfaceswould be hard work! …and every time any one of the system vendors ‘upgrades’ you to a new version, they all have to be re-engineered!!! COLIS: e-Libraries:e-Learning London, 28-Feb-2003

14. learning portal libraryportal adminportal Middleware-for-Anything VLE LMS MIS user interface user interface user interface content manager content manager content manager COLIS: e-Libraries:e-Learning London, 28-Feb-2003

15. Client applications (MLEs, ITEs, external search clients, ANGEL maintenance client) Server / service applications (MLEs, external searchable servers, local proprietary info-systems) CONTENT End-user (Web browser) ANGEL Middleware-for-Anything (other access protocols like Z39.50 also possible) Any web portal via which the user can access managed content Any content resource from which items can be retrieved by any protocol sensible protocol COLIS: e-Libraries:e-Learning London, 28-Feb-2003

16. Portal CLR Organisational Domain Organisational Domain Organisational Domain CLR CMS content Jstor Unicorn EDMS E-journals library data committee docs Supported std protocols;Custom proprietary interfaces Institutional Information Environment CLR = Collection-Level Registry CLR CMS = Content Management System SITS CMS student data content COLIS: e-Libraries:e-Learning London, 28-Feb-2003

17. Portal CLR UA UA UE CLR CMS CMS content content SITS Jstor Unicorn student data User Access to Managed Information CLR EDMS CMS content COLIS: e-Libraries:e-Learning London, 28-Feb-2003

18. [more info] John Paschoud: <j.paschoud@lse.ac.uk> Public information about ANGEL: www.angel.ac.uk (also links to DELIVER and other projects) COLIS: e-Libraries:e-Learning London, 28-Feb-2003