Plan and prepare
When you save a useful guide, create a source note at the same time. Record the title, author or organization, original address, publication or revision date when available, and the date you obtained it. A file called 'water advice final' does not tell a later reader whose advice it contains or when it applied.
Describe how the saved copy relates to the original. It may be an unchanged download, a printed page, a translation, an excerpt, or your own summary. Keep your commentary in a separate section or file so it cannot be mistaken for the source author's words. Preserve the original title even if you use a shorter local filename.
Use a clear process
Add a brief purpose note explaining why the item was selected and what question it helps answer. Record geographic or technical limits that the source states. If a date or author cannot be determined, say so. Absence of metadata is a reason for caution, not an invitation to invent plausible details.
Track changes with a simple history: date, person, change, and reason. When replacing an outdated document, retain the earlier copy in a clearly marked archive if it remains useful for understanding past decisions. Do not let several different files all appear to be the current edition.
Worked example
Suppose you download an equipment manual, print two relevant pages, and write a shorter local checklist. Treat those as related but distinct items. The manual retains its original manufacturer, model, edition, and download address. The printed excerpt identifies its parent document and page locations. The local checklist records who prepared it and when it was checked against the manual. This relationship lets a future reader understand which wording came from the manufacturer and which steps were organized locally. It also makes an update easier when the manufacturer publishes a new edition.
Decisions and exceptions
Use a small source record that can travel with the file. A plain text note is often sufficient for a personal collection, while a catalog can hold the same fields for a group. Add a stable item identifier so a filename change does not break every reference. Record a link's access date, but do not confuse that with the source's publication date. If a page offers no revision information, preserve the uncertainty. Where a saved copy is incomplete, note what is missing, such as an online attachment or a diagram that did not download.
Check and improve
Review provenance during ordinary use. When a reader finds an ambiguous instruction, the source record should provide a route to the original and any later version. Record the outcome of that check and explain whether the local copy changed. Avoid presenting an old access date as evidence that the content remains current. Some documents are mainly historical; others support decisions that need current guidance. Label that purpose explicitly. A clear history helps people assess a document's relevance without forcing them to trust the confidence of its title, layout, or most recent uploader.
Solo and community application
Working alone, put a small text note beside each important download. In a community archive, agree on required fields and let a second person check a sample of records. Test the record by asking someone unfamiliar with the collection to locate the original source and explain which version they are reading.
Reference guidance
The Library of Congress dataset guidance lists contextual metadata, identifiers, and version information among useful preservation details. This guide adapts that principle to a small practical library. A source note does not prove that a claim is correct, but it gives future readers a path to check it.