UNIMARC Manual-Authorities Format 2001 (Concise version)

The following list represents the state of the format as at 25 January 2001. It is an abridged version of UNIMARC Manual-Authorities Format 2nd revised and enlarged edition.

Fields are optional unless marked as mandatory.

UNIMARC 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 BLOCKS

The 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: 1) explain the relationship between the record heading (2--) and other headings; 2) contribute to the identification of the entity described in the authority record.

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 USE

(1) Mandatory Fields

In addition to the Record Label and Directory, the following fields must be present in the machine-readable records:

001 Record identifier
100 General processing data (certain data elements only)
152 Rules
2-- Heading
801 Originating source

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.

(2) Control Functions

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 Bibliographic Format, Appendix J.

(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 "repeatable" is associated with a subfield identifier, then that subfield may occur more than one time in an occurrence of the field.

(4) Subfield Order

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.

(5) Fill Character

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.

(6) Coded Data Values

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.
v	Combination	Used when a combination of the individual coded characteristics occur in the entity.
x	Not applicable	Used when a characteristic is not appropriate for the type of entity being described.
y	Not present	Used when the characteristic being coded is not present for the entity being described.
z	Other	Used when codes are being assigned and the characteristics of the entity are known, but none of the defined codes is appropriate.
|	Fill character	Used when no attempt is being made to assign the codes.

(7) Punctuation

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.

(8) Format Use

Authority Entry Records:

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]
410	01	$aUnited States.$bBureau of Mines.$bPittsburgh Mining and Safety Research Center
		[variant heading as see reference tracing]
510	02	$5a$aPittsburgh Mining and Safety Research Center
		[related heading as see also reference tracing]

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)
200	#1	$aJapp,$bAlexander H.
305	0#	$aFor works of this author written under pseudonyms, see also$bGray, E. Condor$aand$bPage, H.A.
		[related headings in textual see also reference note]
Record 2 (Authority entry record)
200	#1	$aGray,$bE. Condor
500	#1	$5z0$aJapp,$bAlexander H.
		[related heading as see also reference tracing with display suppressed]
Record 3 (Authority entry record)
200	#1	$aPage,$bH.A.
500	#1	$5z0$aJapp,$bAlexander H.
		[related heading as see also reference tracing with display suppressed]

Reference Entry Records:

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)
200		#1		$aKacew$bRomain [variant heading as reference heading]
310		0#		$aÉcrit sous deux pseudonymes$bAjar, Émile)$bGary, Romain
			[textual see reference note]
Record 2 (Authority entry record)
200	#1		$aAjar$bÉmile
400	#1		$5z0$aKacew$bRomain
			[variant heading as see reference tracing with display suppressed]
Record 3 (Authority entry record)
200	#1		$aGary$bRomain
400	#1		$5z0$aKacew$bRomain
			[variant heading as see reference tracing with display suppressed]

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]
320	##	$aConference proceedings are entered under the name of the conference, etc., or the title of the publication if the conference, etc., lacks a name. Thus, see also: Symposium..., Workshop..., etc., [general explanatory reference note]

Parallel Data:

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
001		12345
210	02	$aNational Library of Canada
		[Notes and tracings for an English language catalogue]
710	02	$367890$8frefre$aBibliothèque nationale du Canada
Record 2
001		67890
210	02	$aBibliothèque nationale du Canada
		[Notes and tracings for a French language catalogue]
710	02	$312345$8engeng$aNational Library of Canada

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:

100	##	$aYYYYMMDDaswey0103####ba0
215	##	$8sweswe$aSverige
415	##	$8sweeng$aSweden
415	##	$8swerus$aShvetsiia
415	##	$8swefre$aSuède

In the second edition of this format a distinction is made for a given record between:

1) the language of cataloguing, used for the qualifiers in the headings (2--), see reference tracings (4--), also reference tracings (5--), linking headings (7--), and for notes (3--)

2) the language of the base heading, that is to say the part of the heading that identifies the entity excluding any qualifying data. For example: in the heading 200.#1$aNicolini da Sabbio$bDomenico$cimprimeur-libraire$f15-- to 160-?, the base heading is "$aNicolini da Sabbio$bDomenico", and the language of this base heading is Italian. The language of cataloguing being French, the qualifiers are expressed in French, i.e., "$cimprimeur-libraire".

Alternative Script Data:

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 of cataloguing and script of the base heading 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 of cataloguing and script of the base heading subfield.

Example

001 82-6290
100 ##$aYYYYMMDDaengy03####ba0
200 #1$7ba0yba0a$8engrus$aGlinka,$bMikhail Ivanovich
200 #1$7ba0yca0y$8engrus$a[Glinka etc. in Cyrillic]

