📜
Archive cataloguing
  • Introduction
  • General Guidance
    • Basic cataloguing principles
    • Preparing a collection for cataloguing
      • Audio-visual cataloguing
      • Born-digital cataloguing
  • Quick Reference
    • Mandatory cataloguing fields
      • Mandatory born-digital fields
      • Mandatory visual and material culture fields
    • Additional cataloguing fields
    • Releasing the catalogue: Checklist
  • Metadata fields
    • Introduction
    • IDENTITY
    • CONTEXT
    • CONTENT
    • ACCESS
    • ALLIED MATERIALS
    • Digitisation sensitivity review fields
    • Superseded fields
  • Authorities
    • Name Authority Files
      • Personal name authority files
      • Corporate name authority files
    • Subject Authority Files
  • Appendices
    • Appendix 1: Acceptable date formats
    • Appendix 2: Acceptable extent formats
    • Appendix 3: Terminology resources
  • CATALOGUING PROJECTS
    • Adamson Collection review 2023-2025
      • Background and existing cataloguing
      • Approach
      • Access and Sensitivity Decision Making
      • Cataloguing Workflow
      • Picklist Data
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Authorities

Name Authority Files

PreviousSuperseded fieldsNextPersonal name authority files

Last updated 1 year ago

Was this helpful?

Introduction

Wellcome’s use of name authority files serves three functions:

  • to ensure that all occurrences of a significant individual or body in our holdings are linked and described using a consistent, standard form of a name.

  • to provide a central location for background information on that individual or body, removing the need for cataloguers to repeat research already carried out.

  • to hold that information in a standardised form so that it can be exported and form a resource for other repositories holding material by that individual or body.

The basis for the authority files generated at Wellcome is the .

ISAAR(CPF) standard