Z39.50 Profiles The Bath Profile ZIG Meeting Leuven, Belgium July 2000 William E. Moen School of...

Z39.50 Profiles

The Bath Profile

Z39.50 Profiles

The Bath Profile

ZIG MeetingLeuven, Belgium

July 2000

William E. MoenWilliam E. Moen<[email protected]><[email protected]>

School of Library and Information SciencesSchool of Library and Information Sciences

University of North TexasUniversity of North Texas

Denton, TX 72603Denton, TX 72603

Z39.50 Profiles -- ZIG Meeting Leuven, July 2000 2William Moen

ProfilesProfiles

An auxiliary standards mechanism Defines a subset of specifications from one or

more standards Goal of profiles is to improve interoperability

Profiles are useful for:o prescribing how Z39.50 should be used in a

particular application environmento solving interoperability problems with existing

Z39.50 implementations within a community or across two or more communities


Profiles Z39.50 SpecificationsProfiles Z39.50 Specifications

Represents community consensus on requirements

Identifies Z39.50 specifications to support those requirements

Improves search and retrieval results

Aids in purchasing decisions Provides specifications for

vendors to build Z39.50 products

Complete

Z39.50

Specifications

Z39.50

Profile


A Plethora of Z39.50 Profiles!A Plethora of Z39.50 Profiles! Library applications profiles

o The Bath Profile (International)o ONE-2 and CENL Profiles (Regional and Project)o DanZIG Profile (National)o Union Catalogue Profile

Other information communities’ profileso The GILS Profile (government information)o The CIMI Profile (cultural heritage)o The Geo Profile (geospatial)

Application-support profileso Zthes Profile (thesaurus profile)

Check the Z39.50 Maintenance Agency site


Interoperability: The Fundamental Problem

Interoperability: The Fundamental Problem

Ability of client to successfully search and retrieve information in a meaningful way

Key issue when searching multiple databases containing similar resources

Difficult problem when searching databases containing diverse types of resources

Z39.50 profiles provide a solution


Threats to InteroperabilityThreats to Interoperability

Differences in implementation of the standard

Differences in local information retrieval systemso Z39.50 cannot improve searchability of

resources o It can only support what local and remote only support what local and remote

systems offersystems offer


Levels of InteroperabilityLevels of Interoperability

Low-level protocol (syntactic)o do Z-client and Z-servers interchange PDUs

according to standard?

High-level protocol (functional)o do Z-client and Z-servers support appropriate

Z39.50 services for user tasks

Semantic levelo can Z-clients and Z-servers and local IR systems

preserve and act on meaning of IR tasks


Interoperability and Z39.50 Searching

Interoperability and Z39.50 Searching

Issueso Use attributes supported (Z39.50 Implementation)o Differences in indexing, searchable fields available,

search support, etc. (Local IR System)

Implicationso Different results from similar databases

implemented on separate Z-serverso Different results on same database when searched

locally or through Z39.50


Interoperability and Z39.50 Retrieval

Interoperability and Z39.50 Retrieval

Issueso Z39.50 Record Syntaxes supported (Z39.50

Implementation)o Capability of local IR system to prepare records in

one or more formats for interchange (Local IR System)

Implicationso Clients and servers may or may not be able to

interchange records


The Bath ProfileThe Bath Profile

The Bath Profile: An International Z39.50 Specification for Library Applications and Resource Discovery, Release 1.1

Internationally Registered Profile (IRP) Enables effective use of Z39.50 in a range of

library applications:o Search and retrieval from library catalogueso Search and retrieval of bibliographic holdings infoo Cross-domain searchingo Item ordering and document delivery


Evolution towards BathEvolution towards Bath

ATS-1 Profile (1995) CENL Profile (1997) DanZIG Profile (1997) MODELS Profile (1997) ONE Profile (1997) Virtual Canadian Union Catalogue Profile

(1998) The Z Texas Profile (1999)


Structure of the ProfileStructure of the Profile Modular

Groups related requirements and specifications

Defines 3 Functional Areaso Functional Area A: Basic Bibliographic Search &

Retrievalo Functional Area B: Bibliographic Holdings Search &

Retrievalo Functional Area C: Cross-Domain Search & Retrieval

Defines several Conformance Levels


Bath Profile Functional Area ABath Profile Functional Area A Basic Bibliographic Search

o Conformance Level 0 (4 searches) Author Search — Precision Match for Established Name

Heading Title Search — Keyword Subject Search — Keyword Any Search — Keyword

o Conformance Level 1 (15 searches) Browsing Indexes

o 6 Scans specified Basic Bibliographic Retrieval

o Combination of UNIMARC or MARC21, and o SUTRS and/or XML


Summary of Bib-1 Attributes Required

