The problem here is simple. Ior/r/2 looks like a shelfmark, not a career access code. In British Library catalog records, IOR/R/2 is used for a record group within the India Office Records, specifically the Crown Representative’s Records for Indian States Residencies. That is archive language, not login language.
A researcher who sees this kind of string can mistake one system for another. That happens often when a code is copied without its context. A shelfmark names a body of records. An access code grants entry to a service, account, or portal. The two can look alike to the eye, but they do different work.
The British Library catalogue makes this clear in the record labels and access notes. Items under IOR/R/2 appear as archival holdings with descriptions such as residencies, agencies, and file ranges. The access note attached to these records says they are available for research unless stated otherwise, and that physical items must be requested through the library’s collection form. Digitised items, when present, can be opened through the catalogue. None of that points to a career account or a staff code.
This matters because archival identifiers can be dense. They often mix letters, slashes, numbers, and local file names. To a beginner, that can feel like a password or an internal code. In fact, it is usually just a finding aid. It tells you where a record sits in a larger arrangement, and sometimes what kind of office created it.
A plain example helps. Suppose a catalogue shows IOR/R/2 Hyderabad. That tells you the record belongs to the Hyderabad branch of the Crown Representative’s Records. It does not tell you how to log in to anything. It tells you what the source is, not how to authenticate.
For access, the real question is always different. What is the item type? Is it digitised? Must it be requested in person? Does the institution require a reader pass or local registration? Those are access conditions. They are documented by the holding institution, and they matter far more than the bare code itself.
I read this kind of evidence as a reminder to slow down before making a guess. A code in an archive catalogue often describes provenance, hierarchy, and storage. It does not promise searchable full text, remote access, or any special privilege. If the record is a physical archive item, the catalogue usually says so plainly.
The British Library’s wording is practical in this respect. It separates the shelfmark from the access route. It also notes when digitised content is available online and when a physical visit is still required. That split is useful. It keeps the record description from being confused with the mechanics of getting at the record.
The same caution applies across many digital collections. A label can look cryptic, but the answer is usually in the surrounding metadata. Metadata is the descriptive information attached to a record. It tells you what the item is, where it belongs, and how it can be used. For archives, that is often more important than the bare code on its own.
The honest limitation here is also plain. IOR/R/2 is not documented as a career access code in the material at hand. It is documented as an archival reference within British Library holdings. If someone wants an access route, the correct place to look is the institution’s access note, not the shelfmark itself.
That is the practical lesson. A code should be read in context, and the context should be trusted before the guess is. Once that habit is in place, a researcher can tell an archive reference from an access credential without confusion.
The Source List keeps that same promise: one digital source worth knowing, one search tip, and one honest limitation.