This document provides suggested interpretations for the semantics of the bib-1 Attribute Set.
This document represents consensus among the members of the Z39.50 Implementors Group. It will be maintained as an official document of the Z39.50 Maintenance Agency, and will be revised periodically to reflect the most pragmatic guidelines for interoperability agreed upon by the Implementors Group.
This document contains references to certain definitions and behaviors that are specific to the target. These can be problem areas for interoperability. The specific definitions and behaviors may be described in a "Profile" document. In the absence of a profile, one must contact the service provider and ask. The behavior may be UNIQUE to that target. The expectation is that, over time, more and more will be documented explicitly in the standard and in profiles.
The attributes of Attribute Set bib-1 are used to indicate the characteristics of a search term in a Type-1 query when the query is of the form AttributeList+term (as described in section 3.7.1 of Z39.50-1995). The descriptions in this document apply when all attributes within 'AttributeList' are from the bib-1 attribute set. It does not define semantics when bib-1 is mixed with other attribute sets.
There are six types of attributes: Use, Relation, Position, Structure, Truncation, and Completeness. The Use attribute, if provided, identifies a set of access points against which the term is to be matched. The Relation, Completeness, Truncation and Position attributes, if provided, specify additional match criteria. The Structure attribute, if provided, identifies the form in which the term has been supplied.
Within an attribute list, each attribute type is optional. However, if a particular attribute type is not supplied, this document does not address target behavior -- a given target might supply a default attribute, dynamically select an appropriate attribute based on the other attributes supplied, or fail the search because it requires that the attribute type be supplied.
While Attribute Set bib-1 was originally established for use in the retrieval of records that are representable using the MARC formats for information interchange, it can also be used for the retrieval of records or documents representable in other formats.
Within an attribute list, multiple instances of a given type of attribute element are undefined and discouraged. Use of version 3 semantic actions is encouraged.
The remainder of this section describes each of the six attribute types, in order by the type number:
A Use attribute specifies an access point (e.g., corporate name, personal name, title, subject).
The Use attributes are given below in two separate tables. Table 1 is similar to the listing in Z39.50-1995, Appendix 3, ATR: Attribute Sets, in that the attributes are in order by their values and the same names that appear in the Appendix appear in the left column of Table 1. The right column of Table 1 contains a reference to the name of the attribute that is used in Table 2. Table 2 rearranges the Use attributes alphabetically by group name in an attempt to bring similar Use attributes together. The groups are somewhat arbitrary; no rigorous classification of the attributes has been attempted.
In Table 2, all attribute names are followed by their values, a brief definition or description, and tag values of representative USMARC bibliographic format fields that would contain data that could be described in the search by using the attribute. Whenever possible, definitions are taken from the Anglo-American Cataloguing Rules or the USMARC Format for Bibliographic Data as these are the guidelines that are used by a significant number of libraries for formulating data. In Table 2, the notation '$<alpha>' following a USMARC tag refers to a subfield of the named field. The notation 'i<number>' following a USMARC tag refers to values of the second indicator in the named field; when the second indicator of the field has the value <number>, the data in the field is associated with that Use attribute.
|
Use
|
Value
|
Definition
|
USMARC Tag(s)
|
UKMARC Tag(s) |
|
Abstract
|
62
|
An abbreviated, accurate representation of a work, usually without added interpretation or criticism.
|
520
|
|
|
Any
|
1016
|
The record is selected if there exists a Use attribute that the target supports (and considers appropriate - see note 1) such that the record would be selected if the target were to substitute that attribute.
Notes:
(1) When the origin uses 'any' the intent is that the target locate records via commonly used access points. The target may define 'any' to refer to a selected set of Use attributes corresponding to its commonly used access points.
(2) In set terminology: when Any is the Use attribute, the set of records selected is the union of the sets of records selected by each of the (appropriate) Use attributes that the target supports.
|
|
|
|
Anywhere
|
1035
|
The record is selected if the term value (as qualified by the other attributes) occurs anywhere in the record.
Note: A target might choose to support 'Anywhere' only in combination with specific (non-Use) attributes. For example, a target might support 'Anywhere' only in combination with the Relation attribute 'AlwaysMatches' (see below), to locate all records in a database.
Notes on relationship of Any and Anywhere:
(1) A target may support Any but not Anywhere, or vice versa, or both. However, if a target supports both, then it should exclude 'Anywhere' from the list of Use attributes corresponding to 'Any' (if it does not do so, then the set of records located by 'Any' will be a superset of those located by 'Anywhere').
(2) A distinction between the two attributes may be informally expressed as follows: 'anywhere' might result in more expensive searching than 'any'; if the target (and origin) support both 'any' and 'anywhere', if the origin uses 'Any' (rather than 'Anywhere') it is asking the target to locate the term only if it can do so relatively inexpensively.
|
|
|
|
Author-name
|
1003
|
A personal or corporate author, or a conference or meeting, name. (No subject name headings are included.)
|
100, 110, 111, 400, 410, 411, 700, 710, 711, 800, 810, 811
|
100, 110, 111, 700, 710, 711, 800, 810, 811 |
|
Author-name-and-title
|
1000
|
A personal or corporate author, or a conference or meeting
name, and the title of the item. (No subject name
headings are included.) The syntax of the name-title
combination is up to the target, unless used with the
Structure attribute Key (see below).
|
100/2XX, 110/2XX
111/2XX, subfields $a & $t in following: 400,410, 411, 700, 710, 711, 800, 810, 811
|
100/2XX, 110/2XX
111/2XX, subfields $a & $t in following:
700, 710, 711, 800, 810, 811 |
|
Author-name-corporate
|
1005
|
The organization or a group of persons that is identified by a particular name. (Differs from attribute "name-corporate (2)" in that corporate name subject headings are not included.)
|
110, 410, 710, 810
|
110, 710, 810 |
|
Author-name-conference
|
1006
|
A meeting of individuals or representatives of various bodies for the purpose of discussing topics of common interest. (Differs from attribute "name-conference (3)" in that conference name subject headings are not included.)
|
111, 411, 711. 811
|
111, 711, 811 |
|
Author-name-personal
|
1004
|
A person's real name, pseudonym, title of nobility nickname, or initials. (Differs from attribute "name-personal (1)" in that personal name subject headings are not included.)
|
100, 400, 700, 800
|
100, 700, 800 |
|
Author-Title-Subject
|
1036
|
An author or a title or a subject.
Note: When the Use attribute is Author-name-and-title (1000) the term contains both an author name and a title. When the Use attribute is Author-Title-Subject (1036), the term contains an author name or a title or a subject.
|
1XX, 2XX, 4XX, 6XX, 7XX, 8XX
|
1XX, 2XX, 6XX, 7XX, 8XX |
|
Body of Text
|
1010
|
Used in full-text searching to indicate that the term is to be searched only in that portion of the record that the target considers the body of the text, as opposed to some other discriminated part such as a headline, title, or abstract.
|
|
|
|
Classification-Bliss
|
15
|
A classification number from the Bliss Classification, developed by Henry Evelyn Bliss.
|
|
|
|
Classification-Dewey
|
13
|
A classification number from the Dewey Decimal Classification, developed by Melvyl Dewey.
|
082
|
081, 082 |
|
Classification-government-publication
|
50
|
A classification number assigned to a government document by a government agency at any level (e.g., state, national, international).
|
086
|
|
|
Classification-LC
|
16
|
A classification number from the US Library of Congress Classification.
|
050
|
050 |
|
Classification-local
|
20
|
A local classification number from a system not specified elsewhere in this list of attributes.
|
|
|
|
Classification-NAL
|
18
|
A classification number from the US National Agriculture Library Classification.
|
070
|
|
|
Classification_NLM
|
17
|
A classification number from the US National Library of Medicine Classification.
|
060
|
|
|
Classification-MOS
|
19
|
A classification number from Mathematics Subject Classification, compiled in the Editorial Offices of
Mathematical Reviews and Zentralblatt fur Mathematik.
|
|
|
|
Classification-UDC
|
14
|
A classification number from Universal Decimal Classification, a system based on the Dewey Decimal Classification.
|
080
|
080 |
|
Code-bib-level
|
1021
|
A one-character alphabetic code indicating the bibliographic level such as monograph, serial or collection of the record.
|
Leader/07
|
Leader/07 |
|
Code-geographic-area
|
55
|
A code that indicates the geographic area(s) that appear or are implied in the headings assigned to the item during cataloging.
|
043
|
043, 752 |
|
Code-geographic-class
|
1022
|
A code that represents the geographic area and if applicable the geographic subarea covered by an item. The codes are derived from the LC Classification-Class G and the expanded Cutter number list.
|
052
|
|
|
Code-institution
|
56
|
An authoritative-agency symbol for an institution that is the source of the record or the holding location. The code space is defined by the target.
|
040, 852$a
|
040 |
|
Code-language
|
54
|
A code that indicates the language of the item. The codes are defined by the target.
|
008/35-37, 041
|
008/35-37, 041 |
|
Code-map-scale
|
1024
|
Coded form of cartographic mathematical data, including scale, projection and/or coordinates related to the item.
|
034
|
034 |
|
Code-microform-generation
|
61
|
The code specifying the generation of a microform.
|
007/11
|
|
|
Code-record-type
|
1001
|
A code that specifies the characteristics and defines the components of the record. The codes are target-specific.
|
Leader/06
|
|
|
Concept-reference
|
1015
|
Used within Z39.50-1988; included here for historical reasons but its use is deprecated.
|
|
|
|
Concept-Text
|
1014
|
Used within Z39.50-1988; included here for historical reasons but its use is deprecated.
|
|
|
|
Content-type
|
1034
|
The type of materials contained in the item or publication. For example: review, catalog, encyclopedia, directory.
|
derived value from 008/24-27
|
derived value from 008/24-27 |
|
Control-number-BNB
|
10
|
Character string that uniquely identifies a record in the British National Bibliography.
|
015
|
015 |
|
Control-number-BNF
|
11
|
Character string that uniquely identifies a record in the Bibliotheque Nationale Francais.
|
015
|
|
|
Control number-DB
|
52
|
Character string that uniquely identifies a record in the Deutsche Bibliothek.
|
015
|
|
|
Control number-LC
|
9
|
Character string that uniquely identifies a record in the Library of Congress database.
|
010, 011
|
010 |
|
Control-number-Local
|
12
|
Character string that uniquely identifies a record in a local system (i.e., any system that is not one of the four listed above).
|
001, 035
|
001 |
|
Date
|
30
|
The point of time at which a transaction or event takes place.
|
005, 008/00-05, 008/07-10, 260$c, 008/11-14, 033 etc
|
008/00-05, 008/07-10, 260$d etc |
|
Date-publication
|
31
|
The date (usually year) in which a document is published
|
008/07-10, 260$c.
046,
533$d
|
008/07-10, 260$d |
|
Date-acquisition
|
32
|
The date when a document was acquired
|
541$d
|
|
|
Date/time added to database
|
1011
|
The date and time that a record was added to the database.
|
008/00-05
|
008/00-05 |
|
Date/time last modified
|
1012
|
The date and time a record was last updated.
|
005
|
|
|
Identifier-- authority/format
|
1013
|
Used in full-text searching to indicate to the target system the format of the document that should be returned to the originating system. The attribute carries not only the format code, but also the authority (e.g., system) that assigned that code.
|
|
|
|
Identifier-CODEN
|
60
|
A six-character, unique, alphanumeric code assigned to serial and monographic publications by the CODEN section of the Chemical Abstracts Service
|
030
|
|
|
Identifier-document
|
1032
|
A persistent identifier, or Doc-ID, assigned by a server, that uniquely identifies a document on that server.
|
|
|
|
Identifier-ISBN
|
7
|
International Standard Book Number -- internationally agreed upon number that identifies a book uniquely. Cf. ANSI/NISO Z39.21 and ISO 2108.
|
020
|
021 |
|
Identifier-ISSN
|
8
|
International Standard Serial, Number -- internationally agreed upon number that identifies a serial uniquely. Cf. ANSI/NISO z39.9 and ISO 3297.
|
022, 4XX$x, 7XX$x
|
022 |
|
Identifier-legal- deposit
|
49
|
The copyright registration number that is assigned to an item when the item is deposited for copyright
|
017
|
|
|
Identifier-local-call
|
53
|
Call number (e.g., shelf location) assigned by a local system (not a classification number).
|
|
|
|
Identifier-national- bibliography
|
48
|
Character string that uniquely identifies a record in a national bibliography.
|
015
|
015 |
|
Identifier-publisher- for-music
|
51
|
A formatted number assigned by a publisher to a sound recording or to printed music.
|
028
|
|
|
Identifier-report
|
1027
|
A report number assigned to the item. This number could be the STRN (Standard Technical Report Number) or another report number. Cf. ANSI/NISO Z39.23 and ISO 10444.
|
027, 088
|
|
|
Identifier-standard
|
1007
|
Standard numbers such as ISBN, ISSN, music publishers, numbers, CODEN, etc., that are indexed together in many online public-access catalogs.
|
010, 011, 015, 017, 018, 020, 022, 023, 024, 025, 027, 028, 030, 035, 037
|
010, 015, 021, 022, 024 |
|
Identifier-stock
|
1028
|
A stock number that could be used for ordering the item.
|
037
|
|
|
Identifier-thematic
|
1030
|
The numeric designation for a: part/section of a work such as, the serial, opus or thematic index number.
|
$n in the following:
130, 240, 243, 630, 700, 730
|
|
|
Indexed-by
|
1023
|
For serials, a publication in which the serial has been indexed and/or abstracted
|
510
|
|
|
Material-type
|
1031
|
A free-form string, more specific than the one-letter, code in Leader/06, that describes the material type of the item, e.g., cassette, kit, computer database, computer file.
|
derived value from Leader/06-07, 007.
008
502
|
derived from 008 |
|
Music-key
|
1025
|
A statement of the key in which the music is written.
|
$r in the following: 130, 240, 243, 630, 700, 730
|
|
|
Name
|
1002
|
The name of a person, corporate body, conference, or meeting. (Subject name headings are included.)
|
100, 110, 111, 400, 410, 411, 600, 610, 611, 700, 710, 711, 800, 810, 811
|
100, 110, 111, 600, 610, 611, 700, 710, 711, 800, 810, 811 |
|
Name-and-title
|
57
|
The name of a person, corporate, body, conference, or meeting and the title of an item. (Subject name headings are included.) The syntax of the, name-title combination is up to the target, unless used with the Structure attribute Key (see below).
|
100/2XX, 110/2XX, 111/2XX, subfields $a & $t in following: 400,410, 411, 600, 610, 611, 700, 710, 711, 800, 810, 811
|
100/2XX, 110/2XX, 111/2XX, subfields $a & $t in following: 600, 610, 611, 700, 710, 711, 800, 810, 811 |
|
Name-corporate
|
2
|
An organization or a group of persons that is identified by a particular name. (Subject name headings are included.)
|
110, 410, 610, 710, 810
|
110, 610, 710, 810 |
|
Name-conference
|
3
|
A meeting of individuals or representatives of various bodies for the purpose of discussing topics of common interest. (Subject name headings are included.)
|
111, 411, 611, 711 811
|
111, 611, 711 811 |
|
Name-editor
|
1020
|
A person who prepared for publication an item that is not his or her own.
|
100 $a or 700 $a when the corresponding $e contains value 'ed.'
|
100 $a or 700 $a when the corresponding $e contains value 'ed.' |
|
Name-geographic
|
58
|
Name of a country, jurisdiction, region, or geographic feature.
|
651
|
651 |
|
Name-geographic-place- publication
|
59
|
City or town where an item was published.
|
008/15-17, 260$a
|
008/15-17, 260$a |
|
Name-personal
|
1
|
A person's real name, pseudonym, title of nobility nickname, or initials.
|
100, 400, 600, 700, 800
|
100, 600, 700, 800 |
|
Name-publisher
|
1018
|
The organization responsible for the publication of the item.
|
260$b
|
260$b |
|
Note
|
63
|
A concise statement in which such information as extended physical description, relationship to other works, or contents may be recorded.
|
5XX
|
5XX |
|
Record-source
|
1019
|
The USMARC code or name of the organization(s) that created the original record, assigned the USMARC content designation and transcribed the record into machine-readable form, or modified the existing USMARC record; the cataloging source.
|
008/39, 040
|
008/39, 040 |
|
Server-choice
|
1017
|
The target substitutes one or more access points. The origin leaves the choice to the target.
Notes on relationship of Any and Server-choice:
(1) When the origin uses 'Server-choice' it is asking the target to select one or more access points, and to use its best judgment in making that selection. When 'Any' is used, there is no selection process involved; the target is to apply all of the (appropriate) supported Use attributes. The origin is asking the target to make a choice of access points.
(2) The target might support 'Any' and not 'Server-choice', or vice versa, or both. If the target supports both, when the origin uses 'Server-choice', the target might choose 'Any'; however, it might choose any other Use attribute.
|
|
|
|
Subject
|
21
|
The primary topic on which a work is focused.
|
600, 610, 611, 630, 650, 651, 653, 654, 655, 656, 657, 69X
|
600, 610, 611, 650, 651
653, 655, 660, 661, 668, 695 |
|
Subject-BDI
|
23
|
Subject headings from Bibliotek Dokumentasjon Informasjon -- a controlled subject vocabulary used and maintained by the five Nordic countries (Denmark, Finland, Iceland, Norway, and Sweden).
|
|
|
|
Subject-INSPEC
|
24
|
Subject headings from, Information Services for the Physics and Engineering Communities -- the Information Services Division of the Institution of Electrical Engineers.
|
600i2, 610i2 611i2, 630i2, 650i2, 651i2
|
|
|
Subject-LC
|
27
|
Subject headings from, US Library of Congress Subject Headings.
|
600i0, 610I0, 611i0, 630i0, 650i0, 651i0
|
600, 610,
611, 650,
651 |
|
Subject-LC- children's
|
1008
|
Subject headings, for use with children's literature, that conform to the formulation guidelines in the "AC Subject Headings" section of the Library of Congress Subject Headings.
|
600i1, 610i1, 611i1, 630i1, 650i1, 651i1
|
|
|
Subject-local
|
29
|
Subjects headings defined locally.
|
|
|
|
Subject-MESH
|
25
|
Subject headings from Medical Subject Headings -- maintained by the US National Library of Medicine.
|
600i2, 610i2, 611i2, 630i2, 650i2, 651i2
|
|
|
Subject-name- personal
|
1009
|
A person's real name, pseudonym, title of nobility nickname, or initials that appears in a subject heading.
|
600
|
600 |
|
Subject-PA
|
26
|
Subject headings from Thesaurus of Psychological Index Terms -- maintained by the Retrieval Services Unit of the American Psychological Association.
|
600i2, 610i2, 611i2, 630i2, 650i2, 651i2
|
|
|
Subject-PRECIS
|
45
|
Subject headings from PREserved Context Index System -- a string of indexing terms set down in a prescribed order, each term being preceded by a manipulation code which governs the production of pre-coordinated subject index entries under selected terms -- maintained by the British Library.
|
|
|
|
Subject-RAMEAU
|
22
|
Subject headings from Repertoire d'authorite de matieres encyclopedique unifie -- maintained by the Bibliotheque Nationale (France).
|
|
|
|
Subject-RSWK
|
46
|
Subject headings from Regeln fur den Schlagwortkatalog -- maintained by the Deutsches Bibliotheksinstitut.
|
|
|
|
Subject-RVM
|
28
|
Subject headings from, Repertoire des vedettes- matiere -- maintained by the Bibliotheque de l'Universite de Laval.
|
600i6, 610I6, 611i6, 630i6, 650i6, 651i6
|
|
|
Subject-subdivision
|
47
|
An extension to a subject heading indicating the form, place, period of time treated, or aspect of the subject treated.
|
6XX$x, 6XX$y, 6XX$z
|
6XX$x, 6XX$y, 6XX$z |
|
Title
|
4
|
A word, phrase, character, or group of characters, normally appearing in an item, that names the item or the work contained in it.
|
130, 21X-24X, 440, 490, 730, 740, 830, 840, subfield $t in the following: 400, 410, 410, 600, 610, 611, 700, 710, 711, 800, 810, 811
|
240, 243, 245, 740, 745, 440, 490, subfield $t in the following: 600, 610, 611, 700, 710, 711, 800, 810, 811 |
|
Title-abbreviated
|
43
|
Shortened form of the title; either assigned by national centers under the auspices of the International Serials Data System, or a title (such as an acronym) that is popularly associated with the item.
|
210, 211 (obs.), 246
|
|
|
Title-added-title-page
|
3
|
A title on a title page preceding or following the title page chosen as the basis for the description of the item. It may be more general (e.g., a series title page), or equally general (e.g., a title page in another language).
|
246i5
|
|
|
Title-caption
|
38
|
A title given at the beginning of the first page of the text.
|
246i6
|
|
|
Title-collective
|
34
|
A title proper that is an inclusive title for an item containing several works.
|
243
|
|
|
Title-cover
|
36
|
The title printed on the cover of an item as issued.
|
246i4
|
|
|
Title-expanded
|
44
|
An expanded (or augmented) title has been enlarged with descriptive words by the cataloger to provide additional indexing and searching capabilities.
|
214 (obs.), 246
|
|
|
Title-former
|
42
|
A former title or title variation when one bibliographic record represents all issues of a serial that has changed title.
|
247, 780
|
|
|
Title-host-item
|
1033
|
The title of the item containing the part described in the record, for example, a journal title when the record describes an article in the journal.
|
773$t
|
|
|
Title-key
|
33
|
The unique name assigned to a serial by the International Serials Data System (ISDS).
|
222
|
|
|
Title-other-variant
|
41
|
A variation from the title page title appearing elsewhere in the item (e.g., a variant cover title, caption title, running title, or title from another volume) or in another issue.
|
212 (obs.), 246i3, 247, 740
|
|
|
Title-parallel
|
35
|
The title proper in another language and/or script.
|
246i1
|
|
|
Title-related- periodical
|
1026
|
Serial titles related to this item, either the immediate predecessor or the immediate successor.
|
247, 780, 785
|
|
|
Title-running
|
39
|
A title, or abbreviated title, that is repeated at the head or foot of each page or leaf.
|
246i7
|
|
|
Title-series
|
5
|
Collective title applying to, a group of separate, but related, items.
|
440, 490, 830, 840 subfield $t in the following: 400,410, 411, 800, 810, 811
|
440, 490, subfield $t in the following: 800, 810, 811 |
|
Title-spine
|
40
|
A title appearing on the spine of an item.
|
246i8
|
|
|
Title-uniform
|
6
|
The particular title by which, a work is to be identified for cataloging purposes.
|
130, 240, 730 subfield $t in the following: 700,710, 711
|
|
Relation attributes describe the relationship of the access point (left side of the relation) to the search term as qualified by the attributes (right side of the relation), e.g., Date-publication <= 1975.
Relation attribute Equal -- specifies an exact match (subject to possible qualification by the truncation or structure attributes).
Relation attributes Less than, Less than or equal, Greater than or equal, and Greater than -- meaningful only when both the term value as qualified by the attributes and the access point can be realized as elements of a set that has an inherent implied order.
Relation attributes Stem and Phonetic -- Stem refers to a lexical or linguistic match; the term is to be compared with words in a record to find those with the same stem. Phonetic refers to a match based on aural similarity such as Soundex. In both cases, the match algorithms are defined by the target.
Relation attribute Relevance -- used to select records that are relevant to the term. When used, the Use attribute determines what portion of a record is to be evaluated for relevance. The relevance
Relation attribute AlwaysMatches -- when the Relation attribute AlwaysMatches occurs:
· If a Use attribute other than Any or Anywhere is supplied, all records are selected for which the access point corresponding to the supplied Use attribute is meaningful. For example: if the Use attribute is Title, all records that have a title field are selected.
The Position attribute specifies the location of the search term within the field or subfield in which it appears.
For the purpose of describing the Position attributes, when the expressions "field" or "subfield" do not have another understood meaning (as prescribed, for example, by the schema in use), these two expressions are used as follows:
· "subfield" has no meaning, and the Position attribute "first in any subfield" is not to be used.
The Structure attribute specifies the type of search term (e.g., a single word, a phrase, several words to be treated as multiple single terms, etc.).
The Truncation attribute specifies whether one or more characters may be omitted in matching the search term in the target system at the position specified by the Truncation attribute. For example, a word in a search term may be 1) right truncated, in which case the word is treated both as a complete word and as the beginning of a longer word; 2) left truncated in which case the word is treated both as a complete word and the ending of a longer word; 3) left and right truncated, in which case the word is treated as a complete word and the beginning or ending of a longer word; 4) and embedded truncation, in which case the word is treated as a complete word and as a longer word with additional characters at the point where the truncation symbol, "#", appears in the search term.
For Right truncation, left truncation, and Left and right truncation, the characters affected by the truncation are determined by the value of the structure attribute.
The Completeness attribute specifies that the contents of the search term represent a complete or incomplete subfield or a complete field. Completeness indicates whether additional words should appear in a field or subfield with the search term. Note the difference from Truncation (Section 2.5 above), which handles characters added to words, phrases, or strings.
For the purpose of describing the Completeness attributes, when the expressions "field" or "subfield" do not have another understood meaning (as prescribed, for example, by the schema in use) these two expressions are used as follows:
· "subfield" has no meaning, and the Completeness attribute incomplete subfield is used to mean "incomplete field".
If supplied, the following attribute values would be used for a derived key search.
· Position should always be 'first in field', even for author/title or name/title use attributes.
· Structure is 'word' or 'phrase' depending on whether the number contains internal blanks.
· Position and Completeness attributes are determined for number arguments as they are for textual arguments.
· All naturally occurring blanks, hyphens, slashes, etc., should be in the number search term if possible because different systems handle numbers in different ways in their indexes. The target system should apply normalization to the number according to its requirements, or return appropriate messages to allow the user to reformat the number.
· Search arguments generally should not be normalized by the origin system. They should be normalized by the target system.
· Position attribute 'any position in field' is compatible only with the 'incomplete subfield' Completeness attribute.
The Z39.50 Maintenance Agency manages the addition of attributes to the bib-1 attribute set. Generally, suggestions for new attributes are posted to the Z39.50 Implementors Group list and discussed at a subsequent ZIG meeting before being included in the attribute set.
