1 / 79

DNER Architecture

DNER Architecture. Andy Powell, Liz Lyon UKOLN, University of Bath a.powell@ukoln.ac.uk www.ukoln.ac.uk Consultative group, Charity Centre, London 16 Feb 2001.

emil
Download Presentation

DNER Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DNER Architecture Andy Powell, Liz Lyon UKOLN, University of Bath a.powell@ukoln.ac.uk 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.

  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 • user-profiles • collection description • service description • authentication? • thesauri/terminology • recommendations

  5. Scope

  6. The DNER... • 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. DNER content map External Public libraries home pages Web pages Institutional Museums theses Funded courseware Map data research papers Full-text Primary Content images statistics Northern Light RDN Secondary Content A&I COPAC OPACs Amazon Institutional gateways Yahoo Google

  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

  13. 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. enter discover locate useRecord request deliver useResource High-level view initiate initiate initiate initiate initiate user provider initiate initiate • discover, locate, request, deliver • enter, useRecord, useResource added • user-need -> item on desktop (virtual or physical) and use

  17. enter authenticate landscape enter initiate <<use>> <<use>> user provider • user visits Web service • login (using Athens - may have ‘guest’ account) • service builds personalised landscape (view of available resources)

  18. discover survey savedList savedList search search alert queryAssist browse browse alert queryAssist survey/discover initiate initiate <<use>> <<extend>> initiate user provider initiate <<use>> • survey - high-level collection description search (narrows or widens landscape) • discover - drill-down • same strategies used in each • user-need -> metadata about ‘work’ (book or article) or ‘item’ (Web resource)

  19. detail locate format ratings conditions detail initiate initiate user provider • locate is instance of getting more ‘detail’ about a resource • locations, formats, ratings, terms & conditions • metadata about ‘work’ -> metadata about ‘item’

  20. remember useRecord annotate share useRecord initiate user provider • 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 authorise access download deliver request/access initiate initiate initiate user provider initiate initiate • 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. view unpack useResource incorporate store process useResource initiate user provider • 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 useResource detail useRecord access request

  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?

  25. Network Systems Architecture

  26. Web Web Web Web Web Currently... Content End-user needs to join services together manually as well as learning multiple user interfaces Current services offer mix of survey, discover, detail, request, access, useRecord functionality End-user

  27. Web Web Web Web Web Currently... Content Need to think about what shared services might be required to offer functionality Also useful to think about what entities are being dealt with End-user

  28. enter authenticate landscape enter initiate <<use>> <<use>> user provider • Shared services • authentication • user-profiling • collection description • service description • Entities • person/role • (group) • (organisation) • collection • service

  29. survey savedList search browse alert queryAssist survey initiate initiate user <<use>> provider <<extend>> • Shared services • collection description • thesauri/terminology • Entities • collection

  30. discover savedList search queryAssist browse alert discover initiate user provider initiate <<use>> • Shared services • service description • metadata registry • terminology/thesauri • Entities • collection • service • schema • work • item

  31. detail locate format ratings conditions detail initiate initiate user provider • Shared services • locate • ratings • (terms & conditions) • service description • Entities • work • item • service

  32. remember useRecord annotate share useRecord initiate user provider • Shared services • (bookmark) • (annotation) • Entities • work • item

  33. request authorise access download deliver request/access initiate initiate initiate user provider initiate initiate • Shared services • authorisation • Entities • item • service • person

  34. view unpack useResource incorporate store process useResource initiate user provider • Shared services • Entities • item

  35. discover savedList search queryAssist browse alert discover initiate user provider initiate <<use>> • Shared services • service description • metadata registry • terminology/thesauri • Entities • collection • service • schema • work • item

  36. DNER Entities comprises Role Service providesAccessTo accesses fulfils Profile Person Content has offers isMemberOf has owns isPartOf Group Organisation is hasPart

  37. DNER shared services • authentication • user-profiling • collection description • thesauri/terminology • metadata registry • service description • location (ratings, terms & conditions) • authorisation

  38. Currently... Content Web Web Web Web Authentication End-user

  39. Currently... Content Web Web Web Web Collection description User-profiling Authentication End-user

  40. Shared service model Content Web Web Web Web Authentication Authorisation User-profile Collection Desc Service Desc Thesauri, ... End-user

  41. Joining things together • Framework for shared services • DNER as coherent whole rather than lots of stand-alone services • two areas in particular • discovery • finding stuff from multiple content providers • locate/request/deliver • streamlining access

  42. Discover

  43. Discover • services need to expose Web content for machine use • m2m • expose metadata using search, harvesting or alerting protocols • expose data in machine-readable and persistent ways

  44. Fusion? • In order to remove need for end-user to discover across several individual services • develop services that bring stuff together • fusion • portals • presentation services • searching vs. sharing • alerting Note: I don’t like these words!

  45. Presentation services • ...lots!? • subject portals • data centre portals • institutional portals • personal portals (agents) • virtual learning environments

  46. Searching Content Web Web Web Web Authentication Z39.50 Bath Profile Authorisation User-profile Collection Desc Presentation Service Desc Thesauri, ... End-user

  47. Searching Content Web Web Web Web Z39.50 Bath Profile brokers and gateways Authentication Authorisation Broker User-profile Collection Desc Presentation Service Desc Thesauri, ... End-user

  48. Z39.50 - Bath Profile • cross-domain focus (in part) • DC XML records • DTD-based rather than XML Schema

  49. Sharing Content Web Web Web Web Open Archives Initiative Authentication Authorisation User-profile Collection Desc Presentation Service Desc Thesauri, ... End-user

  50. Sharing Content Open Archives Initiative Web Web Web Web Authentication Authorisation Aggregator User-profile Collection Desc Presentation Service Desc Thesauri, ... End-user

More Related