1 / 14

Dublin Core in Z39.50: The Bath Profile

Learn about the Bath Profile, a solution addressing interoperability challenges in Z39.50, allowing remote searching of databases and cross-domain searches. Discover its functional areas and levels of conformance.

barbarabrock
Download Presentation

Dublin Core in Z39.50: The Bath Profile

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. Dublin Core in Z39.50:The Bath Profile Paul Miller Interoperability Focus UK Office for Library & Information Networking (UKOLN) P.Miller@ukoln.ac.uk http://www.ukoln.ac.uk/ UKOLN is funded by the Library and Information Commission, the Joint Information Systems Committee (JISC) 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 Universities of Bath and Hull where staff are based.

  2. Introducing Z39.50 • North American Standard (ANSI/NISO Z39.50–1995 [version 3]) • International Standard (ISO 23950) • Originally library–centric • Permits remote searching of databases • Access via Z client or over web • Relies upon ‘Profiles’ • CIMI profile for cultural heritage • GEO profile for Geospatial data. See http://www.ariadne.ac.uk/issue21/z3950/

  3. Z39.50 Challenges • Profiles for each discipline • Defeats interoperability? • Vendor interpretation of the standard • Bib–1 bloat • Largely invisible to the user • Seen as complicated, expensive and old–fashioned • Surely no match for XML/RDF/ whatever. See http://www.ariadne.ac.uk/issue21/z3950/

  4. DC and Z39.50 • Dublin Core Element Set can be seen within Z39.50 in a number of ways… • As a mapping from DC Elements to Bib–1 Use Attributes • DC Title = Use Attribute 4 (Title) • DC Subject = Use Attributes 21, 22, 23, etc. • As separate Use Attributes in their own right • DC Title = Use Attribute 1097 (DC–Title) • DC Creator = Use Attribute 1098 (DC–Creator), etc. • As a key aspect of the Cross–Domain Attribute Set in the new Attribute Architecture.

  5. Need for the Bath Profile • System vendors implement areas of the Z39.50 standard differently • Regional, National, and disciplinary Profiles have appeared over previous years, many of which have basic functions in common • Users wish to search across national/regional boundaries, and between vendors. See http://www.ukoln.ac.uk/interop–focus/activities/z3950/int_profile/bath/

  6. Accommodating the Profiles • The Bath Profile is heavily influenced by • ATS–1 • CENL • DanZIG • MODELS • ONE • Z Texas • vCUC See http://www.ukoln.ac.uk/interop–focus/activities/z3950/int_profile/bath/

  7. Accommodating the Profiles See http://www.ukoln.ac.uk/interop–focus/activities/z3950/int_profile/bath/

  8. Doing the work • ZIP–PIZ–L mailing list, hosted by National Library of Canada • Meeting face–to–face • The UK’s Joint Information Systems Committee (JISC) supported a face–to–face meeting in Bath over the summer • A draft, being widely circulated for comment. See http://www.ukoln.ac.uk/interop–focus/activities/z3950/int_profile/bath/

  9. What we’ve suggested • Minimisation of ‘defaults’ • Where possible, every attribute is defined in the Profile (Use, Relation, Position, Structure, Truncation, Completeness) • Three Functional Areas • Basic Bibliographic Search & Retrieval • Bibliographic Holdings Search & Retrieval • Cross–Domain Search & Retrieval • Three or more Levels of Conformance in each Area. See http://www.ukoln.ac.uk/interop–focus/activities/z3950/int_profile/bath/

  10. Cross–Domain S&R • Level 0 Search • Keyword Creator Search • Keyword Title Search • Keyword Subject Search • ‘Any’ Search. See http://www.ukoln.ac.uk/interop–focus/activities/z3950/int_profile/bath/

  11. Cross–Domain S&R • Level 1 Search • All of Level 0 and… • Greater control over location of terms in Creator/Subject/Title searches • Standard Identifier Search • Date of Publication Search. See http://www.ukoln.ac.uk/interop–focus/activities/z3950/int_profile/bath/

  12. Returning results across domains • At Level 0 in this Functional Area, results are returned as a SUTRS record • At Level 1 in this Functional Area, results must be returnable as either SUTRS or a Dublin Core record encoded with an XML DTD • Other record syntaxes are allowed, but this minimum must be supported. See http://www.ukoln.ac.uk/interop–focus/activities/z3950/int_profile/bath/

  13. http://www.ukoln.ac.uk/interop–focus/activities/z3950/int_profile/bath/http://www.ukoln.ac.uk/interop–focus/activities/z3950/int_profile/bath/ Soliciting comments from the community until 12 November, at which time we can revise the document accordingly. P.Miller@ukoln.ac.uk (me) bath–profile@ukoln.ac.uk (myself and the other editors)

  14. <?xml version="1.0" ?><!DOCTYPE dublin-core-simple [<!-- DC 1.0, RFC 2413 --><!ELEMENT dublin-core-simple (dc-record*)><!ELEMENT dc-record (title*, creator*, subject*, description*, publisher*, contributor*, date*, type*, format*, identifier*, source*, language*, relation*, coverage*, rights*)><!ELEMENT title (#PCDATA) ><!ELEMENT creator (#PCDATA) ><!ELEMENT subject (#PCDATA) >… <!ELEMENT source (#PCDATA) ><!ELEMENT language (#PCDATA) ><!ELEMENT relation (#PCDATA) ><!ELEMENT coverage (#PCDATA) ><!ELEMENT rights (#PCDATA) >]

More Related