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

LC-PCC policy statements for authorized access point for corporate body

Prerecording

Prerecording

LC/PCC Core for authority records in the LC/NAF.

LC/PCC practice: Consult the PCC Post RDA Test Guidelines for up-to-date instructions on the issues related to RDA and AACR2 authority records and their use in bibliographic records.

LC/PCC practice: See the Metadata Guidance documentation: Corporate Body elements.

LC/PCC practice: See the Metadata Guidance documentation: Corporate Body: SES: Access point for Corporate Body.

Recording

Recording an unstructured description

Recording a structured description

Option

LC/PCC practice: If an authorized form has been established in the LC/NACO Name Authority File, apply the option by recording that authorized form.

Option

LC/PCC practice: If no authorized form has been established in the LC/NACO Authority file, apply the option by (1) establishing a value of Corporate Body: access point for corporate body as the authorized form in the LC/NACO Name Authority file, and/or (2) Recording a value of Corporate Body: access point for corporate body on a bibliographic record.

Option

LC/PCC practice: Apply the option.

LC/PCC practice: For a prosecuting attorney of a jurisdiction, apply the option according to the following guidelines:

  1. Use the authorized access point for the appropriate jurisdiction as the first element in the access point.
  2. Add the conventional name for the office, e.g., "Attorney," "District Attorney."
  3. Add the name of the particular area served, in parentheses, in a conventionalized form.
Note: In the states of the United States, prosecuting attorneys are agents of the states as a whole; they are not agents of a particular county as publications might suggest.

Base authorized access point for corporate body

Option

LC/PCC practice: Apply the option.

Change of name

Change of name

LC practice/PCC practice: See Corporate Body: preferred name of corporate body for guidelines on identifying minor changes of name.

Condition Option

LC/PCC practice: Apply the option.

Condition Option

LC/PCC practice: Apply the option.

Condition Option

LC/PCC practice: Do not apply the option. See instead Corporate body: related corporate body of corporate body for guidelines on recording relationships between earlier/later corporate bodies, including corporate bodies that have resumed an earlier name.

Terms indicating incorporation or state ownership

Option

LC/PCC practice: Apply the option.

Format of base authorized access point for corporate body

Additional elements and designations in authorized access point for corporate body

Additional elements and designations in authorized access point for corporate body

LC/PCC practice: See the Metadata Guidance documentation: Corporate Body: authorized access point for corporate body: additional elements and designations.

Option

LC/PCC practice: Apply the option.

LC/PCC practice: When two or more bodies have the same name, make an addition to each name. Determine that a conflict exists when the preferred name or authorized access point for one body is the same as the preferred name or authorized access point for another body. "Conflict" is restricted to names already created or being created in the catalog. If a variant name conflicts with a form used in the authorized access point for another body, apply the provisions for resolving conflicts only to the variant name. Ignore the conflict that is only between names used as variants.

LC/PCC practice: If the name chosen for the authorized access point for a corporate body is an initialism or acronym written in all capital letters (with or without periods between them), add a Corporate Body: category of corporate body qualifier to the name. Alternatively, a spelled out form of the name may be used as an Other designation addition if such an addition better identifies the corporate body.

LC/PCC practice: See the Metadata Guidance documentation: Corporate Body: authorized access point for corporate body: additional elements and designations: initialisms and acronyms.

LC/PCC practice: When establishing an authorized access point for a ship, add an appropriate designation in English if the name alone does not convey the idea of a corporate body. For powered vessels, the appropriate designation is "(Ship)." If there is more than one powered vessel with the same name, add a more specific term to each to resolve the conflict.

For sailing vessels, the appropriate designation is the type of rigging. Because the term "ship" as applied to sailing vessels refers to a particular rigging, that term is not always appropriate. If there is more than one sailing vessel with the same name and the same rigging, add another addition (e.g., dates of existence, date launched, date ceased, port) to resolve the conflict. If the particular rigging is unknown, use "(Sailing vessel)."

LC/PCC practice: See the Metadata Guidance documentation: Corporate Body: authorized access point for corporate body: additional elements and designations: ships.

LC/PCC practice: When a place has been used as an additional element in an authorized access point for corporate body and the geographic name changes or the corporate body moves from one locale to another, revise an existing authorized access point to reflect the changed situation.

