The Library of Congress >> Especially for Librarians and Archivists >> Standards
HOME >> MARC Development >> Proposals List
DATE: May 17, 2010
REVISED:
NAME: Encoding the International Standard Name Identifier (ISNI) in the MARC 21 Bibliographic and Authority Formats
SOURCE: British Library
SUMMARY: This paper proposes ways to encode the International Standard Name Identifier (ISNI) in the MARC 21 Bibliographic and Authority formats.
KEYWORDS: Field 024 (AD); control subfield $0 (BD, AD); Other standard identifier (AD)
STATUS/COMMENTS:
5/17/10 – Made available to the MARC community for discussion.
6/26/10 – Results of MARC Advisory Committee discussion: Approved. Subfield $0 is not used in 1XX fields of the MARC Authority Format (and is not defined there).
08/26/10 - Results of LC/LAC/BL review - Agreed with the MARBI decision.
“The International Standard Name Identifier (ISNI) is a draft ISO Standard (ISO 27729) whose scope is the identification of Public Identities of parties: that is, the identities used publicly by parties involved throughout the media content industries in the creation, production, management, and content distribution chains. The ISNI provides a tool for disambiguating Public Identities that might otherwise be confused”. (http://www.isni.org)
The ISNI Draft International Standard (DIS) stage obtained 100% approval in March 2010. The Memorandum of Understanding to form a consortium of founding members who agree to establish the ISNI International Agency is expected to be signed in June. The British Library and the Bibliothèque nationale de France will be the library-domain representatives on behalf of CENL (Conference of European National Libraries) on the Board of the ISNI International Agency. The legal incorporation of the International ISNI Agency as the official Registration Authority for the ISNI and the publication of the standard are expected to be completed by April 2011.
By relying on a unique identifier, the ISNI will provide a mechanism enabling automated processes between libraries, other data providers and different rights management societies. The ISNI will also enable more efficient management of rights monitoring and payments in the future. Whilst the natural home of the ISNI is in the MARC 21 Authority format, it also needs to be recorded in the MARC 21 bibliographic record as it is anticipated that one of the routes through which libraries will get the ISNI is via publishers’ metadata, i.e. bibliographic metadata.
At the MARBI meeting of January 2010 the MARC Advisory Committee discussed options for recording the ISNI in the MARC formats as outlined in Discussion paper 2010-DP03. It was agreed that subfield $0 could be redefined for such a purpose, provided it was recorded in a manner similar to the one currently used to record system control numbers in subfield $0. There also was some discussion about the position of that subfield, which would require further examination.
The ISNIs used in the examples below are fictitious and for illustrative purposes only.
“An ISNI can be allocated to any entity that is or was either a natural person, a legal person, a fictional character, or a group of such entities, whether or not incorporated. Further, ISNIs are assigned to the Public Identities of Parties that participate in the creation, production, management or distribution of cultural goods in the digital environment” (http://www.isni.org/).
In MARC terms the ISNI therefore identifies a person, family, fictional character, corporate body or meeting. These entities can therefore occur in the following fields in the Bibliographic format:
Main entry fields
100, 110, 111 – Main entry – Personal, Corporate, and Meeting names
Subject Access fields
600, 610, 611 – Subject added entry – Personal, Corporate, and Meeting names
650 – Subject added entry – Topical term (for fictional characters)
Added entry fields
700, 710, 711 – Added entry – Personal, Corporate, and Meeting names
Series added entry fields
800, 810, 811 – Series added entry – Personal, Corporate, and Meeting names
These fields may also identify other entities in FRBR terms: works, expressions, concepts, objects which are not entities that come under the scope of the ISNI. Subfield $0 was defined by Proposal 2007-06 to enable the number of the related authority record to be recorded in headings fields. No clear guidance was provided regarding the related authority record. The assumption in this paper is that the “related authority record” represents the entity represented by the complete heading, not entities which constitute components of the heading. For example: in a name-title heading, subfield $0 contains the identifier for the name-title (work or expression) not the identifier for the person, corporate body or meeting.
The implication therefore is that the ISNI will only be used in the following MARC 21 bibliographic fields:
Main entry fields
100, 110, 111 – Main entry – Personal, Corporate, and Meeting names
Subject Access fields – excluding subdivided headings
600, 610, 611 – Subject added entry – Personal, Corporate, and Meeting names
650 – Subject added entry – Topical term (for fictional characters)
Added entry fields - excluding name-title entries
700, 710, 711 – Added entry – Personal, Corporate, and Meeting names
This paper proposes to extend subfield $0 to record the ISNI. Subfield $0 is currently defined as follows in Appendix A – Control subfields:
$0 - Authority record control number
System control number of the related authority record preceded by the MARC code, enclosed in parentheses, for the agency to which the control number applies. See MARC Code List for Organizations for a listing of sources used in MARC 21 records.
100 1# $aBach, Johann Sebastian.$4aut$0(DE-101c)310008891
Whilst the ISNI is not an authority record control number, it fulfills a similar purpose. The ISNI uniquely identifies the entity encoded in the 1XX of the authority record, itself uniquely identified by the authority record control number.
MARBI suggested that the ISNI (and other name identifiers) should be encoded in a way similar to the one currently used for authority record control numbers in subfield $0, i.e. preceded by a MARC organisation code in parentheses. This paper suggests a similar approach; it proposes that code “isni” be defined in the list of Standard Identifier Source Codes, is enclosed in parentheses and precedes the standard number recorded in subfield $0.
This paper therefore suggests extending subfield $0 as follows:
$0 – Authority record control number or standard number
Subfield $0 contains the system control number of the related authority record, the International Standard Name Identifier (ISNI) or, other name identifiers. The control number or identifier is preceded by the appropriate MARC Organization code (for a related authority record) or the Standard Identifier source code (for a standard identifier scheme), enclosed in parentheses. See MARC Code List for Organizations for a listing of organization codes used in this subfield and Standard Identifier Source Codes for code systems for standard identifiers. Subfield $0 is repeatable for different control numbers or name identifiers.
Examples of the use of the ISNI in subfield $0 in bibliographic records are as follows:
Example no. 1
020 ## $a0140433260 (pbk.) :$c£4.99
100 1# $aTrollope, Anthony,$d1815-1882.$0(isni)1234567899999799 [ISNI for Anthony Trollope]
245 10 $aDoctor Thorne /$cAnthony Trollope ; with an introduction and notes by Ruth Rendell.
260 ## $aLondon :$bPenguin,$c1991.
700 1# $aRendell, Ruth,$d1930-$0(isni)8462832856536435 [ISNI for Ruth Rendell]
Example no. 2
100 1# $aStorr, Anthony.$0(isni)6666123478953321 [ISNI for Anthony Storr]
245 10 $aFreud :$ba very short introduction /$cAnthony Storr.
260 ## $aOxford :$bOxford University Press,$c2001.
600 10 $aFreud, Sigmund,$d1856-1939.$0(isni)3001456712349876 [ISNI for Sigmund Freud]
650 #0 $aPsychoanalysis.
At the MARBI meeting of January 2010, there was some discussion about the position and repeatability of subfield $0, in particular in relation to hierarchical name headings, subdivided subjects and name-title headings. As discussed above, the assumption on which this paper is based is that the identifier or authority record control number represents the entity represented by the whole heading, not entities which constitute components of the heading. The $0 is repeatable for different identifiers for the entity, but the position of the $0 has no semantic value.
Example no. 3
110 2# $aBritish Broadcasting Corporation.$0(isni)0023000010011234 [ISNI for the BBC]
245 10 $aBuilding public value :$brenewing the BBC for a digital world.
260 ## $aGlasgow :$bBBC.,$c[2004?]
610 20 $aBritish Broadcasting Corporation.$0(isni)0023000010011234 [ISNI for the BBC]
650 #0 $aDigital television.
Example no. 4
222 #0 $aBBC Monitoring global newsline. South Asia political$b(Online)
245 00 $aBBC monitoring global newsline.$pSouth Asia political$h[electronic resource].
260 ## $aReading :$bBBC Monitoring,$c[2000-]
710 2# $aBritish Broadcasting Corporation.$bMonitoring Service.$0(isni)0023000010015678 [ISNI for the BBC Monitoring Service]
Example no. 5
020 ## $a0140433260 (pbk.)$c£4.99
100 1# $aTrollope, Anthony,$d1815-1882.$0(isni)1234567899999799$0(DLC)n78089077
$0(abc)X12345678
245 10 $aDoctor Thorne /$cAnthony Trollope ; with an introduction and notes by Ruth Rendell.
260 ## $aLondon :$bPenguin,$c1991.
700 1# $aRendell, Ruth,$d1930-$0(isni)8462832856536435$0(DLC)n79056533
$0(abc)Y88881234
[The example above includes an ISNI, an LC authority record control number and an identifier from a (fictitious) ABC name identifier standard.]
The ISNI can be assigned to entities which are recorded in the MARC 21 Authority format in the following fields:
Heading fields
100, 110, 111 – Heading – Personal, Corporate, and Meeting names
150 (for fictional characters) – Heading – Topical term
151 (for jurisdictions).- Heading – Geographic term
See also from tracing fields
500, 510, 511 – See also from tracing – Personal, Corporate, and Meeting names
550 – See also from tracing – Topical term
551 – See also from tracing – Geographic term
Heading linking entry fields
700, 710, 711 – Established heading linking entry – Personal, Corporate, and Meeting names
750 – Established heading linking entry – Topical term
751 – Established heading linking entry – Geographic term
Field 024: Other standard identifier is also defined in the MARC 21 Authority format. It was specifically defined to record standard identifiers relevant to the entity described in the authority record (Proposal 2003-04). It can therefore be used to identify the entity recorded in fields 100, 110, 111, 150 and 151. As stated previously, code “isni” needs to be added to the list of Standard Identifier Source codes.
Example no. 6:
024 7# $a8462832856536435$2isni [ISNI for Ruth Rendell]
100 1# $aRendell, Ruth,$d1930-
670 ## $aHer From Doon with death, 1964.
However, field 024 cannot be used to record the ISNI in the 5XXs and 7XXs listed above as well as the 1XXs. It would be difficult to associate the correct identifier to the appropriate entity.
This paper therefore proposes re-defining subfield $0 in the Authority format in a similar way to the one outlined above for the Bibliographic format.
Examples of use of subfield $0 in authority records are as follows:
Example no. 7
024 7# $a8462832856536435$2isni [ISNI for Ruth Rendell]
100 1# $aRendell, Ruth,$d1930-
500 1# $aVine, Barbara,$d1930$0(isni)1422458635730476 [ISNI for Barbara Vine]
670 ## $aHer From Doon with death, 1964.
670 ## $aHer A dark-adapted eye, 1986:$bCIP t.p. (Barbara Vine)
670 ## $aInfo. from pub., 1/28/86$b(Barbara Vine is pseud. used by Ruth Rendell)
Example no. 8
024 7# $a6678232200017533$2isni
100 0# $aAugustine,$cSaint, Bishop of Hippo [LAC English heading]
700 05 $wa$aAugustin,$cSaint, évêque d’Hippone.$0(Ca00NL)0053A1978F#
$0(isni)6678232200017533 [Corresponding LAC French heading]
Extend subfield $0 – Authority record control number in the MARC 21 Bibliographic and Authority formats as follows:
$0 – Authority record control number or standard number
Subfield $0 contains the system control number of the related authority record, the International Standard Name Identifier (ISNI) or, other name identifiers. The control number or identifier is preceded by the appropriate MARC Organization code (for a related authority record) or the Standard Identifier source code (for a standard identifier scheme), enclosed in parentheses. See MARC Code List for Organizations for a listing of organization codes used in this subfield and Standard Identifier Source Codes for code systems for standard identifiers. Subfield $0 is repeatable for different control numbers or name identifiers.
HOME >> MARC Development >> Proposals List
| The Library of Congress >> Especially for Librarians and Archivists >> Standards ( 02/08/2011 ) |
Legal | External Link Disclaimer | Contact Us |
