While digitizing our garden's harvest cards, I learned that an archive can become tidier as it becomes less true. My spreadsheet preserved dates and weights but erased the gardeners' conflicting explanations. Adding audio interviews restored uncertainty the columns could not hold and left me with a question: how should institutions describe records without making one official voice seem complete?
Lakeside's History of the Book seminar would give me a vocabulary for the material choices inside records, while the undergraduate practicum at the Neighborhood Memory Lab would let me examine how description standards affect discoverability. I would use the Digital Scholarship Studio to compare a fixed catalog entry with layered community annotations, testing which interface makes disagreement visible without turning it into noise.
I can contribute the consent checklist and interview workflow our garden developed, but I also want them challenged by communities with different histories of collection. Lakeside's combination of material study, public history, and interface design fits the way my question has grown: not from wanting to preserve everything, but from learning that preservation always gives someone the power to name.
I would also join the campus oral-history collective as a listener before proposing a tool. Its training in narrator review could help me redesign our annotation interface so contributors approve context, not merely a transcript. That work would challenge my instinct to solve disagreement through display alone and make consent part of the archive's continuing structure rather than a checkbox completed at intake, review, and every later revision.
Original teaching sample written by Writivia. Do not copy its language, identity, or events.