Note: The printed text of UNIMARC Authorities contains the correct forms in a Cyrillic character set (as would any catalogue entry)

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 of cataloguing and script of the base heading 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

EX 1

Record 1
100 ##$aYYYYMMDDaengy03######ba0
215 ##$aUnited States
415 ##$aUSA
715 ##$7ca0yca0y$8rusrus$a[United States in Cyrillic]

Record 2
100 ##$aYYYYMMDDarusy0r######ca0
215 ##$a[United States in Cyrillic]
415 ##$a[USA in Cyrillic]
715 ##$7ba0yba0y$8engeng$aUnited States

Note: The printed text of UNIMARC Authorities contains the correct forms in a Cyrillic character set (as would any catalogue entry)

EX 2

Record 1
001 82-6290
100 ##$aYYYYMMDDaengy03####ba0
200 #1$7ba0yba0a$8engrus$aGlinka,$bMikhail Ivanovich
<Notes and tracings for a Latin script catalogue>
700 #1$382-3498$7ca0yca0y$8rusrus$a[Glinka etc. in Cyrillic]

Record 2
001 82-3498
100 ##$aYYYYMMDDarusy02####ca0
200 #1$a[Glinka etc. in Cyrillic]
<Notes and tracings for a Cyrillic script catalogue>
700 #1$382-6290$7ba0aba0a$8engrus$aGlinka,$bMikhail Ivanovich

Note: The printed text of UNIMARC Authorities contains the correct forms in a Cyrillic character set (as would any catalogue entry)

Composite Headings:

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 Bibliographic Format, 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 $j, $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
Areas as Specified in GARE

Present in all types of records:

0-- Identification Block	ISADN area (where applicable)
1-- Control Information Block
8-- Source Information Block	Cataloguer's note area, Source area

Authority entry record:

(Type of record = x)

2-- Heading block (uniform heading)	Authority heading area
300 Information note	Information note area
305 Textual see also reference note	Information note area
4-- See reference tracing block	See reference tracing area
5-- See also reference tracing block	See also reference tracing area
7-- Linking heading block	Authority heading area

Reference entry record:
(Type of record = y)

2-- Heading block (variant heading)	Reference heading area
300 Information note	Information note area
310 Textual see reference note	Uniform heading area
7-- Linking heading block	Reference heading area

General explanatory entry record:
(Type of record = z)

(10) Correspondance Between UNIMARC/Authorities and UNIMARC/Bibliographic

UNIMARC/Authorities Heading Fields Heading Usage in UNIMARC Bibliographic Fields

200 Personal name	700, 701, 702 4-- with embedded 700, 701, 702 600 604 with embedded 700, 701, 702
210 Corporate or meeting name	710, 711, 712 4-- with embedded 710, 711, 712 601 604 with embedded 710, 711, 712
215 Territorial or geographic name	710, 711, 712 4-- with embedded 710, 711, 712 601, 607 604 with embedded 710, 711, 712
216 Trademark	716 [Reserved for future use]
220 Family name	720, 721, 722 4-- with embedded 720, 721, 722 602 604 with embedded 720, 721, 722
230 Title	500 4-- with embedded 500 605
240 Name and title (embedded 200, 210, 215, or 220 and 230)	4-- with embedded 7-- and 500 7-- 604 with embedded 7-- and 500 500
245 Name and collective title (embedded 200, 210, 215, or 220 and 235)	4-- with embedded 7-- and 501 604 with embedded 7-- and 501 7-- 501
250 Topical subject	606
260 Place access	620
280 Form, genre or physical characteristics	608

(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 NOTES

Throughout 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) Since it is intended that this document be used with the UNIMARC Manual Bibliographic Format, descriptions of the data subfields for headings are not given. The UNIMARC Manual Bibliographic Format contains detailed descriptions with numerous examples.

(6) Externally maintained code lists are needed in some subfields. These code lists are contained in the following Appendices of the UNIMARC Manual - Bibliographic Format:

Appendix A: Language Codes
Appendix B: Country Codes
Appendix C: Relator Codes
Appendix D: Geographic Area Code
Appendix G: Subject-System Codes
Appendix H: Cataloguing Rules
Appendix J: Character Sets

 

FIELD LIST

All fields defined for this format are listed below:

