> 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/transcribe-wellcome/project-management/importing-itemisation-batches.md).

# Importing itemisation batches

For the most part these are very straightforward, as you are simply new entries in the Visual Collections table, not having to overwrite placeholder records. 

1. Spot check to ensure the batch is not currently represented in the Visual Collections table.
2. Log in to TW as admin.
3. Import the spreadsheet using RecordID# as the merge field. You only need to import columns which have data in them - if they are entirely blank, click 'do not import' instead. The columns to import are generally:
   * Visual Accession Number Prefix 
   * CC number \[Visual Accession Number without prefix]
   * WA/HMM reference \[Register]
   * Image number
4. Spot check that links to digitised images are working correctly.
5. Move spreadsheet into 'Imported into QB' folders and mark import as complete in Transcribers spreadsheet.


---

# 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/transcribe-wellcome/project-management/importing-itemisation-batches.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.