Transcript Bath Profile Z39.50 Client/Server Compliance The Current State of Affairs http://nofish.library.mun.ca/m25bath.ppt Slavko Manojlovich Assistant to the University Librarian for Systems and Planning Memorial University of Newfoundland Email:

Bath Profile Z39.50 Client/Server Compliance
The Current State of Affairs
http://nofish.library.mun.ca/m25bath.ppt
Slavko Manojlovich
Assistant to the University Librarian
for Systems and Planning
Memorial University of Newfoundland
Email: [email protected]
Bath Profile M25
Outline
Bath compliance (circa 2001)
 Bath compliance (2001 – 2003)
 Bath compliance (future prospects)

Bath Profile M25
Bath Server Compliance (circa 2001)
Server
Requirements(max.41)
SIRSI (Bath Profile)
40
OCLC WorldCat
31
Nat. Lib. Of Canada AMICUS
25
Gaylord Polaris
20
--------------------------------------------------Endeavor Voyager
12
Sagebrush Athena
12
epixtech Horizon
11
Geac Advance (test)
11
epixtech Dynix
9
See: http://nofish.library.mun.ca/bathtest.htm
Bath Profile M25
Bath Server Compliance (2001-2003)

OCLC FirstSearch Services are now fully
compliant with Bath release 1.0 except for
the following:
Functional Area A: character set and
language negotiation
Functional Area C: unanchored title, subject
and any searches
See the following (updated June 11, 2003):
http://www.oclc.org/firstsearch/documentation/z3950/bath.htm

National Library Of Canada Amicus
improved compliance of its server.
Bath Profile M25
Bath Server Compliance (2001-2003)

Other vendors who should have Bath Compliant Z
Servers in 2003 include:
–
–
–
–
–


Autographics
Dynix (1)
III (3)
CyberTools for Libraries (claim Bath/Texas compliance)
Sirsi (2)
Support for Standard Identifier (1007):
313 out of 771 targets (41%) on Indexdata
list of targets.
The remaining major vendors are silent regarding
Bath compliance. One major vendor has stated
that they have no plans on supporting Bath on the
basis that they believe it will just disappear.
Bath Profile M25
Bath Server Compliance (2001-2003)

M25 Sirsi Servers
– Sirsi developed Bath compliance in 2001 even before
the official release of the profile.
– Bath compliant server became available in the 2002
release of the software.
– By the fall of 2003 Sirsi anticipates that at least 10
M25 Sirsi sites will be running Bath release 1.0
compliant servers.
– All new Sirsi installations running Unicorn 2003 will
have Bath release 1.0 compliant servers and the
associated recommended Bath indexing policies.
Bath Profile M25
Bath Client Compliance (2001 – 2003)
Acadia University Search Logs
29,000+ Searches For 1 Week In June, 2003
U
R
P
S
T
C
No. %
4
7
1003
4
1007
4
1016
4
4
0
0
0
0
0
0
0
3
3
0
0
0
0
0
0
0
3
3
0
0
0
1
0
2
0
1
2
0
0
0
0
0
0
0
1
100
0
0
0
0
0
0
0
1
1
9643 32.9
8119 27.7
4250 14.5
888 3.0
783 2.7
623 2.1
548 1.9
543 1.9
71
.2
Bath Profile M25
BookWhere 4.0 Z Client
Bath Profile M25
BookWhere 4.0 Z Client
Bath Profile M25
BookWhere 4.0 Z Client
(multi-term Bath keyword search)
Bath Profile M25
BookWhere 4.0 Z Client
Bath Profile M25
BookWhere 4.0 Z Client
Error Diagnostic 125 (Malformed search term). Your client
has probably sent an improperly formatted multi-word
keyword search. Retry your search using single terms.
OCLC doesn’t return the error, just “0” hits.
Bath Profile M25
ILL Requires Bath Compliance


Relais ILL/DD and Sirsi Bath Z Servers in Atlantic
Canada
Search for requested title: American Literature
Results From Acadia University Sirsi Z Server
Type of Search
No. of Hits
Title Exact
4
Title First Characters*
46
Title Unanchored Phrase
422
Title Keyword
624
*245 |aAmerican Literature: |ba study and research
guide
Bath Profile M25
Bath Profile Compliance
(future prospects)

XML Record Syntax
At the present time there is no way to request
an XML record associated with a specific
schema (e.g. XML MARC, XML Dublin Core, XML
Holdings).
By July 30, 2003 the following agreement
should take effect:
Proposed Agreement: To retrieve XML records, supply the
object identifier (1.2.840.10003.5.112), XML-b, as the
record syntax , and supply a globally unique identifier of
the desired XML definition as the element set name.
Bath Profile M25
Bath Profile Compliance
(future prospects)

Functional Area B: Holdings
– Release 2.0 includes the XML schemas
associated with the three levels of
holdings.
– Real-world implementation experience will
be required to determine the viability of
the schemas.
– There is still a need to determine the
relationship between the Bath Profile
holdings, NCIP, and ISO ILL.
Bath Profile M25
Bath Profile Compliance
(future prospects)

Z39.50 Directory Service
The Problem:
– Many vendors don’t publish details regarding
the attribute combinations supported by a
server.
– Some vendors publish inaccurate information.
– Different installed versions of a vendor’s
server support different attribute
combinations.
– Some libraries have the capability of modifying
the default settings supplied by a vendor.
Bath Profile M25
Bath Profile Compliance
(future prospects)
Sirsi’s solution in Unicorn Release 2003:
Deliver preconfigured search profiles
for 20+ vendor/version servers. All you
need to determine is the Vendor/Version
of a server (via the implementation id)
and the client will send the appropriate
attribute combinations for a search to
that server. For a broadcast search the
Sirsi clients send appropriate attribute
combinations to each server.
 Other possible solutions: M25 directory
service, profile negotiation, etc.

Bath Profile M25