Summary of Bib-1 Attributes Required

Attribute Type Attribute Values Attribute Name

Use (1) 4, 21, 31, 1003, 1007, 1016

title, subject heading, date of publication, author, identifier-standard, any

Relation (2) 1, 2, 3, 4, 5 less than, less than or equal, equal, greater than or equal, greater than

Position (3) 1, 3 first in field, any position in field

Structure (4) 1, 2, 101 phrase, word, normalized

Truncation (5) 1, 100 right truncation, do not truncate

Completeness (6)

1, 3 incomplete subfield, complete field


Bath Profile Functional Area BBath Profile Functional Area B

Bibliographic Holdings Search and Retrieval Requires new Holdings Schema Conformance Level 1 defines two Element Set

Nameso Locations Onlyo Locations, Summary Information, and Count if

available

Work on this functional area will be completed in Fall 2000.


Bath Profile Functional Area CBath Profile Functional Area C

Cross-Domain Search and Retrieval Defines two levels

o Conformance Level 0 (4 searches) Creator Search — Keyword Title Search — Keyword Subject Search — Keyword Any Search — Keyword

o Level 1 (9 searches) SUTRS and XML as record syntaxes Dublin Core DTD for XML record syntax Conformance Level 2 will specify Cross Domain

and Utility Attribute Sets


Addressing InteroperabilityAddressing Interoperability

Identify searching requirements (tasks)o Several levels of searching: recall-oriented, precision-

oriented Defining the searches (semantics and behavior) Specifying Z39.50 query to represent the search

o Standard combination of Z39.50 Attribute Types and Values

o Clients must send all attribute type values specifiedo Servers must be able to process all values

Suggested mapping and indexing of local systems (e.g., MARC fields to index, etc.)


Level 0 Title Keyword SearchLevel 0 Title Keyword Search

Attribute Type Attribute Value

Attribute Names

Use (1) 4 Title

Relation (2) 3 Equal

Position (3) 3 Any

Structure (4) 2 Word

Truncation (5) 100 Do not truncate

Completeness (6) 1 Incomplete subfield

Uses: Searches for complete word in a title of a resource.


Level 1 Title First Words in FieldLevel 1 Title First Words in Field

Attribute Type Attribute Value

Attribute Names

Use (1) 4 Title

Relation (2) 3 Equal

Position (3) 1 First in field

Structure (4) 1 Phrase

Truncation (5) 100 Do not truncate

Completeness (6) 1 Incomplete subfield

Uses: Searches for complete word(s) in the order specified in fields that contain a title of a resource. The field must begin with the specified character string. This search is useful when the beginning words in a title are known to the user.


Bath as Core SpecificationsBath as Core Specifications

National and regional profiles based on the Bath Profileo DanZIG Profileo ONE-2 Profileo CENL Profile

Compatible supersets of Bath

Addressing how different profiles will work together o Bath and CIMIo Bath and GILS


Z Texas and BathZ Texas and Bath

Z Texas Profileo Z Texas as companion profile to Batho Z Texas as compatible superset of Bath

Final revisions to Z Texas to harmonize with Bath

Continuing development on Texas-specific requirements:o for searchingo for retrievalo for addressing other types of information

A US National Profile – developed by NISO


Next Steps: Indexing GuidanceNext Steps: Indexing Guidance

Prescribing Z39.50 implementation specifications is half the battle

Developing indexing and mapping guidance is necessary

Can we as a community define a standard way to index bibliographic data?


Next Steps:Assuring Quality of Products

Next Steps:Assuring Quality of Products

Approacheso Taking the vendor’s word for ito Conformance testingo Interoperability testing

Challenges of interoperability testingo Rigorous methodologyo Tests for different levels of interoperabilityo Metrics for benchmarks and comparisono Setting up an interop testbed


Z Texas and Bath Profile Resources

Z Texas and Bath Profile Resources

Bath Profileo Copy of draft profile

http://www.ukoln.ac.uk/interop-focus/activities/z3950/int_profile/bath/draft/

o Listserv for Discussion ZIP-PIZ-L (subscribe by sending message to:

[email protected])

Z Texas Profileo Project Website

http://www.tsl.state.tx.us/ld/projects/z3950/

o TZIG Member Listhttp://www.tsl.state.tx.us/ld/projects/z3950/committee.htm

o Texas Z39.50 Listservhttp://www.tsl.state.tx.us/ld/projects/z3950/list.htm

Z39.50 Profiles The Bath Profile ZIG Meeting Leuven, Belgium July 2000 William E. Moen School of...

Documents

Transcript of Z39.50 Profiles The Bath Profile ZIG Meeting Leuven, Belgium July 2000 William E. Moen School of...