Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
10 minute  practical  guide to the JISC Information Environment (for  p ublishers ! ) Andy Powell UKOLN, University of Bat...
What do you need to do? <ul><li>support machine oriented (m2m) interfaces to your content/services </li></ul><ul><li>not c...
Allow searching… <ul><li>support distributed searching of your content by remote services </li></ul><ul><li>offer Bath Pro...
Allow harvesting… <ul><li>enable remote services to gather your metadata records </li></ul><ul><li>offer Open Archives Ini...
Share news/alerts using RSS <ul><li>offer machine-readable news and alerting channel(s) </li></ul><ul><li>news/alerts migh...
Become an OpenURL source <ul><li>adopt ‘open’, ‘context-sensitive’ linking in the form of OpenURLs </li></ul><ul><li>add O...
Become an OpenURL target <ul><li>allow links back into your services from OpenURL resolvers </li></ul><ul><li>publicise  y...
Use persistent IDs <ul><li>Z39.50, OAI-PMH and RSS expose your metadata to other services </li></ul><ul><li>allow deep-lin...
Authentication issues <ul><li>how do I control access? </li></ul><ul><li>same as currently - using Athens (or your own sys...
Branding vs. visibility <ul><li>will exposing metadata to external service lead to loss of branding? </li></ul><ul><li>not...
Final thought... <ul><li>not just about a one-way low of information - from ‘you’ to ‘us’ </li></ul><ul><li>also exposes c...
Links to further information <ul><li>JISC Information Environment technical architecture </li></ul><ul><li>www.ukoln.ac.uk...
 
Upcoming SlideShare
Loading in …5
×

10 minute practical guide to the JISC Information Environment (for publishers!)

514 views

Published on

A presentation to the PALS meeting, London.

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

  • Be the first to like this

10 minute practical guide to the JISC Information Environment (for publishers!)

  1. 1. 10 minute practical guide to the JISC Information Environment (for p ublishers ! ) Andy Powell UKOLN, University of Bath [email_address] 21 June 2002
  2. 2. What do you need to do? <ul><li>support machine oriented (m2m) interfaces to your content/services </li></ul><ul><li>not contentious... </li></ul><ul><ul><li>in line with ‘Web services’ approach </li></ul></ul><ul><li>not just about ‘portals’... </li></ul><ul><ul><li>subject portal, reading list tool in VLE, library ‘portal’ (e.g. Zportal or MetaLib), SFX service component, personal desktop reference manager </li></ul></ul>
  3. 3. Allow searching… <ul><li>support distributed searching of your content by remote services </li></ul><ul><li>offer Bath Profile compliant Z39.50 target </li></ul><ul><li>use Z39.50 to expose simple Dublin Core metadata about your content </li></ul><ul><li>note possible use of SOAP (Simple Object Access Protocol) in the future </li></ul>
  4. 4. Allow harvesting… <ul><li>enable remote services to gather your metadata records </li></ul><ul><li>offer Open Archives Initiative repository using the OAI Protocol for Metadata Harvesting </li></ul><ul><li>use OAI-PMH to expose simple DC metadata about your content </li></ul><ul><li>‘ as well as’ OR ‘instead of’ offering Z39.50 target </li></ul>
  5. 5. Share news/alerts using RSS <ul><li>offer machine-readable news and alerting channel(s) </li></ul><ul><li>news/alerts might include </li></ul><ul><ul><li>service announcements </li></ul></ul><ul><ul><li>list(s) of new resources </li></ul></ul><ul><li>RSS = RDF Site Summary </li></ul><ul><ul><li>simple XML application </li></ul></ul><ul><li>use RSS in addition to existing email alerting </li></ul>
  6. 6. Become an OpenURL source <ul><li>adopt ‘open’, ‘context-sensitive’ linking in the form of OpenURLs </li></ul><ul><li>add OpenURLs into search results </li></ul><ul><ul><li>e.g. SFX buttons next to each result </li></ul></ul><ul><li>support mechanism to associate preferred OpenURL resolver with each user </li></ul><ul><ul><li>e.g. cookies or user-preferences database </li></ul></ul>
  7. 7. Become an OpenURL target <ul><li>allow links back into your services from OpenURL resolvers </li></ul><ul><li>publicise your ‘link-to’ syntax, e.g. </li></ul><ul><ul><li>ISSN-based URLs </li></ul></ul><ul><ul><li>DOI-based URLs </li></ul></ul><ul><li>support deep-linking direct to resources </li></ul><ul><ul><li>direct to resource, OR </li></ul></ul><ul><ul><li>indirect via abstract page </li></ul></ul>
  8. 8. Use persistent IDs <ul><li>Z39.50, OAI-PMH and RSS expose your metadata to other services </li></ul><ul><li>allow deep-linking from metadata (e.g. search results) to resource </li></ul><ul><li>deep-linking URLs should be unique and persistent </li></ul><ul><ul><li>possibly based on DOIs </li></ul></ul><ul><li>why? allows long-term use of URLs, e.g. in course reading list </li></ul>
  9. 9. Authentication issues <ul><li>how do I control access? </li></ul><ul><li>same as currently - using Athens (or your own system) </li></ul><ul><ul><li>user challenged on entry to ‘portal’ </li></ul></ul><ul><ul><li>portal can determine some ‘search’ access rights from Athens, but you may need to ‘trust’ portal </li></ul></ul><ul><ul><li>ZBLSA portal/pub query mechanism </li></ul></ul><ul><ul><li>you retain final control at point of access </li></ul></ul>
  10. 10. Branding vs. visibility <ul><li>will exposing metadata to external service lead to loss of branding? </li></ul><ul><li>not really - expect external services to carry your branding as ‘quality stamp’ </li></ul><ul><ul><li>e.g. RSS channel carries your name, URL and logo </li></ul></ul><ul><li>following URL in search results leads direct to your site </li></ul><ul><ul><li>so more visibility rather than less </li></ul></ul>
  11. 11. Final thought... <ul><li>not just about a one-way low of information - from ‘you’ to ‘us’ </li></ul><ul><li>also exposes content within the academic community </li></ul><ul><li>for example... </li></ul><ul><ul><li>RDN offers Z39.50 access to 50,000 resource descriptions (soon to offer SOAP interface) </li></ul></ul><ul><ul><li>you can integrate this into your ‘portals’ </li></ul></ul>
  12. 12. Links to further information <ul><li>JISC Information Environment technical architecture </li></ul><ul><li>www.ukoln.ac.uk/distributed-systems/dner/arch/ </li></ul><ul><li>JISC Information Environment and Web services </li></ul><ul><li>www.ariadne.ac.uk/issue31/information-environments/ </li></ul>

×