1 / 11

RDN Architecture

RDN Architecture. Andy Powell UKOLN, University of Bath a.powell@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

lacota-pacheco
Download Presentation

RDN 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. RDN Architecture Andy Powell UKOLN, University of Bath a.powell@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 • HUMBUL • SciGate • Creative Artsand Industries • ... EMC Centre MODELS 9 - Oct 99

  3. Gateway architecture Gateways SOSIG SOSIG BIOME OMNI Biz/Ed SOSIG EEVL EMC MODELS 9 - Oct 99

  4. RDNC Broker SOSIG SOSIG BIOME RDNC Broker ‘ResourceFinder’ EMC MODELS 9 - Oct 99

  5. Hub Brokers SOSIG SOSIG BIOME Hub Broker EMC MODELS 9 - Oct 99

  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!) MODELS 9 - Oct 99

  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 MODELS 9 - Oct 99

  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 MODELS 9 - Oct 99

  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 MODELS 9 - Oct 99

  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’ MODELS 9 - Oct 99

  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 MODELS 9 - Oct 99

More Related