AUMLayer · Institutional manuscript guide
Searchable manuscript collections
Connect the catalogue, the page and the passage. Help readers discover a collection with context.
A catalogue tells a reader that a manuscript exists. Page images let them inspect it. A reviewed transcription opens its contents to text discovery. The most useful collection experience connects these layers, so finding a passage becomes the beginning of informed reading rather than the end of a search.
LipiForge by AUMLayer approaches manuscript discovery through those relationships. Original catalogue identifiers, source pages and reviewed text remain connected, helping institutions bring their existing holdings into a more useful digital reading and publication workflow.
How can a manuscript catalogue connect to searchable digital text?
Keep catalogue records, page images and reviewed text linked through stable manuscript and page references. LipiForge’s source-linked approach brings these layers together so a reader can identify a work, find a relevant passage and return to the source page and edition behind that result.
Build on the institution’s existing catalogue
Shelfmarks, collection names and manuscript identifiers often carry years of curatorial work. They are useful foundations for a digital programme. Mapping them alongside the incoming files preserves the relationship between a physical holding, a digital manuscript and the pages a reader sees.
Language, script, title and attribution can enrich that context. Where a date or author is uncertain, the record can retain that uncertainty. The objective is to make the existing collection easier to understand, not to replace its curatorial knowledge with apparently precise but unsupported values.
Keep the record layers clear
A catalogue match and a full-text match answer different questions. The first may identify a relevant work; the second may identify a passage within it. Source images and review status then help a reader understand what the result represents and how it can be used.
The example below uses invented identifiers to illustrate a record relationship. It is not an extract from a customer catalogue. A real programme maps the institution’s own fields and identifiers before defining search and edition delivery.
| Record layer | Example reference | Meaning for the reader |
|---|---|---|
| Collection | Collection A | The custodial and catalogue context |
| Manuscript | MS-012 | The identified work or holding |
| Page | Page 008 | The source image for comparison |
| Text version | Reviewed edition 1 | The reading used in this result |
Connect discovery to close reading
Useful discovery gives the reader a route from a passage to its source. A result can identify the manuscript, the relevant page and the text version being searched. The reader can then inspect the source and understand which editorial reading underlies the passage.
LipiForge’s approach connects reviewed text and source references for that purpose. Exact wording, normalised discovery and broader semantic retrieval are different behaviours to define in a programme; they should be described in terms of what the reader needs to find and how the result will be checked.
Use interoperability to support the reading experience
The IIIF Presentation API describes the structure and presentation of digital objects, including ordered views and annotations. It provides a useful reference when discussing how manuscript pages and associated content can be presented in a viewer. Presentation, metadata discovery and full-text search are nevertheless separate interface concerns.
For an institution receiving a new collection, the practical question is how its chosen tools will exchange the required images, text and metadata. Agreeing a sample exchange and the receiving system’s requirements makes interoperability concrete. LipiForge programme discussions can include those handover needs alongside recognition and scholarly review.
Give access and publication their own decisions
A catalogue entry may be public while its images or working text remain restricted. Some readers may need an approved edition, while scholars need access to review material. Treating these as distinct decisions helps institutions share useful knowledge without confusing internal work with released publications.
The same distinctions matter in large manuscript initiatives: preservation, catalogue access and reusable text support different stages of discovery. The Gyan Bharatam guide provides a broader programme context, while a LipiForge discussion focuses on the collection, audiences and outputs your institution wants to connect.
Questions institutions ask
- Can we keep our existing catalogue identifiers?
- Those identifiers are an important starting point. A LipiForge programme maps the existing collection, manuscript and page relationships so that text and editions can retain their connection to the institution’s catalogue.
- Does a catalogue search also search the manuscript’s contents?
- Not necessarily. Metadata discovery identifies records, while full-text discovery searches a textual reading. Connecting the two gives a reader both the work’s context and a route to relevant passages.
- What should accompany a source-linked search result?
- The manuscript identity, passage, page reference and relevant text version help a reader understand the result. Access and review status should reflect the institution’s intended audience and publication policy.