Name the retrieval problem
A useful filename begins with the way someone will need to find an image later. A project may need to locate every view of one basket, compare a repair sequence, or identify photographs from a workshop day. Before deciding on abbreviations, write down those retrieval questions and the people who will answer them. The Library of Congress's guidance on born-digital access discusses persistent identifiers and file organization as parts of managing digital material. Its photographic archive practices also show the value of systematic names at scale. A filename cannot preserve every detail about a maker, technique, place, and permission, but it can point reliably to the fuller record. Keep the scheme small enough to teach and consistent enough that different photographers can apply it.
Select stable fields and a readable order
A practical pattern might include project or object identifier, date, sequence number, and view abbreviation, separated by underscores: FN042_20260930_003_detail. Define each field in plain language and state which fields are required. Use a date order that sorts chronologically and numbers with leading zeros so that image 12 does not appear before image 2. Choose terms that can be understood by collaborators instead of private shorthand. Avoid spaces or punctuation that may behave differently across systems, and do not rely on folder order as the only sequence. The exact pattern depends on the project's scale; three stable fields are better than an elaborate string no one can maintain.
Keep names unique without making them stories
A filename should identify a file, not carry a full narrative. Short, controlled fields reduce transcription mistakes and preserve flexibility as context changes. If a photograph shows a maker's hands, a restricted pattern, or a sensitive material source, do not encode personal names, sacred terms, or precise locations in the filename unless permission and policy explicitly allow it. Such information may appear in previews, exports, or backups long after a folder's access restrictions are forgotten. Use a neutral identifier and store richer description in the access-controlled record. A naming plan should be designed with privacy and community authority in mind, not just search convenience.
Separate original captures from edited derivatives
Preserve the original camera file as received and give edited versions a separate, predictable relationship to it. Cropped, color-adjusted, annotated, resized, or publication images should never silently replace the original documentation file. A derivative can append a short suffix such as edit or web, but record what was changed and why in a metadata field or production log. Retain an explicit link between source and derivative identifiers. This practice makes it possible to discover whether a view was altered for publication and to return to the unedited capture if a new question arises. Follow the institution's preservation formats and storage policies for the file types involved; changing an extension does not convert a file or preserve its contents.
Test the scheme with a real sequence
Before using the pattern for hundreds of images, test it on a small set that includes an overall view, detail views, a process sequence, and one image that should remain restricted. Ask someone who did not design the system to locate all images of the object and put the process views in order. Check what happens when a photographer repeats a sequence number, changes the date, or transfers images between folders. Update the written rule based on observed confusion, not preference alone. A pilot can also reveal whether terms such as front, reverse, or stage mean the same thing to everyone. If terms vary regionally or culturally, record local vocabulary in the fuller metadata while using a neutral retrieval code for the filename.
Connect filenames to description and consent
A filename cannot carry all the information that makes a craft photograph responsible to use. Maintain a record that links identifiers to subject, date, photographer, context, description, rights, consent, and access conditions. Note whether a maker approved public attribution, prefers anonymity, or allowed documentation only for internal teaching. If permission changes, the image identifier can remain stable while its access status is updated in the record. Preserve the agreement or consent note according to project policy. UNESCO's guidance on community involvement in intangible cultural heritage inventorying underscores that documentation is connected to the people and communities concerned. A technical naming scheme should support those relationships, not bypass them.
Document changes to the naming rule
Projects evolve: a new partner may require another view field, an archive may adopt a persistent identifier, or a community may request that a public label change. Keep a versioned scheme document that explains what changed, when, and which earlier files are affected. Do not rename a large archive casually because a new convention looks cleaner. If renaming is necessary, preserve a mapping between old and new names and test links, catalogue records, and derivatives. A controlled change protects references already cited in reports or teaching materials. It also helps a future archivist understand why two naming patterns appear in the same collection.
Control access beyond the folder name
A folder called private is not a complete access policy. State who can view, copy, edit, publish, and remove files, and how those permissions are reviewed. Store sensitive images and records in systems that support appropriate access controls, backups, and retention decisions. A filename should not reveal hidden information simply because the file itself is in a protected folder. Ask participants what level of access they intend and explain that copies can travel when downloaded or emailed. Where the subject involves restricted knowledge, a public catalogue entry may use a non-sensitive description while the detailed record remains limited. The scheme must make room for no-publication decisions as well as open access.
Keep the system maintainable
A durable plan can fit on one page: the pattern, field definitions, examples, character rules, original-versus-derivative policy, and access review contacts. Store that instruction beside the project metadata and include it in staff onboarding. Check filenames for duplicates before ingest and preserve file checksums or other fixity information where the archive workflow provides it. The Library of Congress resources offer a broader context for maintaining digital images and access over time, but local repositories may have their own requirements. The right scheme is the one that survives handoff. Consistent identifiers help photographs remain connected to craft knowledge, while description, consent, and stewardship remain in records designed to carry those meanings.