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
Contents
general issues
provision
fusion
presentation
shared infrastructure
Based on main headings in the study…
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
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)
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?
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
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?
Why do I need a portal when I’ve got Firefox, Google and my favourite RSS channel reader installed on my desktop?
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
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
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
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
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
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
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
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
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
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
0 comments
Post a comment