DNER Architecture Andy Powell, Liz Lyon UKOLN, University of Bath [email protected]www.ukoln.ac.uk Consultative group, Charity Centre, London 16 Feb 2001 UKOLN is funded by Resource: The Council for Museums, Archives and Libraries, the Joint Information Systems Committee (JISC) of the Higher and Further Education Funding Councils, as well as by project funding from the JISC and the European Union. UKOLN also receives support from the University of Bath where it is based.
DNER Architecture. Andy Powell, Liz Lyon UKOLN, University of Bath [email protected] www.ukoln.ac.uk Consultative group, Charity Centre, London 16 Feb 2001. - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
DNER ArchitectureAndy Powell, Liz LyonUKOLN, University of Bath
UKOLN is funded by Resource: The Council for Museums, Archives and Libraries, the Joint Information Systems Committee (JISC) of the Higher and Further Education Funding Councils, as well as by project funding from the JISC and the European Union. UKOLN also receives support from the University of Bath where it is based.
2
Overview
• scope - what is the DNER?• functional model - builds on scenarios• entity model - what are we dealing with?• network systems architecture• discover• locate, request, deliver• other shared services
3
General questions
• please raise them!• is this a coherent view• what’s wrong?• what’s missing?• there are gaps - need to try and fill them• ...in this study or further work
4
Aims
• validate current thinking• raise issues generally• specifically, think about
• is a set of content• is an information environment that provides
secure and convenient access to that content• is comprehensive?• is managed?• complements institutional and other resources• weaves rich information resources into the fabric
of the Web
• provides cost-effective support for new modes of learning, research and communication
7
What’s in the DNER
• a national, strategicresource.
• licensed, created• available through data centres, ...
• a framework for access to a community resource• deposit - AHDS, data archive, ...• discovery - archives hub, COPAC, …• extend to local informational assets
• access to a quality controlled global resource • Resource Discovery Network, A&I services
8
Primary Content
Secondary Content
Funded
Institutional
External
Web
pag
es
Museum
s
home pages
thes
es
research papers
OPACs
Institutional gateways
Google Yahoo
No
rthe
rnL
igh
tRDN A&I
imagesFull-textstatistics
Map data
COPAC
Amazon
Public libraries
cour
sew
are
DNER content map
9
User view
• personalised landscape• own information foremost• …then
• institutional (Intranet/MLE)•external•DNER
• subject focus• media-type focus
10
Scope summary...
• stuff is…• local / remote•primary / secondary•digital / physical•policy controlled / non-policy controlled• in / out
• process includes•discover / locate and access•use / reuse / create• receive / provide
11
DNER Collections• content typically in the form of
‘collections’• collections of stuff (text, images, data, ...)• collections of metadata about stuff (e.g
subject gateway’s Internet Resource Catalogues)
• services make stuff available• people access stuff thru services
12
Primary DNER entities
Content
Person Service
Functional Model
14
Web Web Web Web Web
Currently...Content
End-user
15
Functional model
• think about what people are doing (or want to do) with the DNER
• based on MODELS verbs•discover, locate, request, deliver
• ...and later MODELS Information Architecture work
• addition of new verbs• modelled using UML• generic - applicable to finding Web
resources, buying books, buying cars, ...
16
High-level view
discover
locate
useRecord
request
deliver
useResource
enterinitiate
initiate
initiate
initiate
initiate
initiate
initiate
user provider
• discover, locate, request, deliver• enter, useRecord, useResource added• user-need -> item on desktop (virtual or physical)
and use
17
enter
enter
authenticate landscape<<use>><<use>>
initiate
user provider
• user visits Web service• login (using Athens - may have ‘guest’ account)• service builds personalised landscape (view of
• discover - drill-down• same strategies used in each• user-need -> metadata about ‘work’ (book or article) or ‘item’ (Web
resource)
19
detail
detail
locate format
initiate
user providerratings conditions initiate
• locate is instance of getting more ‘detail’ about a resource
• locations, formats, ratings, terms & conditions• metadata about ‘work’ -> metadata about ‘item’
20
useRecord
useRecord
annotate
initiate
user providerremember share
• locate is instance of getting more ‘detail’ about a resource
• locations, formats, ratings, terms & conditions
• metadata about ‘work/item’ -> richer metadata about ‘work/item’ and location of ‘item’ or ‘delivery service’ for ‘item’
21
request/access
request
authorise
access
download deliver
initiate
initiate
initiate
initiate
initiateuser provider
• authorisation required before access• download (user initiated, e.g. clicking on link)• deliver (provider initiated, e.g. Amazon delivering book)• metadata about ‘work/item’ and location of ‘item’ or ‘delivery
service’ for ‘item’ -> item
22
useResource
incorporate
initiate
user providerview storeunpack process
useResource
• not thoroughly modelled here
• unpack - e.g. dealing with IMS package
• view - simplest case (looking at document)
• process - run software
• incorporate - embed into multimedia essay
• store, share, publish(?)
23
DNER information flow
discover
useRecorddetail
request
access
useResource
24
DNER information flow
• DNER not just a ‘provider to user’ flow• users are both recipients of and creators
of both primary and secondary content• DNER architecture needs to support
• collaboration•creation
• …as well as discovery, etc.• current work on architecture doesn’t really
address this. Does that matter?
Network Systems Architecture
26
Web Web Web Web Web
Currently...Content
End-user
Current services offer mix of survey, discover, detail, request, access, useRecord functionality
End-user needs to join services together manually as well as learning multiple user interfaces
27
Web Web Web Web Web
Currently...Content
End-user
Need to think about what shared services might be required to offer functionality
Also useful to think about what entities are being dealt with
28
enter
enter
authenticate landscape<<use>><<use>>
initiate
user provider
• Shared services• authentication• user-profiling• collection description• service description
• what is identified...?• the resource (image, text, map, data,
sound, ...)• the resource in context (e.g.
embedded into VADS page)• metadata about the resource (e.g.
from subject gateway)
62
Identifiers
• could use URLs, PURLs, DOIs, ... but...• URLs, locators not identifiers• DOIs and PURLs resolved centrally• all resolve to same thing irrespective of
who/where the user is. E.g.• 10.1045/october2000-granger always resolves
to US version even though D-Lib mirrored in UK• http://purl.org/dc always resolves to US version
even though DC pages mirrored in UK
• DOI and PURL resolved thru US resolver
63
Web content - issues
• Need guidelines on good practice for using URIs?
• Need to investigate possibilities for use of DOIs?
• Other suggestions?
locate, request, deliver
65
Multiple-item content
• For mutiple-item content, need to move from discovery thru locate, request and access
• move from generic ‘work’ to particular ‘item’
• find appropriate copy• location is context sensitive - need to
know who, where end-user is• best carried out locally to end-user?
66
Physical content
• discover typically results in metadata about the ‘work’ or a global identifier (ISBN or ISSN)
• in other words, a citation for the resource• need to encode citation in machine
readable way• need to resolve citation in context
sensitive way
67
Locate and identifiers
Discover
Locate
Request
ISBN
Item URL
URI DOI
OpenURL or Z39.50 request
Citation/metadata
Discovery services
Web resource BookJournal issue Article
Delivery service URLor
Item URL
Locate services
Persistent ‘identifiers’- context independent
Transient ‘locators’- context sensitive
68
OpenURL
• OpenURL - way to encode citation for a resource
• OpenURL = BaseURL + Description• BaseURL = http://sfx.bath.ac.uk/sfxmenu• Description = Origin + ObjectDescription• ObjectDescription is either a global
identifier (e.g. A DOI) or a description (a citation) or a local identifier of some kind