← Browse the public library

Build research notes that remain useful

An illustrated field notebook, map, magnifying glass and compass overlook a meadow and watershed.

Can another reader find the source, understand the reasoning and see what changed?

Keep source records, claims and your interpretation linked. Give each a stable identifier, preserve important versions and make corrections visible enough to revisit a decision.

Evidence checked October 17, 2026 (America/Denver; research received October 18 UTC). Version 1.0. Desk review; no hands-on testing.

What this guide helps you do

For personal research, community projects and small public knowledge collections. Start with a few sources and a method you can maintain. Software supports the record; checking the evidence remains a separate task.

Give each research session an answerable question

Write the question, its intended use and what would count as useful evidence. For example, ask which records establish when a local project opened rather than collecting everything about its history. Record the date and boundaries of the search. Keep a short list of unanswered questions. This makes it easier to stop collecting duplicate material and return deliberately when new information appears.

Create one dependable record for each source

Record creator, title, publisher, edition or date, original location and the exact page or section you used. Give the record an identifier that survives a folder move. A reference manager can connect metadata, notes and tags, but compare imported fields against the original. Distinguish a link to a changing webpage from a saved version; decide what you may retain or share before attaching files. Source: Zotero reference-manager overview.

Separate the source from what you infer

Use clearly labeled fields for a short paraphrase, a locator and your interpretation. Then add why the source matters, its audience, limitations and relationship to other sources. Mark an uncertain conclusion as uncertain and retain evidence that complicates it. This turns a collection of highlights into a research trail. A polished citation alone cannot establish that the cited work supports a particular statement. Source: Cornell annotated-bibliography guide.

Connect notes through claims and useful topics

Give a recurring question or claim its own entry and link all relevant sources to it. Add a few consistent topic terms and a plain-language description of each relationship: supports, limits, contradicts or supplies background. Reuse the original source record across topics. Include common alternative words so a future search can reach it. Try retrieving one item using the question someone else would naturally ask.

Make versions and corrections traceable

Choose a clear version identifier, record who changed what and why, and identify the current master. Keep milestone versions and link notes to the source version actually examined. When evidence changes a conclusion, mark the earlier conclusion as superseded and explain the reason. Decide how collaborators reconcile changes before several copies diverge. Treat backup and recovery as additional tasks beyond version naming. Source: UK Data Service version-control guidance.

Leave a small operating guide

Create a readme explaining identifiers, tags, storage locations, access limits, the correction process and the next source check. Ask an authorized colleague to follow one claim back to its original page. Repair missing locators, ambiguous filenames and unexplained judgments. A sustainable system is one another person can use after its creator leaves; increase complexity only when a demonstrated retrieval problem calls for it.

A pathway to practice

  1. Frame the question: State the decision and evidence needed.
  2. Describe the source: Keep identity, version and an exact locator.
  3. Connect the reasoning: Link claims, evidence and disagreements.
  4. Revise and hand over: Record corrections and make retrieval possible.

Resources and their limitations

Zotero reference-manager overview

Use it for: Connect source descriptions, notes, tags and citations in a research library.

Access and cost: Publisher describes Zotero as free. Equipment, support and optional attachment-storage services have separate conditions; no paid plan selected.

How to use it: Read The Basics, Organize and Collect; compare a small source record with the original before depending on imported metadata.

Evaluation and limits: Overview only; no installation, account, sync, export or plugin tested. Automated metadata is not verified evidence; attachment sharing requires separate permission. No version compatibility guarantee.

Alternatives: A source-linked spreadsheet or plain-text index; a librarian-supported reference manager.

Open Zotero reference-manager overview

UK Data Service version-control guidance

Use it for: Make changes, file relationships and current versions understandable.

Access and cost: Public guidance is free; software, storage and staff time may cost extra.

How to use it: Choose version identifiers, a change log and a master location appropriate to the number of editors and copies.

Evaluation and limits: No substantive revision date established. Old software examples, including SyncToy, are not current recommendations. Version history does not by itself establish source truth or provide a backup.

Alternatives: A simple document-control table; institution-supported versioning tools and backup arrangements.

Open UK Data Service version-control guidance

Cornell annotated-bibliography guide

Use it for: Write a short source note that evaluates relevance and perspective as well as content.

Access and cost: HTML guide is free to read; access to underlying works varies.

How to use it: Use Explanation and The Process with the actual source, including contrasting perspectives.

Evaluation and limits: Metadata modified March 10, 2026. Examples are teaching examples, not current research findings adopted here. No linked citation guide or underlying article reviewed; third-party text not republished.

Alternatives: A reference librarian; a source-linked notes table with a separate interpretation field.

Open Cornell annotated-bibliography guide

Checklist

  1. State a question and its intended use.
  2. Create source records with exact locators and dates.
  3. Keep paraphrase, quotation and interpretation distinct.
  4. Link evidence and disagreements to identifiable claims.
  5. Record versions, corrections and the master location.
  6. Have another person retrieve one source and leave handover instructions.

Related guides

Finding primary sources (SG-D18-S02); Checking claims and comparing evidence (SG-D18-S03); Archives, oral history and local knowledge (SG-D18-S05); Systems of Trust (SG-D18-S07); Privacy, security and identity (SG-D17-S03); Backups and digital preservation (SG-D17-S04); Personal learning plans (SG-D19-S01); Intergenerational knowledge and support (SG-D20-S05).

From the Whole Earth registry to current practice

Data Study discusses organization and retrieval; the adjacent McBee Keysort review illustrates a physical card-index system. Use the historical retrieval question, not the card system’s performance, prices or obsolete workflow, as the bridge to source-linked research notes.

Whole Earth Spring 1969 archive edition

Sources and review notes

No reference software was installed or tested; no metadata import, synchronization, export, restore or shared account was exercised. Tool features are publisher descriptions. Privacy, rights and institutional retention policies require the actual project’s review.