Resource Discovery Landscape

  • 344 views
Uploaded on

A presentation to the Joint JIIE/JCS Meeting 2005, London

A presentation to the Joint JIIE/JCS Meeting 2005, London

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
344
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. UKOLN is supported by: Resource Discovery Landscape Andy Powell, UKOLN, University of Bath [email_address] Joint JIIE/JCS Meeting 2005, London www.bath.ac.uk a centre of expertise in digital information management www.ukoln.ac.uk
  • 2. Contents
    • general issues
    • provision
    • fusion
    • presentation
    • shared infrastructure
    Based on main headings in the study…
  • 3. JISC IE and Google
    • previous paper considered relationships between JISC IE and Google:
      • complimentary rather than alternative approaches
      • develop guidance for exposing content to Google
      • investigate use of Google APIs
      • special treatment for community’s ‘high-quality’ material – c.f. Google Scholar
      • encouraging use of OpenURLs by academic and commercial content providers
    http://www.ukoln.ac.uk/distributed-systems/jisc-ie/arch/ie-google/
  • 4. General issues
    • service oriented ‘frameworks’
    • maturity of the JISC IE
    • manual vs. automated approaches
    • semantic Web
    • community-driven activities
    • p2p
  • 5. General issues
    • service oriented approaches
    • maturity of the JISC IE
    • manual vs. automated approaches
    • semantic Web
    • community-driven activities
    • p2p
  • 6. General issues
    • service oriented approaches
    • maturity of the JISC IE
    • manual vs. automated approaches
    • semantic Web
    • community-driven activities
    • p2p
  • 7. General issues
    • service oriented approaches
    • maturity of the JISC IE
    • manual vs. automated approaches
    • semantic Web
    • community-driven activities
    • p2p
  • 8. General issues
    • service oriented approaches
    • maturity of the JISC IE
    • manual vs. automated approaches
    • semantic Web
    • community-driven activities
    • p2p
  • 9. General issues
    • service oriented approaches
    • maturity of the JISC IE
    • manual vs. automated approaches
    • semantic Web
    • community-driven activities
    • p2p
  • 10. Provision layer issues
    • the ‘R’ word
    • complex objects
    • metasearch vs. full-text indexing
    • simple search interfaces
    • identifiers
    repository eprint archive learning object repository CMS
  • 11. Provision layer issues
    • the ‘R’ word
    • complex objects
    • metasearch vs. full-text indexing
    • simple search interfaces
    • identifiers
    eprint (work) PDF manifestation PDF (manifestation) MS-Word (manifestation) PDF (manifestation) MS-Word (manifestation) eprint (work) now: expose separate simple objects (metadata only) future: expose complex objects (metadata and full text)
  • 12. Provision layer issues
    • the ‘R’ word
    • complex objects
    • metasearch vs. full-text indexing
    • simple search interfaces
    • identifiers
    Do I make my content available for indexing by Google or do I make my metadata available for harvesting using OAI-PMH? Do I support Z39.50 or SRW? What do I do about OpenURLs?
  • 13. Provision layer issues
    • the ‘R’ word
    • complex objects
    • metasearch vs. full-text indexing
    • simple of search interfaces
    • identifiers
    Z39.50 SRW Google API A9 Opensearch complexity
  • 14. Provision layer issues
    • the ‘R’ word
    • complex objects
    • metasearch vs. full-text indexing
    • simple search interfaces
    • identifiers
    What did this identifier used to identify? Has this resource already been assigned an identifier? How do I resolve this identifier?
  • 15. Fusion layer issues
    • union catalogues and Google
    • indexing and data mining
    • hiding a complex provision layer
    • performance measurement
  • 16. Fusion layer issues
    • union catalogues and Google
    • indexing and data mining
    • hiding a complex provision layer
    • performance measurement
  • 17. Fusion layer issues
    • union catalogues and Google
    • indexing and data mining
    • hiding a complex provision layer
    • performance measurement
    fusion layer ‘federator’ repository repository repository repository repository portal portal portal portal portal heterogeneous - metadata formats, content formats, identifiers, packaging standards homogeneous - metadata formats, content formats, identifiers, packaging standards
  • 18. Fusion layer issues
    • union catalogues and Google
    • indexing and data mining
    • hiding a complex provision layer
    • performance measurement
  • 19. Presentation layer issues
    • the ‘P’ word
    • the other ‘P’ word
    • OpenURL ‘link servers’
      • making openurl.ac.uk work globally
      • making OpenURLs work as URIs
    Why do I need a portal when I’ve got Firefox, Google and my favourite RSS channel reader installed on my desktop?
  • 20. Presentation layer issues
    • the ‘P’ word
    • the other ‘P’ word
    • OpenURL ‘link servers’
      • making openurl.ac.uk work globally
      • making OpenURLs work as URIs
    > portlets WSRP JSR 168
  • 21. Presentation layer issues
    • the ‘P’ word
    • the other ‘P’ word
    • OpenURL ‘link servers’
      • making openurl.ac.uk work globally
      • making OpenURLs work as URIs
    http://sfx4.exlibrisgroup.com:9003/bath?sid=ISI%3AWoS &issn=0213-3911&date=2005&spage=575&volume=20&issue=2 http://openurl.ac.uk/?sid=ISI%3AWoS &issn=0213-3911&date=2005&spage=575&volume=20&issue=2 http://???/?sid=ISI%3AWoS &issn=0213-3911&date=2005&spage=575&volume=20&issue=2 works for member of University of Bath works for member of UK university works for everyone
  • 22. Shared services issues
    • distributed service registries
    • metadata schema registries
    • identifier services
    • terminology services
    • licensing services
      • who’s using what licences?
      • ensuing persistence of licensing agreements?
    • automated metadata-generation tools
    • name authority services
    Note: I’m not going to talk about AAA
  • 23. Shared services issues
    • distributed service registries
    • metadata schema registries
    • identifier services
    • terminology services
    • licensing services
      • who’s using what licences?
      • ensuing persistence of licensing agreements?
    • automated metadata-generation tools
    • name authority services
  • 24. Shared services issues
    • distributed service registries
    • metadata schema registries
    • identifier services
    • terminology services
    • licensing services
      • who’s using what licences?
      • ensuing persistence of licensing agreements?
    • automated metadata-generation tools
    • name authority services
  • 25. Shared services issues
    • distributed service registries
    • metadata schema registries
    • identifier services
    • terminology services
    • licensing services
      • who’s using what licences?
      • ensuing persistence of licensing agreements?
    • automated metadata-generation tools
    • name authority services
  • 26. Shared services issues
    • distributed service registries
    • metadata schema registries
    • identifier services
    • terminology services
    • licensing services
      • who’s using what licences?
      • ensuing persistence of licensing agreements?
    • automated metadata-generation tools
    • name authority services
  • 27. Shared services issues
    • distributed service registries
    • metadata schema registries
    • identifier services
    • terminology services
    • licensing services
      • who’s using what licences?
      • ensuing persistence of licensing agreements?
    • automated metadata-generation tools
    • name authority services
  • 28. Shared services issues
    • distributed service registries
    • metadata schema registries
    • identifier services
    • terminology services
    • licensing services
      • who’s using what licences?
      • ensuing persistence of licensing agreements?
    • automated metadata-generation tools
    • name authority services
  • 29. Conclusions
    • the study makes 26 suggestions – too many to consider here – but general need to recognise that…
      • our services are not (and will never be) the sole focus of the end-user’s attention
      • our services fit into broader fabric of the Internet – therefore need to be able to be integrated by others
      • some things are better done by others
      • possible tension between Web-based ‘portal and browser ‘desktop application framework’ approaches
      • need to align eLeaning and ‘digital library’
  • 30. Questions?