• Article Type: General
• Product: Aleph
• Product Version: 20

Description:
We are not sure if this problem stems from our configuration settings on the OCLC (now Open Source) SiteSearch software suite (version 4.x?), or comes from the settings in our own z39_server_base configurations. When one performs a z39.50 query on our site using SiteSearch, they will see a result set from our database. But when clicking on the result set to display them, one will get the following error message:"Sorry, an error occurred processing your command.
The error code generated was "34", and the error message generated was "Z39.50 Present Error - 238 / Available syntax: USmarc, OPAC, XML, SUTRS"

Here is what we're seeing in the Aleh z39_server log:
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition out-scan-char_conv in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition out-find-char_conv in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition in-record-char-conv in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] out-record-fix should have parameter
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition in-record-char-conv in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] out-record-fix should have parameter
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition in-record-char-conv in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] out-record-fix should have parameter
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition in-record-char-conv in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] out-record-fix should have parameter
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition format in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition scan in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition scan in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition scan in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition scan in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition scan in profile
11:03:17-01/09: /exlibris/aleph/a16_1/aleph/exe/z39_server(7029) [warn] Unknown definition scan in profile

Finally, the z39.50 queries work well with our catalog from all of the following sites or tools: LC z39.50 gateway, Metalib, Refwork, and Yaz client.

Resolution:
Here is the problem. The Z39.50 client has asked for results back in a record syntax that ALEPH does not support. The client is asking for a record syntax of 1.2.840.10003.5.1000.17.1

Here is the relevant section of the log:
presentRequest {
resultSetId 'vcw5'
resultSetStartPoint 1
numberOfRecordsRequested 1
preferredRecordSyntax OID: 1 2 840 10003 5 1000 17 1

If you look at the register of standard record syntaxes on LC's Z39.50 Maintenance Agency's web site you won't find this syntax at all:

http://www.loc.gov/z3950/agency/defns/oids.html#5

Any record syntax that starts with 1.2.840.10003.5.1000 is a locally registered syntax. When I searched for the OID (1.2.840.10003.5.1000.17.1) on the internet, I found it is a privately used OCLC syntax that is used for proprietary database update. Any standard Z39.50 server won't know of this syntax. To use SiteSearch client you describe, it will have to be configured to request records in a standard syntax, like MARC, OPAC, XML, etc.

Here is the link at OCLC where I learned about the privately registered record syntax:

http://www.oclc.org/americalatina/en/support/documentation/z3950/databaseupdate/

• Article last edited: 10/8/2013