Week 33: Building Your Research Archive: Documentation Standards for the Serious Collector

Cross-Reference: Week 1 (Manifesto), Week 2 (Project Rosetta)

In Week 1, we established this mandate: "We treat the systematic study of footwear authentication, preservation, and documentation as a legitimate field of inquiry." In Week 2, we introduced Project Rosetta—the collaborative effort to build reference documentation that survives individual collectors.

Today we address implementation. How do you actually build a research archive? What standards should your documentation meet? How does personal collection documentation interface with collective knowledge-building?

The methodology matters as much as the data. Documentation without standards is noise. Documentation with rigorous standards becomes research infrastructure.

Photography Protocols: The Scanner Aesthetic

Project Rosetta established the visual language of serious documentation: clean backgrounds, consistent lighting, systematic angles, measurement references. We call this the Scanner Aesthetic—imagery that prioritizes information transfer over visual appeal.

Background Requirements:

Neutral gray (18% gray card standard) provides optimal color accuracy and eliminates reflection contamination. White backgrounds blow out highlight detail; black backgrounds obscure shadow information. Gray backgrounds reveal.

For practical implementation: seamless paper rolls in neutral gray (Savage #60 Focus Gray or equivalent) provide affordable, replaceable surfaces. Avoid textured backgrounds—they create visual noise that complicates detail extraction.

Lighting Protocol:

Two-light setup minimum, positioned at 45-degree angles to eliminate harsh shadows while maintaining dimensional information. Avoid direct overhead lighting, which flattens dimensional detail and creates specular highlights on glossy materials.

Color temperature: 5500K daylight balanced. Consistent color temperature across all documentation enables accurate colorway comparison. Mixed lighting sources introduce color contamination that compromises reference value.

Standard Angles:

Every documented specimen should include: 1. Lateral view (outside profile) 2. Medial view (inside profile) 3. Top-down view 4. Heel view 5. Toe box view 6. Outsole view 7. Interior view (insole removed) 8. Detail shots of authentication points

Angle consistency across specimens enables comparative analysis. If your Jordan 1 lateral shots are taken from different perspectives, you cannot overlay them for deviation analysis.

Scale Reference Integration:

Every photograph should include a millimeter-marked reference scale within frame. This serves two purposes: it provides measurement verification, and it proves the image hasn't been digitally manipulated.

Position the scale consistently—bottom edge of frame, parallel to subject's base. This standardization enables automated measurement extraction as image analysis tools develop.

Overlay Documentation:

For authentication-critical features, create annotated versions with measurement overlays. Document dimensions directly on images with clear callouts. These overlays transform photographs from documentation into reference tools.

Database Structure for Personal Collections

Your archive requires systematic organization. Random folders of images provide no research value.

Recommended Hierarchy:

/Archive
  /[Brand]
    /[Model Line]
      /[Specific Colorway-Size-Date Code]
        /Photographs
        /Documentation
        /Authentication
        /Provenance

File Naming Convention:

[Brand]_[Model]_[Colorway]_[Size]_[DateCode]_[ViewType]_[Sequence].[ext]

Example: Nike_AJ1_ChicagoRed_US10_20220315_Lateral_001.jpg

This naming convention enables sorting, searching, and automated processing. When you have 500 documented specimens, the convention that seemed excessive becomes essential.

Database Fields:

Beyond file organization, maintain structured data for each specimen:

• Identification: Brand, model, colorway, size, style code, production date code
• Acquisition: Date acquired, source, acquisition cost, acquisition method
• Valuation: Current estimated value, valuation date, valuation methodology, comparable sales references
• Condition: Current grade, condition notes, flaw documentation
• Authentication: Status (verified/unverified/suspected counterfeit), methodology applied, confidence level, authenticator
• Storage: Physical location, storage method, last condition check
• Documentation: Date documented, documentation completeness, photograph count

Spreadsheet implementation (Excel, Google Sheets) works for collections under 200 specimens. Beyond that scale, consider database solutions (Airtable, Notion databases) that provide relational capability and better search functionality.

Contributing to Project Rosetta

Personal archives serve individual needs. Project Rosetta serves collective advancement. The transition from personal to collective documentation requires additional rigor.

Contribution Requirements:

1. Complete Documentation Sets Partial documentation has limited reference value. Rosetta contributions should include all standard angles plus authentication-point details. Incomplete sets may be rejected.

2. Methodology Transparency Document how photographs were captured—lighting setup, camera specifications, any post-processing applied. This enables future contributors to match standards and allows researchers to assess documentation reliability.

3. Authentication Verification Contributed specimens should carry authentication confidence supported by methodology documentation. Explain why you believe the specimen is legitimate. Unverified specimens may be accepted for Morgue documentation (see below) but not reference status.

4. Provenance Statement Where did this specimen originate? Direct retail? Secondary market? Inherited collection? Provenance affects authentication confidence and provides context for future researchers.

5. Permission Grant Contributions must include explicit permission for collective use. Your documentation becomes community property—credited to you, but available to all researchers.

Submission Protocol:

Contact Project Rosetta coordinators before contributing. Volume contributions require coordination to maintain organizational standards. Random submissions overwhelm curation capacity.

The Value of Failure Documentation: The Morgue

We introduced The Morgue concept in Week 2: the systematic documentation of failed authentication, confirmed counterfeits, and research dead-ends. This documentation carries research value that rivals—perhaps exceeds—successful authentication records.

Why Failure Documentation Matters:

Every confirmed counterfeit reveals counterfeiter methodology. Every failed authentication exposes detection vulnerabilities. Every research dead-end prevents future researchers from repeating wasted effort.

Legitimate specimens show what should exist. Counterfeits show what does exist in the marketplace. Understanding the counterfeit landscape requires studying counterfeits.

Morgue Documentation Standards:

Counterfeit documentation follows the same photography and data protocols as legitimate specimen documentation, with additional requirements:

• Detection Narrative: How was the counterfeit identified? What specific features triggered suspicion? What methodology confirmed the determination?
• Comparison Documentation: Side-by-side photography with legitimate reference specimens highlighting deviation points
• Counterfeiter Signature Analysis: What patterns emerge? Can this fake be connected to known production sources?
• Marketplace Context: Where was this fake encountered? What listing characteristics accompanied it? This context enables platform-pattern recognition.

The Psychological Barrier:

Collectors resist documenting their authentication failures. The fake pair you bought represents embarrassment, financial loss, personal failure. Documentation forces confrontation with that failure.

Overcome this resistance. Your failure protects future collectors. Your embarrassment has research value. The collector who documents a fake they purchased contributes more than the collector who quietly discards it.

Long-Term Data Preservation

Digital documentation faces preservation challenges that physical specimens don't. Hard drives fail. Cloud services discontinue. File formats become obsolete. The documentation you create today may be unreadable in twenty years without preservation planning.

The 3-2-1 Backup Protocol:

• 3 copies of all data
• 2 different storage media types
• 1 copy off-site

For research archives, this means: local hard drive, cloud backup (multiple providers for redundancy), and periodic physical archive (external drive stored separately).

Format Considerations:

Use open, standardized formats that don't require proprietary software: - Images: TIFF for archival quality, JPEG for distribution - Data: CSV for tabular data (in addition to any application-specific formats) - Documents: PDF/A for long-term preservation

Avoid proprietary formats as sole storage. Your Notion database should export to CSV. Your specialized cataloging software should support standard export formats.

Metadata Embedding:

Embed critical metadata directly in image files using IPTC/EXIF fields. If your organizational structure is ever lost, embedded metadata provides recovery pathway.

Succession Planning:

Cross-reference: Week 31 (The Inheritance Protocol) addressed estate planning for physical collections. The same principles apply to research archives. Document access credentials, identify succession custodians, establish transfer protocols.

Your research has value beyond your lifetime. Plan accordingly.

The Archive as Living Document

Documentation standards evolve. New authentication points emerge. Better methodologies develop. Your archive must accommodate this evolution.

Version Control:

When you update documentation—improved photographs, corrected data, refined authentication analysis—maintain version history. Don't overwrite; create new versions. The evolution of your documentation has research value.

Regular Review Cycles:

Schedule periodic archive reviews. Annual at minimum. Assess: - Documentation completeness gaps - Outdated methodologies requiring update - New specimens requiring documentation - Valuation updates needed - Authentication confidence changes based on new information

Integration with Community Evolution:

As Project Rosetta standards develop, retrofit your archive where practical. Your early documentation may not meet evolved standards—update priority specimens while acknowledging that complete retrofit may be impractical.

The Documentation Imperative

In Week 1, we asked: "What if we documented everything?" Thirty-three weeks later, we've established the framework for answering that question. The protocols exist. The standards are defined. The collective infrastructure develops.

What remains is execution.

Every specimen you document contributes to collective knowledge. Every failure you record prevents future failures. Every standard you maintain raises the methodological floor for all researchers.

This isn't hobby organization. This is field development. The archive you build today becomes the reference infrastructure of tomorrow.

Document rigorously. Preserve systematically. Contribute generously.

The research continues.

Data over deadstock.

Sean Lucas, Lead Researcher The Research Lab | Sole Cartel