Digital File Management

Digital file management is the organised creation, naming, storage, description, protection, retrieval, maintenance and transfer of electronic records associated with a collectible. It applies to photographs, scans, invoices, certificates, appraisals, correspondence, auction listings, research notes, condition records, videos, database exports and every other digital file used to support the object's identity, ownership, authenticity, condition, history or significance.

The central problem is not simply whether a file exists. Supporting documentation becomes weak when it cannot be found, opened, matched to the correct item, distinguished from an edited copy, traced to its source or understood without the original collector. A large folder of files is not yet a documentary archive.

The aim is proportionate control rather than archival perfection. A collector should be able to preserve important originals, explain what each record is, detect unexpected change, recover from ordinary failure and pass a coherent dossier to another person. A modest system used consistently is stronger than an elaborate system abandoned after its initial setup.

Collector scenario

The certificate you know you saved somewhere

A collector needs to provide an insurer with the invoice, certificate, appraisal and purchase photographs for a rare item. The invoice is in an old email account, the certificate survives only as a cropped phone image, two edited photographs have replaced their originals, and the appraisal filename does not identify which of three similar items it describes.

The evidence has not necessarily vanished, but its practical and evidential value has fallen because the relationships and source context were not managed. Digital file management exists to prevent this quiet disappearance.

1. Orientation

What the digital archive must preserve

Good management contributes several distinct qualities. They overlap, but they should not be treated as synonyms. A file may be available without being authentic, authentic without being usable, or readable without being linked to the correct object.

Availability

The record still exists, can be located and can be opened when it is needed. A file that is present but trapped in an obsolete account or unreadable format is not meaningfully available.

Identity

The file can be matched confidently to the correct collectible, component, transaction, condition event or research question rather than merely to a broad collection.

Integrity

There is a reasonable way to detect whether the file has been corrupted or unexpectedly altered after it entered the collector's archive.

Authenticity

The record retains enough source, custody and contextual information to support a judgement that it is what it claims to be. Good management supports this judgement but cannot guarantee the truth of the content.

Context

The creator, source, date, purpose, relationship to the object and relationship to other files remain understandable without relying on the collector's memory.

Continuity

The documentary archive can pass to a buyer, insurer, appraiser, institution, executor or family member without losing the links and explanations that give it meaning.

2. Judgement

A digital file is evidence, but not automatically reliable evidence

A PDF certificate may be genuine, altered, fabricated or copied from another item. A photograph may show an object but not establish when it was taken. A screenshot may reproduce a listing while omitting the URL, seller, date, lot number or later correction. A file-system creation date may record a copy operation rather than the document's true date.

Digital file management strengthens evidence by preserving source information, relationships, versions, metadata and an audit trail. Critical evaluation of the record itself remains necessary.

Evidence boundary

Good file management is evidence stewardship, not automatic proof

A well-managed file can show that a record came from an identifiable source, was linked to a particular item, existed by a documented point in time and has not changed since a recorded checksum was created. It can also preserve a clear history of conversions, redactions and transfers.

It cannot, by itself, prove that the source was honest, the collectible is authentic, the attribution is correct, the transaction was lawful or the issuer of a certificate was competent. Those conclusions belong to authentication, provenance, legal, grading and valuation enquiries as appropriate.

3. File roles

Preserve the original; work on derivatives

The most damaging routine mistake is destructive overwriting: cropping the only image, redacting the only invoice, converting the only signed PDF or allowing an application to replace a high-quality source with a compressed copy. Assign every significant file a role and preserve the relationship between versions.

Retain

Received or created original

The file in the form in which it was first received or created: the camera original, seller PDF, native email export, laboratory report, spreadsheet export or unedited video. Preserve it before renaming, editing or uploading elsewhere.

Protect

Preservation copy

A controlled copy retained primarily for long-term protection. It should not be casually edited and should have its source, date admitted to the archive and integrity information recorded.

Use

Working copy

A version used for cropping, rotation, annotation, colour correction, OCR, redaction, combination or conversion. Its relationship to the source file should be explicit.

Access copy

A convenient version for routine viewing, publication, sharing or upload: for example, a JPEG derived from a TIFF, a searchable PDF derived from scans or a redacted invoice.

Keep together

Sidecar and dependent files

