resource discovery landscape

30
UKOLN is supported by: Resource Discovery Landscape Andy Powell, UKOLN, University of Bath [email protected] Joint JIIE/JCS Meeting 2005, London www.bath.ac.u k a centre of expertise in digital information management www.ukoln.ac.u k

Upload: andy-powell

Post on 05-Dec-2014

911 views

Category:

Education


0 download

DESCRIPTION

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

TRANSCRIPT

Page 1: Resource Discovery Landscape

UKOLN is supported by:

Resource Discovery Landscape

Andy Powell, UKOLN, University of Bath

[email protected]

Joint JIIE/JCS Meeting 2005, London

www.bath.ac.uk

a centre of expertise in digital information management

www.ukoln.ac.uk

Page 2: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 2

Contents

• general issues• provision• fusion• presentation• shared infrastructure

Based on main headings in the study…

Based on main headings in the study…

Page 3: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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/http://www.ukoln.ac.uk/distributed-systems/jisc-ie/arch/ie-google/

Page 4: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 4

General issues

• service oriented ‘frameworks’• maturity of the JISC IE• manual vs. automated approaches• semantic Web• community-driven activities• p2p

Page 5: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 5

General issues

• service oriented approaches• maturity of the JISC IE• manual vs. automated approaches• semantic Web• community-driven activities• p2p

Page 6: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 6

General issues

• service oriented approaches• maturity of the JISC IE• manual vs. automated approaches• semantic Web• community-driven activities• p2p

Page 7: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 7

General issues

• service oriented approaches• maturity of the JISC IE• manual vs. automated approaches• semantic Web• community-driven activities• p2p

Page 8: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 8

General issues

• service oriented approaches• maturity of the JISC IE• manual vs. automated approaches• semantic Web• community-driven activities• p2p

Page 9: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 9

General issues

• service oriented approaches• maturity of the JISC IE• manual vs. automated approaches• semantic Web• community-driven activities• p2p

Page 10: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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

Page 11: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 11

Provision layer issues

• the ‘R’ word• complex objects• metasearch vs. full-text indexing• simple search interfaces• identifiers

eprint (work)

PDFmanifestation

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)

Page 12: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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?

Page 13: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 13

Provision layer issues

• the ‘R’ word• complex objects• metasearch vs. full-text indexing• simple of search interfaces• identifiers

Z39.50

SRW

Google APIA9

Opensearchcom

ple

xit

y

Page 14: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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?

Page 15: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 15

Fusion layer issues

• union catalogues and Google• indexing and data mining• hiding a complex provision layer• performance measurement

Page 16: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 16

Fusion layer issues

• union catalogues and Google• indexing and data mining• hiding a complex provision layer• performance measurement

Page 17: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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 - metadataformats, content formats,identifiers, packagingstandards

homogeneous - metadataformats, content formats,identifiers, packagingstandards

Page 18: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 18

Fusion layer issues

• union catalogues and Google• indexing and data mining• hiding a complex provision layer• performance measurement

Page 19: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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?

Page 20: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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

WSRPJSR 168

Page 21: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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 memberof University of Bath

works for memberof UK university

works for everyone

Page 22: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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

Note: I’m not going to talk about AAA

Page 23: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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

Page 24: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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

Page 25: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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

Page 26: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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

Page 27: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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

Page 28: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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

Page 29: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 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’

Page 30: Resource Discovery Landscape

                                                             

Joint JIIE/JCS Meeting 30

Questions?