Historians work with sources across time, institutions, and formats — archival documents photographed in a single visit, books borrowed from libraries, primary sources that can't be removed from special collections, digital repositories with varying access terms. The organizational challenge is compounded by the long timelines of historical research: the archival notes from a 2022 visit to a state archive may be the primary source evidence for a chapter drafted in 2025.
The software stack for historians needs to address four professional knowledge problems: source management and archival organization (the challenge of organizing sources gathered across years, institutions, and formats), research and argument development (converting sources into historical argument), writing and publication (the long-form writing process and the professional publication workflow), and professional and career knowledge (the accumulated professional wisdom about the field, the discipline, and the career).
Problem 1: Source Management and Archival Organization
The historian's source management challenge has two dimensions: the diversity of source formats (handwritten documents, typed transcripts, printed documents, photographs, digital files, microfilm scans, oral history recordings) and the temporal gap between gathering and using sources. A source captured in an archive three years ago needs to be retrievable when writing the chapter that depends on it.
The source capture discipline:
Every source gathered in an archive or from a repository needs to be captured with enough metadata that it can be cited and contextualized without returning to the archive. This is especially critical for archival sources that may be difficult or impossible to access again.
SOURCE MANAGEMENT KB
SOURCE ENTRY:
Repository: [Archive, library, database, or collection name]
Collection: [The specific collection or finding aid]
Box/Folder/Item: [Specific location within collection]
Date accessed: [When I accessed this source]
DOCUMENT IDENTIFICATION:
Title/Description: [What the document is]
Date of document: [When it was created]
Author/Creator: [Who created it]
Format: [Handwritten / Typed / Printed / Photograph / Recording / Other]
WHAT I CAPTURED:
Transcription or summary: [Verbatim for key passages; summary for context]
Image file: [Filename of photograph if I photographed it]
RELEVANCE TO RESEARCH:
How this relates to my project: [Why I captured this source]
Argument function: [Evidence / Counterargument / Context / Illustration / Other]
Chapter(s) relevant to: [If I know]
CITATION INFORMATION:
Complete archival citation: [Drafted at time of capture, in the appropriate style]
TRANSCRIPTION STATUS:
[ ] Fully transcribed [ ] Key passages transcribed [ ] Summary only
[ ] Still needs full transcription
Citation at capture time is the historian's most important organizational discipline. Reconstructing a complete archival citation after the fact — which archive, which collection, which box and folder, which item number — from incomplete notes can be impossible if the notes don't include the necessary information. Drafting the complete citation at the time of capture means it's available when writing.
Problem 2: Research and Argument Development
Historical argument is built through the interpretation of sources — what the evidence shows, what it doesn't show, and how it relates to existing historiography. The research and argument development knowledge infrastructure organizes both the sources and the evolving argument.
The interpretive record:
Historians not only need to remember what sources they have; they need to remember their interpretations of those sources and how those interpretations have evolved as they gathered more evidence. The note that says "this suggests X" in year one may be contradicted or complicated by year three's archival findings.
RESEARCH AND ARGUMENT KB
BY ARGUMENT/INTERPRETATION:
Argument: [A historical claim or interpretation]
Status: [ ] Hypothesis [ ] Working argument [ ] Supported [ ] Revised [ ] Abandoned
CURRENT FORMULATION:
How I'd state this now: [The current version]
EVIDENCE:
Sources supporting this: [References to source KB entries]
Sources complicating this: [Evidence that complicates the argument]
What's still needed: [Evidence gaps]
HISTORIOGRAPHICAL CONTEXT:
How this relates to existing scholarship: [Where it fits in the field]
What it revises or challenges: [If applicable]
HOW IT'S EVOLVED:
Earlier formulation: [How I first stated this]
What changed it: [Evidence or reading that developed the interpretation]
BY HISTORIOGRAPHY:
Historiographical debate: [A debate in the field]
MAJOR POSITIONS:
Position A: [Who holds it + main argument]
Position B: [Who holds it + main argument]
My position: [Where I stand + why]
KEY WORKS:
Essential reading: [Works I need to know for this debate]
Recent developments: [What's changed recently in this debate]
Problem 3: Writing and Publication
Historical writing has specific professional conventions — footnotes, archival citations, historiographical engagement — and a long-form writing process that may span years. The writing and publication knowledge infrastructure supports both the craft of historical writing and the professional publication workflow.
Project tracking:
WRITING AND PUBLICATION STATUS
Project: [Book / Article / Chapter title]
Type: [ ] Monograph [ ] Journal article [ ] Edited volume chapter [ ] Reference work
Status: [ ] Research [ ] Draft [ ] Revision [ ] Under review [ ] Accepted [ ] Published
DRAFT STATUS:
Current draft: [Version + date]
Word count: [Current]
Target: [Target for submission]
PEER REVIEW:
Submitted to: [Journal or press]
Status: [ ] Under review [ ] Revise and resubmit [ ] Accepted [ ] Rejected
Review received: [Date + main points if received]
Response plan: [How I'm addressing reviewer comments]
Problem 4: Professional and Career Knowledge
Professional and career knowledge covers the accumulated understanding of the discipline: how to navigate peer review, how to develop a research agenda, how the job market works at different career stages, and what the historian has learned about building a sustainable scholarly career.
The professional KB:
PROFESSIONAL AND CAREER KB
By professional area:
AREA: [e.g., "Peer review process" or "Grant applications"]
WHAT I KNOW NOW:
Current understanding: [What I've learned]
NON-OBVIOUS THINGS:
What I didn't understand until I experienced it: [Practical wisdom]
What doesn't work despite conventional advice: [Where standard guidance fails]
The Pre-Archive Workflow
Before any archival visit:
- Source KB: which sources have I already gathered that are relevant to this visit's collections?
- Argument KB: what are the current gaps in my argument's evidence base that this visit might fill?
- Research priorities: given the evidence gaps and the argument's needs, what should I prioritize in the archive's available time?
The pre-archive workflow converts archival visits from general source collection into targeted evidence gathering for the argument's specific needs.
Key Takeaways
-
Complete archival citations drafted at time of capture. Reconstructing from incomplete notes after leaving an archive may be impossible; complete citation at capture is the discipline that makes all future writing possible.
-
The interpretive record documents how arguments have evolved. The interpretation that was revised by later evidence is part of the intellectual history; documenting the evolution shows the thinking rather than only the conclusion.
-
Historiographical context should be captured for each argument. Where the argument sits in relation to existing scholarship — what it revises, what it challenges, what it builds on — is the professional location that makes the argument publishable.
-
The pre-archive workflow converts visits from general collection to targeted evidence gathering. Knowing what the argument specifically needs before arriving at the archive makes the limited access time more productive.
-
Professional and career KB should capture what doesn't work despite conventional advice. The academic discipline has significant received wisdom about careers, peer review, and research development that doesn't hold uniformly; experience that refines this advice is the most practically valuable professional knowledge.
Conclusion
The historian's software stack addresses four professional knowledge problems: source management and archival organization (complete citations at capture, image file tracking, transcription status); research and argument development (interpretive record with evolution documented, historiographical context, evidence gaps); writing and publication (project tracking through the professional publication process); and professional and career knowledge (what doesn't work despite conventional advice). The pre-archive workflow — clarifying argument evidence gaps before each archival visit — is what converts archival time from general source collection into targeted evidence gathering that directly advances the book's argument.
Related reading: Clip Articles for Later Reading.