> 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/research/people/alphabetical/keighley-mr.md).

# Keighley, Mr

Mr Keighley (DATES) Registrar

active: \[recorded active c.1932- set up and oversaw system of registration

!! Oral history from oral history of Margaret Rowbottom. Discussing registration department work, inc after HSW’s death:

<<< “A Registration department was set up under Mr Keighley, and a new system of registration inaugurated. The intention was that an object should only be ‘registered’ when it had been properly identified and scientifically described, but unfortunately Captain Saint, possibly under pressure from the Trustees \[after HSW’s death] to produce results, had a lot of material renumbered with no correction of the information given on the accession cards or in the old registers.”

<<< //Further research needed:// \[dates for when new system was set up can be XR from WAHMM/CM files, where it is discussed. New reg numbers start from c.1929?]

\[\[museum staff]] registration


---

# 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/research/people/alphabetical/keighley-mr.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.