DSC_4187.jpg tells you almost nothing about the band, venue, photographer or right to publish the image. Move it away from the folder where those facts were recorded, and it may no longer serve as useful archive evidence. Give each set of concert photos a stable home, preserve the originals and write down what you know while the messages and memories are still available.
That care matters in a small scene. A photograph of a Finnish thrash band from the late 2000s or early 2010s may be one of the few surviving visual records of a particular lineup or local bill. But a tidy filename cannot make an uncertain date true. The picture, its context and the limits of that context need to stay together.
Start with an inventory, not a mass rename
Find out where the photos live: camera cards, phone exports, external drives, cloud folders, old computers and attachments from contributors. Make a short inventory of each source, noting whether it holds originals, edits or copies of uncertain origin. Do not empty a card or delete a folder just because the pictures seem to exist elsewhere. A smaller exported JPEG is no substitute for a camera RAW file.
Before reorganizing a large collection, copy it to a separate drive and check that a sample of the files opens. If you have room, keep the old directory structure untouched until you have checked the new one. Work on a second copy in manageable batches—one camera import or contributor delivery at a time. If something lands in the wrong place, you can retrace that batch rather than the whole archive.
Note where each batch came from. “Received from photographer by email, March 2024; files said to cover several shows” is more useful than assigning every image to an event you have not verified. Keep emails, notes and permission terms with the batch, but leave private contact details out of public exports.
Choose folders that answer one question
A folder tree should tell you where a file belongs, not try to hold every fact about it. In a music archive, confirmed show photos can be filed by event date and location. Keep portraits, release artwork and unidentified material separately. Personal photos unrelated to public scene history deserve their own top-level area, away from concert records.
For instance, a confirmed show could sit under Events/2012/2012-04-21_Helsinki_VenueName/, with Originals, Edits and Web folders inside. The date and venue here illustrate a naming pattern; they are not a historical claim. If the date is unverified, put the files in Unidentified or Dates-to-check rather than inventing a precise event name.
A band-by-band master folder creates problems when one photo could document a shared bill, a guest appearance or an unidentified performer. Keep the original in its event folder and use a catalog or sidecar note to identify the bands depicted. That way, one image does not need several master copies.
Use names that survive outside their folders
Folder context disappears when a file is emailed or placed in a publication layout. A name such as 2012-04-21_Helsinki_EventID_0042.jpg keeps a confirmed date, place and unique sequence attached to the image. The event ID can distinguish two shows in the same city on the same day. Avoid slashes and colons, which can cause trouble across operating systems, and use one date format: YYYY-MM-DD sorts chronologically.
Record the original camera names even if you rename working files. A simple manifest can map DSC_4187.NEF to its archival name, which helps when a photographer later refers to a camera file number. Do not rename an image to make a shaky identification look settled. For unidentified photos, a neutral batch ID and sequence number are safer than a guessed band name.
Keep facts, guesses and permissions distinct
A modest spreadsheet may do more for the archive than specialist photo software. Give each photograph—or each event set, where that makes sense—a stable ID. Start with fields you can maintain:
- File ID and path: a unique identifier and the current location of the original.
- Creator and source: who made the image, who supplied it and when it was received.
- Event details: date, venue, city and bill, with a way to flag unverified details.
- People and subjects: identified bands or musicians, plus the basis for each identification.
- Rights and credit: permission granted, permitted uses, required credit and restrictions.
- Version: original, edit, scan or web export.
Use labels such as confirmed, probable and unidentified, and note the evidence behind them. “Venue identified from stage banner” is different from “date supplied by photographer.” Camera timestamps help with sorting, but the clock may have been unset, crossed a time zone or reset after a battery failure. Check a timestamp against a flyer, ticket, set list or contemporaneous note before putting the date in a public caption.
Give permissions their own field: having a file does not grant publication rights. A photographer might allow a low-resolution archive page but not a printed sleeve, promotional poster or unrestricted download. Save the permission message and its scope rather than reducing it to “OK to use.” If permission is missing, keep the image in a private research collection while you check its publication status.
Use metadata without depending on one app
Embedded metadata can carry titles, descriptions, credits and keywords in supported image formats. Sidecar files can hold similar information beside files you do not want to rewrite. Neither method guarantees that every program will retain those fields on export. Keep a separate catalog or manifest, and test a few edits to see whether credits and captions survive your usual workflow.
Describe what the image shows without claiming more than you can support. “Guitarist onstage, band unconfirmed; venue sign visible” is better than naming the likeliest band as fact. Keep alternate spellings as search terms when useful, but choose one documented form for the displayed name. If a later correction changes an identification, update the catalog and published caption, and retain a note explaining why.
Find duplicates without throwing away originals
Repeated card imports, email attachments and site exports all produce duplicates. Matching filenames prove little: cameras reuse numbers, while identical copies may have different names. A tool that compares file hashes can find byte-for-byte matches. Visually similar edits still need a person to review them.
Group apparent duplicates, then compare their formats, dimensions, file sizes and embedded information. Keep the best-quality original and any edit that serves a distinct purpose. A cropped web JPEG, for example, may record the version previously published even when the uncropped RAW remains the preservation master. Delete redundant copies only after confirming what you have retained, updating the manifest and checking the backup. Avoid automatic deletion across an unsorted collection.
Look at near-identical stage shots at full size before deciding. A drummer’s position, a poster in the background or a musician at the edge of the frame may help identify a show later. Technical similarity does not make two photographs archivally redundant.
Build search routes that match real questions
Few people search an archive by folder path alone. Someone may recall a venue but not the year, a band but not its support acts, or an instrument but not the player. Consistent catalog fields let you search by city, venue, performer, photographer and level of certainty without duplicating files. Use consistent names for recurring venues and bands; keep former names and known spelling variants in searchable notes.
A numbered contact sheet makes a batch easier to review and ties each observation to a file ID. If a contributor recognizes a performer, record who made the identification, when they made it and whether other evidence supports it. A helpful recollection is not necessarily a verified credit. Keep private annotations and contact details out of public captions and exports, even if they share a spreadsheet.
For a small collection, folders and a spreadsheet may be enough. Photo-management software becomes useful when the volume of keywords, searches and edits grows beyond what a sheet handles comfortably. Whatever you use, test whether you can export its metadata in a readable form. The event history should not be trapped in one application's database.
Protect the collection against more than a failed drive
A backup is a separate, recoverable copy—not another folder on the same disk. Keep working files on one device, an updated copy on another and, when feasible, a further copy in a different physical location. Cloud storage can fill that last role, but synchronization can spread a mistaken deletion as readily as a good edit. Version history or a disconnected backup gives you a way back.
Periodically restore a small sample and check that it includes readable originals, catalogs and permission records. For a larger collection, checksums can reveal unexpected changes between copies. Note when each backup was made and which drives it covers. Drives and accounts can be replaced; undocumented identification work and consent records may be much harder to recover.
Restrict access to photographs that should not be public, including private gatherings and images with unresolved permission. If volunteers help catalog the collection, give them working copies or suitable account permissions rather than passing around the only master folder. Keep a brief change log for renamed events, corrected captions and moved originals so the next editor can follow what happened.
Make new imports routine
A repeatable intake process keeps the next contributor delivery from becoming another mystery directory. Copy incoming files to an Inbox folder, leave their supplied names intact at first and record the source. Check that the copies open and make a backup. Then assign the set to a confirmed event or an unidentified batch, and enter its basic catalog details and permission status before making publication edits. Rename working copies and move the batch to its permanent folder only after those checks.
Do not let a few uncertain photos stall the whole import. If 180 images clearly belong to one documented show but five seem to come from another night, catalog the 180 and put the five in a numbered review batch. Note the discrepancy. When a poster, contact sheet or photographer’s message turns up later, the batch ID and original camera numbers will lead you back to those five images.
