RDN Architecture - PowerPoint PPT Presentation

About This Presentation
Title:

RDN Architecture

Description:

BIOME. EMC. Hubs. Centre. HUMBUL. SciGate. Creative Arts. and Industries. MODELS 9 - Oct 99 ... BIOME. Hub Broker. MODELS 9 - Oct 99. 6. Terminology recap ... – PowerPoint PPT presentation

Number of Views:14
Avg rating:3.0/5.0
Slides: 12
Provided by: andyp74
Category:

less

Transcript and Presenter's Notes

Title: RDN Architecture


1
RDN Architecture
Andy Powell UKOLN, University of
Bath a.powell_at_ukoln.ac.uk http//www.ukoln.ac.uk/
UKOLN is funded by the Library and Information
Commission, the Joint Information Systems
Committee of the Higher 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
Organisational architecture
BIOME
Hubs
SOSIG
SOSIG
RDNC
EMC
  • HUMBUL
  • SciGate
  • Creative Artsand Industries
  • ...

Centre
3
Gateway architecture
Gateways
SOSIG
SOSIG
BIOME
OMNI
Biz/Ed
SOSIG
EEVL
EMC
4
RDNC Broker
SOSIG
SOSIG
BIOME
RDNC Broker ResourceFinder
EMC
5
Hub Brokers
SOSIG
SOSIG
BIOME
Hub Broker
EMC
6
Terminology recap
  • hub - an organisation offering various services
  • gateway - a resource discovery service offered by
    a hub - aka, subject gateway
  • broker - a proxy that connects to one or more
    services on behalf of the user. E.g. the RDN
    ResourceFinder
  • portal - a Z39.50 broker (DNER usage!)

7
Protocols - Z39.50
  • gateways MUST support Z39.50
  • gateways MUST support the Bath Profile
  • the Bath Profile is...
  • new - still under development
  • DC based
  • search on sub-set of DC attributes from Bib-1
  • results returned using DC/XML (DC DTD) or DC/SUTRS

8
Protocols - Whois
  • gateways MAY support Whois
  • if so, MUST support CIP (for cross-searching)
  • strongly encouraged to use registered Template
    Types
  • DOCUMENT and SERVICE templates in common usage
  • DUBLINCORE template type may cause
    interoperability problems

9
Cataloguing Rules
  • need rules to provide consistent record creation
    across the RDN
  • basis for current and future services
  • enhanced ROADS Cataloguing Guidelines
  • Bath Profile guidelines required
  • need to formulate guidelines in implementation
    independent way

10
Classification
  • subject classification across RDN for Keywords
    (DC.Subject) attribute
  • subject specific vs. broad scheme
  • RDNC TopicFinder
  • thesauri usage
  • other lists may also be required
  • e.g. Category (DC.Type) attribute - this is a
    learning resource

11
Collection Description
  • hubs provide many services
  • RDNC ServiceFinder...
  • a ROADS database of hub service (collection)
    descriptions
  • searchable
  • currently maintained centrally
  • move to distributed maintenance by hubs
  • basis for selective cross-hub services
Write a Comment
User Comments (0)
About PowerShow.com