R | D | A TOOLKIT
  • Entities
    • RDA Entity
    • Work
    • Expression
    • Manifestation
    • Item
    • Agent
    • Person
    • Collective Agent
    • Corporate Body
    • Family
    • Nomen
    • Place
    • Timespan
  • Guidance
    • Introduction to RDA
      • Objectives and principles governing RDA
      • Standards related to RDA
      • Data elements
    • Aggregates
    • Application profiles
    • Content and carrier
      • RDA resource categorization
      • RDA carrier and content categories
      • RDA resource category extension
      • Extension plans
    • Data provenance
    • Diachronic works
    • Entity boundaries
    • Fictitious and non-human appellations
    • Manifestation statements
    • Nomens and appellations
    • RDA implementation scenarios
    • Recording methods
    • Representative expressions
    • Resource description
      • Coherent description of an information resource
      • Minimum description of a resource entity
      • Effective description
      • Describing a work
      • Describing an expression
      • Describing a manifestation
      • Describing an item
    • Terminology
    • Transcription guidelines
      • Guidelines on basic transcription
      • Guidelines on normalized transcription
    • User tasks
    • Well-formed RDA
  • Policies
    • BLPS
      • BLPS Entities
      • BLPS Guidance
      • BL PS Community Resources
    • LAC PS
      • LAC PS Entities
      • LAC PS Guidance
    • LC-PCC PS
      • LC-PCC PS Entities
      • LC-PCC PS Guidance
      • LC-PCC PS Community Resources
    • MLA BP
      • MLA BP Entities
      • MLA BP Guidance
      • MLA BP Community Resources
    • NLNZ PS
      • NLNZ PS for Entities
      • NLNZ Guidance
      • NLNZ PS Community Resources
  • Resources
    • Glossary
    • VES Vocabularies
    • Community Resources
      • Legacy RDA Community resources
    • Revision History
  • Original Toolkit
  • Help
    • Accessibility of RDA Toolkit
    • Getting Started
    • Navigating RDA Toolkit
    • Searching RDA Toolkit
    • Personalizing RDA Toolkit
    • Using the Administration Services
    • RDA Toolkit Support
  • English
    • English
    • Catalan
    • Finnish
    • French
    • Norwegian
    • English
    • Catalan
    • Finnish
    • French
    • Norwegian
    • Normal
    • Large
  • Submit Feedback
  • Entities
    • RDA Entity
    • Work
    • Expression
    • Manifestation
    • Item
    • Agent
    • Person
    • Collective Agent
    • Corporate Body
    • Family
    • Nomen
    • Place
    • Timespan
  • Guidance
    • Introduction to RDA
      • Objectives and principles governing RDA
      • Standards related to RDA
      • Data elements
    • Aggregates
    • Application profiles
    • Content and carrier
      • RDA resource categorization
      • RDA carrier and content categories
      • RDA resource category extension
      • Extension plans
    • Data provenance
    • Diachronic works
    • Entity boundaries
    • Fictitious and non-human appellations
    • Manifestation statements
    • Nomens and appellations
    • RDA implementation scenarios
    • Recording methods
    • Representative expressions
    • Resource description
      • Coherent description of an information resource
      • Minimum description of a resource entity
      • Effective description
      • Describing a work
      • Describing an expression
      • Describing a manifestation
      • Describing an item
    • Terminology
    • Transcription guidelines
      • Guidelines on basic transcription
      • Guidelines on normalized transcription
    • User tasks
    • Well-formed RDA
  • Policies
    • BLPS
      • BLPS Entities
      • BLPS Guidance
      • BL PS Community Resources
    • LAC PS
      • LAC PS Entities
      • LAC PS Guidance
    • LC-PCC PS
      • LC-PCC PS Entities
      • LC-PCC PS Guidance
      • LC-PCC PS Community Resources
    • MLA BP
      • MLA BP Entities
      • MLA BP Guidance
      • MLA BP Community Resources
    • NLNZ PS
      • NLNZ PS for Entities
      • NLNZ Guidance
      • NLNZ PS Community Resources
  • Resources
    • Glossary
    • VES Vocabularies
    • Community Resources
      • Legacy RDA Community resources
    • Revision History
    • Original Toolkit;
    • AACR2;

Policies

Music Library Association Best Practices for identifier for manifestation

Prerecording

Prerecording

Routinely record the element. If feasible, record all standard identifiers present on the resource, including but not limited to ISBN, ISMN, EAN, and UPC. Also routinely record identifiers issued by publishers, including audio recording issue numbers and video recording numbers. Optionally, record identifiers issued by distributors.

For ISMNs: If feasible, record an additional instance of the element containing the equivalent 10- or 13-character version of the ISMN. To convert one ISMN format to another, replace "M" with "9790" or vice versa. The final check digit is the same in both ISMN formats.

For modern commercial recordings, record matrix numbers if they are the only numbers shown on the resource, or if deemed important for identification or access. For rare or historical recordings, record matrix numbers even if other publisher numbers are present.

