LC-PCC PS for 1.7.1
GENERAL GUIDELINES ON TRANSCRIPTION
Introduction
LC practice/PCC practice: This Policy Statement is an overall statement related to punctuation/spacing conventions. For convenience, it addresses in one place conventions applicable to access points in bibliographic and name authority records and those applicable to other parts of the bibliographic record.
Much of the data in a MARC record are explicitly identified by content designation (tags, indicators, subfield codes). Upon output or display, the content designation is used to determine various display conventions including spacing. Internally there is often no spacing at all but instead content designation, particularly subfield codes. In displays that do not show content designation, spacing is substituted. How much spacing is at the discretion of a particular system. However, for data that are not subfielded (e.g, the constituent elements of a corporate name serving as a qualifier, the unsubfielded units in a linking entry field (hereafter "linking entry"), unsubfielded statements or data in MARC field 245
), it is necessary to establish the spacing to be input. The computerized environment is oriented to a single-space convention throughout authority and bibliographic records.
), it is necessary to establish the spacing to be input. The computerized environment is oriented to a single-space convention throughout authority and bibliographic records. Note that some systems display a space on either side of a subfield code to aid the comprehension of subfielded data. Such "spaces" are also a function of display, i.e., they are not carried internally. In the examples in this policy statement, no spaces are used on either side of a MARC subfield code to insure that there is no confusion about the spacing convention being illustrated.
Access Points in Name Authority and Bibliographic Records (General)
LC practice/PCC practice: These general conventions are applicable to MARC fields 1XX, 4XX, 5XX in authority records and MARC fields 1XX, 240, 6XX, 70X-75X, and 8XX in bibliographic records. For bibliographic linking entries (MARC fields 76X-78X) see the section "Bibliographic Linking Entries"
in this Policy Statement.
, 4XX, 5XX in authority records and MARC fields 1XX, 240, 6XX, 70X-75X, and 8XX in bibliographic records. For bibliographic linking entries (MARC fields 76X-78X) see the section "Bibliographic Linking Entries" in this Policy Statement.1.
Punctuation/spacing within access points. Use internal punctuation to set off unambiguously the units of access points (including name/title portions of name/title fields). The marks of punctuation for this purpose are a period ( . ), a comma ( , ), a quotation mark ( " ), a question mark ( ? ), an exclamation mark ( ! ), and a hyphen ( - ).
a)
Spaces following periods. Leave one space after a period or other mark of ending punctuation that serves to separate units of access points. If the period or other mark of ending punctuation is followed by a subfield code, the space can be generated on display. If no subfield code follows, e.g., as in units within parenthetical qualifiers, input the space.
b)
Punctuation preceding the name of a language in authorized access points of works or expressions. Precede the language by a period as instructed in RDA E.1.2.5 unless another mark of ending punctuation is present.
unless another mark of ending punctuation is present.c)
Ampersand. Input one space on either side of an ampersand or an ampersand equivalent used in an access point.
d)
Parenthesis. If a unit of an access point other than the last ends in a closing parenthesis, input after the closing parenthesis the same punctuation, usually a period, that would be used if there were no parenthesis.
EXAMPLE
| 110 1# | $aNew York (State).$bGovernor (1929-1932 : Roosevelt) |
Authorized access point on either a bibliographic or name authority record
| 110 2# | $aCatholic Church.$bPope (1978-2005 : John Paul II).$tRedemptor hominis.$lEnglish |
Authorized access point on a name authority record
| 400 1# | $aSmith, A. G.$q(Albert Gray),$d1945-$tDiscovering Canada |
Variant access point on a name authority record
e)
Quotation mark. Use double quotation marks instead of other forms of quotation marks. If a unit of an access point other than the last ends in a quotation mark, input a period or other mark of ending punctuation inside the quotation mark.
EXAMPLE
| 110 2# | $aCasa de la Cultura Ecuatoriana "Benjamin Carrión."$bNúcleo de Bolívar |
Authorized access point on a name authority record
| 111 2# | $aSimposio "Antropólogos y Misioneros: Posiciones Incompatibles?"$d(1985 :$cBogotá, Colombia) |
Authorized access point on either a bibliographic or name authority record
| 130 #0 | $aCollection "Bibliothèque des matières premières."$pSérie "Energie" |
Authorized access point on a name authority record
f)
Open date. Leave one space between an open date and any data that follow it within the same subfield. When a subfield code immediately follows an open date, do not leave a space.
2.
Ending mark of punctuation. For access points, an ending mark of punctuation is a period ( . ), closing parenthesis ( ) ), closing bracket ( ] ), quotation mark( " ), question mark ( ? ), exclamation mark ( ! ), hyphen ( - ; usually used at the end of an open date).
a)
Name authority records. Do not end access points with an ending mark of punctuation except when it is part of the data (e.g., a period in an abbreviation) or is called for by the cataloging instructions (e.g., an element enclosed within parentheses).
EXAMPLE
| 100 1# | $aSmith, John |
| 100 1# | $aSmith, John A. |
| 100 1# | $aSmith, J. A.$q(John A.) |
| 100 1# | $aSmith, John,$d1648?- |
| 100 1# | $aSmith, John,$d1924- |
| 110 2# | $aLibrary of Congress |
| 110 1# | $aNew York (State).$bGovernor (1929-1932 : Roosevelt) |
| 110 2# | $aMoskovskĭ fotoklub "Novator" |
| 130 #0 | $a Collection "Bibliothèque des matières premières."$pSérie "Energie" |
b)
Bibliographic records. Generally, end authorized access points with either a period or other ending mark of punctuation. End a MARC 240 field for a work or expression with an ending mark of punctuation only when such a mark of punctuation is part of the data. If an authorized access point is followed by $5 (Institution to which field applies), do not include punctuation at the end of the field.
for a work or expression with an ending mark of punctuation only when such a mark of punctuation is part of the data. If an authorized access point is followed by $5 (Institution to which field applies), do not include punctuation at the end of the field.When an authorized access point ends in a quotation mark, place any mark of final punctuation that is also part of the data inside the quotation mark. Otherwise, place a period inside the mark of punctuation.
c)
Relationship designators in Bibliographic access points. Relationship designators that follow authorized access points are not capitalized and are always preceded by a comma, unless the authorized access point ends in an open date.
EXAMPLE
| 100 1# | $aBaker, Joseph,$d1779-1800?,$edefendant. |
| 700 1# | $aBrett, Jan,$d1949-$eillustrator. |
| 700 1# | $aHitchcock, Alfred,$d1899-1980,$edirector,$eproducer. |
| 710 2# | $aRaymond Foye Editions,$edonor.$5DLC |
Note that, as the last example above shows, when an authorized access point ends in a relationship designator, it may also be followed by subfield $5 and the field itself does not end with punctuation.
and the field itself does not end with punctuation.When subfield $i for relationship designator is used, it is the first subfield, the first word is capitalized, and the subfield ends with a colon.
EXAMPLE
| 700 1# | $iLibretto based on (work):$aShakespeare, William,$d1564-1616.$tOthello. |
Access Points for Persons in Name Authority and Bibliographic Records
LC practice/PCC practice:
1.
Initials/letters
a)
Name portion of authorized access point
i)
Periods. If the name of a person consists of or contains initials, input a period after an initial if it is certain that the letter is an initial. In case of doubt, do not input a period. If the name consists of separate letters that are presumed not to be initials, omit or include periods according to the predominant usage of the person.
ii)
Spaces. If the name contains two or more forenames represented by initials, consists entirely of initials, or consists entirely of separate letters that are not initials, input a single space between the initials/letters in all cases (regardless of whether they are followed by periods or not).
b)
Other elements in authorized access point
i)
Periods. With initials, include periods unless the author’s predominant usage makes it clear that the author omits them.
ii)
Spaces. Do not leave spaces between single initials/letters.
2.
Abbreviated or missing portions of preferred names. If a part of a preferred name is abbreviated (two or more letters present as opposed to a single letter used as an initial) or if a forename is missing from a name entered under surname, do not leave open space after the abbreviation or missing forename. Instead, insert, as appropriate,
3.
Prefixes (articles and prepositions) in certain names. Once authorized and variant access points for a person have been determined according to RDA 9.2.2.11 and RDA 9.2.3.10, use the following guidelines in encoding the constituent parts of the authorized and variant access points. Apply these guidelines, as appropriate, to authorized and variant access points in a name authority record and to authorized access points (including subjects) in a bibliographic record. In the examples used in the guidelines, only the germane variants have been shown.
and RDA 9.2.3.10, use the following guidelines in encoding the constituent parts of the authorized and variant access points. Apply these guidelines, as appropriate, to authorized and variant access points in a name authority record and to authorized access points (including subjects) in a bibliographic record. In the examples used in the guidelines, only the germane variants have been shown.a)
Prefix immediately follows the first element. If the first element of an authorized or variant access point for a person is followed directly by a prefix without intervening data (e.g., forename(s), name(s) serving the function of a forename as in the case of certain Portuguese names, forename initial(s)), separate the prefix from the first element by a comma and place the prefix, etc., in the MARC record as part of the $c subfield, the subfield for words and phrases associated with the authorized or variant access point. The purpose of this practice is to prevent prefixes from being treated as forenames.
EXAMPLE
b)
Prefixes in names lacking forenames but containing words or phrases associated with an authorized or variant access point. Formulate such authorized or variant access points with the prefixes following any words or phrases associated with the name.
EXAMPLE
| 100 1# | $aLa Fayette,$cMadame de$q(Marie-Madelaine Pioche de La Vergne),$d1634-1693 |
| 400 1# | $aLaFayette,$cMadame de$q(Marie-Madelaine Pioche de La Vergne),$d1634-1693 |
| 400 1# | $aFayette,$cMadame de La$q(Marie-Madelaine Pioche de La Vergne),$d1634-1693 |
| 400 1# | $aDe La Fayette,$cMadame$q(Marie-Madelaine Pioche de La Vergne),$d1634-1693 |
| 400 0# | $aMadame de La Fayette$q(Marie-Madelaine Pioche de La Vergne),$d1634-1693 |
c)
Names in category b. above that include qualifications. Formulate the data constituting the authorized or variant access points according to the pattern: first element of the authorized or variant access point, words or phrases associated with the name ($c subfield), prefix, qualifier, date.
), prefix, qualifier, date.EXAMPLE
4.
Subfield $i (Relationship information) in authority records. When subfield $i for relationship designator is used in a 5XX field, begin the field with subfield $w r. Give subfield $i as the second subfield; the first word in the relationship designator is capitalized, and the subfield ends with a colon.
for relationship designator is used in a 5XX field, begin the field with subfield $w r. Give subfield $i as the second subfield; the first word in the relationship designator is capitalized, and the subfield ends with a colon.5.
Bibliographic description. Note that the spacing and punctuation conventions applied to personal names used in access points may differ from those used in the descriptive portion of a bibliographic record.
Access Points for Corporate Names, Including Meetings, in Name Authority and Bibliographic Records
LC practice/PCC practice:
1.
Quotation marks. If the form of name in the access point includes quotation marks around an element or elements of the name, retain them. Use double quotation marks in the access point instead of other forms of quotation marks.
2.
Initials. If the form of name in the access point consists of or contains initials, regularize the spacing and put one space after an initial that is followed by a word or other element that is not an initial and no space after an initial that is followed by another initial consisting of one letter.
3.
Abbreviations. Precede or follow abbreviations consisting of two or more letters with a space, e.g., "Gauley Bridge (W. Va.)," "Ph. D. Associates."
4.
Place name at end. If the form of name in the access point includes a place name at the end and the place is enclosed within parentheses or is preceded by a comma-space, retain in the access point the punctuation as found.
5.
Subfield $i (Relationship information) in authority records. When subfield $i for relationship designator is used in a 5XX field, begin the field with subfield $w r. Give subfield $i as the second subfield; the first word in the relationship designator is capitalized, and the subfield ends with a colon.
for relationship designator is used in a 5XX field, begin the field with subfield $w r. Give subfield $i as the second subfield; the first word in the relationship designator is capitalized, and the subfield ends with a colon. Bibliographic Linking Entries
LC practice/PCC practice: For linking entries (MARC fields 76X-78X), in general follow the conventions in the sections above with respect to punctuation/spacing. Note, however, unlike name authority access points, the individual components of names in subfields $a (Main entry heading), $s (Uniform title), and $t (Title) are not subfielded.
), in general follow the conventions in the sections above with respect to punctuation/spacing. Note, however, unlike name authority access points, the individual components of names in subfields $a (Main entry heading), $s (Uniform title), and $t (Title) are not subfielded.When subfield $i for relationship designator is used, it is the first subfield, the first word is capitalized, and the subfield ends with a colon.
for relationship designator is used, it is the first subfield, the first word is capitalized, and the subfield ends with a colon.EXAMPLE
| 775 08 | $iReproduction of (manifestation):$aVerdi, Giuseppe, 1813-1901.$tOtello$dMilano : Ricordi, 1913 |
For the guidelines for other subfields in linking entries, see section 1 on Punctuation and section 2 on Spacing under "Editing instructions" in CONSER Editing Guide (CEG) – Section E. MARC 21 Format for Serials as Applied within CONSER – Variable Data Fields – 76X-78X Linking Entries – Linking Entry Fields General Information.
.LC practice: In subfield $w (Record control number) LC does not, for system reasons, supply the blank (space) at the end of a two-digit year LCCN called for by MARC 21.
Punctuation at the End of MARC Fields 245, 246-247, 250, 264, 300, 310/321, 362, 490
LC practice/PCC practice: The ISBD punctuation between areas (period-space-dash-space) is omitted only when the next area is paragraphed.
2.
3.
Field 264. Field 264 usually ends with a period, a closing bracket, or a hyphen. Exceptionally, when no date is present in a serial or integrating resource description, the field does not end in a mark of ending punctuation unless it is part of the name of the publisher (i.e., in the absence of a date, no punctuation is added). Because it is LC practice for monographs to enclose temporary data within angle brackets (see "Temporary/Uncertain Data" below), this field may also end in an angle bracket. When field 264 is used for the Copyright Notice Date, it does not have ending punctuation.
. Field 264 usually ends with a period, a closing bracket, or a hyphen. Exceptionally, when no date is present in a serial or integrating resource description, the field does not end in a mark of ending punctuation unless it is part of the name of the publisher (i.e., in the absence of a date, no punctuation is added). Because it is LC practice for monographs to enclose temporary data within angle brackets (see "Temporary/Uncertain Data" below), this field may also end in an angle bracket. When field 264 is used for the Copyright Notice Date, it does not have ending punctuation.4.
5.
6.
Field 362. For the ending mark of punctuation, apply the convention stated below in the section "Punctuation in Notes," 2. Ending mark of punctuation (5XX).
. For the ending mark of punctuation, apply the convention stated below in the section "Punctuation in Notes," 2. Ending mark of punctuation (5XX).Punctuation in Subfields $3 in MARC Fields 264, 490
LC practice/PCC practice: When a subfield $3 (Materials specified) is used in MARC 264, 490, or 8XX fields to indicate the issues, parts, or iterations applicable to the field, use $3 as the first subfield, followed by the numeric designation, chronological designation, publication date, etc., followed by a colon ( : ). If the designation, publication date, etc., represents incomplete information designated by a hyphen ( - ), insert a single space between the hyphen and the colon for clarity in displays.
, 490, or 8XX fields to indicate the issues, parts, or iterations applicable to the field, use $3 as the first subfield, followed by the numeric designation, chronological designation, publication date, etc., followed by a colon ( : ). If the designation, publication date, etc., represents incomplete information designated by a hyphen ( - ), insert a single space between the hyphen and the colon for clarity in displays.EXAMPLE
$3volumes 1-3:
$3v. 9-,〈10〉:
$3April 2010-〈July 2010〉:
$32010- :
$3-volume 4:
$3-May 2010:
Punctuation in Subfield $x in MARC 8XX Fields
LC practice/PCC practice: To allow for accurate sorting of authorized series access points, predictable validation of ISSN strings, and/or validation of authorized series access points, append subfield $x (International Standard Serial Number) used in MARC 8XX fields to the end of the field as the final subfield. A mark of punctuation, e.g., a period, a right parenthesis, that ends the authorized series access point would precede subfield $x. Do not add any punctuation to subfield $x except for the hyphen in the middle position of the ISSN.
used in MARC 8XX fields to the end of the field as the final subfield. A mark of punctuation, e.g., a period, a right parenthesis, that ends the authorized series access point would precede subfield $x. Do not add any punctuation to subfield $x except for the hyphen in the middle position of the ISSN.Punctuation in Notes
LC practice/PCC practice:
1.
Additional information expected. When additional information is expected, precede or follow a hyphen with one space.
2.
Ending mark of punctuation (5XX). See also the section "g. Notes (5XX) below under "Temporary/Uncertain Data."
For 5XX notes, an ending mark of punctuation is a period ( . ), quotation mark ( " ), question mark ( ? ), exclamation mark ( ! ), hyphen ( - ; used at the end of an open date, etc.), and (LC practice/PCC practice) angle bracket ( > ). End each note with a period or other mark of ending punctuation.
, an ending mark of punctuation is a period ( . ), quotation mark ( " ), question mark ( ? ), exclamation mark ( ! ), hyphen ( - ; used at the end of an open date, etc.), and (LC practice/PCC practice) angle bracket ( > ). End each note with a period or other mark of ending punctuation. If a note ends in a quotation mark, input a period or other mark of ending punctuation inside the quotation mark.
Note that these guidelines relate to punctuation at the end of the data constituting a note itself. Under certain circumstances, a field may actually end with MARC subfields as follows:
a)
$5 (Institution to which field applies), in which case there is no punctuation at the end of the field.
, in which case there is no punctuation at the end of the field.b)
$u (Uniform Resource Identifier), in which case the last character in the field is whatever is the last character of the URI.
, in which case the last character in the field is whatever is the last character of the URI.3.
Square brackets. Do not use square brackets in notes except when they are used in quoted data.
EXAMPLE
| 500 ## | $a"Types of prayer wheels found in south central Tibet, by Mei Lin": pages 310-375. |
Not "... pages [310]-[375]."
| 500 ## | $a"2090245PMA"–-Page 4 of cover. |
Not "... –Page [4] of cover."
| 500 ## | $a"This lavishly illustrated book is a beautifully crafted reproduction of a Russian journal [i.e. photographs collected by Nikolai Efros] from 1914 ..." |
Square brackets used in quote itself.
| 500 ## | $a"ZG24-6722-00." Number is incorrect; number should be SG24-6722-00. |
| 500 ## | $a"April 2008." Year is incorrect; date should be April 2009. |
Temporary/Uncertain Data
LC practice/PCC practice:
1.
General. Indicate that data are temporary or uncertain by enclosing them within angle brackets ( 〈 〉 ). Such data display in all cases. Treat angle brackets as regular characters, applying normal spacing conventions preceding and following them as illustrated in the examples.
When a date is enclosed within angle brackets, do not use spacing to show that it is an open one: "〈1981-〉." When an open date occurs outside angle brackets, use normal spacing preceding or following a hyphen unless preceded or followed by a temporary date enclosed within angle brackets, e.g., "1979-〈1980〉" or "〈1979〉-1980."
When spans of beginning and/or ending dates or numbers include temporary data, give the hyphen within or outside the angle brackets as shown in the following examples:
EXAMPLE
〈1966-〉
〈-no. 47〉
〈May 2001-v. 3, no. 2〉
1998-〈fall 2001〉
〈Bd. 4〉-Bd. 12
When holdings are enclosed within angle brackets, do not use spacing to show that they are temporary.
EXAMPLE
| 505 1# | $a-- volume 2. La foto-restituzione grafico-numerica. part 1. Generalita (2 volumes). part 2. Fotographie oblique 〈volume 1〉 |
2.
Detailed guidelines for recording temporary/uncertain data.
a)
EXAMPLE
| 246 1# | $iAdded title page title 〈release 5, published 1999〉:$aMath education scholarships |
Updating loose-leaf
| 246 1# | $iParallel title in HTML header 〈January 13, 2002〉:$aChildren and young persons |
Updating Web site
| 246 14 | $aState publications monthly checklist$f〈July 1976-〉 |
Serial
| 247 10 | $aMembership directory$f〈update 2, published 1999〉 |
Updating loose-leaf
b)
Publication etc., dates (264). These conventions do not apply to serials or integrating resources (temporary data not recorded in this field).
). These conventions do not apply to serials or integrating resources (temporary data not recorded in this field).i)
Permanent date. If an entire date is judged to be permanent, record it without angle brackets.
EXAMPLE
, 1980-
not
〈1980-〉 or, 1980-〈 〉
v. 1 held; v. 1 published in 1980
ii)
Temporary date. If a portion of a date is temporary, enclose the portion in angle brackets.
EXAMPLE
, 1980-〈1981〉
v. 1-2 held; v. 2 published in 1981
, 〈1981-〉
v. 2 held; v. 1-2 published in 1981
, 〈1979〉-1981.
v. 2-3 held of a 3-volume set
, 〈1978-1980〉
v. 2-3 held of a 5-volume set
iii)
Non-Christian era date. When the expression of date includes one from the non-Christian era and that date is temporary (as when cataloging a multipart monograph from other than volume 1), consider the whole expression of date as temporary and give the whole in angle brackets, e.g., 〈Shōwa 57- [1982]-〉
c)
Incomplete multipart monographs when the total number of units is not known. During the time a multipart monograph is incomplete, record only the general term designating the type of unit (RDA 3.4.1.10) in MARC field 300 (e.g., "volumes") of the bibliographic record. At the time the multipart monograph is complete, update field 300 to record the number of units preceding the term designating the type of unit (e.g., "6 volumes").
) in MARC field 300 (e.g., "volumes") of the bibliographic record. At the time the multipart monograph is complete, update field 300 to record the number of units preceding the term designating the type of unit (e.g., "6 volumes").d)
EXAMPLE
Updating loose-leaf
Updating Web site
Serial
e)
Series statement: open entry multipart monographs in series (MARC 490). When a multipart monograph itself is in a series and the multipart monograph is classified as a collection and not analyzed, record the numbering of the series in the collected set record according to the following guidelines until the multipart monograph is complete.
). When a multipart monograph itself is in a series and the multipart monograph is classified as a collection and not analyzed, record the numbering of the series in the collected set record according to the following guidelines until the multipart monograph is complete.i)
Record the series numbering for the first or last volume as permanent data, i.e., not within angle brackets.
ii)
Record all the series numbering as permanent data when the first or last volume is in hand with other consecutive volumes of the multipart monograph and the series numbering is scattered.
iii)
In all other situations, record the series numbering as temporary data, i.e., within angle brackets.
iv)
Use a hyphen to separate consecutive numbers and a comma to separate scattered numbers. When the multipart monograph is complete, show all numbering as permanent data.
EXAMPLE
Volumes other than first or last volume of multipart monograph being cataloged -- more than one volume in hand and series numbering consecutive
v. 2-4 of multipart monograph are no. 9-11 of series
EXAMPLE
Volumes other than first or last volume of multipart monograph being cataloged -- more than one volume in hand and series numbering scattered
v. 2, 4 of multipart monograph title are no. 31, 42 of series
f)
Series statement: only some issues or parts of a serial or multipart monograph or iterations of an integrating resource in a series (490). If some issues or parts of a serial or multipart monograph or iterations of an integrating resource are in a series and others are not, precede the series title with an indication of the particular issues, parts, or iterations to which the series applies.
). If some issues or parts of a serial or multipart monograph or iterations of an integrating resource are in a series and others are not, precede the series title with an indication of the particular issues, parts, or iterations to which the series applies.g)
Notes (5XX)
)i)
Dates. Record dates as provided in 1. General above under "Temporary/Uncertain Data."
ii)
Volume numbers. Use angle brackets to record volume numbers when the data are still temporary.
Do not use "empty" angle brackets; instead, insert one space after or before a hyphen if additional information is expected.
iii)
Contents notes. If volume one is not held, begin the field with two adjacent hyphens followed by a space and the number of the first volume actually held.
EXAMPLE
holdings in LC
| v. 2, pt. 1 (in 2 v.); v. 2, pt. 2 |
bibliographic record
| 505 1# | $a—volume 2. La foto-restituzione grafico- numerica. part 1. Generalita (2 volumes). part 2. Fotographie oblique 〈volume 1〉 |
If the set is incomplete but volume one is held, put the space-dash-space before each title (other than for volume one) that is being recorded and leave four spaces for the missing volume(s).
When the number of bibliographic units differs from the number of physical units and the parts of each bibliographic unit are indicated in the contents note, record the numbers/designations of the parts that are incomplete in angle brackets. In general, include in the angle brackets any designation of the part, especially if this varies from the designation of the larger unit of which it is a part.
EXAMPLE
holdings in LC
| pt. 1 (in 2 v.); pt. 2, v. 1 |
bibliographic record
| 505 1# | $apt. 1. Historical study. v. 1, Text. v. 2, Notes. -- pt. 2. Annexes: alphabetic repertory of noble families 〈v. 1〉 |
h)
Bibliographic linking entry notes (76X-78X). Record dates and/or numbers as provided in 1. General under "Temporary/Uncertain Data" above. When subfield $i for relationship designator is used, it is the first subfield, the first word is capitalized, and the subfield ends with a colon.
). Record dates and/or numbers as provided in 1. General under "Temporary/Uncertain Data" above. When subfield $i for relationship designator is used, it is the first subfield, the first word is capitalized, and the subfield ends with a colon.[2016-07]