Metadata, checksum manifests, captions, transcripts, attachments, XML or JSON exports, schemas, readme files and technical instructions may be essential to interpreting the principal file.

Changes that should create a new file

Cropping, annotation, automatic enhancement, AI upscaling, background removal, OCR, redaction, page combination, compression and format conversion may all change content, context or technical properties. Keep the source and create a clearly labelled derivative.

Record the parent file, version number, date, person or system responsible, software, transformation, reason, known loss and new checksum where the record is important.

4. Connection

Link every file to the correct collectible

Storage is only one half of the problem. The archive must preserve the relationship between the file and the object, component, transaction or event it documents.

Use a persistent item identifier

Give each collectible a stable internal identifier, such as COL-000184. The identifier should survive renaming, reclassification, relocation and transfer so that the object, database record, photographs and documents remain connected.

State the scope of the file

A file may concern the whole item, one component, packaging, a signature, a particular defect or a shared transaction. Record that scope rather than assuming the filename makes it obvious.

Support shared documents

One invoice, appraisal or auction lot may cover several objects. Link one authoritative file to several item records where possible rather than creating uncontrolled duplicates that later diverge.

Keep the relationship exportable

Database-led management is powerful, but the archive should still be intelligible outside the application. Preserve exports, identifiers and manifests so links do not disappear if the platform changes.

COL-000184 — Red Dragon Miniature — 1983 — Grenadier
COL-000184-C03 — rear box panel — water-damage detail

A descriptive title can change; a stable identifier should not. For multi-part items, use component identifiers or explicit scope notes so that evidence about packaging, inserts, accessories, signatures or localised damage is not mistaken for evidence about the whole object.

5. Structure

Choose a structure that remains understandable and portable

No single folder model is universally correct. Collection size, shared records, batch workflows and the strength of the catalogue all matter. The test is whether a collector can find the evidence now and export a coherent dossier later.

Item-centred folders

Each object has its own folder, with subfolders for acquisition, provenance, condition, images, authentication, valuation, correspondence and transfer records.

Intuitive for small and medium collections.
Easy to transfer one item's dossier.
Can duplicate shared invoices or research.
May become deep or repetitive at scale.

Record-type folders

Files are grouped centrally by type, such as invoices, photographs, correspondence or appraisals, and linked to items through identifiers or a catalogue.

Efficient for batch processing and common controls.
Useful where one record covers many items.
Depends heavily on reliable identifiers.
Harder to export one complete object dossier.

Database-led management

A collection system associates files with items, variants, acquisitions, owners, events, repairs, valuations and sources while folders provide underlying storage.

Best for complex relationships and search.
Can reduce duplication and expose context.
Requires regular independent exports.
Must not become the only way to understand the archive.

Collectibles/
  COL-000184/
    01_Identity/
    02_Acquisition/
    03_Provenance/
    04_Condition/
    05_Authentication/
    06_Valuation/
    07_Images/
      Originals/
      Derivatives/
    08_Correspondence/
    09_Research/
    10_Transfer/
    Metadata/

6. Naming

Treat filenames as visible metadata

A good filename is consistent, meaningful, sortable and stable. It should identify the item and the record without attempting to encode every fact. Retain the source filename in metadata when renaming matters to evidential continuity.

Useful pattern

[ItemID]_[Date]_[DocumentType]_[Source]_[Sequence]_[Version].[extension]

COL-000184_2025-04-17_PurchaseInvoice_SmithAuctions_01_original.pdf
COL-000184_2025-04-18_Photo_Front_01_original.tif
COL-000184_2025-04-18_Photo_Front_01_access-v02.jpg

Good practice

Use dates as YYYY-MM-DD where a date belongs in the filename.
Use leading zeros for sequences such as 01, 02 and 03.
Use hyphens or underscores consistently.
Keep names reasonably short and cross-platform compatible.
Document the naming convention where another person can find it.

Avoid

Vague names such as scan1, new, important or final-final2.
Unnecessary confidential information in filenames.
Unsupported characters or excessively long paths.
Renaming without retaining the previous name where continuity matters.
Using a filename as proof of the date, source or authenticity it asserts.

7. Description

Metadata keeps the archive intelligible

