As of 22 April 2009 IFLA has a totally redesigned new website
This old website and all of its content will stay on as archive – http://archive.ifla.org
As of 22 April 2009 IFLA has a totally redesigned new website
This old website and all of its content will stay on as archive – http://archive.ifla.org
    IFLA Universal Bibliographic Control and International MARC Core Programme (UBCIM)UNIMARC / Authorities 1991CONTENTSForewordIntroductory Notes Definitions Guidelines for Format Design Functional Blocks Guidelines for Use Mandatory Fields Outline of Content of Records Explanatory Notes Record Label FOREWORDThe establishment of UNIMARC as the format for the international exchange of bibliographic records created an immediate need to develop a companion format to transmit the records for authoritative forms of headings. IFLA responded to this need by first developing a standard for content and display of authority information: Guidelines for Authority and Reference Entries (GARE). GARE sets forth the data elements that appear in authority and reference entries in eye-readable form. It thus serves as a foundation for building the machine format, UNIMARC/Authorities, to exchange the specified data.Since UNIMARC/Authorities is part of the UNIMARC group of interdependent formats there are several standards to which it must adhere. These relate to the three basic parts of a machine-readable record format: 1) The structure of the record, which is the physical representation
and layout of the information. First the authorities format must be structure-compatible with UNIMARC, since the two types of records will be used together in systems. Thus the International Organization for Standardization standard format for bibliographic information interchange (ISO 2709) must be utilized choosing the same options as in UNIMARC. Second, the content designation for headings must be the same as that used in UNIMARC, where the same data elements appear in both formats. The interaction of headings in bibliographic and authority records should not be burdened with differences in content designation, since the degree of compatibility will have a direct effect on the ease of understanding and use of the format. This generally means subfields should correspond for like data elements, although tagging will differ because of the different functions of data elements in bibliographic and authority records. Also, the user of the UNIMARC formats is best served if the same guidelines for design are used in this format wherever the concepts correspond. Another standard that the format must follow is the new GARE. The basic data elements in certain types of authority records are specified by the GARE, which identifies the headings, relationships, and information that comprise authority entries and reference entries. The form of the data recorded in the authority record is subject to the rules and codes used by an agency that creates the record. There are, however, recommendations that have been published by IFLA for the form of headings, such as Form and Structure of Corporate Headings, and these should be followed where possible. The IFLA recommendations are used by or influence many cataloguing codes. The IFLA group responsible for the GARE was the IFLA Working Group on an International Authority System which was organized in 1979 by the Section on Information Technology and the Section on Cataloguing to carry out a number of tasks relating to the international exchange of authority data. In 1983, that work was largely completed with the submission of the GARE to IFLA committees for approval. That Working Group suggested that one task, the development of a format, be undertaken immediately. Thus the Steering Group on a UNIMARC Format for Authorities was formed with the following members: Marie-Louise Bachmann, Kungliga Biblioteket, Stockholm The project editor for the UNIMARC/Authorities format was Sally McCallum. The Steering Group was responsible for general advice and for comments on draft texts. This work was mainly carried out by correspondence. Three successive drafts were sent out to all Steering Group members for comment: 1st draft 1984-26-05; 2nd draft 1985-10-21; 3rd draft 1987-03-13. Based on the comments received the 4th draft was prepared for wider distribution and comment. In February of 1988 the 4th draft was circulated to members of the Section on Cataloguing and the Section on Information Technology. In closing, I would like to thank Sally McCallum who carried the main burden in drafting the format and preparing the documents, and all members of the Steering Group who contributed so much of their time and effort to the development of the UNIMARC/Authorities format. Christine Boßmeyer
INTRODUCTORY NOTESScope: The UNIMARC/Authorities format specifies the tags, indicators and subfield identifiers to be assigned to authority, reference, and general explanatory entry records in machine-readable form. These records are created to provide guidance on the use in a catalogue of names (personal, family, corporate, meeting, and geographic), uniform titles for works not entered under specific authors, uniform titles for works by individual authors, and topical subjects. These names titles and topicals are used on bibliographic records as primary, secondary and alternative entries, as series entries, and as subject entries. The record format takes into account the display requirements specified in Guidelines for Authority and Reference Entries (GARE) for records involving names and uniform titles for anonymous classics. Similar display guidelines have not yet been developed for subjects, and other types of uniform titles. Authority records for series entries are limited to heading information in this format. Series treatment data that is included in authority records by some agencies is not accommodated. Purpose: The primary purpose of UNIMARC/Authorities is to facilitate the international exchange of authority data in machine-readable form among national bibliographic agencies. Use: It is anticipated that each national bibliographic agency will be responsible for the conversion of authority records into UNIMARC/Authorities for transmission to other national agencies and will receive machine-readable records in the UNIMARC/Authorities format from other national agencies. UNIMARC/Authorities is intended to provide the information required for a range of bibliographic activities. It therefore includes content designation which may be essential to one or another of these activities, but not to all. Standards: UNIMARC/Authorities assumes the use of the following standards: ISO 646 - 1983: Information processing - ISO 7-bit coded character set
for information processing interchange. 15p. Other Related Documents: International Federation of Library Associations and Institutions.
Guidelines for Authority and Reference Entries. London: IFLA International
Programme for UBC, 1984. 40 p. DEFINITIONSThe terms defined below are those used in special sense in UNIMARC/Authorities; terms used in their normal bibliographic sense are not defined. A more complete listing of definitions relating to parts of an authority entry are contained in Guidelines for Authority and Reference Entries (GARE). Record And Entry Types: Authority entry record - A machine-readable record for an authority entry. Authority entry - An entry for which the initial element is the uniform heading for a person, corporate body, work, or topical subject, as established by the cataloguing agency responsible. In addition to the uniform heading, the record contains, as applicable: information notes; a record of all variant and related headings from which references have been made (tracings); notes recording sources consulted, etc.; an identification of the cataloguing agency responsible for the entry; and the International Standard Authority Data Number (ISADN). General explanatory entry record - A machine-readable record for a general explanatory entry. General explanatory entry - An entry for which the initial element normally consists of a truncated or otherwise stylized or exemplary form, from which the user is directed to a general class or defined category of headings. It serves to inform the user of the list, catalogue, bibliography, etc. of a convention that applies either generally or to a defined category of headings, and to provide guidance in locating such headings. Reference entry record - A machine-readable record for a reference entry. Reference entry records are defined only for variant headings. Reference entry - An entry for which the initial element is either a variant heading or a uniform heading, and which is designed to direct the user of the list, catalogue, bibliography, etc. either from the variant heading to the appropriate uniform heading (i.e. a "see" reference), or from the uniform heading to related headings (i.e. a "see also" reference). Heading Types: Heading - (1) The initial element of an entry used as the principal filing element when the entry is arranged in an alphabetical listing. See also authority heading, reference heading, and general explanatory heading. (2) The word heading may also be used in terms such as "uniform heading", "variant heading", etc. to refer to the status of an element as it relates to other similar elements, and in those cases is used independently of its function within the authority or reference entry. See also uniform heading, parallel heading, related heading, variant heading, and alternative script heading. (3) Terms such as "corporate name heading" and "personal name heading" may be used to designate the type of heading by reference to the type of name or title on which the heading is based, without regard to its function or relationship to other headings. Headings categorized by function within an entry (record): Authority heading - The heading for an authority entry. Reference heading - The heading for a reference entry. General explanatory heading - The heading for a general explanatory entry. Headings categorized by relationship to other headings: Uniform heading - A heading established in a form to be followed without variation whenever the heading appears in a bibliographic record. Parallel heading - An alternative form of the authority heading based on another language form of the name or title. Related heading - One of two or more uniform headings, each of which is bibliographically related to the other(s). Variant heading - A heading in a form other than that established as the uniform heading. Generally such a heading is either based on a variant name sometimes used by the person or corporate body itself, or sometimes used by others to identify the person, corporate body, or work; or constructed on a pattern different from that used to establish the uniform heading. It may be a uniform subject heading that is not the entry element part. Alternative script heading - A heading represented in another script. Record Components: Tracing - The identification within an authority entry of a variant or related heading from which a reference is to be made directing the user of the list, catalogue, bibliography, etc. to the uniform heading which serves as the heading for the authority entry. The tracing is designed to provide for the generation of references and assist the cataloguer in readily determining what references have been made. Information Note - A note of the type that is generally given in catalogues, bibliographies, etc. under an authority heading, a reference heading, or an general explanatory heading for the purpose of explaining the relationship between that heading and other headings that are referenced from it. Primary Entity - The entity, named in the 2-- block of the record, for which the record was created. Data in the 1-- block generally pertain to characteristics of the primary entity. Technical Elements of Records: Content designator - The means of identifying data elements and/or providing additional information about a data element. Content designators consist of tags, indicators and subfield identifiers. Data element - The smallest unit of information that is explicitly identified. Within a variable field, a data element is identified by a subfield identifier and it forms a subfield. Within the record label, directory, and fixed length subfields, the data elements are identified by their character positions. Data element identifier - See subfield identifier. Field - A defined character string, identified by a tag, which contains data. Variable field - A field in which the length of an occurrence of the field is determined by the length (in characters) required to contain the data elements (including indicators, subfield identifiers, and the field separator) stored in that occurrence. The length may vary from one occurrence to the next. A variable field may contain one or more data elements or subfields. Tag - A series of three characters used to specify the name or label of an associated field. Indicator - A character (numeric or alphabetic) associated with a variable field which supplies additional information about the contents of the field, about the relationship between the field and other fields in the record, or about the action required in certain data manipulation processes. Subfield - A defined unit of information within a field (see also data element). Subfield identifier - A code consisting of two characters to identify individual subfields within a variable field. The first character is always control function 1/15 from ISO 646 and the second character is either numeric or alphabetic. Subfield identifiers are synonymous with data element identifiers. Field separator - A control character used at the end of each variable field to separate it from the next field (control function 1/14 of ISO 646). Record terminator - The final character in each record (control function 1/13 from ISO 646). GUIDELINES FOR FORMAT DESIGNUNIMARC is designed according to an agreed set of principles. These have been adopted for UNIMARC/Authorities. (1) Tags should identify a field in two respects: i) the type of character string (e.g., a personal name) and ii) the function the character string performs in the record (e.g., tracing). These aspects will be shown by assigning specific values to the character positions of the tags. Tags may be both numeric and alphabetic. First assignment will be numeric values, expanded to alphabetic values (lower case preferred) when required. (2) Indicators should be tag dependent but used as consistently as possible across all fields. Indicators may be both numeric and alphabetic. First assignment will be numeric values, expanded to alphabetic values (lower case preferred) when required. (3) Subfield identifiers will be tag dependent, but, as far as possible, common data elements will be identified by the same subfield identifiers across fields. Subfield identifiers may be both numeric and alphabetic. First assignment will be alphabetic values (lower case preferred), expanded to numeric values when required. Subfield identifiers will be given values for identification rather than for file arrangement. There will be no specified order for subfield identifiers, as order is determined by the data. (4) The fields on an authority record have been regarded as relating primarily to broad categories of information such as "Heading of Record," "See Also Reference Tracings," etc. In a machine-readable record the primary grouping of fields will be according to these fundamental categories. (5) Descriptive information carried in notes is not intended for use as access points. FUNCTIONAL BLOCKSThe fields of the authority or reference record are divided into functional blocks; the first (left most) digit of the tag indicates the block of the field. 0-- Identification Block: contains numbers that identify the record or the authority. 1-- Coded Information Block: contains fixed length data elements (frequently coded) describing various aspects of the record or data. 2-- Heading Block: contains the authority, reference, or general explanatory heading for which the record has been created. 3-- Information Note Block: contains notes, intended for public display, that explain the relationship between the record heading (2--) and other headings. 4-- See Reference Tracing Block: contains variant headings from which a reference is to be made to see the heading of the record. 5-- See Also Reference Tracing Block: contains related uniform headings from which a reference is to be made to see also the heading of the record. 6-- Classification Number Block: contains classification numbers that are related to the heading of the record. 7-- Linking Heading Block: contains a form of the record heading (2--) in another language or script and links to another record in which that form is the 2-- heading. 8-- Source Information Block: contains the source of the record, and cataloguer's notes about the data not intended for public display. 9-- National Use Block: contains data local to the originator of the record. Field tags will not be defined in UNIMARC/Authorities for intersystem exchange. GUIDELINES FOR USEIn addition to the Record Label and Directory, the following fields must be present in the machine-readable records: 001 Record identifier The presence of other fields depends upon the particular record being converted into machine-readable form. The data content of a record is controlled by the cataloguing code and practice of the bibliographic agency responsible for the creation of the record, i.e., the presence or absence of a data element is determined, not only by format specifications, but by the national cataloguing code or practice. However, if a data element is present, it must be fully content designated according to the prescriptions defined in this document. Elements of information that are represented in coded form are generally not specified by cataloguing codes. Certain of these coded data elements are mandatory and are so identified in the format. Control functions permitted in UNIMARC/Authorities are confined to those used for subfield codes, field separators, and record terminator, as specified in ISO 2709; character set escape sequences as specified in ISO 2022; and those for indicating filing information, superscripts, and subscripts as specified in ISO 6630. No control functions are allowed to specify typographical functions such as italics. The use of control functions in UNIMARC/Authorities records is fully described in the UNIMARC Manual, Appendix F. (3) Field and Subfield Repetition If the word "repeatable" is associated with a field, then that field may occur more than once in a record. If R (= repeatable) is associated with a subfield identifier, then that subfield may occur more than one time in an occurrence of the field. There is no specified order implied in the values of the subfield identifiers. Subfield identifiers are assigned values for identification purposes, not for file arrangement. A complete record, fully content designated, is naturally the preferred record for international exchange purposes. In some cases, however, it may not be possible to convert a national record into the UNIMARC/Authorities format and provide the full content designation and, coded information as prescribed. To minimize the ambiguities that could result if the indication of this lack of information were left to the discretion of each national agency faced with the circumstances described above, a character, hereafter referred to where this occurs as a "fill character," is used in place of the required information. This character will be the "|" (vertical line, code table position 7/12 in ISO 646). The fill character can be used whenever a content designator or coded information cannot be determined by the encoding agency. It thus occurs in the following situations: i) encoding agency does not use this content designator or code this information, or ii) encoding agency uses this content designator or codes this information but in this particular record does not know the correct value, or iii) encoding agency uses similar values for this content designator or coded information but they cannot be translated to the exact UNIMARC/Authorities equivalents. The following rules apply to the use of the fill character: fill characters may only be used for indicators and coded data values that are not mandatory, thus fill characters may not be used in the Record Label or Directory, as subfield identifiers or to replace punctuation or other special characters in the data portion of fields. The following conventions are used in the assignment of coded values in the Record Label and coded data subfields: u - Unknown. Used when codes are being assigned, but the appropriate
specific value cannot be determined. GARE prescribed punctuation is not carried at the subfield boundaries. GARE prescribed punctuation consists of = (used with parallel headings), <, >, <<, and >> symbols (used with tracings), ; and , (used in the source area). All other punctuation in headings, notes, etc., are carried in the record according to the practice of the bibliographic agency issuing the record. This format is designed to support primarily the communication of authority entry records for uniform headings. These records may also carry tracings of variant or related headings (as outlined in GARE, 0.3.1) from which reference entries are generated for display. A 4-- field is used for a "see from" reference tracing containing a variant form of the authority heading. A 5-- field is used for a "see also from" reference tracing containing a related uniform heading. The reference entry can be generated from a tracing as desired for display. Example: 210 02$aPittsburgh Research Center [uniform heading as authority heading] In exceptional cases, references are carried in authority entry records in note form: field 305, Textual See Also Reference Note. Reference notes are used when a reference is too complex to be adequately constructed from one or more tracings. The 2-- heading is also generally traced as see also reference tracing in a 5-- field of each of the records for headings mentioned in the 305 note. Such tracings would usually have the Reference Suppression Code in the $5 subfield set to suppress automatic generation of a simple reference, since the 305 reference note provides the reference. Examples: Record 1 (Authority entry record) Record 2 (Authority entry record) Record 3 (Authority entry record) Reference entry records for variant headings are only made when see references are too complex to be adequately generated from see reference tracings in authority entry records. The reference entry record contains the variant heading in the 2-- field and a 310 Textual See Reference Note. The 2-- heading is also generally traced as a see reference tracing in a 4-- field of the authority entry record for each of the uniform headings referred to in the 310 note. These tracings would generally have the Reference Suppression Code in the $5 subfield set to suppress automatic generation of a simple reference, since the reference entry record provides the reference. Examples: Record 1 (Reference entry record) Record 2 (Authority entry record) Record 3 (Authority entry record) General Explanatory Entry Records: General explanatory entry records are made when see references from explanatory headings are required. The general explanatory entry record contains an explanatory heading in the 2-- field and a 320 General Explanatory Reference Note. The 2-- explanatory heading is not traced on any authority entry records. Examples: 210 12$aConference... [general explanatory heading] Option 1 A general principle for the construction of a record using this format is that one form of one heading is being described and that heading is appropriate for a catalogue in the language designated by the 100 field. The reference tracings constitute the reference structure for that heading in that catalogue. If a cataloguing agency needs to construct a parallel catalogue based on another language, the agency may want to transmit equivalent or parallel language forms of the 2-- heading and the notes and tracings appropriate to the parallel headings. It is not recommended that the notes and tracings for the parallel headings based on language differences be co-resident in a single authority record. In using this format, these parallel headings should have separate authority entry records in which they are the authority heading and where their reference structure will be recorded in the 4-- and 5-- reference tracing and 3-- note fields. Note that when these parallel headings are in a different script, in addition to being in a different language, they are still encoded following the rules for parallel data. If the headings are in a different script but the same language as their corresponding fields then the rules for alternative scripts should be followed. The records for the different formulations of the heading designed for different language catalogues may be linked through the 7-- linking fields. In each authority entry record, each parallel heading and its associated record number (subfield $3) may be recorded in 7-- linking fields. Examples: Record 1 Record 2 Option 2 Alternatively, an agency may treat parallel forms of the 2-- heading as simple variants or references: 4-- or 5-- reference tracings with or without specifying language. The reference structures of the parallel forms are not needed and are not included in the record. The choice of technique depends on the practices of the establishing agency. Example: 215 ##$aSverige The emphasis has been placed in this format on identification of the language of the catalogue in which a heading fits, rather than on the actual language of the heading. There are two reasons for this. The language of the heading may not be the language of the catalogue because of cataloguing rules that prescribe use of the original language for certain headings. The language of the heading does not therefore establish the foundation for the accompanying reference structure, but could mislead the user into presuming the references are suitable in a catalogue for the language of the heading. In addition some headings are mixed language as the following examples illustrate: Italy. Ministero del bilancio e della programmazione economica The significant information about these headings is the catalogue into which they fit, not the languages that are used in their formulation. The script of cataloguing (heading, notes, tracings, etc.) is identified in the 100 field of the record. Some agencies need to record headings, notes, and tracings in more than one script form because of transliteration and alternative script orthographies used for a language (e.g., kana and kanji scripts for Japanese; devanagari, khmer, and lao scripts for Pali). Alternative script representations of the headings, notes, and the tracings may be co-resident in an authority record or may reside in separate linked records. Note, however, that if the alternative script representations differ in language from their corresponding headings, then the rules for parallel data apply. When the alternative script representations are co-resident, then the alternative script forms of the 2-- record heading are recorded in additional 2-- heading fields, with a $7 script subfield that indicates the difference from the script defined in the 100 field. The alternative script forms of notes or tracings are carried as repeated tags in their respective blocks. The various script forms of the same note or tracing are linked through a $6 linking subfield and the scripts are identified by a $7 script subfield. Examples: 100 $a, character position 21-22 = ba If the alternative script representations reside in separate records, then the records are linked through 7-- linking fields which contain the alternative script form of the 2-- field. The 7-- contains a $7 script subfield. The record control number of the authority record for the alternative script form of the heading may be recorded in the 7-- field. Examples: Record 1 Record 2 In UNIMARC/Authorities, headings or parts of headings are designated by field tag as one of several types: personal name, corporate/meeting name, territorial name, family name, uniform title, collective title, and topical subject. If a heading is composed of a name and title, fields for the name and the title are embedded in a special name/title field. The embedded field technique is described under the 240 HEADING - NAME/TITLE field description. For a fuller description of embedding see the UNIMARC Manual, as the basic technique is the same as that used in the UNIMARC 4-- Linking Entry block. If the heading is composed of a territorial name followed by a corporate or meeting name, the heading is considered a corporate or meeting name. If a heading is composed of a name, title, or topical followed by subject subdivisions, the subject subdivisions are carried in $x, $y, and $z subfields of the name, title, or topical subject that they follow. In name/title entries, the subject subdivisions reside in the embedded title field. (9) Outline of Content of Records Content Record
(10) Correspondance Between UNIMARC/Authorities and UNIMARC
(11) Display of Reference and Authority Entries The following methods may be used in coding data to allow flexibility in displaying reference and authority entries in order to accommodate the variations in display allowed in the GARE. (a) Tracings are divided into 4-- fields for see reference tracings and 5-- fields for see also reference tracings. The first character of these tags thus signal the need for the > and >> symbols, respectively, for use in displays of reference entries. For authority entries, the 4-- and 5-- signal that the symbols < and << should be displayed. (b) The relationship code in the tracing control subfield $5 may be used in a field to indicate in coded form one of several standard relationships the tracing may have with the 2-- record heading. These codes allow systems to display specific relationship information in reference and authority entries. Since the textual reference information generated as a result of the code is system dependent, the specific relationship or instruction may be in the language choice of the recipient. This relationship or instruction information is displayed in addition to, not in lieu of, the symbols >, >>, <, and <<. (c) If the particular relationship between the 2-- record heading and a tracing is not one of those for which a code value is defined in the relationship code of the $5 subfield, but is still a one-to-one relationship, subfield $0, instruction phrase, is provided to supply the instruction in textual form. Since this instruction phrase is in textual form, agencies that cannot use the information in the language given can omit it in displaying authority and reference entries since the less precise >, >>, <, and << symbols will also be generated from the field tag. If the $0 subfield occurs in addition to the relationship code in the $5 subfield, the instruction in the $0 should be preferred for display unless it is undesirable for language or other reasons. (d) If a relationship between the reference and the referred to heading is several-to-one or has other complexities that make it desirable to transmit the reference as an information note (in addition to tracings), then the 3-- information notes may be used. Variant headings referred from and uniform headings referred to in information notes should also appear as tracings in appropriate authority records. This will allow an agency that cannot use the information note to still display (less precise) reference information from the tracings based on the 4-- and 5-- fields. EXPLANATORY NOTESThroughout the text of the format, the following conventions have been used. (1) The dollar sign ($) has been used in place of the ISO character IS2 (of ISO 646) as the first character of a subfield identifier. (2) The character # has been used in the examples to indicate a blank. (3) In the examples the field separator character is assumed and is not shown explicitly. (4) The phrase "not defined" associated with an indicator position means that no values have been given to that indicator position. (5) R is used in the comment columns to indicate that a subfield is repeatable; NR indicates not repeatable. (6) Since it is intended that this document be used with the UNIMARC Manual, descriptions of the data subfields for headings are not given. The UNIMARC Manual contains detailed descriptions with numerous examples. (7) Externally maintained code lists are needed in some subfields. These code lists are contained in the following Appendixes of the UNIMARC Manual: Appendix A: Language Codes FIELD LISTAll fields defined for this format are listed below: 001 Record Identifier 100 General Processing Data 200 Heading - Personal Name 300 Information Note 400 See Reference Tracing - Personal Name 500 See Also Reference Tracing - Personal Name 675 Universal Decimal Classification (UDC) 700 Linking Heading - Personal Name 801 Originating Source FORMATRECORD LABEL (Mandatory, Not repeatable) The Record Label is constructed according to the provisions of ISO-2709. List of fixed length data elements:
(1) Record Length (character positions 0-4) Five decimal digits, right justified with zero fill. (2) Record Status (character position 5) Codes: c = corrected or revised record (3) Implementation Codes (character positions 6-9) (a) Type of Record. (character position 6) Codes: x = authority entry record (b) Undefined. (character positions 7-9) Three blanks. (4) Indicator Length. (character position 10) One decimal digit (for the UNIMARC/Authorities format the value is 2). (5) Subfield Identifier Length (character position 11) One decimal digit (for the UNIMARC/Authorities format the value is 2). (6) Base Address of Data (character positions 12-16) Five numeric digits, right justified with leading zeros, indicating the starting character position of the first data field relative to the beginning of the record. (7) Additional Record Definition. (character positions 17-19) (a) Encoding Level. (character position 17) A one-character code indicates the degree of completeness of the machine record. The following codes have been defined, and others may be added at a later date. Codes: # = Full (i.e., record contains necessary data including applicable
tracings) (b) Undefined. (character positions 18-19) Two blanks. (8) Directory Map (character positions 20-23) (a) Length of "length of field" part of each directory entry. (character position 20) One decimal digit (for the UNIMARC/Authorities format the value is 4). (b) Length of "starting character position" part of each directory entry. (character position 21) One decimal digit (for the UNIMARC/Authorities format the value is 5). (c) Undefined. (character positions 22-23) Two blanks. The entries in the record directory are constructed according to the specifications in ISO 2709. Entries in the record directory are arranged in ascending order according to the first character of the tag. This block contains numbers that identify the record and the record version. The following fields are defined: 001 Record Identifier This field contains the record control number assigned by the organization creating, using, or distributing the record. Field is not repeatable. Examples: 001 78-34279 005 Version Identifier This field consists of 16 characters indicating the date and time of the latest record transaction. The date is recorded according to ISO 2014 and the time according to ISO 3307. The date portion of the field requires eight numeric characters (4 for the year, 2 for the month, and 2 for the day). The time portion also requires eight numeric characters (2 for the hour, 2 for the minute, 2 for the second, and 2 for a decimal fraction of the second, including the decimal point). Field is not repeatable. Examples: 005 19810901141236.0 015 International Standard Authority Data Number Reserved for the ISADN. This block contains coded data fields. Data in these fields is generally defined in terms of the position of a character in a subfield. If some data in a field is supplied but not all, the omitted data element positions will contain fill characters. The following fields are defined: 100 General Processing Data This field contains basic coded data applicable to all authority records. Data elements not supplied will contain fill characters. Field is not repeatable. Subfield $a General processing data NR List of fixed length data elements:
(1) Date Entered on File (Mandatory) (character positions 0-7) Eight numeric characters which give the date the record was entered into the system as an indication of the currency of the record. A record corrected because of errors in keying or editing will not have a change of date. This date is divided into three sub-elements: The first sub-elements of four characters representing years and two following sub-elements, each two characters long, representing month and day respectively. Example: 5 October 1967: 19671005 (2) Status of Authority Heading Code (character position 8) A one-character alphabetic code is used to indicate the level of establishment of a heading in an authority entry record. Note: This data element should not be confused with record label byte 17 (encoding level) which relates to the fullness of the entire record. a = Established (i.e., heading is established) c = Provisional (i.e., heading cannot be established definitively due to inadequate information; when the heading is next used, it should be reconsidered in the light of any additional information) x = Not applicable (i.e., the record is a reference entry record or a general explanatory entry record and, therefore, the 2-- record heading field contains a variant heading) (3) Language of Cataloguing (Mandatory) (character positions 9-11) A three-character code indicates the language used in cataloguing. The 2-- heading appears as it would in a catalogue based on the language specified here. Also any notes or other instructional information will be in the language of cataloguing. The UNIMARC Language Codes are used for this position. The codes are listed in Appendix A of the UNIMARC Manual. The heading itself may be in a language different from the language of cataloguing. For example, under some cataloguing rules a uniform title for a French anonymous work would be established in its French form no matter what the language of cataloguing is. (4) Transliteration Code (character position 12) A one-character code indicates the transliteration system used for the 2-- heading in the record. a = ISO transliteration scheme (5) Character Set (Mandatory) (character positions 13-16) These four character positions indicate the principal graphic character sets used in the record. Positions 13-14 designate the G0 set and positions 15-16 designate the G1 set. If a G1 set is not needed, positions 15-16 contain blanks. 01 = ISO 646, IRV version (basic Latin set) 50 = ISO 10646 Level 3 Note that ISO 10646, being a 16-bit character set, contains all necessary characters. When positions 13-14 contain '50' this will be used for the C0, C1 and G0 sets. Positions 15-20 will contain blanks. Examples: Transmission is an 8-bit code with G0 set of ISO 646 and G1 set of ISO
extended Latin: 0103 (6) Additional Character Set (character positions 17-20) Two two-character codes indicate up to two additional graphic character sets used in communication of the record. The codes are the same as those used in character positions 13-16. Positions 17-18 designate the G2 set and positions 19-20 designate the G3 set. If no additional character sets are needed, the bytes contain blanks. (The UNIMARC Manual, Appendix J, describes the action required when more than four sets must be accessed.) If no additional sets are involved, the four positions contain blanks. (7) Script of Cataloguing (character position 21-22) A two-character code indicates the script used in cataloguing. The 2-- record heading appears in this script, as do notes and other instructional information.
150 Coded Data Field For Names When the heading in the 2-- heading field is a name (corporate, meeting, or geographic name), then this coded data field is used to convey additional information about the name. Field is not repeatable. Subfield $a Name processing data NR List of fixed length data elements: Name of Data Element Number of Characters Character Position (1) Type of Government Agency 1 0 (1) Type of Government Agency (character position 0) A one-character code indicates whether the heading is for a government organization. (Academic institutions are not considered government agencies.) a = federal/national 152 Rules This field identifies the rule system under which the 2-- heading and its accompanying reference structure were formulated. Field is not repeatable. Subfield $a Cataloguing
rules NR The $a subfield identifies the cataloguing rules used to formulate the heading/reference structure. This would be applicable for most names, titles, and name/titles. The cataloguing rules should be specified using the codes from Appendix H of the UNIMARC Manual or the full name of the rules. For display, codes can be used to generate the abbreviations specified in Guidelines for Authorities and References, Appendix C. The $b subfield identifies the subject system used to formulate the heading/reference structure. This would be especially applicable to topical subjects, but is applicable to names and titles also. In some systems, a heading/reference structure may be formulated under cataloguing rules but also be used in a subject system. Thus the name would be coded for both the descriptive rules and the subject system. The codes from Appendix G of the UNIMARC Manual or the full name of the thesaurus may be used to specify the subject system. Examples: 152 ##$aAACR2$blc 152 ##$blc 152 ##$aAACR2$blc 152 ##$aAACR2$bcaf 152 ##$aAACR2 154 Coded Data Field For Uniform Titles When the heading carried in the 2-- heading field is a uniform title, this coded data field may be used to convey additional information. Field is not repeatable. Subfield $a Title processing data NR List of fixed length data elements: Name of Data Element Number of Characters Character Position (1) Type of series code 1 0 (1) Type of Series Code (character position 0) A one-character code indicates the type of series when the heading is a uniform title of a series. a = monographic series 160 Geographic Area Code This field contains the geographic area code if there is a geographic area associated with the heading. The coding scheme contains seven alphabetic characters and hyphens and, so far as possible, provides a hierarchical breakdown of geographic and political entities. The UNIMARC geographic area codes are used. They are listed in Appendix D of the UNIMARC Manual. Field is not repeatable. Subfield $a Geographic area code R Example: A heading related to England is coded as: The following subfields are used to carry additional information about a heading, tracing or note. $0 Instruction phrase These subfields are defined for all 2-- heading, 4-- and 5-- tracing, and 7-- linking heading fields although they are only used under specific circumstances, thus will never occur in some blocks. Several of these subfields may also appear in the 3-- Note fields. The introductory sections for each of these blocks indicates which of these subfields may appear in those blocks. When these subfields are used they precede all other subfields in the field. $0 Instruction Phrase This subfield $0 (zero) contains a special introductory phrase that can be used when displaying the tracing as a reference. The instruction phrase may be carried in lieu of or in addition to the Relationship Code in subfield $5. The instruction phrase may be used with 4-- and 5-- reference tracing fields. See Guidelines for Use, (11), Display of Reference and Authority Entries, for additional discussion of this and related subfields. Example: Authority entry record: 200 #1$aOrwell,$bGeorge Reference entry display: Blair, Eric Arthur Note: The instruction phrase serves to introduce the 200 heading in the reference generated from the reference tracing. $2 Subject System Code This subfield identifies the subject system in which a tracing or heading belongs (1) when it is different from that of the record heading, which is specified in field 152, $b, or (2) when a topical subject tracing appears in a name or title authority entry record for a heading that is not appropriate for use as a subject. Generally a subject heading and its tracings are part of the subject system specified in field 152, $b, but headings as they would appear in another subject system may be carried as reference tracings to provide links between systems. The subject system code may be used in 4-- and 5-- reference tracing or 7-- linking heading fields. A variable length alphabetic code with maximum length of seven characters is used. The codes that may be used are listed in Appendix G of the UNIMARC Manual. Instructions for obtaining a code are also given in that publication. Example: 152 ##$blc $3 Record Number This subfield identifies a record in which the heading in the field is the heading. It may be used in 5-- see also reference tracing and 7-- linking heading and 4-- see reference tracing fields. In 5-- and 7-- fields, the related record is the authority entry record for the heading. In a 4-- see reference tracing fields, the related record is a reference entry record that is used for display in preference to generating a dis- play from the 4--. Subfield $3 may be used in a 4-- field when the 4-- also contains subfield $5 (Tracing control) in which character position 1 (Reference suppression code) contains value 0 (suppress reference). Example: 210 02$aNational Library of Canada See also Example 1 under 310. $5 Tracing Control This subfield contains fixed position coded data pertinent to the use or display of 4-- and 5-- reference tracings. If special instructions are not needed for a given field, the control subfield need not be used in that field. If it is used, the coding of any position mandates that each prior position be explicitly coded also. The fill character may be used in any position required solely because a subsequent position is needed. Any positions following the last one required for a field are omitted. Thus if no special relationship is to be given and no reference suppression information is needed, subfield $5 does not appear. If only a relationship is needed, then subfield $5 will contain only one character position. If only a reference suppression code is needed, then character position 0 will contain a fill character. If both data elements are needed, both will contain valid values. The following data elements are defined for subfield $5: Name of Data Element Number of Characters Character Position (1) Relationship code 1 0 (1) Relationship Code (character position 0) A one-character alphabetic code indicates a specific relationship between a tracing and the 2-- record heading. The relationship code is used to generate the instruction phrase when displaying the reference traced in the field (as indicated in the table below). The relationship expressed is thus semantically the obverse of the instruction phrase generated for the reference. The meaning of the relationship code may be used directly when displaying an authority entry (see example below). The use of a special phrase is optional when displaying a record, however. It is not incorrect to use the > or >> instruction alone. The relationship code may be used with 4-- and 5-- reference tracing fields. See Guidelines for Use, (11), Display of Reference and Authority Entries, for additional discussion of this and related subfields. The following code values are defined:
Example of instructional phrases generated from relationship codes (in English):
Examples: Authority entry record: 210 02$aDunedin Savings Bank Authority entry display: Dunedin Savings Bank Note: the value "a" in the $5 was used to display the relationship information "(earlier heading)" in this authority entry record display, in addition to its intended use to generate the instruction phrase for the reference entry display illustrated below. Reference entry display: Otago Savings Bank (2) Reference Suppression Code (character position 1) A one-character numeric code indicates that a reference entry should not be automatically generated from a heading in a tracing because a 305 reference note exists in the authority record for the heading or a separate reference record for the heading exists with a 310 reference note. In both cases it is intended that only the note form of the reference should be used in displays. 0 = suppress reference Examples Record 1 (Reference entry record) Record 2 (Authority entry record) Record 3 (Authority entry record) See also Example 1 under field 305. $6 Interfield Linking Data This subfield contains information allowing a field to be linked for processing purposes to other fields in the record. Both of the fields being linked will contain a $6 subfield as specified below. The subfield also contains a code indicating the reason for the link. The first two elements in the subfield must always be present when the subfield is used; the third element is optional. This subfield may be used in the 3-- information note and 4-- and 5-- tracing fields. The following data elements are defined for subfield $6: Name of Data Element Number of Characters Character Position (1) Linking
explanation code 1 0 (1) Linking Explanation Code (character position 0) This code specifies the reason for the interfield linkage. a = alternate script (2) Linking Number (character positions 1-2) This two-digit number is carried in subfield $6 of each of the fields to be linked together. The function of the linking number is to permit matching of associated fields. (It is not intended to act in any way as a sequence or site number.) The linking number may be assigned at random, so long as it is identical in each of the fields to be linked together and does not duplicate the number used to link any other groups of fields in the record. (3) Tag of Linked Field (character positions 3-5) This data element indicates the tag of the field to which a link is being made. The element is optional. If the tag of the field being linked to is the same as the tag of the field being linked, this element would ordinarily be omitted. Example: 100 $a, character positions 21-22: ba The cataloguing agency gives the vernacular and Roman formsof each heading and reference in its records. The optional tag is omitted from the linked fields. $7 Script This subfield identifies the script of the data in the field when a heading, tracing, or note is carried in multiple scripts, e.g., Japanese written in kanji or kana, Hebrew written in Hebrew script and Roman script. The $7 subfield may be used with 2-- headings, 3-- information note, 4-- and 5-- tracing, and 7-- linking heading fields. The script for the first 2-- heading, and the default script for all other field content not otherwise designated by a $7 subfield, is given in field 100, character positions 21-22. If there is more than one 2-- heading, then the additional ones are included for their alternate scripts, and they will contain $7 subfields indicating the script. See Guidelines for Use, (8), Alternative Script Data, for more discussion of scripts. A two-character alphabtic code specifies the script of a heading when the identical heading appears in the record in a different script. The following code values are used:
Example: 100 $a, character positions 21-22: ba $8 Language of Cataloguing This subfield identifies the language of a catalogue for which this heading or tracing was formulated when it is different from that of the 2-- record heading. The language of cataloguing for the 2-- record heading, hence the default language for all data in the record, is given in field 100. A language may be used in 4-- tracing and 7-- linking heading fields. See Guidelines for Use, (8), Parallel Data, for more discussion of language of cataloguing. A three-character alphabetic code specifies the language of the catalogue into which the heading in the field is designed to fit. The UNIMARC Language Codes should be used. The codes are listed in Appendix A of the UNIMARC Manual. Example: 100 $a, character positions 9-11 = fre This block contains the heading for which the record is made. The heading will be a uniform heading if the record is an authority record, and a variant heading if the record is a reference entry or general explanatory entry record. The 2-- fields may be repeated for versions of the 2-- heading in different scripts. If, however, the alternative script form links to a separate record that contains the alternative form as the 2-- heading with appropriate tracings and notes in that script, then the alternative script form should be carried in a 7-- linking heading field. The relator subfield $4 is included in the name fields for its infrequent use with name/title headings. The relator codes used are listed in Appendix C of the UNIMARC Manual. The subfields listed under tags in this block are also used in the heading fields in the 4--, 5--, and 7-- blocks. In the description of the corresponding fields in those blocks, the subfields are not repeated but reference is made to the 2-- block. Since some of the control subfields $0, $2, $3, $5, $6, $7, and $8 are not valid in some blocks, the introductory paragraphs for the block indicate which control subfields can be used. Detailed descriptions of heading data subfields are contained in the UNIMARC Manual under the 7-- block. Only the following control subfield may be used in the 2-- fields: $7 Script The following fields are defined: 200 Heading - Personal Name 230 Heading - Uniform Title 250 Heading - Topical Subject 200 Heading - Personal Name This field contains a personal name heading. Field is repeatable for alternative script forms. First indicator is not defined; contains a blank. Second indicator specifies the way the name is entered:
Examples: 200 #1$aHorne,$bDonald,$f1921- 210 Heading - Corporate Body Name This field contains a corporate or meeting name heading. Territorial names followed by a corporate body subheading are considered corporate body names (tag 210); territorial names alone or only with subject subdivisions as additions are considered territorial names (tag 215). Field is repeatable for alternative script forms. Second indicator specifies the way the names are entered:
Examples: 210 02$aBrunel University.$bEducation Liaison Centre 215 Heading - Territorial or Geographical Name This field contains a territorial or geographical name heading. Territorial names alone or only with subject subdivisions as additions are considered territorial names (tag 215); territorial names followed by a corporate body subheading are considered corporate body names (tag 210). Field is repeatable for alternative script forms.
Examples: 215 ##$aUnited States$xHistory 220 Heading - Family Name This field contains a family name heading. Field is repeatable for alternative script forms.
Example: 220 ##$aDuecker family 230 Heading - Uniform Title This field contains a uniform title heading. A uniform title heading is intended to bring together the records for issues of a work that has been published under different titles or items in series. Field is repeatable for alternative script forms.
Examples: 230 ##$aBible.$mEnglish.$qAuthorized.$iSelections 235 Heading - Collective Uniform Title This field contains a collective uniform title heading. A collective uniform title heading is intended to bring together the records for various works by prolific authors. This field is only used in a 245 HEADING - NAME/COLLECTIVE UNIFORM TITLE field. Field is repeatable for alternative script forms. 0 Complete collected works Second indicator is not defined; contains a blank.
Examples: See field 245 240 Heading - Name/Title This field contains a name/title heading. A name/title heading is intended to bring together the records for various issues of a work or items in series. Each element is coded according to the 2-- field appropriate to the element: 200 HEADING - PERSONAL NAME, 210 HEADING - CORPORATE BODY NAME, 215 HEADING - TERRITORIAL OR GEOGRAPHICAL NAME, or 220 HEADING - FAMILY NAME for the name; and a 230 HEADING - UNIFORM TITLE for the title. The tag, indicators, and data subfields for the name and title are embedded in a field 240, with each preceded by subfield identifier $1. Subject subdivisions are carried in the embedded title field. When control subfields are needed, they should precede the first $1 subfields containing embedded data. (Control subfields defined for the 200, 210, 215, 220, or 230 fields are not embedded in a $1 subfield.) A more detailed description of embedded fields is contained in the UNIMARC Manual under the 4-- field block. Field is repeatable for alternative script forms.
Examples: 240 ##$1215##$aFrance.$1230##$a Bulletin officiel du registre du commerce See also Example under field 540 for use of control subfields in an embedded field. 245 Heading - Name/Collective Uniform Title This field contains a name/collective uniform title heading. A name/collective title heading is intended to bring together records for various works by prolific authors. Each element is coded according to the 2-- field appropriate to the element: 200 HEADING - PERSONAL NAME, 210 HEADING - CORPORATE BODY NAME, 215 HEADING - TERRITORIAL OR GEOGRAPHICAL NAME, or 220 HEADING - FAMILY NAME for the name; and a 235 HEADING - COLLECTIVE UNIFORM TITLE for the collective title. The tag, indicators, and data for the name and title of these are embedded in a field 245, with each preceded by subfield identifier $1. Subject subdivisions are carried in the embedded collective title field. When control subfields may be needed, they should precede the first $1 subfields containing embedded data. (Control subfields defined for the 200, 210, 215, 220 or 235 fields are not embedded in a $1 subfield.) A more detailed description of embedded fields is contained in the UNIMARC Manual under the 4-- field block. Field is repeatable for alternative script forms.
Examples: 245 ##$1200#1$aShakespeare,$bWilliam,$f1564-1616.$12350# $aWorks.$mRussian 250 Heading - Topical Subject This field contains a topical subject heading.
Examples: 250 ##$aEducation$yItaly Information notes are used in an authority entry record to provide historical information about a heading or to provide information when simple references generated from tracings do not explain adequately a relationship. An information note in a reference entry record explains relationships between the reference heading and the uniform heading(s) to which the user of the reference is directed. Information notes in general explanatory entry records give the conventions used in formulating or filing uniform headings of the type one might expect to find under the form given in the explanatory heading. All information notes are in a textual form suitable for display to the public, for whom they are intended. Notes intended primarily to guide cataloguers are carried in the 8-- SOURCE INFORMATION BLOCK. Only the following control subfields may be used in the 3-- fields: $6 Interfield Linking Data The following information note fields are defined: 300 Information Note 300 Information Note This field is used in an authority entry or a reference record to assist in explaining the relationship between the 2-- heading and other entities. This field is also used to provide historical information about a heading. Field is repeatable. First indicator specifies the type of note: Second indicator is not defined; contains a blank.
Example 1: Record 1 (Authority entry record) Record 2 (Authority entry record) Example 2: Record 1 (Authority entry record) Record 2 (Authority entry record) Record 3 (Authority entry record) Record 4 (Authority entry record) Example 3: 210 01$aCanada.$bRoyal Commission on Banking Finance Note: Example of an information note with no related references. 305 Textual See Also Reference Note This field is used in an authority entry record when an adequate see also reference cannot be constructed solely from the content of one or more 5-- see also reference tracing field(s) contained in authority records for the related headings. The uniform heading referred from is the 2-- record heading of the authority entry record. Each uniform heading referred to and the "see also" (or similar) instruction, are given in a 305 field. This note is generally used in addition to, not in lieu of, the 5-- see also reference tracings in records for the related headings. The uniform heading in the 2-- record heading field is traced as a 5-- see also reference tracing in the authority entry record for each heading referred to in the 305 note. If the relationship among the uniform headings is reciprocal, the authority entry record that carries this note also carries 5-- see also reference tracings for each heading referred to in the note. If the note does not refer directly to other uniform headings but only gives examples, then there will be no corresponding tracings. The example headings should be cited in an 825 EXAMPLE UNDER NOTE in the authority entry record for each heading. Field is repeatable. Second indicator is not defined; contains a blank.
Example 1: Record 1 (Authority entry record) Record 2 (Authority entry record) Record 3 (Authority entry record) Example 2: (Authority entry record) Example 3: Record 1 (Authority entry record) Note: This note gives information and includes examples but does not point to other specific uniform headings, thus there are no 5-- tracings in records for the headings given as examples. Those records should contain an 825 EXAMPLE UNDER NOTE that cites this record. Record 2 (Authority entry record) 310 Textual See Reference Note This field is used in a reference entry record when an adequate see reference cannot be constructed solely from the content of one or more 4-- see reference tracing field(s). The variant form of name referred from is the 2-- record heading of the reference entry record. Each heading referred to and the "see" (or similar) instruction are given in a 310 field. The heading of the 2-- field of the reference record is traced as a 4-- see reference tracing field in the authority entry record for each heading referred to, unless the note gives only examples, in which case there are no 4-- tracings but an 825 EXAMPLE UNDER NOTE is used in the authority entry record for each heading. Field is repeatable. First indicator specifies the type of note: Second indicator is not defined; contains a blank.
Example 1: Record 1 (Reference entry record) Record 2 (Authority entry record) Record 3 (Authority entry record) Example 2: Record Label, character position 6 = y (reference entry record) 320 General Explanatory Reference Note This field is used in a general explanatory entry record to provide explanatory information to assist in searching or filing. The word or phrase referred from is given in the 2-- field and the explanatory information is given in a 320 field. The reference is not traced on any authority entry record. Field is not repeatable.
Example: Record Label, character position 6 = z (general explanatory entry record) 330 General Scope Note This field is used in an authority entry record to describe the scope of the heading in the 2-- field. Scope information may give a precise definition of a potentially ambiguous term, contrasting information about similar terms, notices to users, etc. Field is repeatable. 0 Note concerns name or title use of heading Second indicator is not defined; contains a blank.
Example 1: 200 #1$aShakespeare,$bWilliam,$f1564-1616 Example 2: Record 1 Record 2 4-- SEE REFERENCE TRACING BLOCK 5-- SEE ALSO REFERENCE TRACING BLOCK These two blocks contain the see and see also reference tracings that form the reference structure for the heading in the 2-- field of the record. The fields for the 2-- heading and the 4-- and 5-- reference tracings have the same indicators and subfield identifiers. The subfields are listed under their respective 2-- fields and are not repeated below. The following control subfields may be used in the 4-- fields: $0 Instruction Phrase The following control subfields may be used in fields in the 5-- fields: $0 Instruction Phrase $7 Script The use of the control subfields is described in a special section immediately preceding the 2-- HEADING BLOCK description. The following fields are defined: 400 See Reference Tracing - Personal Name 500 See Also Reference Tracing - Personal Name This field contains the tracing for a form of personal name referred from. Field is repeatable. Examples: 200 #1$aDuMaurier,$cDame$bDaphne 200 #1$aWaterman,$bAnthony M.C.,$f1931- 200 #1$aRolfe,$bFr. 410 See Reference Tracing - Corporate Body Name This field contains the tracing for a form of corporate body name referred from. Territorial names followed by a corporate body subheading are considered corporate body names (tags 410); territorial names alone or only with subject subdivisions as additions are considered territorial names (tags 415). Field is repeatable. Examples: 210 02$aDelaware Racing Commission 210 02$aSchweizerisches Rotes Kreuz 210 12$aSymposium on Endocrines and Nutrition$f(1956 ;$eUniversity of
Michigan) 210 01$aUnited States.$bCongress$xCommittees 415 See Reference Tracing - Territorial or Geographical Name This field contains the tracing for a form of a territorial or geographical name referred from. Territorial names alone or only with subdivisions as additions are considered territorial names (tags 415); territorial names followed by a corporate subheading are considered corporate names (tags 410). Field is repeatable. Examples: 215 ##$aAustralia 215 ##$aMcAlester (Okla.) 420 See Reference Tracing - Family Name This field contains the tracing for a form of family name referred from. Field is repeatable. Example: 220 ##$aMedici, House of 430 See Reference Tracing - Uniform Title This field contains the tracing for a form of uniform title referred from. Field is repeatable. Examples: 230 ##$aNibelungenlied 230 ##$aBible$xMusic 440 See Reference Tracing - Name/Title This field contains the tracing for a form of name/title referred from. The data are carried in appropriate 2-- fields embedded in the 440 field according to the technique described under field 240. Field is repeatable. Example: 240 ##$1200#1$aShakespeare,$bWilliam,$f1564-1616.$1230##$aHamlet 445 See Reference Tracing - Name/Collective Uniform Title This field contains the tracing for a form of name/collective uniform title referred from. The data are carried in appropriate 2-- fields embedded in the 445 field according to the technique described under field 245. Field is repeatable. Example: 245 ##$1200#1$aShakespeare,$bWilliam,$f1564-1616.$12350#$aWorks. $mRussian. 450 See Reference Tracing - Topical Subject This field contains the tracing for a topical subject term that is referred from. Field is repeatable. Example: 250 ##$aFederal aid to education 500 See Also Reference Tracing - Personal Name This field contains the tracing for a uniform personal name heading that is related to the heading in the 2-- field. Field is repeatable. Examples: 200 #1$aEdwards,$bP.$g(Paul) 200 #0$aPseudo-Brutus 200 #0$aKumbel 200 #1$aRossi$bJean-Baptiste 200 #1$aMorris,$bJohn 510 See Also Reference Tracing - Corporate Body Name This field contains the tracing for a uniform corporate body name heading that is related to the heading in the 2-- field. Territorial names followed by a corporate body subheading are considered corporate body names (tags 510); territorial names alone or only with subject subdivisions as additions are considered territorial names (tags 515). Field is repeatable. Examples: 210 01$aGreat Britain.$bBoard of Trade 210 02$aAmerican Material Handling Society 515 See Also Reference Tracing - Territorial or Geographical Name This field contains the tracing for a territorial or geographical name heading that is related to the heading in the 2-- field. Territorial names alone or only with subject subdivisions as additions are considered territorial names (tags 515); territorial names followed by a corporate subheading are considered corporate names (tags 510). Field is repeatable. Examples: 215 ##$aSri Lanka 215 ##$aKabwe (Zambia) 520 See Also Reference Tracing - Family Name This field contains the tracing for a uniform family name heading that is related to the heading in the 2-- field. Field is repeatable. Example: 220 ##$aDuecker family 530 See Also Reference Tracing - Uniform Title This field contains the tracing for a uniform title heading that is related to the heading in the 2-- field. Field is repeatable. Example: 230 ##$aCaedmon manuscripts 230 ##$aKoran$xReadings 540 See Also Reference Tracing - Name/Title This field contains the tracing for a name/title heading that is related to the heading in the 2-- field. The data are carried in appropriate 2-- fields embedded in the 540 field according to the technique described under field 240. Field is repeatable. Example: 240 ##$1200#1$aFauré,$bGabriel,$f1845-1924.$1230##$aBallades,$rpiano,$sop.19 545 See Also Reference Tracing - Name/Collective Uniform Title This field contains the tracing for name/collective uniform title that is related to the heading in the 2-- field. The data are carried in appropriate 2-- fields embedded in the 545 field according to the technique described under field 245. Field is repeatable. Example: 245 ##$1200#1$aShakespeare,$bWilliam,$f1564-1616.$12350#$aPlays 550 See Also Reference Tracing - Topical Subject This field contains the tracing for a valid topical subject heading that is related to the heading in the 2-- field. Field is repeatable. Example: 250 ##$aElectronic data processing$xData preparation 6-- CLASSIFICATION NUMBER BLOCK This block contains fields for classification numbers that have a subject correspondance with the 2-- heading of the record. These numbers may be single numbers or ranges of numbers. Provision is made for including textual explanatory terms with the numbers. The following fields are defined: 675 Universal Decimal Classification (UDC) 675 Universal Decimal Classification (UDC) This field contains the UDC number or range of numbers associated with an authority heading. The UDC number may be accompanied by terms that identify the UDC number. Field is repeatable.
676 Dewey Decimal Classification (DDC) This field contains the DDC number or range of numbers associated with an authority heading. The DDC number may be accompanied by terms that identify the DDC number. Field is repeatable.
Example: 250 ##$aGold 680 Library of Congress Classification (LCC) This field contains the LC number or range of numbers associated with an authority heading. The LC number may be accompanied by terms that identify the LC number. Field is repeatable.
Examples: 250 ##$aScaffolding 250 ##$aString quartet 686 Other Classification Numbers This field contains a class number or range of numbers (from classification systems which are not internationally used but which are widely understood published schemes) associated with an authority heading. The classification scheme is identified in a subfield $2. Codes for identification of classification schemes are given in Appendix G of the UNIMARC Manual. Field is repeatable.
This block contains parallel or alternative script forms of the heading in the 2-- block and link to a separate record in which the 7-- heading is the primary entity. Under certain practices additional parallel forms of the heading, in a language other than that which is the valid form under the Language of Cataloguing specified in field 100, character positions 9-11, may be specially identified and carried in this block. For each parallel heading the language of the catalogue into which the heading fits is recorded in a $8 subfield. These fields are also used to record alternate script representations of the 2-- record heading when another record exists for the alternative script heading and its reference structure. For an alternative script heading, a $7 Script subfield is added to the 7-- field. (A $6 Interfield Linking Data subfield is not required since all headings in 7-- fields link to the heading in the 2-- field by definition.) The fields in this block are repeatable to accommodate multiple headings. See Guidelines for Use, (8), Parallel Data and Alternative Script Data for general discussion of these types of data. Only the following control subfields may be used in the 7-- fields: $2 Subject System Code The following fields are defined: 700 Linking Heading - Personal Name 730 Linking Heading - Uniform Title 750 Linking Heading - Topical Subject 700 Linking Heading - Personal Name This field contains a uniform personal name heading that is another form of the 2-- heading. Field is repeatable. EXAMPLE 1: Record in English language catalogue: Record in French language catalogue: EXAMPLE 2: Record in Roman script catalogue: Record in Japanese script catalogue: 710 Linking Heading - Corporate Body Name This field contains a uniform corporate body name heading that is another form of the 2-- heading. Territorial names followed by a corporate body subheading are considered corporate body names (tag 710); territorial names alone or only with subject subdivisions as additions are considered territorial names (tag 715). Field is repeatable. EXAMPLES: Record in English language catalogue: Record in French language catalogue: 715 Linking Heading - Territorial or Geographical Name This field contains a territorial or geographical name heading that is another form of the 2-- heading. Territorial names alone or only with subject subdivisions as additions are considered territorial names (tag 715); territorial names followed by a corporate body subheading are considered corporate body names (tag 710). Field is repeatable. Examples: Record in German language catalogue: Record in French language catalogue: Record in Italian language catalogue: 720 Linking Heading - Family Name This field contains a uniform family name heading that is another form of the 2-- heading. Field is repeatable. Indicators and subfields are defined as in field 220. Example: 220 ##$aDuecker family 730 Linking Heading - Uniform Title This field contains a uniform title heading that is another form of the 2-- heading. Field is repeatable. Example: 100 $a, character positions 9-11 = spa 740 Linking Heading - Name/Title This field contains a name/title heading that is another form of the 2-- heading. The data are carried in appropriate 2-- fields embedded in the 740 field according to the technique described under field 240. Field is repeatable. Example: 100 $a, character positions 9-11 = fre 745 Linking Heading - Name/Collective Uniform Title This field contains a name/collective uniform title heading that is another form of the 2-- heading. The data are carried in appropriate 2-- fields embedded in the 745 field according to the technique described under field 245. Field is repeatable. 750 Linking Heading - Topical Subject This field contains a topical subject heading that is another form of the 2-- heading. Field is repeatable. Examples: Record in English language catalogue: Record in French language catalogue: This block contains information concerning the agencies responsible for the record and cataloguer's notes recorded by those agencies. Cataloguer's notes are primarily intended to guide cataloguers and thus are usually not written in a form suitable to public display. Notes intended for public display are in the 3-- INFORMATION NOTE BLOCK. The following fields are defined: 801 Originating Source 801 Originating Source - Mandatory This field identifies the agency responsible for the creation of the record and the date of the entry. It is repeatable to show the transcribing, modifying or issuing agency. The date for new records is the date of the creation of the entry. For revised records, the date recorded is the date of the latest revision. Field is repeatable. Second indicator specifies the function performed by the agency: 0 Original cataloguing agency
Example: 801 #0$aUS$bDLC$c19800516 The country is coded according to ISO 3166. The name of the agency may be in coded form using the identifiers found in the Guidelines for Authorities and References, Appendix B; the codes from Symbols of American Libraries which includes many non-U.S. library agencies; or the full name of the agency or a national code. The date of latest transaction should be recorded according to ISO 2014, i.e., in the form YYYYMMDD.810 Source Data Found This field contains a citation to a reference source when information about the heading was found. The first 810 field usually contains the citation for the bibliographic work for the cataloguing of which the heading has been established. Field is repeatable.
Examples: 200 #1$aAvery,$bHarold Eric 215 ##$aCalanques, Massif des (France) 200 ##$aHailsham of Saint Marylebone,$bQuintin Hogg,$cBaron 815 Source Data Not Found This field contains the citations for consulted reference sources in which no information about the heading was found. Field is not repeatable. Subfield $a Citations R Examples: 200 #1$aJones,$bA. Wesley 240 ##$aCalanques (France) 820 Usage or Scope Information This field contains information limiting the use of the 2-- record heading and/or differentiating persons or bodies with similar names. Field is repeatable. Subfield $a Note text R Examples: 200 #1$aSmithe,$bSam 200 #1$aLafontaine,$bJacques,$f1944- 250 ##$aHoly Year 825 Example Under Note This field is used in a record to indicate that the heading in the 2-- field has been used as an example or has been cited in a note in another record. This field contains the 2-- of the other record. Field is repeatable. Subfield $a Note Text NR Examples: 210 02$aLeague of Nations$xOfficials and employees 250 ##$aJudges$xTravel regulations 830 General Cataloguer's Note This field is used to record biographical, historical, or other information about the heading. The data may include references to specific rules applied, notes justifying the choice of form of heading, etc. Such data could also appear as part of other fields, e.g., 810 SOURCE DATA FOUND. Field is repeatable. Subfield $a Note text R Examples: 200 #1$aKorman,$bGerd 200 #1$aOtter$bA.A. den$g(Andy Albert den),$f1941- 835 Deleted Heading Information This field is used to record why the heading in the 2-- is being deleted from an authority file. It appears in a record in which Record Label, Record Status (character position 5), contains value d, deleted record. Field is repeatable.
Example: Record Label, character position 5 = d (deleted record) EXAMPLESExample 1: Record status - n 001 n##81123456b Example 2: Record 1: Record status - n 001 A369875 Record 2: Record status - n 001 B329638
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Latest Revision: May 25, 1999 |
Copyright © 1995-2000
International Federation of Library Associations and Institutions www.ifla.org | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||