Successfully reported this slideshow.

The JISC IE: shared, global or common services?

1,163 views

Published on

A presentation at the JISC Common Services Integration Meeting – 27 October 2004

Published in: Education, Business
  • Be the first to comment

  • Be the first to like this

The JISC IE: shared, global or common services?

  1. 1. UKOLN is supported by: The JISC IE: shared, global or common services? JISC Common Services Integration Meeting – 27 October 2004 Andy Powell, UKOLN, University of Bath [email_address] www.bath.ac.uk A centre of expertise in digital information management www.ukoln.ac.uk
  2. 2. JISC IE diagram JISC-funded content providers institutional content providers external content providers brokers aggregators catalogues indexes institutional portals subject portals learning management systems media-specific portals end-user desktop/browser presentation fusion provision OpenURL resolvers shared infrastructure authentication/authorisation (Athens) institutional profiling services terminology services service registries resolvers metadata schema registries
  3. 3. JISC IE Architecture <ul><li>presents a view of the world in terms of 'service components‘ </li></ul><ul><li>fairly significant chunks of functionality offered thru network services (e.g. a portal, a repository, etc.) </li></ul><ul><li>loosely-coupled, semi-monolithic applications </li></ul><ul><li>structured and unstructured network services – i.e, machine–oriented and human-oriented Web interface </li></ul>
  4. 4. Danger of mismatch between… JISC-funded content providers institutional content providers external content providers brokers aggregators catalogues indexes institutional portals subject portals learning management systems media-specific portals end-user desktop/browser presentation fusion provision OpenURL resolvers shared infrastructure authentication/authorisation (Athens) JISC IE service registry institutional preferences services terminology services user preferences services resolvers metadata schema registries What the architecture says…
  5. 5. …and reality! end-user desktop/browser … what the end-user sees :-(
  6. 6. JISC IE scope (function) <ul><li>“resource discovery” </li></ul><ul><li>D2D (discovery to delivery) </li></ul><ul><li>functional model (UML) </li></ul><ul><ul><li>discover, access, use </li></ul></ul><ul><ul><li>survey, discover, detail, access, use </li></ul></ul><ul><ul><li>discover = search, browse and/or alert </li></ul></ul><ul><li>in today’s terminology “metasearch” and “context sensitive linking” </li></ul><ul><ul><li>cross-searching multiple collections/targets </li></ul></ul><ul><ul><li>linking to most appropriate copy </li></ul></ul>
  7. 7. IE Standards Framework <ul><li>The JISC IE standards framework lays out a set of interfaces (the protocols and standards) that these service components use to talk to each other in m2m ways for the purpose of supporting 'resource discovery'. </li></ul>
  8. 8. JISC IE technologies <ul><li>cross-searching </li></ul><ul><ul><li>Z39.50 (Bath Profile) and SRW/SRU </li></ul></ul><ul><li>harvesting </li></ul><ul><ul><li>OAI-PMH </li></ul></ul><ul><li>link resolution </li></ul><ul><ul><li>OpenURL 1.0 </li></ul></ul><ul><li>alerting (news-feeds and related stuff) </li></ul><ul><ul><li>RDF Site Summary (RSS) 1.0 </li></ul></ul><ul><li>metadata </li></ul><ul><ul><li>DC (largely simple DC) and LOM (UK LOM Core) </li></ul></ul><ul><li>shared infrastructural services </li></ul><ul><ul><li>SOAP (or REST) </li></ul></ul>
  9. 9. E-Learning Framework <ul><li>provides a set of lower-level, functional components/APIs (the ELF services) </li></ul><ul><li>much broader in functional scope than the IE </li></ul><ul><li>can think of these as the building blocks that can be used to create larger ‘service components’ </li></ul><ul><li>and/or that are used to offer interfaces (APIs) between one service component and another </li></ul>
  10. 10. ELF IE <ul><li>the ELF and the IE meet when the API used to deliver an ELF service is the same as the standard/protocol specified in the IE standards framework </li></ul><ul><li>can enumerate the sub-set of ELF services that are used as building blocks for the current set of JISC IE service components </li></ul><ul><ul><li>Alert, Authentication, Authorisation, Content Management, DRM, Federated Search, Format Conversion, Harvesting, Identifier, Metadata Management, Metadata Schema Registry, Packaging, Rating / Annotation, Resolver, Search, Service Registry, Terminology, User Preferences </li></ul></ul>
  11. 11. Shared vs. common services <ul><li>IE “shared” infrastructural service components… </li></ul><ul><ul><li>service components that support the functionality of other IE service components </li></ul></ul><ul><ul><li>where it makes sense to ‘share’ the delivery of that functionality </li></ul></ul><ul><ul><li>shown as single ‘boxes’ on the IE architecture diagram – but may be distributed </li></ul></ul><ul><li>ELF “common” services… </li></ul><ul><ul><li>the building blocks and/or interfaces that are common to many service components </li></ul></ul>
  12. 12. Shared infrastructural service It doesn’t make much sense for lots of libraries to deliver a Dewey terminology service. Better for OCLC to deliver as a “shared” infrastructural service… JISC-funded content providers institutional content providers external content providers brokers aggregators catalogues indexes institutional portals subject portals learning management systems media-specific portals end-user desktop/browser presentation fusion provision OpenURL resolvers shared infrastructure authentication/authorisation (Athens) institutional profiling services terminology services service registries resolvers metadata schema registries
  13. 13. Common service Many service components will offer a search interface. Therefore, “search” is an example of a “common” service… JISC-funded content providers institutional content providers external content providers brokers aggregators catalogues indexes institutional portals subject portals learning management systems media-specific portals end-user desktop/browser presentation fusion provision OpenURL resolvers shared infrastructure authentication/authorisation (Athens) institutional profiling services terminology services service registries resolvers metadata schema registries
  14. 14. Shared, global or common? <ul><li>yes! </li></ul><ul><li>“shared” as in “shared infrastructure”… </li></ul><ul><li>“common” as in making use of common APIs </li></ul><ul><li>“global” as in… </li></ul><ul><ul><li>services offered from within JISC IE to external parties (e.g. requests to host external service registries within IESR) </li></ul></ul><ul><ul><li>services offered from outside JISC IE to IE parties (e.g. OCLC Dewey auto-classification service, purl.org, DCMI metadata registry, handle.net, DOI, …) </li></ul></ul><ul><ul><li>need to integrate and be integrated </li></ul></ul>
  15. 15. Questions…

×