Metadata is information about the file, its management and its history. Some metadata is embedded inside the file; other metadata belongs in a catalogue, spreadsheet, sidecar or manifest. Important records often need both.

Descriptive metadata

What the record concerns and how a person should understand it.

Item identifier
Title and document type
Subject and description
People, organisations and keywords

Administrative metadata

How the record is controlled and who may use it.

Owner or responsible person
Access and confidentiality
Rights and permitted uses
Retention or disposal status

Technical metadata

The characteristics needed to manage and render the file.

Format and version
File size and dimensions
Codec, colour profile or software
Checksum and technical timestamps

Provenance metadata

The history of the digital record itself.

Creator or supplier
How and when it was received
Previous filename or location
Known transformations and custody history

Preservation metadata

The actions taken to keep the record usable and trustworthy.

Format identification
Fixity checks
Migration or repair events
Redactions, restrictions and preservation decisions

Embedded metadata

EXIF data, PDF properties, author fields, GPS, captions and document revision data can travel with a file and preserve useful capture information.

It can also be stripped, edited, mis-set by a device or expose private information. Do not rely on it as the only record of context.

External metadata

A catalogue, spreadsheet, XML or JSON export, sidecar or manifest can describe relationships across many files and preserve information a file format cannot hold.

It must use stable identifiers and remain physically or logically connected to the files it describes.

8. Interpretation

Understand what digital dates actually mean

A single record may have a content date, capture date, scan date, download date, file-system creation date, last-modified date, upload date, email sent date and archive ingest date. They describe different events.

Content or document date

The date represented by the record: for example, the date of an invoice, appraisal, message or inspection. It should not be inferred from the file system without corroboration.

Capture or creation date

The time a camera, scanner, application or device says the file was created. Device clocks can be wrong and copying may alter some timestamps.

Receipt and ingest dates

When the collector received the file and when it entered managed storage. These dates are often more defensible than an assumed original creation date.

Modification, upload and migration dates

These indicate later technical events, not necessarily changes to the underlying historical content. Record what each date means rather than collapsing them into one vague 'file date'.

Collector caution

Copying a file to a new computer can change a file-system creation date while leaving embedded camera metadata unchanged. Device clocks and time zones may also be wrong. State what a date represents and do not call a technical timestamp the document date without verification.

9. Long-term access

Choose formats carefully, then keep monitoring them

Broad adoption, documented specifications, multiple software implementations, metadata support and freedom from fragile platform dependencies all reduce risk. No format is guaranteed to remain usable forever, so identification, testing and migration remain part of preservation.

Still images

Retain camera originals where available. TIFF can be suitable for high-quality preservation masters, PNG for lossless graphics and screenshots, and JPEG for practical access images. Converting a poor JPEG to TIFF does not restore discarded detail.

Documents and data

PDF or PDF/A may be suitable for fixed-layout documents; plain text for simple notes; CSV for tabular exports; XML or JSON for structured data. Retain original office files where formulas, comments, layers or functionality matter.

Email and correspondence

Native message files or mailbox exports usually preserve more evidence than screenshots because they can retain headers, attachments and thread context. A PDF access copy may still be useful for reading and sharing.

Audio and video

Media files can depend on containers, codecs, subtitles, colour information and metadata. Retain originals, document transcoding and test that migrated copies preserve the intended content.

Databases and application exports

Preserve the data, field definitions, relationships, code lists, application version, attachments and a human-readable report. A raw database file without its schema or software may be unusable.

Identification, validation and rendering are different tests

Identification: What is the actual file format and version, regardless of its extension?
Validation: Does the file conform structurally to the rules of that format?
Characterisation: What technical properties, codecs, dimensions, profiles or embedded features does it contain?
Rendering test: Can the file actually be opened and interpreted correctly with available software?

10. Integrity

Use checksums to detect unexpected change

A checksum is a calculated value derived from a file's contents. A small change normally produces a different result. For ordinary modern collection management, SHA-256 is a practical choice for important originals and transfer packages.

Typical fixity process

Calculate a checksum when the file enters the managed archive.
Store it in a protected manifest or catalogue.
Recalculate it after transfer or during periodic checks.
Compare the result with the recorded value.
Investigate unexpected differences.
Restore from a verified copy where appropriate.
Record the event and outcome.

What a checksum does not prove

