Name Research Files Without Losing the Source Citation

A filename can tell you what an image is, but it cannot comfortably carry everything needed to cite it. Give the file a short, stable identifier and keep the fuller source description in an index or companion note. The two should remain connected even if the file moves to another folder.

Start with a small batch of current research. There is no need to rename an entire collection before improving today’s downloads. Choose a pattern you can understand at a glance and write it down. Consistency matters more than an elaborate code.

Separate identification from description

An identifier such as “SG-042” can connect an image to a source note. Add a short readable phrase if helpful, but avoid placing an unverified conclusion in the name. “Storefront-undated” is safer than assigning a business and year that the evidence has not established.

Keep the repository’s own item identifier in the source note. Your private number helps your system; the repository number helps another person find the original. Record the title or description, collection, date as supplied and stable link when available.

For a page from a longer work, retain the publication details and page reference. A page image named after the person you were researching may hide the fact that it came from a directory or a newspaper. The source note should explain both the item and the reason you saved it.

Keep versions recognizable

Store an unaltered research copy separately from a crop, a contrast-adjusted reading copy or an image with your annotations. Label the working versions clearly. A reader should never have to guess whether a mark was present on the original or added during your investigation.

When a record has several pages, use a consistent page sequence and preserve any original numbering in the note. Do not let a file browser’s alphabetical order silently rearrange a letter. Check the sequence after renaming and before sharing the group.

If you receive a new copy of the same item, record its source and relationship to the earlier file. A higher-resolution scan may replace a working copy, but do not discard context or annotations without checking what they contain. Keep one clear route to the preferred research version.

Make the index easy to maintain

A simple table can hold the identifier, brief description, source reference and file location. Add a field for unresolved questions if you use it. Avoid creating dozens of empty columns that make each new item feel like an administrative project.

Test retrieval from both directions. Starting with the image, can you find the source note? Starting with the note, can you locate the exact page? If either route depends on remembering a folder you recently moved, adjust the system before the collection grows.

Keep personal or restricted information out of public filenames. A shared image may need a different access arrangement from your private working folder. Follow repository conditions and the permissions of people who contributed material before distributing it.

At the end of a research session, process the new files while their context is fresh. Save the citations, mark uncertainties and check that the items open. The system has done its job when a future question sends you back to evidence rather than into a long search for where a promising picture came from.