# CONTENT

### Alternative\_Title

To record parallel titles and other titles a work is known by, aside from the title proper, such as working titles or translated titles. Also used to record any previous titles used in the catalogue record if they are changed.

**Rules**

* Use a separate instance of the field for each alternative title being recorded.
* Where the field is recording a previous title, include the date it was changed.
* Record the original title here if it has been altered for the title field at point of cataloguing. Prefix it with “Original title: ”

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

Previous title, replaced April 2021: Sterilizers, circa 1900.

&#x20;

Original title: “1975-77”
{% endhint %}

***

### Description

\[ISAD(G) 3.3.1]

{% hint style="info" %}
Mandatory at **Collection** level
{% endhint %}

To provide information about the material that is not apparent from the title.

**Rules**

* Do not use this field if the title is self-explanatory and there is no additional information required.
* Provide explanations to data in other fields such as gaps in the date range, uncertain or contested creator attribution, approximations made etc.
* Be specific. For instance, do you have correspondence or individual letters? Reprints from where? Manuscript or typescript?
* Include any relevant cross-references with other records in the same archive collection. (Cross-references to other archives or items held by Wellcome should be noted in the Related\_Material field).
* Use paragraph tags \<p> \</p> to break up large amounts of text.
* For **born-digital** material, if appropriate you may wish to include an overview of directory structure, filenames or notable file formats.
* For **visual and material culture,** if appropriate you may wish to record notable visual elements including text incorporated into a visual design, [colour](https://app.gitbook.com/s/-MYL8eOUpmONV4iPo291/metadata-framework/metadata-elements/colour) characteristics, or include a [detailed visual description](https://app.gitbook.com/s/-MYL8eOUpmONV4iPo291/metadata-framework/metadata-elements/detailed-visual-description). You may also consider including the work's [place of creation](https://app.gitbook.com/s/-MYL8eOUpmONV4iPo291/metadata-framework/metadata-elements/place), particularly if the creator is unknown.
* At Collection level, for collections that contain uncatalogued material, please follow section 4.8 of [the Acquisition and Accessioning manual](https://wellcomecloud.sharepoint.com/:w:/r/sites/wc2/Policies%20%20Procedures/Procedural%20Manual/3_Procedures/2.%20Acquisition%20and%20Accessioning%20Procedure/Acquisition%20and%20accessioning%20manual%20text%20only.docx?d=w41a2b057f9454f8881039d59f4802d90\&csf=1\&web=1\&e=UbcCzX).

{% hint style="success" %}
**Examples**&#x20;

Contains / Includes X relating to…

Subjects covered include…

Letters to/from…

Correspondence between…
{% endhint %}

***

### Appraisal

\[ISAD(G) 3.3.2]

{% hint style="info" %}
Mandatory at **Collection**&#x20;

Mandatory at **Item** level for born digital material
{% endhint %}

To record information on any appraisal, destruction and scheduling action taken.

**Rules**

* Where appropriate, record the authority by which the action has been taken.
* Use paragraph tags \<p> to break up large amounts of text.
* For **born-digital** material, the collection level record should include the following: “Digital material has been transferred from the original physical media to secure storage. The physical media has not been retained.”
* For **born-digital** material at lower levels, this field should record general appraisal information but do not list individual filenames; these are recorded in the metadata export. As a minimum include the first statement below in the example box. This information can be recorded at the most appropriate level.

{% hint style="success" %}
**Examples**&#x20;

Collection level (general):

The collection represents the entirety of records transferred…No appraisal was deemed appropriate. Gaps in record series do exist, which could suggest loss / disposal of material prior to transfer, or that these records were simply not created.

&#x20;

Series level (specific):

The following video cassettes have been removed from this collection and destroyed, either due to format obsolescence, damage or duplication:

"Threads, BBC 2 23 Sep, B Hines" (betamax)…

&#x20;

Born-digital examples:

Thumbs.db and .DS\_Store files were removed during the automated ingest process

&#x20;

A duplicate copy of disk \[X] has been removed
{% endhint %}

***

### Accruals

\[ISAD(G) 3.3.3]

To record if future accruals, additional transfers or deposits are expected. It can also be used to record a brief description of any material which remains to be catalogued.

{% hint style="success" %}
**Examples** &#x20;

Born-digital material expected.

&#x20;

Further accruals to the collection are anticipated.

&#x20;

The following is an interim description of material that has been acquired since this collection was catalogued. This description may change when cataloguing takes place in future: AGM Minutes, 1987-1990, Committee Minutes, 1979-1989…
{% endhint %}

***

### Arrangement

\[ISAD(G) 3.3.4]

{% hint style="info" %}
Mandatory at **Collection** level
{% endhint %}

To provide information on the arrangement of the unit of description, to assist researchers to make sense of the material.

**Rules**

* Differentiate between the creator’s original arrangement and any arrangement imposed by the cataloguer.
* Include a list of sections into which the material has been divided.
* Use paragraph tags \<p> to break up large amounts of text.

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

Example 1:

\[person] kept records with their papers split by subject into different drawers and files around the house. There were hanging files of correspondence and hanging files of research subjects but as these grew too large they organised certain subjects into dedicated drawers. Rather than have a long list of Subject Files the cataloguer has split the files using an arrangement as close to the original. The listing is as follows…

&#x20;

Example 2:

The files have been arranged with the assistance of \[creator] to best reflect how they were created and used. Arranged by section as follows…

&#x20;

Example 3:

The records have been kept in their original order and have been arranged to reflect the original filing system as far as possible.

&#x20;

Example 4:&#x20;

The collection is split into an A and B section, these relate to the Registered and Non-Registered files. The registered section (A) contained files labelled with a registered number as a form of internal cataloguing. This has been followed in the cataloguing structure and is recorded in the "Previous Numbers" section of the catalogue. The non-registered section (B) contained files and loose papers with no registered number. The structure of section B follows the registered sections where possible…
{% endhint %}

***

### Subject

To highlight key subjects covered in the material. Predominantly used at Collection level, but also useful at lower levels.

**Rules**

* **Only one subject per field.** Repeat the field as required.
* Use MeSH or LCSH as the controlled vocabulary to identify subjects.
* A **maximum** of 10 subject terms attached to a record.
* See [Subject Authority Files](https://docs.wellcomecollection.org/collections-information/lQ0fMyP8xr8hWWJiQkfl/archive-cataloguing/authorities/subject-authority-files) for further information