That the original statement was truthful.
Who created the file or whether it was acquired lawfully.
That it had never changed before the first checksum was created.
That it describes the correct physical object.
That all attachments and contextual records are present.

11. Capture

Digitise paper and photographs without discarding context

Digitisation improves access and creates a security copy, but it does not automatically replace a paper original. The physical document may preserve paper, ink, seals, embossing, watermarks, annotations, bindings and other features that a scan cannot fully reproduce.

Capture the complete document

Front, reverse, envelopes and attachments.
Stamps, seals, watermarks, embossing and handwritten notes.
Blank pages or page edges where their existence matters.
Staple, binding and page-order relationships.
Colour or scale references where interpretation depends on them.

Record the digitisation event

Date, operator and scanner or camera used.
Resolution, colour mode and output format.
Processing, cropping, rotation or enhancement applied.
Whether OCR was added and whether the scan is complete.
Where the physical original is stored.

OCR is an access aid, not a perfect transcription

Retain the page image and treat OCR text as a derivative or searchable layer. Check names, serial numbers, dates and monetary figures manually before relying on extracted text.

12. Online and correspondence records

Capture context before platforms change it

A bookmark, live marketplace listing or message thread is not a preserved record. Pages can change or disappear; messaging platforms may permit edits or deletions; account access can be lost.

For important web evidence

Record the URL, title, publisher, author or account.
Record publication and access dates.
Preserve a complete page capture, PDF, screenshot or lawful web archive.
Record lot number, seller identity, final price and corrections where relevant.
Keep structured source details as well as a visual capture.

For important correspondence

Preserve the full message, sender, recipient, date, time and subject.
Retain thread context, attachments and relevant headers.
Record the platform, account and export date.
State the message's relationship to the collectible and the claim it supports.
Export promptly where editing or deletion is possible.

13. Resilience

Build backups that survive ordinary failure

Hardware failure, accidental deletion, ransomware, account closure, subscription lapse, password loss, synchronisation errors, theft and obsolete media are normal digital risks. No single device, account or platform should be treated as permanent.

Primary working copy

The managed copy used for routine cataloguing and reference. It should be organised, access-controlled and not dependent on one temporary device.

Separate local backup

A second copy on different media or hardware. It should not remain permanently connected if ransomware, synchronisation errors or accidental deletion could affect it immediately.

Geographically separate copy

A cloud or off-site copy protects against fire, flood, theft and local hardware loss. Check export capability, version history, deleted-file retention and succession access.

Tested recovery

Restore samples, open files, compare checksums and confirm that metadata, passwords and encryption keys are available. An untested backup is only an assumed backup.

Backup is not the same as synchronisation

Synchronisation may reproduce accidental deletion, corruption, ransomware-encrypted files or unwanted edits across every connected device. A true backup provides recoverable historical versions or an independent copy that is not immediately changed by the same event.

14. Security and rights

Protect confidential information without destroying the evidence

Supporting records may expose addresses, seller details, payment information, signatures, insurance values, authentication methods and collection locations. Security controls should be proportionate to the sensitivity of the archive.

Reasonable controls

Strong unique passwords and multi-factor authentication.
Device encryption and encrypted backups where appropriate.
Restricted sharing and separate public and private copies.
Documented recovery keys and succession access.
Software updates, malware protection and secure disposal.

Redaction workflow

Retain the unredacted original securely where lawful.
Create a separate redacted access copy.
Record the date, reason and scope of redaction.
Label the derivative clearly.
Remove data from the underlying file, not only from visual display.

Possession is not publication permission

Holding a copy does not necessarily confer copyright, database rights or permission to publish it. Record the supplier, permitted uses, attribution, confidentiality, contractual restrictions and whether those permissions transfer with the object.

15. Audit trail

Record significant actions affecting important files

An audit trail does not need to capture every routine click. It should record actions that materially affect authenticity, integrity, interpretation, access or transfer.

Events worth recording

Creation, receipt, ingest, rename, copy, transfer, checksum calculation, fixity verification, metadata update, format identification, conversion, redaction, publication, restriction, deletion and restoration from backup.

Minimum event record

Event type, date and time, file identifier, responsible person or system, reason, outcome, related source or derivative and previous and new checksum where relevant.

