Using Search Attributes

Search attributes control the query that is sent to the server. They are independent of the information that will be sent back. Think of these as being how you ask the question. You can ask a general question or a very detailed question, depending on the attributes you use. Different databases will support different sets of attributes, so you may need to experiment with these settings. Most of the time, using the default settings will fit your needs, and to use those you can simply leave most of the fields blank. You can use the information below to customize the search attributes, but please remember that the Z39.50 server you are connecting to controls which attributes it will accept.

The Use Attribute

This attribute describes what type of information is being searched for. It’s easy to think of this as just the field being searched, but it is more detailed than that. For example, Use value 1 equals a personal name, so you might use it when searching for a person’s name but not a corporation’s name. Use attribute 2 equals a corporate name. Not all use attributes will be supported for all databases. When you create a new, blank connection file it will be prepopulated with the most commonly-used use attributes, but can then be edited.

For a detailed list of Use attributes, see https://www.loc.gov/z3950/agency/defns/bib1.html.

The Relation Attribute

EndNote does not support editing this field.

The Position Attribute

The position attribute specifies the location of the search term within the field or subfield in which it appears.  The options are—

  • 1 = First in field:  The search term must be the first data in the field.
  • 2 = First in subfield:  The search term may appear in any subfield but must be the first data in the subfield.
  • 3 = Any position in field:  The search term may appear anyplace in the field.

The Structure Attribute

The structure attribute specifies the type of search term, for example a single word or a phrase.

  • 1 = Phrase:  One or more groups of characters separated by blanks, in exactly the order they are entered.
  • 2 = Word:  A group of characters with no blanks.
  • 3 = String:  The entire term is to be treated as a string, rather than a sequence or set of individual words.  An example might be a telephone number with blanks within it.
  • 4 = Word List:  One or more groups of characters separated by blanks, in which there is no implied order.

The Truncation Attribute

Truncation determines if one or more characters may be omitted when matching the search term.  The effects of truncation vary depending on what the structure attribute is set to, as explained below.

  • 1 = Right Truncation:
    Word or Phrase:  Last word of the term is right truncated.
    String:  Entire term is right truncated.
    Word List:  Each word is right truncated.
  • 2 = Left Truncation:
    Word or Phrase:      First word of the term is left truncated.
    String:  Entire term is left truncated.
    Word List:  Each word is left truncated.
  • 3 = Left and Right Truncation:
    Word or Phrase:      First word of term is left truncated and last word of term is right truncated.
    String:  Entire term is left and right truncated.
    Word List:  Each word is left and right truncated.
  • 100 = Do Not Truncate:  No truncation is applied.

The Completeness Attribute

  • 1 = Incomplete Subfield:  Words other than those in the search term may appear in the subfield or field in which the term appears.
  • 2 = Complete Subfield:  No words other than those in the search term should appear in the entire subfield in which the term appears, but additional words may appear in other subfields in the field.
  • 3 = Complete Field:  No words other than those in the search term should appear in the entire field in which the term appears.

Tip for Editing Search Attributes

When modifying the search attributes in a connection file, it is useful to first test the search with the new attribute combination before actually changing the connection file. If you are an advanced user and familiar with Z39.50 terminology, you can do this by entering the new attribute values using the command-line search method. This lets you test new attribute combinations without having to edit and save the connection file, and then reconnect to the server every time you want to test a modification. See Using the Z39.50 Command-Line Syntax.

You can find more information on Z39.50 search attributes at https://www.loc.gov/z3950/agency/defns/bib1.html.