0--	IDENTIFICATION BLOCK
001	Record Identifier
005	Version Identifier
015	International Standard Authority Data Number
035	Other System Control Numbers
1--	CODED INFORMATION BLOCK
100	General Processing Data
101	Language of the entity
102	Nationality of the entity
106	Coded Data Field : Personal/Corporate/Family Name/Trademark used as Subject Heading
120	Coded Data Field : Personal Name
123	Coded Data Field : Territorial or Geographical Name
150	Coded Data Field: Corporate Name
152	Rules
154	Coded Data Field for Uniform Titles
160	Geographic Area Code
2--	HEADING BLOCK
200	Heading - Personal Name
210	Heading - Corporate Body Name
215	Heading - Territorial or Geographical Name
216	Heading - Trademark
220	Heading - Family Name
230	Heading - Uniform Title
235	Heading - Collective Uniform Title
240	Heading - Name/Title
245	Heading - Name/Collective Uniform Title
250	Heading - Topical Subject
260	Heading - Place Access
280	Heading -Form, Genre or Physical Characteristics
3--	NOTES BLOCK
300	Information Note
305	Textual See Also Reference Note
310	Textual See Reference Note
320	General Explanatory Reference Note
330	General Scope Note
340	Biography and Activity Note
356	Geographical Notes
4--	SEE REFERENCE TRACING BLOCK
400	See Reference Tracing - Personal Name
410	See Reference Tracing - Corporate Body Name
415	See Reference Tracing - Territorial or Geographical Name
416	See Reference Tracing - Trademark
420	See Reference Tracing - Family Name
430	See Reference Tracing - Uniform Title
440	See Reference Tracing - Name/Title
445	See Reference Tracing - Name/Collective Uniform Title
450	See Reference Tracing - Topical Subject
460	See Reference Tracing - Place Access
480	See Reference Tracing - Form, Genre or Physical Characteristics
5--	SEE ALSO REFERENCE TRACING BLOCK
500	See Also Reference Tracing - Personal Name
510	See Also Reference Tracing - Corporate Body Name
515	See Also Reference Tracing - Territorial or Geographical Name
516	See Also Reference Tracing - Trademark
520	See Also Reference Tracing - Family Name
530	See Also Reference Tracing - Uniform Title
540	See Also Reference Tracing - Name/Title
545	See Also Reference Tracing - Name/Collective Uniform Title
550	See Also Reference Tracing - Topical Subject
560	See Also Reference Tracing - Place Access
580	See Also Reference Tracing - Form, Genre or Physical Characteristics
6--	CLASSIFICATION NUMBER BLOCK
675	Universal Decimal Classification (UDC)
676	Dewey Decimal Classification (DDC)
680	Library of Congress Classification (LCC)
686	Other Classification Numbers
7--	LINKING HEADING BLOCK
700	Linking Heading - Personal Name
710	Linking Heading - Corporate Body Name
715	Linking Heading - Territorial or Geographical Name
716	Linking Heading - Trademark
720	Linking Heading - Family Name
730	Linking Heading - Uniform Title
740	Linking Heading - Name/Title
745	Linking Heading - Name/Collective Uniform Title
750	Linking Heading - Topical Subject
760	Linking Heading - Place Access
780	Linking Heading - Form, Genre or Physical Characteristics
8--	SOURCE INFORMATION BLOCK
801	Originating Source
810	Source Data Found
815	Source Data Not Found
820	Usage or Scope Information
825	Example Under Note
830	General Cataloguer's Note
835	Deleted Heading Information
836	Replaced Heading Information
856	Electronic Location and Access
886	Data not Converted from Source Format
9--	NATIONAL USE BLOCK

RECORD LABEL (Mandatory, Not repeatable)

Fixed Length Data Elements

Name of Data Element	Number of Characters	Character Position
Record Length	5	0-4
Record Status	1	5
Implementation Codes	4	6-9
Indicator Length	1	10
Subfield Identifier Length	1	11
Base Address of Data	5	12-16
Additional Record Definition	3	17-19
Directory Map	4	20-23

 

Notes on Field Contents

0-4	Record Length
5	Record Status
	c = corrected or revised record
	d = deleted record
	n = new record
6-9	Implementation Codes
	6	Type of Record
		x = authority entry record
		y = reference entry record
		z = general explanatory entry record
7-8	Undefined
9	Type of entity
		a = personal name entry
		b = corporate name entry
		c = territorial or geographical name
		d = trademark
		e = family name
		f = uniform title
		g = collective uniform title
		h = name/title
		i = name/collective uniform title
		j = topical subject
		k = place access
		l = form, genre or physical characteristics
10	Indicator Length	= 2
11	Subfield Identifier Length	= 2
12-16	Base Address of Data
17-19	Additional Record Definition
	17	Encoding Level
		# = Full
		3 = Partial