16. Transfer

Prepare a documentary package that another person can verify

Files may need to move to a new device, collection system, appraiser, insurer, buyer, auction house, archive or executor. A controlled package preserves both the records and the information needed to understand and verify them.

COL-000184_TransferPackage/
  Files/
  Metadata/
  manifest.csv
  checksums-sha256.txt
  README.txt
  rights-and-restrictions.pdf

Manifest content

Item and file identifiers.
Filename, description and document type.
File size, format and checksum.
Document or creation date and source.
Original or derivative status.
Rights, restrictions and confidentiality.

Verify after copying

Compare file counts and total size.
Verify checksums.
Open representative files.
Confirm folders, metadata and manifests transferred.
Record the transfer and authoritative copy.

17. Migration

Convert formats without silently losing meaning

Migration may be necessary when old software, codecs, media or proprietary platforms become risky. The objective is to preserve meaningful information and necessary functionality, not merely to produce a file with a newer extension.

Possible migration losses

Formatting, fonts, formulas, comments, hidden cells, macros, layers, colour profiles, embedded files, hyperlinks, digital signatures, metadata, interactive features and revision history may all be altered or lost.

Controlled migration

Retain the source file.
Record software, settings and reason.
Test the converted file.
Document known losses or differences.
Create a new checksum.
Link the migrated version to its source.

Digitally signed files need special care

Printing and rescanning a signed PDF may preserve its visible appearance while destroying the machine-verifiable signature. Preserve the signed original, validation result, certificate details, timestamp data and date of validation. A valid signature supports signer identity and integrity; it does not prove every statement in the document.

18. Recognition

Warning signs of weak or manipulated digital evidence

Digital anomalies are prompts for investigation. Their significance depends on the material, source, normal workflow and available corroboration.

Investigate

The original file is missing

Only a screenshot, social-media image, printout or recompressed copy survives where a native file would normally exist.

Investigate

Dates or metadata conflict

Timestamps, embedded metadata, editing software, format version or stated source do not fit the claimed history. This may have an innocent explanation, but it requires clarification.

Investigate

Versions differ without explanation

Certificates, photographs or correspondence exist in several forms with changed wording, missing pages, broken signatures or unexplained crops.

Investigate

Context has been deliberately narrowed

Screenshots omit the account, URL, lot number, attachments, thread or surrounding text needed to evaluate the claim.

Investigate

The record appeared only after challenge

Documentation was created or surfaced only after authenticity, ownership or condition was disputed, with no earlier custody or archive record.

Do not overstate

A warning sign is not proof of fraud

Poor practice, device changes, copying, privacy redaction and software migration can all produce anomalies. Treat them as prompts for further evidence, not automatic conclusions.

19. Action

A practical collector workflow

The most reliable archive is built through repeated small actions at natural points in the object's life rather than through occasional large reorganisations.

At acquisition

Capture evidence while listings, messages and transaction records are still available and before any original files are changed.

Assign the collectible a stable identifier.
Save the original listing, catalogue page, invoice and purchase confirmation.
Export important correspondence with attachments and context.
Photograph the item on receipt and record the purpose and date of the images.
Preserve original files before editing, renaming or uploading them elsewhere.
Record source, date received and relationship to the item.
Create integrity information for significant originals and back everything up.

During ownership

Keep the archive aligned with the changing object. New damage, restoration, valuations, research and transfers should extend the record rather than overwrite earlier evidence.

Add condition, repair, conservation and restoration records as events occur.
Keep originals, derivatives, redacted copies and migrated versions distinct.
Check that important files still open and that unusual formats remain supported.
Run periodic integrity checks and review unexpected changes.
Test recovery from backup and review privacy and access controls.
Export collection data, metadata and file relationships periodically.

At sale, donation or succession

Transfer the documentary value of the object without unnecessarily transferring private or restricted information.

Identify which records may and should accompany the object.
Separate private originals from buyer-facing or public access copies.
Create redacted derivatives rather than overwriting unredacted originals.
Export files, metadata and relationships into a comprehensible package.
Provide a manifest, checksums and a short readme describing the package.
Record what was transferred, when, to whom and under what rights or restrictions.
Retain any records required for tax, insurance, legal or provenance purposes.

20. Documentation standard