LC/PCC practice: See the Metadata Guidance documentation: Corporate Body: authorized access point for corporate body: additional elements and designations: place.

LC/PCC practice: For ongoing conferences, separate authority records may be created for the collective conference (typically made when cataloging a serial), an individual instance of an ongoing conference (typically made when cataloging a monograph), or both. These records may coexist in the LC/NACO authority file. A record for the collective conference should always be made to connect the earlier and later names of the collective conference.

LC/PCC practice: When creating an authority record for an individual instance of an ongoing conference, the additions for number, date, and location of a conference, etc. are given in the authorized access point. Variant access points may be given for variant names of the individual conference, such as acronyms for a spelled-out form. Generally do not connect an individual instance of an ongoing conference to the earlier or later instance of the conference as a related corporate body of corporate body, or to an authority record for the collective conference.

LC/PCC practice: See the Metadata Guidance documentation: Corporate Body: authorized access point for corporate body: additional elements and designations: individual instance of an ongoing conference.

General guidelines for constructing authorized access points for subordinate or related corporate bodies

Option

LC/PCC practice: Apply the option.

Condition Option

LC/PCC practice: Apply the option. If the preferred name of the subordinate or related corporate body includes the name of the body to which it is subordinate or related, construct the authorized access point by recording the authorized access point for the body to which it is subordinate or related, followed by a period and space, followed by the preferred name of the subordinate or related body, omitting from the last the name of body to which it is subordinate or related unless required for clarity.

Condition Option

LC/PCC practice: Apply the option. If the preferred name of the subordinate or related corporate body includes the name of the body to which it is subordinate or related, construct the authorized access point by recording the authorized access point for the body to which it is subordinate or related, followed by a period and space, followed by the preferred name of the subordinate or related body, retaining in the last the name of body to which it is subordinate or related if required for clarity.

Types of names that indicate a subordinate corporate body

Body whose name implies it is part of another

Condition Option

LC/PCC practice: Apply the option.

Body whose name implies administrative subordination

Body whose name implies administrative subordination

LC/PCC practice: See the Metadata Guidance documentation: Corporate Body: authorized access point for corporate body: additional elements and designations: body whose name implies administrative subordination.

Condition Option

LC/PCC practice: Apply the option.

Condition Option

LC/PCC practice: Apply the option.

Body whose name is general in nature or simply indicates a geographic, chronological, or alphanumerical designation of subdivision of a parent body

Condition Option

LC/PCC practice: Apply the option.

Body whose name does not convey the idea of a corporate body and does not contain the name of the higher body

Condition Option

LC/PCC practice: Apply the option.

University faculty, etc., with name that simply indicates a particular field of study

Condition Option

LC/PCC practice: Apply the option.

Non-governmental body with name that includes the entire name of the higher or related body

Non-governmental body with name that includes the entire name of the higher or related body

LC/PCC practice: See the Metadata Guidance documentation: Corporate Body: authorized access point of corporate body: Non-governmental body with name that includes the entire name of the higher or related body.

Condition Option

LC/PCC practice: Apply the option, subject to additional conditions for application and exclusions from application. See the Metadata Guidance documents for more detail.

Condition Option

LC/PCC practice: If a named meeting contains the entire name of a higher or related corporate body, treat the meeting subordinately to the authorized access point for the body only if the name contains, in addition to the name of the body, no more than a generic term plus one or more of the following elements: the venue of the meeting; number, date, or other sequencing element. See the Metadata Guidance documents for more detail.

Types of subordinate bodies

Ministry or similar major executive agency

Government officials

Heads of state, heads of government, etc.

Heads of state, heads of government, etc.

LC/PCC practice: See the Metadata Guidance documentation: Corporate Body: authorized access point for corporate body: additional elements and designations: heads of state, heads of government, etc.

Condition Option

LC/PCC practice: Apply the option.

Data provenance

Option

LC/PCC practice: Apply the option if specifically required by policy or the metadata system, as stated in the Metadata Guidance documentation.

Option

LC/PCC practice: Do not apply the option.

Recording an identifier

Recording an IRI

View in Context Example

Document Date: 2025/05/23
Document: https://access.rdatoolkit.org/en-US_ala-da087fc2-93b0-3c91-b0c5-c334a9ede87e

  • Previous: LC-PCC policy statements for author corporate body of
  • Next: LC-PCC policy statements for binder corporate body of

© 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