1 the ridir project identifier interoperability between repositories vif workshops 22 nd april 2008...

12
1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

Upload: rosalyn-booth

Post on 03-Jan-2016

215 views

Category:

Documents


3 download

TRANSCRIPT

Page 1: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

1

The RIDIR Project

Identifier interoperability between repositories

VIF Workshops22nd April 2008

Richard Green (University of Hull)

Page 2: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

2

What’s an identifier?

In the context of RIDIR’s work, an identifier is simply a label associated with some content.

Maybe:an object identifier: hull:34a web address:

edocs.hull.ac.uk/fedora/get/hull:34a handle or DOI: http://dx.doi.org/10.1000/182

but...

Page 3: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

3

Identifiers

...it could also be:an ISBN: 1 85074 895 0a catalogue entry: 007C8371a title: Stonehenge – a history in photographs...

Identifiers may be unique, they may not. The RIDIR Project is building a demonstrator to show how identifiers stored in repositories could aid interoperability

Page 4: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

4

Two over-arching use cases

An object moves outside its original curation boundary and becomes ‘lost’. The original URL generates a ‘404 error’. How to find the object and preserve the knowledge?

A user discovers a potentially useful object and wants to see related digital content that may be of use. How to find such content and preserve the knowledge?

Page 5: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

5

Identifiers to the rescue!

In either situation the user will need to search for the desired objects.

Embedding of identifiers in the object metadata provides a starting point for discovery. ANY identifier is better than none!

...but how to record and systematise the discovery results – and who says they are right?

Page 6: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

6

RIDIR

The RIDIR system will provide a discovery tool with integrated facilities for

recording and persisting relationships(relationships can be authoritative or non-authoritative)

recalling links to related resources and associated metadata

Page 7: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

7

Relationships

Relationships in the system can be built up over a period of time.

A user can navigate an existing network of relationships and/or add to them.

Potentially a wide range of relationships, but we need to keep some control...

Page 8: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

8

Relationships

Possible examples:

PrintisSameAsisVersionOf (!) [needs more granularity]isExtractFrom

BroadcastisSameAsisExtractFromisSignedVersionOfisRepeatOf

etc

Page 9: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

9

A broadcast exampleSpoken Word Services

Excess Baggage

Guest presenter: John McCarthy

TRILTTelevision Index for Learning and Teaching

Excess Baggage

Sandy Toksvig withtravellers’ tales

Spoken Word ServicesPodcast

Broadcast 1 clip

Excess Baggage clip

Broadcast n clip

hasFurtherDetailAtisSameAs

isExtractFrom

Page 10: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

10

RIDIR scopeRIDIR users

RIDIR demonstrator applications

PIMS

RIDIR repository services

Mulgara triple-store

Fedora Repository Services

Resource Index API

Fedora object store

RIDIR core services

RIDIR API

Discovery Services

RIDIR Discovery API

IRSThe

European Library?

xISBN?

User Interface

Application Services and Logic

Fedora API

create/update/delete “identified

thing”

create/update/delete

“relationship”

query and return results

static entry page

browse & edit objects,

relationships & metadata

search

view resource

add new object, relationships &

metadata

“Depot” application logic “Locate Related Version” application logic

view candidate matches

“new identifier” splash page

depot common locate related version

Resolution AccessQuery

Browser404 detector

plugin

Browser404 detector

plugin

Browser404 detector

plugin

RIDIR Core Scope

query

Institutional Repositories

Note that this diagram represents a first pass at a structure and will be refined in the completed demonstrator

Page 11: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

11

VIF and RIDIR

Identifiers are key to establishing relationships

Clear identification of ‘versions’ important

Any identifiers, all identifiers, aid discovery

Page 12: 1 The RIDIR Project Identifier interoperability between repositories VIF Workshops 22 nd April 2008 Richard Green (University of Hull)

12

Contact etc

Website: www.hull.ac.uk/ridir

Project Manager: Richard Green ([email protected])