Recommended minimum metadata for significant files

Not every casual image requires a full archival description. Apply these fields to the files whose loss, ambiguity or alteration would materially weaken the collection record.

Field	Why it matters
File identifier	Uniquely identifies the digital record.
Item identifier	Links the record to the collectible or component.
Original and current filename	Preserves source context and supports present management.
Document type and title	States what the record is and what it concerns.
Source, creator or issuer	Records where it came from and who was responsible.
Document, receipt and archive dates	Separates the date represented from later custody events.
Format, version and file size	Supports identification, validation and transfer checking.
Checksum	Supports fixity checking and duplicate comparison.
Original or derivative status	Clarifies evidential role and version relationship.
Rights and access status	Records permitted uses, restrictions and confidentiality.
Related files or physical original	Keeps attachments, versions and paper sources connected.
Notes and uncertainty	Records qualifications, anomalies and unresolved questions.

21. Proportionate improvement

Build capability in stages

A collector does not need an institutional preservation system on day one. Progress from basic protection to description, monitoring and controlled transfer as the value, complexity and risk of the archive justify it.

Level 1

Protect

Establish stable item identifiers, meaningful filenames, basic folders, more than one copy and a rule that originals are retained.

Level 2

Know

Maintain a file inventory, record source and date metadata, distinguish originals from derivatives and classify privacy or access restrictions.

Level 3

Monitor

Use checksums, periodic fixity checks, tested backups, format-risk review and a basic audit trail for significant preservation actions.

Level 4

Preserve and transfer

Manage controlled migration, document restoration or repair, preserve exportable metadata and prepare clear succession or transfer arrangements.

22. Specialist threshold

When ordinary collector practice is no longer enough

Seek specialist digital-preservation, forensic, legal, privacy or information-security advice when the evidence is disputed, technically complex, encrypted without recovery arrangements, dependent on obsolete systems, required for litigation or insurance, or likely to contain sensitive personal data at scale.

Escalate for technical preservation when

Files depend on obsolete hardware, software, licences or network services.
Corruption, failed media or lost encryption keys threaten the only surviving copy.
Born-digital collectibles require emulation, disk imaging or environment capture.
Migration must preserve signatures, formulas, layers, databases or complex media.

Escalate for evidential or legal review when

Authenticity or chain of custody is contested.
Metadata anomalies may be legally significant.
Publication, privacy, confidentiality or data-protection rights are unclear.
A transfer package must meet institutional, court, insurer or auction requirements.

23. Final review

Collector checklist

Use this checklist for each significant record or as a periodic review of the whole documentary archive.

What collectible, component, transaction or event does this record concern?
Is the link to the item explicit and based on a stable identifier?
Is this the original file, a preservation copy, a working copy or an access derivative?
Who created or supplied it, and how was it received?
What does each recorded date actually represent?
Has the file been edited, converted, redacted or enhanced, and are those actions documented?
Are attachments, sidecar files and related versions present?
Can the file still be identified, opened and interpreted correctly?
Is useful embedded and external metadata preserved?
Has integrity information been recorded for significant originals?
Is there more than one independent copy, and has recovery been tested?
Does the record contain confidential, personal or security-sensitive information?
Are rights, publication restrictions and permitted uses known?
Could another person understand the archive without relying on my memory?
Could the complete documentation be exported and transferred with the object?
What would be lost if the current device, account or collection platform disappeared?

Key takeaways

The objective is not to accumulate files but to preserve a trustworthy, intelligible and transferable record around each collectible.
Digital file management strengthens evidence by preserving source, context, relationships, versions and integrity history; it does not prove that the underlying claim is true.
A stable item identifier is the most important link between the physical object and its documentary archive.
Preserve originals and create derivatives for editing, sharing, OCR, migration and redaction rather than destructively overwriting source files.
Backups must be independent enough to survive ordinary failure and should be tested by restoring real files.
The strongest archive can be understood and transferred by someone other than its creator.

Continue learning

Published & Online References

Return to preserving and evaluating books, catalogues, websites, archives and online research used to support collector claims.

→

Back to Supporting Documentation

Return to the Supporting Documentation section and its complete group of collector evidence topics.

→

Documentation

Return to the Documentation domain overview after completing the Supporting Documentation sequence.

→