The following summarizes Open SiteSearch WebZ 4.1.1 compliance for Levels 0 and 1 in the Bath Profile, version 1.1 (June 2000). (Refer to http://www.ukoln.ac.uk/interop-focus/bath/current/).

Important Notes

• OCLC has included a list of non-compliance issues below. Because of the nature of the Open SiteSearch WebZ toolkit, it is possible for WebZ users to configure their specific WebZ implementation so that additional functionality that is necessary for compliance is "turned off" (particularly Functional Area A search and retrieval functionality). However, WebZ does provide the functionality for users unless otherwise noted below.

• Because Open SiteSearch WebZ acts as a Z39.50 client, any remote or local Z39.50 server that users connect to for searching must also support certain Bath Profile functionality to take full advantage of WebZ’s compliance. For example, the Z39.50 Scan Service support described in Functional Area A, must also be supported on the remote and local Z39.50 server to utilize this functionality.

• This documentation is specific to only the Open SiteSearch WebZ software, version 4.1.1, and does not address compliancy issues that may be present in older versions of the WebZ software.

• The ZTexas Profile has adopted the Bath Profile, version 1.1, as their recommended implementation guidelines for Z39.50 clients and servers. ZTexas is currently adding to the Bath Profile by developing detailed guidelines for the types of indexes catalogs and databases should provide for Z39.50 clients. While OCLC will continue to observe the status of the ZTexas Profile development, OCLC does not anticipate any compliancy issues with the Open SiteSearch product at this time.

Functional Area A – Basic Bibliographic Search and Retrieval, with Primary Focus on Library Catalogues

Level 0 – WebZ is not compliant in the following area:

1. 5.A.0.1. Author Search – Precision Match for Established Name Heading
While WebZ does support author searching, the Profile does require that Z39.50 clients use the structure attribute of 101 (normalized name) to perform implicit proximity searches of the component words in an author name. WebZ does not meet this requirement within Level 0. Specifically, the Profile requires that Z39.50 clients formulate author searches using the comma to separate surname and firstname (e.g., aardt, j), which WebZ does not enforce.

Estimated Implementation Timeframe: Second half of 2001 (SiteSearch 4.2.0 release)

Level 1 – WebZ is not compliant in the following areas:

1. XML record syntax support

WebZ currently supports BER, GRS, MARC, NORMARC, NOTIS_OPAC, OPAC, TEXT (which is used for SUTRS), UNIMARC, and UKMARC record syntaxes, but does not support the XML record syntax.

Estimated Implementation Timeframe: Second Quarter 2001 (SiteSearch 4.1.2 release)

2. UNIMARC Support

While WebZ does support UNIMARC, there may be new characterset support issues that OCLC has not addressed yet. OCLC is investigating this now to ensure we are up-to-date with the UNIMARC characterset.

Estimated Implementation Timeframe: If new characterset support issues are identified, OCLC will make the adjustments in the second half of 2001 (SiteSearch 4.2.0 release).

3. Z39.50 Scan Service functionality


In reference to 5A.1SCAN Functional Area A: Level 1 Use of Scan, WebZ currently supports Term, but does not implement the DisplayTerm required in the profile. Thus, WebZ displays the Term instead of the DisplayTerm required in the profile. OCLC considers this redundant data, and Ralph LeVan will discuss our desire to remove DisplayTerm from the profile at the September Z39.50 meeting.

Estimated Implementation Timeframe: If DisplayTerm continues to be required in the Bath Profile after the September Z39.50 meeting, OCLC will make the necessary adjustments to WebZ in the second quarter of 2001 (SiteSearch 4.1.2 release).

Functional Area B - Bibliographic Holdings Search and Retrieval

Level 0 – WebZ is compliant.

Level 1 – WebZ is not compliant in the following areas:

1. GRS-1 Holdings Support


While WebZ does support the GRS record syntax, WebZ (specifically the ZBase server) does not generate GRS-1 holdings records.

Estimated Implementation Timeframe: OCLC will make the adjustments in the second half of 2001 (SiteSearch 4.2.0 release).

Functional Area C - Cross-Domain Search and Retrieval

Level 0 – WebZ is not compliant in the following areas:

1. XML record syntax support


WebZ currently supports BER, GRS, MARC, NORMARC, NOTIS_OPAC, OPAC, TEXT (which is used for SUTRS), UNIMARC, and UKMARC record syntaxes, but does not support the XML record syntax.

Estimated Implementation Timeframe: Second quarter 2001 (SiteSearch 4.1.2 release)

Level 1 - WebZ is not compliant in the following areas:

1. XML record syntax support


WebZ currently supports BER, GRS, MARC, NORMARC, NOTIS_OPAC, OPAC, TEXT (which is used for SUTRS), UNIMARC, and UKMARC record syntaxes, but does not support the XML record syntax.

Estimated Implementation Timeframe: Second quarter 2001 (SiteSearch 4.1.2 release)

Note: WebZ is Z39.50, version 3 compliant as required in Level 1. WebZ does not support the following optional services/facilities in version 3:

1. Segmentation not supported: is not applicable to the software due to the robustness of today's hardware and telecommunications environment and is no longer needed.
2. Accounting/Resource Control Facility: Trigger Resource Control is not provided and plans for this facility have not been determined at this date.
3. Explain Facility: is currently not provided because no standard is currently sufficiently defined to implement this facility.