> For the complete documentation index, see [llms.txt](https://docs.wellcomecollection.org/collections-information/lQ0fMyP8xr8hWWJiQkfl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wellcomecollection.org/collections-information/lQ0fMyP8xr8hWWJiQkfl/archive-cataloguing/authorities/name-authority-files/corporate-name-authority-files.md).

# Corporate name authority files

The authority record has two basic areas: The **Identity Area**, which generates the authorised form of the name, and the **Description Area**, which gives background information. It is not necessary to fill in every field in the description area.

Use paragraph tags \[\<p>\</p>] to break up large amounts of text.

### Code

Comprises the Wellcome NRA code (GB 0120) and a machine-generated unique identifier. The Wellcome code is used to identify the source of the data should it be exported.

{% hint style="info" %}
Autogenerated field. No input is required from the cataloguer.
{% endhint %}

***

### AuthorizedFormOfName

An autogenerated field based on the data in the identity area's other fields.

***

### CorporateName

To record the legally recognised or registered title

**Rules**

* Where the body is a firm owned by an individual and does not have a registered name, use the proprietor’s full name in natural language order.
* For brands, enter the brand name here.

{% hint style="success" %}
**Examples**

Firms owned by individuals: W\.H. Smith (not Smith, W\.H.)

Brands: Valtrex
{% endhint %}

***

### Jurisdiction

To record if a corporate body or brand is associated with a national or local jurisdiction and the name of that jurisdiction is not implicit in the body’s title. Can be useful when the authority file relates to a brand rather than the manufacturing organisation.

{% hint style="success" %}
**Examples**

Jurisdiction: Croydon Borough Council

CorporateName: Parks Department

Jurisdiction: Wellcome Foundation Limited

CorporateName: Zovirax
{% endhint %}

***

### Subordinate

To record organisations subordinate to the authority.

***

### DatesofExistence

To record covering dates of the organisation’s activity.

**Rules**

* When only one year is known, enter this only and the authorised form of name will generate appropriately.
* If only approximate dates are known, use “approximately[^1]” rather c. or fl.&#x20;

{% hint style="success" %}
**Examples**

Only foundation year is known: 1932-

Only end year is known: -1948
{% endhint %}

***

### Epithet

To enter a description that would help to distinguish the organisation from others of a similar name. Used sparingly, as the basic information about what the organisation did will be entered into the Activities field.

**Rules**

* Include a profession or place qualifier
* Can use to record a married woman's maiden name if she is known under both, if it is desired to emphasise a family connection, or to distinguish two women of similar names. Use with "née".&#x20;

{% hint style="success" %}
**Examples**

Wellcome Foundation Ltd.; Wellferon; 1957-; Pharmaceutical Brand
{% endhint %}

***

### ParallelEntry

To record other forms authorised under RDA in a different language or script system. Rarely used.

***

### OtherFormsOfName

To record other names under which the person was known other than the authorised form. The “A.K.A.” field.

**Rules**

* Can include nicknames, pseudonyms or acronyms.
* **Only one name per field**. Repeat the field as required for each name.

***

### DatesAndPlaces

To record a general overview of dates and places of founding, dissolution etc. Use in conjuction with the `Address` field (see below).

{% hint style="success" %}
**Examples**

Founded in 1957

Incorporated 1 Oct 1984

Formed in 1936 as the Board of Trustees. Renamed the Board of Governors in 1992.
{% endhint %}

***

### Address

To enter known place(s) from which the body operated: address of head office, factory address(es) etc.

{% hint style="success" %}
**Examples**

28 Portman Square, London (c.1946-1958)&#x20;

52 Queen Anne Street, London (1958-1927)&#x20;

1 Park Square West, London (1972-1992)&#x20;

185 Euston Road, London (1992-2004)&#x20;

215 Euston Road, London (2004-present)
{% endhint %}

***

### Nationality

To record nationality.

**Rules**

* Use rather than English or Scottish, and Spanish rather than Catalan or Castilian.
* For countries that have subsequently achieved political independence or political union it is legitimate and relevant to use the modern nationality (e.g. “Italian” even when referring to documents created before the creation in 1861 of “Italy” as it known today.)

***

### Activity

To provide contextual background information, as you would in the [Admin\_History](/collections-information/lQ0fMyP8xr8hWWJiQkfl/archive-cataloguing/metadata-fields/context.md#admin_history) field in the main catalogue record.

***

### LegalStatus

To record the status of the corporate body: e.g. British limited company, private company, charity, etc.

**Rules**

* Record any Acts of Parliament, Royal Charters etc. relevant to its founding or evolution.

{% hint style="success" %}
**Examples**

Registered company

Private limited company

Registered charity
{% endhint %}

***

### IdentifiersForCorporateBodies

To record company registration number, registered charity number, etc., as appropriate.

{% hint style="success" %}
Registered Charity No. 229642

Registered Number: 236211
{% endhint %}

***

### Relationships

To note significant relationships with other organisations: predecessors, successors, separate bodies that engage in collaborative projects with it etc.

{% hint style="success" %}
**Examples**

Parent body: Tavistock Institute of Human Relations (TIHR).

A department of the Wellcome Trust. Preceded by the Medical Photographic Library.

Governing body and legal entity for the Wellcome Trust Sanger Institute.
{% endhint %}

***

### Notes

To record any other relevant information.&#x20;

{% hint style="warning" %}
Use this field very sparingly.
{% endhint %}

***

### ArchivistNotes

To record the name of the person creating the authority entry, the date done (in format MMM YYYY) and sources used.

***

### Rules

To record the rules under which the authority record was compiled.&#x20;

{% hint style="warning" %}
Default text sets these out and should not normally require alteration.
{% endhint %}

***

### Library\_of\_Congress\_identifier

To record a Library of Congress authority record serial number, when one exists.

***

### Creator, Creater, Modifier, Modified

To record the creator and modifier of the records, and the date created and modified

{% hint style="info" %}
Content is autogenerated. No action by the cataloguer is required.
{% endhint %}

[^1]: This diverges from AACR2


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wellcomecollection.org/collections-information/lQ0fMyP8xr8hWWJiQkfl/archive-cataloguing/authorities/name-authority-files/corporate-name-authority-files.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
