|
Ask a Librarian / FAQs:
Z39.50 Configuration for IRIS
About Z39.50
Z39.50 is an international communications standard that specifies a client/server based protocol for searching and
retrieving information from remote databases. The advantage of this standard is that computer systems can be separately
developed with custom search syntaxes but can talk to each other as long as they comply with the protocol.
The database engine that underlies the IRIS catalog comes with a Z39.50 server. Patrons can use standalone Z39.50
client software, like BookWhere, or bibliographic management software containing Z39.50 clients, like EndNote, ProCite
or Reference Manager, to connect to IRIS and search and retrieve citations relating to bibliographic records. This web
page describes the elements that are needed to make a connection to IRIS's Z39.50 server and to perform successful
searches of the IRIS catalog.
At the bottom of this page we have also provided a preconfigured
connection file to IRIS for the Windows version of
EndNote. To download the file, click on the underlined link. Your browser should prompt you to save the file. Click the
appropriate button to save the file. Your browser should then prompt you to choose the appropriate directory to save
the connection file. Navigate through the list of directories until you find the directory where you installed EndNote.
Select the EndNote subdirectory called Connect, then click Save. The next time you launch EndNote and select Connect
you should see IRIS as one of options.
Connection File
Download
EndNote to IRIS Connection File for Windows
Site Information
Organization Data
| Site Name: | Rutgers University Libraries |
| Address: | 169 College Ave |
| City: | New Brunswick |
| State/Prov: | NJ |
| Country: | USA |
| Zip Code: | 08901 |
Technical Support Point of Contact
Ask A Librarian
Database Information
| Database Name: | Unicorn |
| Database Description: | Rutgers University Libraries Online Catalog (IRIS) |
Server Information
| Domain Name: | www.iris.rutgers.edu |
| Port Number: | 2200 |
| Server Software Vendor: | Sirsi Corporation |
| |
| |
Initialization Service
| Z39.50 Protocol Version: | 3 |
| Preferred Message Size: | 65530 bytes |
| Maximum Record Size: | 65530 bytes |
Server Options Supported
General Options
- Sorting
- Scanning
- Cross Reference
- Result Set Naming
- Intermediate Results
- Result Set Deletes
Attribute Type
Element Set Names
Record Syntax
5.5 Attribute Set ID
- Bib-1 Attribute Set Profiles:
Encoding Definitions
The Z39.50 standards makes use of attributes to "code" a client's query so that the receiving server can process the
query correctly. There are provisions for six encoding definitions in the Z39.50 standard.
- USE or INDEX
- - Specifies which data field(s) the query should be processed to
- RELATION
- - Controls the order of numerical expression
- POSITION
- - Specifies the location of term(s) within the fields for matching query
- STRUCTURE
- - Specifies the structure of data in the query
- TRUNCATION
- - Specifies type of truncation processing for query
- COMPLETENESS
- - Specifies query processing by subfield
Attribute Value Notes
| Relation Attributes |
1=less than |
2=less than or equal to |
3=equal |
| 4=greater or equal |
5=greater than |
6=not equal |
| Position Attributes |
1=first in field |
3=any position in field |
|
| Structure Attributes |
1=phrase |
4=year |
6=word list |
| Truncation Attributes |
1=right truncation |
100=do not truncate |
|
| Completeness Attributes |
1=incomplete subfield |
3=complete field |
|
Attribute Combination Summary
Queries structured with Use Attributes other than 30 and 31:
| Relation: |
NONE |
| Position: |
1,3 |
| Structure: |
1,6 |
| Truncation: |
1,100 |
| Completeness: |
1,3 |
| |
|
Queries structured with Use Attributes 30 and 31:
| Relation: |
1,2,3,4,5,6 |
| Position: |
1,3 |
| Structure: |
4 |
| Truncation: |
1,100 |
| Completeness: |
1,3 |
| |
|
Server Supported Attribute Table
| Z39.50 Bib-1 Value |
Field Description |
Unicorn Index (MARC Tag #) |
Relation |
Position |
Structure |
Truncation |
Completeness |
| 1 |
Personal Name |
100,600,700 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 2 |
Corporate Name |
110,610,710 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 3 |
Conference Name |
111,611,711 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 4 |
Title |
130,222,240,241
242,245,246,440
490,730,740,830 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 5 |
Title Series |
440,490,830,840 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 6 |
Title Uniform |
130,240,630,730 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 7 |
ISBN |
020 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 8 |
ISSN |
022 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 9 |
LC Card Number |
010 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 13 |
Dewey Classification |
082 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 16 |
LC Call Number |
050 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 17 |
NLM Call Number |
060 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 20 |
Local Classification |
090,092 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 21 |
Subject Heading |
600,610,611,630
650,651,690,691 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 25 |
MESH Subject |
650 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 27 |
LC Subject Heading |
650 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 29 |
Local Subject Index |
690,691 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 31 |
Date of Publication |
PBYR |
1,2,3,4,5,6 |
1,3 |
4 |
1,100 |
1,3 |
| 33 |
Title Key |
222 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 50 |
Number Government Publication |
074,086 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 51 |
Number Publisher of Music |
028 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 53 |
Number Local Call Number |
090,092,096,099 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 54 |
Code-language |
LANG |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 60 |
CODEN |
030 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 61 |
Microform Generation |
533 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 62 |
Abstract |
520 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 63 |
Note |
500,501,502,503
504,505,506,507
508,510,511,515
517,520,530,534
540,545,590 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 1003 |
Author |
100,110,111,
400,410,411
700,705,710,711
800,810,811 |
|
1,3 |
1,6 |
1,100 |
1,3 |
| 1016 |
Any Field |
|
|
1,3 |
1,6 |
1,100 |
1,3 |
| 1018 |
Publisher |
260 |
|
1,3 |
1,6 |
1,100 |
1,3 |
|
