Folder Structures
A folder structure is the visible framework that keeps photographs connected to the collectible objects, capture events and evidential purposes they document. For a serious collector, the aim is not simply to make a picture library look tidy. It is to preserve a visual record of identity, condition, completeness, provenance, restoration, ownership and change over time.
The strongest structure is usually anchored to the individual owned object. Dates, categories and projects remain useful, but they are secondary routes. A physical copy may be photographed repeatedly over decades, reidentified, restored, valued, displayed and eventually sold. Its photographs should still form one coherent and understandable dossier.
The governing question
Not “Where should I put this photograph?” but “What relationship does this image have to the object, the capture event and the collection record?”
Once that relationship is clear, the permanent home of the file, its filename, metadata and catalogue links can reinforce one another instead of competing.
What the structure must preserve
Identification
Every image must lead back to a particular owned copy, component, group view or documented event.
Separation
Original captures, masters, working files, derivatives, exports and external references must not become an undifferentiated mass.
Sequence
The archive should retain meaningful order: whole before detail, front before back, and before-treatment before after-treatment.
Retrieval
A collector should be able to find photographs by object, purpose, condition issue, acquisition, restoration episode or project.
Resilience
The archive must remain understandable when software changes, files are copied, a database export is incomplete or an heir receives the collection.
Recoverability
Backups and manifests must preserve the relationships among files, sidecars, metadata and the folder hierarchy itself.
The primary anchor: owned-copy identity
General photography often begins with date folders. That suits travel, weddings or editorial assignments because the event is the subject. In collecting, the object is usually the continuing subject. A date-only archive scatters one collectible across every occasion on which it was photographed.
Category-only structures are also unstable. One object may simultaneously be a Dungeons & Dragons item, a Ravenloft title, a module, a first printing, a signed copy and a graded object. A folder can occupy only one physical path without duplication, while a catalogue can express all of those relationships at once.
Durable item-centred principle
Collectible_Image_Archive/
01_Owned_Items/
OWN-000271_ravenloft-i6/
OWN-000843_ravenloft-i6/
OWN-001115_ravenloft-i6/Product identity is not owned-copy identity
Three copies of the same printing may share one catalogue product and variant, yet each has its own condition, marks, provenance, acquisition history and value. Their photographs therefore belong under three owned-item identifiers.
Neutral product-level reference photography can exist separately, but it must not be confused with evidence about a particular physical copy.
A practical top-level archive
The following areas establish controlled boundaries before the archive reaches the detail of individual item folders. Number prefixes keep the sequence predictable and leave room for deliberate separation between ordinary, exceptional and administrative material.
Inbox
A temporary landing area for camera cards, phone imports, scans, seller photographs and unidentified files. Nothing should remain here indefinitely.
Owned items
The main object-centred archive. Each folder represents one specific physical copy, not merely a product or variant in the catalogue.
Group and collection views
Shelf views, complete runs, displays, storage overviews and other photographs in which several objects are genuine co-subjects.
Reference images
Auction, seller, publisher and comparison imagery that does not prove ownership and must remain clearly separated from owned-copy evidence.
Projects
Purpose-specific working areas for insurance renewals, exhibitions, sale preparation, restoration case studies or website publishing.
Exports
Reproducible outputs for marketplaces, insurers, social media, websites or print. These are not the authoritative masters.
Registers and manifests
README files, item and image registers, checksum manifests, naming rules and migration logs that explain and audit the archive.
Quarantine
Corrupt, unidentified, duplicate, rights-uncertain or otherwise untrusted files retained for review without entering the controlled archive.
Archive administration
Metadata templates, controlled vocabularies, software exports, colour profiles, scripts and disaster-recovery instructions.
Recommended top-level model
Collectible_Image_Archive/
├── 00_Inbox/
├── 01_Owned_Items/
├── 02_Group_and_Collection_Views/
├── 03_Reference_Images/
├── 04_Projects/
├── 05_Exports/
├── 06_Registers_and_Manifests/
├── 90_Quarantine/
└── 99_Archive_Administration/The item dossier: choosing the right depth
No single internal model suits every collection. The correct depth depends on image volume, the evidential importance of the objects and whether the collector is managing RAW captures, repeated condition reviews or treatment documentation.
Simple item structure
Best for: Ordinary collections with relatively few photographs per object.
Strengths
- Easy to understand and maintain
- Clear distinction between originals, edits and exports
- Low filing overhead
Weaknesses
- Different documentary purposes become mixed
- Can become cluttered for heavily researched objects
Subject-based dossier
Best for: Objects documented for identity, condition, completeness and provenance.
Strengths
- Matches the questions collectors naturally ask
- Easy to browse for insurance or authentication evidence
Weaknesses
- Originals and edited files can become mixed
- One image may legitimately serve several subjects
Lifecycle-first structure
Best for: RAW-based workflows and collections requiring strong preservation control.
Strengths
- Separates source files, masters, working files and outputs
- Supports backup, integrity checking and migration
Weaknesses
- Less intuitive when looking for a particular defect or mark
- Relies more heavily on filenames and metadata
Event-based structure
Best for: Condition monitoring, acquisition records and restoration histories.
Strengths
- Preserves chronology and documentary context
- Makes change over time visible
Weaknesses
- Similar views become distributed across sessions
- The user must know roughly when an image was made
Recommended for serious collections: the hybrid dossier
A hybrid separates the capture event, trusted masters, editable work and generated outputs, while allowing the master area to follow collector-facing documentary purposes such as identity, condition, contents and provenance.
OWN-000271_ravenloft-i6/
├── 00_Record/
├── 01_Original_Captures/
│ ├── 2026-07-14_acquisition/
│ └── 2027-07-15_condition-review/
├── 02_Masters/
│ ├── identity/
│ ├── identification/
│ ├── condition/
│ ├── contents/
│ ├── provenance/
│ ├── authentication/
│ └── restoration/
├── 03_Working_Files/
├── 04_Derivatives/
│ ├── large/
│ ├── web/
│ └── thumbnails/
└── 05_Exports/
├── insurance/
├── marketplace/
└── social/Originals, masters, working files and outputs
Original capture
The file created by the camera or scanner. Preserve it unchanged after ingest: do not destructively crop, resave, strip metadata or silently overwrite it.
Preservation master
The trusted, high-quality file retained for long-term use. It may be a RAW file, rendered TIFF, archival scan or high-quality JPEG where no better source exists.
Working file
An editable layered or intermediate file used for retouching, stitching, focus stacking, colour correction or other reversible production work.
Access derivative
A convenient viewing copy such as a web image, application preview, mobile-sized JPEG or thumbnail generated from the master.
Destination export
A derivative made for a defined recipient or platform - insurer, auction house, marketplace, print catalogue or social-media service.
External reference
An image not created as evidence of the owned copy. It needs creator, source, retrieval date, rights status and clear separation from owner photography.
Do not organise by file extension alone
A folder tree called JPEG, TIFF and RAW expresses technical format but not documentary role. A JPEG might be the only original, a carefully edited master, a tiny thumbnail or a seller download. The archive must say what the file is for, not merely how it is encoded.
Filename and folder-name relationship
The folder supplies context, but the filename should remain meaningful when the file is separated from that context. This is especially important when images are emailed, exported, copied into a project, restored from an incomplete backup or downloaded from a service that flattens folder paths.
Collector-oriented filename pattern
[item-id]_[date]_[purpose]_[view]_[sequence]_[status].[extension]
OWN-000271_20260714_identity_front_001_master.tif
OWN-000271_20260714_condition_spine_002_master.tif
OWN-000271_20260714_identity_front_001_web-1600.jpgEvidence
Can the image still be identified outside its folder?
A durable archive does not rely on inherited path alone. The owned-item identifier should also appear in the filename and catalogue record so that a copied, emailed or exported file remains intelligible.
Meaning
Does the path express archival role rather than format?
A JPEG may be a camera original, a master, a thumbnail or a marketplace export. Organise by role - originals, masters, working files, derivatives and exports - rather than by extension alone.
Collector risk
Could a downloaded image be mistaken for ownership proof?
Reference and seller imagery must have an explicit archival home, source label and rights record. Mixing it with owner-created photographs can distort provenance, condition history and sale disclosure.
From capture card to controlled archive
The inbox is not a permanent category. It is a controlled transition zone. A defined ingest sequence prevents unidentified imports from being mixed immediately with trusted masters and makes it less likely that the only copy is deleted with the camera card.
Ingest
Copy files from the capture device into a dated temporary intake area without altering the source files.
Protect
Create a second copy before formatting the card or deleting the phone import. Capture checksums where the collection warrants them.
Review and identify
Reject obvious failures, mark uncertain files, establish the owned-item identity and separate external-source imagery.
Name and describe
Apply globally unique filenames, capture dates, documentary-purpose terms, captions and rights or source information.
Place
Move files into the permanent item dossier, preserving original captures while creating masters or derivatives as required.
Verify
Confirm file counts, sidecars, catalogue links and backups before clearing the inbox or retiring the capture media.
Documentary-purpose folders
Within the trusted master area, collector-specific purposes are more useful than broad technical labels. They answer why the photograph belongs in the dossier and what judgement it supports.
Identity
Whole-object views: front, back, sides, spine, top, base, open view or three-quarter view.
Identification
Product codes, copyright pages, logos, serial numbers, hallmarks, signatures, labels and manufacturing details.
Condition
Wear, stains, tears, corrosion, cracks, fading, repairs, mould, losses and missing components.
Contents
Completeness evidence for boxed sets, kits, games and multipart objects, including component groups and inserts.
Provenance
Physical ownership inscriptions, dealer labels, collection stickers, auction tags and other evidence attached to the object.
Authentication
Comparison details, security marks, print patterns, construction evidence and suspected counterfeit indicators.
Restoration
Dated before, during and after sequences for each treatment episode, with the intervention kept distinct from ordinary condition views.
Storage and display
Shelving, supports, enclosures, packing, mounts, frames and exhibition installations that document care and exposure context.
One image may support several judgements
A close-up of a signature may document identification, authentication, condition and provenance simultaneously. Do not create several uncontrolled master copies simply to occupy several folders.
Give the master one principal archival home, then use metadata keywords, catalogue relationships or virtual collections to express the additional meanings.
Complex objects and repeated events
Boxed sets and components
Keep the complete set as the primary dossier. Create component identifiers only where the catalogue genuinely manages those parts independently or where replacement and component-level condition require it.
Pairs and grouped objects
Retain the group identity while allowing component-A and component-B views where comparison, matching or individual condition matters.
Slabbed or encapsulated objects
Document the object, holder and grading label separately so that damage to the case is not mistaken for damage to the enclosed collectible.
Condition through time
Use dated condition events and repeat the same view sequence. Do not overwrite last year's image; even an unchanged later view proves that an inspection occurred.
Acquisition evidence
Separate seller images, arrival packaging, unboxing, initial condition and included documents. This preserves what was represented and what was actually received.
Sale and disposal
Create purpose-specific sale exports but retain an appropriate historical dossier. Change ownership status in the catalogue rather than treating the archive as disposable.
Folder tree versus catalogue or DAM
Folder tree
- Physical placement of files
- Separation of lifecycle stages
- Backup and migration scope
- Offline browsing and disaster recovery
- Basic human comprehension without specialist software
Catalogue or digital asset manager
- Multiple categories and relationships
- Search, keywords, captions and rights
- Variant, provenance and condition histories
- One photograph linked to several records
- Dynamic filtering without moving master files
The folder tree should be conservative and stable. The catalogue can be expressive, revisable and richly connected. Do not recreate the entire collection taxonomy in the filesystem, and do not use folder position as the only record of important states such as primary image, approval, publication, authentication, insurance or sale.
Boundary with collection software
Production storage and preservation export do not need identical paths
An application may securely store files under UUID-based object keys such as user/{user_id}/owned_item/{owned_item_id}/photo/{photo_id}/original.jpg. That is technically sound when the database records the human meaning.
The long-term safeguard is the ability to export a complete human-readable package containing item identifiers, original filenames, metadata, image relationships and manifests.
Myths and recurring failures
Myth or weak practice
Everything in one folder
Reality
Browsing deteriorates, names collide and there is no reliable boundary between source files, working files and outputs.
Myth or weak practice
Camera dates as the permanent archive
Reality
Capture chronology is retained, but the visual history of one collectible becomes scattered across years of unrelated sessions.
Myth or weak practice
Catalogue taxonomy recreated as folders
Reality
A reidentified printing, corrected title or changed category can force a disruptive move through a deep and fragile tree.
Myth or weak practice
Cloud sync treated as backup
Reality
Deletion, ransomware, conflict files and account failure may propagate through every synchronised copy. A tested, isolated backup is still required.
Myth or weak practice
The application's library is the archive
Reality
Albums, ratings and relationships may disappear when software is replaced unless there are documented, human-readable exports.
Myth or weak practice
The neatest structure is the best structure
Reality
An elaborate hierarchy that is not consistently maintained is weaker than a modest structure with stable identifiers, clear roles and reliable retrieval.
Migration is the real test
A structure that works only on the current computer or inside the current application is not yet proven. Before moving an archive, inventory the files, generate or preserve checksums, export catalogue metadata and sidecars, document software dependencies, copy rather than move, and verify counts before retiring the old environment.
Migration hazards to inspect deliberately
Documentation checklist
A concise README and archive register turn a private habit into a transferable system. They are particularly important when another person may one day need to restore, inherit, audit or migrate the collection.
When specialist or preservation advice is warranted
Most collectors can design and maintain a sound folder structure themselves. Specialist help becomes proportionate when the archive is very large, contains unique research imagery, depends heavily on proprietary software, includes legal or rights-sensitive material, or must support institutional transfer.
- The collection contains hundreds of thousands of files or complex component relationships.
- Migration must preserve checksums, sidecars, embedded metadata and catalogue links at scale.
- Scientific, conservation or treatment imagery requires formal chain-of-custody or audit controls.
- The archive is being prepared for donation, estate administration or transfer to an institution.
- No complete software-independent export has ever been tested.
A lighter model that collectors will actually maintain
Complexity is not a virtue by itself. A collector with a modest image volume may need only an inbox, one folder per owned object, clear separation between originals, masters and exports, plus distinct group and reference areas.
Practical small-collection model
Collection_Photos/
├── Inbox/
├── Owned_Items/
│ ├── OWN-000271_ravenloft/
│ │ ├── originals/
│ │ ├── masters/
│ │ └── exports/
│ └── OWN-000272_dragonlance/
│ ├── originals/
│ ├── masters/
│ └── exports/
├── Group_Photos/
└── Reference_Images/The decisive standard is not visual elegance. It is whether the archive can retrieve the right evidence, distinguish trusted files from generated or external material, survive migration and be understood by someone other than its creator.
Key takeaways
- Organise primarily around the identity of the physical owned object, not only the date or catalogue category.
- Use folders for stable identity and file lifecycle; use metadata and catalogue records for changing classifications and multiple relationships.
- Keep originals, preservation masters, working files, derivatives and destination-specific exports conceptually distinct.
- Separate owned-copy evidence from seller, auction and other reference imagery.
- Use globally unique filenames because files inevitably become detached from their original path.
- The best structure is the simplest one that preserves identity, meaning, provenance and recoverability in actual daily use.
Continue learning
Backup and Redundancy
Build a storage strategy that protects the archive from deletion, corruption, device failure and account loss.
Back to Digital Image Management
Return to the complete image-management chapter and its full sequence of topics.
Metadata and Captions
Add the descriptive, administrative and rights information that folders cannot carry on their own.
Related topics
File Naming Conventions
Design names that preserve item identity, sequence and documentary context when files leave their folders.
Originals, Edits and Derivatives
Distinguish source captures, preservation masters, editable working files and generated outputs.
Linking Images to Catalogue Records
Connect the filesystem or object store to the owned-item, component and documentary-event records it supports.
Long-Term Digital Preservation
Extend good organisation into integrity checking, migration, software independence and succession planning.