If the resource is a reprint, reissue, reproduction, issue in an alternate format, etc., and provides an identifier for the original manifestation or an equivalent in an alternate format, record the identifier as a Manifestation: related manifestation of manifestation; do this in addition to formulating a structured or unstructured description of the original manifestation.

For additional guidance for notated music, see Manifestation: plate number for notated music and Manifestation: publisher number for notated music.

Option

Generally do not record manifestation statements. Refer to the Best Practices for Guidance: Manifestation statements for details.

Recording

Recording

In MARC: Record as an identifier using field 020 (ISBN), 024 (UPC, first indicator 1; ISMN, first indicator 2; EAN, first indicator 3), or 028 (audio recording issue number, first indicator 0; matrix number, first indicator 1; videorecording number, first indicator 4; distributor number, first indicator 6).

Routinely encode a 13-digit, EAN-formatted identifier beginning with 979-0 as an ISMN using 024 first indicator 2. Optionally, also encode such an identifier as an EAN using 024 first indicator 3.

See examples in MARC format: identifier for manifestation . For related examples see also: plate number for notated music ; publisher number for notated music

Option

Apply the option for standard identifiers.

In MARC: follow MARC input standards for numbers recorded in 020 or 024: that is, record the identifier without internal spaces or punctuation and without a preceding label.

Option

Apply the option for issue, matrix, videorecording, and distributor numbers.

Option

Apply the option for issue, matrix, plate, publisher, videorecording, and distributor numbers. Record the name of the publisher or distributor (or a trade name, brand name, or label name used by the publishing company) in the same form as transcribed in Manifestation: name of publisher or Manifestation: name of distributor.

In MARC: Record in field 028 $b.

Option

Cataloger's judgment.

In MARC: Generally prefer field 020, 024, or 028 subfield $q for simple clarifications and qualifiers. If more detailed explanation is needed, optionally provide details or clarification as an unstructured description in field 500.

Two or more identifiers for a manifestation

Condition

Also consider this condition to apply when a publisher's or distributor's number appears in variant forms on an audio or video recording, its container, accompanying material, etc. In such cases record at least the form on the recording itself (e.g., the labels of a disc). Record other forms as well if deemed useful for identification or access.

Condition Option

When recording identifiers for multiple units, cite the unit(s) to which the identifier applies. When recording identifiers that appear in variant forms in various locations, cite the location in which the identifier is found. For matrix numbers, always record the qualifier matrix even if only one identifier is present.

In MARC: Record in field 020, 024, or 028 subfield $q.

LC/PCC practice: Apply the option.

LC practice: When recording multiple ISBNs, record first the number that is applicable to the manifestation being described. Record other numbers in the order presented, with appropriate qualification to distinguish.

Condition Option

LC/PCC practice: Apply the option.

Condition Option

LC/PCC practice: Apply the option when adding a part to a multipart monograph description. Optionally, apply the option for any parts of a multipart monograph or serial.

Condition Option

Apply the option. Record identifiers for all units if feasible, including cases where scores and parts bear separate identifiers. Follow each identifier by a qualifier indicating the unit(s) to which it refers.

In MARC: Record qualifiers in field 020, 024, or 028 subfield $q.

Condition Option

LC/PCC practice: Do not apply the option. Give each identifier instead of a span.

Condition Option

LC/PCC practice: Do not apply the option. Give each identifier instead of a span.

Condition Option

LC/PCC practice: Do not apply the option. Give each identifier instead of a span.

Incorrect identifiers

Condition

Also consider this condition to apply to identifiers known to refer to a Manifestation: related manifestation of manifestation (for example, an identifier on a print resource that has been digitized and issued as an online resource; an identifier from an audio recording's packaging that has been reproduced in facsimile as the packaging for a reissue of that recording).

Condition Option

LC/PCC practice: Apply the option.

Condition Option

In MARC: For standard identifiers recorded in fields 020 or 024, record the identifier in subfield $z (invalid or canceled number) rather than $a. For any identifier in an 02x field, supply a qualifying term in subfield $q.

LC/PCC practice: Apply the option.

Recording an unstructured description

Recording a structured description

Recording an identifier

Option

Cataloger's judgment.

In MARC: Amend standard identifier formatting if necessary to conform to MARC input conventions.

Option

Cataloger's judgment.

Data provenance

Option

LC/PCC practice: Apply this option if 1) the metadata has been taken from a source other than the manifestation being described and there is a requirement to record that source OR 2) if directed to do so by other LC/PCC documentation.

Recording an IRI

Document Date: 2025/03/25
Document: https://access.rdatoolkit.org/en-US_ala-8f740d57-2d43-325b-b2fa-a0746bee7717

  • Previous: Music Library Association Best Practices for groove width
  • Next: Music Library Association Best Practices for illustrative content

© 2025

ISSN 2167-3241

Administration
About RDA and RDA Toolkit
FAQ
Support/Contact

Create Link

Link Copied to Clipboard

View Citation

Citation Copied to Clipboard

R | D | A TOOLKIT

Log Out