Hunt Institute for Botanical Documentation
A Research Division of Carnegie Mellon University

Hunt Institute Archives Text Discovery Platform

Search a large and growing portion of our online collections, including handwritten documents.
PROTOTYPE

This prototype uses state-of-the-art artificial intelligence, including a vision-language model (VLM) capable of reading handwritten documents as well as typed and printed text, to create searchable transcriptions of digitized materials in the Hunt Institute Archives. This makes it possible to search the textual contents of individual pages, including material that may not be described in the archival catalog.

Use Keyword search for specific words, names, dates, scientific names, or phrases. Try Semantic search (experimental) to describe a topic, question, or kind of material when you do not know the exact wording used in the documents.

About the AI-generated transcriptions

The transcriptions are generated automatically from page images and may contain errors, especially with difficult handwriting, unusual names, multiple languages, image-quality problems, or complex layouts. They are intended primarily as a discovery aid rather than authoritative transcriptions.

Each result provides the generated transcription and links to the original digitized material and associated archival description so that readings can be checked against the source. The transcription workflow uses AI models run locally by the Hunt Institute.

About Keyword and Semantic search

Keyword search is the default and matches the wording in the transcriptions. Results contain all your terms. Use quotes for an exact phrase. Substring matching is supported, so aceae can find plant-family names ending in -aceae.

Semantic search (experimental) is useful when you know what kind of material you are looking for but do not know the words used in the documents. It ranks transcribed passages by similarity of meaning, so relevant results may not contain the exact words in your query.

Semantic queries can be broad research topics, descriptions of activities or relationships, or natural-language questions. For example:

Semantic search is not a chatbot: a question is used as a search query, and the system returns archival passages that appear conceptually related to it rather than generating an answer or summary. Short descriptions and ordinary research questions generally work better than lists of disconnected keywords. Quotation marks have no special meaning in Semantic mode. Cross-language matching may work in some cases, but it should not be treated as translation.

Keyword and Semantic search are complementary. Keyword search lets you require particular wording; Semantic search can surface differently worded passages about the same subject. Depending on the research question, trying both can reveal different useful material.

Open a result: use the prominent page-and-transcription link to see the metadata, PDF, and full transcription. Keyword-search terms are highlighted in the transcription.

Archives Collections Database (ArchivesSpace): the Collection, Item/Folder, and Digital Object links open the corresponding archival records. Collection-level dates describe the collection as a whole, not necessarily the specific item or page.

If a PDF does not load: on the detail page, use the Digital Object link, click “Go to file” in ArchivesSpace, and navigate to the page number shown here.

Current limitations
  • Automated transcriptions can contain missing or incorrect text or unintended repetition. Difficult handwriting, image quality, unusual layouts, and multiple languages can reduce accuracy. Always consult the original page image when an exact reading matters.
  • Semantic search remains experimental. Its rankings are an additional discovery aid, not a complete or definitive set of relevant results, and highly ranked pages can sometimes be only broadly related.
  • This is an active prototype. Search coverage, transcriptions, functionality, and the interface may continue to change as additional archival material is processed and the system is improved.

← Back to results

Page 85 · DO #1310 · Archer Vol.1_2_r

Collection
William Andrew Archer (1894–1973) papers
Item/Folder
Volume 1, 1937
Digital Object
DO #1310, page 85
Collection-level dates
1929–1964
Open PDF at page 85 ↗

Page transcription

Western Shoshone Reservation, Owyhee, Nevada. Indian Plant Uses. 5.

Common name    Indian name   Number   Manner of Use.
Trumpet Phlox "Enea mowenna & wife", SH   M666 Whole plant steeped for blood diseases by Paiutes. Not used here by Shoshones.
False Hellebore "SH. "Tabassop", Wunda-vassop"   M267 Root mashed and rubbed raw on swellings, or snake-bite, sore throat or glands.
Coral Root None   M273 Because of unusual origin, it is highly regarded as a medicine in penumonte, or to build up the blood. Whole plant is dried, or to be boiled. Same is true of the snow plant.
Blue Gentian None   M274 No Indian use was found for this plant, but it has its place in regular medicine, tincture of the root being used in mild intermittent fevers, and as bitter bits. Same is true of the snow plant.
Indian hemp None as yet. M275 Sent in by an old Indian who said it was useful to Indians, but did not mention that an Apocynum and rosemary could be made from it. Used thus by California Indians.
Alder "Howl-up" M277 California Indians use bark are also collected and added to the brew.
Hulseam Fir SH. "Wungobe" M276 Tea from needles is valued in pulmonary troubles, and resinsous bitters on bark are also used by Indians.
Little Locoo None   M279 This plant is undoubtedly res-
Stone Seed "Not-misha" SH. M288 Tea for diarrhea from roots.
Slender Loco "Hoont", SH. M290 Tea from whole dry plant cures dier-
Book cross Elderberry "Hubu", P. M292 Berries used for food. Wood formerly used for "fletestokes" on account of its lightness and in-