> 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/collections-information-systems/calm/multiple-items-packaged-together.md).

# Multiple items packaged together

## The issue

Item-level records are the orderable units we use at Wellcome, i.e. the thing that can be requested by users.

Each item is packaged appropriately and when it is requested by a user, it is delivered within that packaging. For safety and preservation reasons, users cannot request partial items: they request and receive an entire item.

Multiple items packaged together is a problem, because it either requires an item to be removed from it's packaging in order to be retrieved (bad for security and preservation), or it requires all the items to be retrieved and brought to the RMR. This is bad for location & movement control as these other items will not have been requested and not have an audit trail when they are moved. It also causes problems if these other items are requested by other users.

## Solution 1: packaging each item separately

Often the most straightforward solution is to repackage the items so that each one is packaged separately.

See the [repackaging instructions](/collections-information/lQ0fMyP8xr8hWWJiQkfl/archive-cataloguing/general-guidance/preparing-a-collection-for-cataloguing.md#repackaging) in the Archive Cataloguing Gitbook for guidance.

If the resulting repackaging means the items no longer fit in the box, an additional box will need to be used:

* Put the excess material in the new box. Check Calm and/or the physical material to see what the next box number in the sequence should be.
* Create a [box label ](https://wellcomecloud.sharepoint.com/:w:/s/wc2/cr/ci/EVb3OyWdnilMnCc_KzYMGb8BqLyCxDUqWBgCBf50RmzAZw?e=XPmLpD)listing the relevant PublicRefs and giving the box number.
* Update the Calm `BoxNumber` field with the new box number for the relevant items
* Contact the Storage Manager for a stacks location for the new box. Update the Calm `location` field with the new location. 

## Solution 2: recatalogue the physical package as the item

Solution 1 is often the preferred solution, but if a large number of items are packaged together and splitting them would be too time consuming, then recataloguing the material is an option.

In this solution, instead of having several Calm item records, there will be one record which aggregates the items (and the items effectively become piece records).

{% hint style="success" %}
**Example:**

A series contains 6 item records, 4 of which are packaged together: PP/ABC/A/1/1; PP/ABC/A/1/2; PP/ABC/A/1/3; PP/ABC/A/1/4

An item record is created to encompass all 4 records: PP/ABC/A/1/1-4
{% endhint %}

* Either create a new Calm record for the new item, or repurpose the first existing item record to become the new item
* The PublicRef should be a range of the old items it includes
* The old items should now be treated as piece-level records. Move the data into the new item record and edit it following the instruction given in [Removing piece-level records](/collections-information/lQ0fMyP8xr8hWWJiQkfl/collections-information-systems/calm/removing-piece-level-records.md#editing-the-calm-item-record)
* In the `ArchivistNotes` field, add a statement to explain that the items have been recatalogued due to being packaged together.

{% hint style="info" %}
If the items to be recatalogued comprise an entire series, rather than creating a new item record you can turn the series record into an item

For example, PP/ABC/A/1 (series record) comprises 4 items: PP/ABC/A/1/1; PP/ABC/A/1/2; PP/ABC/A/1/3; PP/ABC/A/1/4. Rather than creating a series with a single item, turn PP/ABC/A/1 into the item 
{% endhint %}

   


---

# 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/collections-information-systems/calm/multiple-items-packaged-together.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.