How to Build a Searchable Digital Archive of Your Kirksville Family History

A folder named Grandma Photos is easy to understand today.

Twenty years later, it may not tell anyone which grandmother, which side of the family or which photographs are inside.

Searchability comes from stable identifiers and metadata—not from deeper and deeper folder trees.

Decide what the archive should answer

A useful archive should let you find:

• one person;
• one address;
• one business;
• one cemetery;
• one year;
• one family branch;
• one event.

If answering those questions requires manually opening hundreds of files, the collection is stored but not meaningfully searchable.

Give every item a stable ID

Use identifiers that do not change when your interpretation changes.

Examples:

• KIRK-FAM-PH-000001
• KIRK-FAM-DOC-000001
• KIRK-FAM-AV-000001

Use the ID in:

• filename;
• metadata table;
• transcript;
• derivative;
• physical-sleeve reference when appropriate.

Do not renumber the archive because a surname or date was corrected.

Keep the folder structure shallow

A simple structure is easier to preserve.

For example:

• 00_ADMIN
• 01_PHOTOS
• 02_DOCUMENTS
• 03_AUDIO
• 04_VIDEO
• 05_RESEARCH
• 06_DERIVATIVES
• 07_EXPORTS

Do not try to encode the entire family tree into nested folders.

People appear in more than one branch, place and event.

Build a portable metadata index

A spreadsheet, CSV, TSV or SQLite database can work well.

Useful fields include:

• item ID;
• path;
• type;
• short title;
• date or date range;
• people;
• place;
• address;
• event;
• creator;
• source/provenance;
• rights;
• confidence;
• related IDs;
• notes.

The format should be exportable without the original application.

Normalize people without erasing original wording

One person may appear as:

• William H. Smith;
• W.H. Smith;
• Bill Smith;
• Grandpa.

Use a person authority table.

Give the person a stable ID and record:

• preferred name;
• aliases;
• birth/death dates if known;
• relationships;
• evidence.

Preserve the original caption separately.

Do not rewrite historical wording just to make the database tidy.

Do the same for places

Addresses and place names change.

A place table can track:

• stable place ID;
• historic address;
• modern address;
• cemetery;
• farm;
• town;
• coordinates where known;
• confidence.

This makes later research far easier than trying to normalize every filename.

Add OCR to printed documents

OCR can turn scanned text into searchable text.

Keep the scan.

Store OCR output separately.

OCR is an index aid, not authoritative transcription.

Old newspapers, unusual typefaces and damaged documents can produce bad recognition.

Transcribe handwriting separately

Handwritten material may require manual transcription.

Keep two layers when interpretation matters:

• literal transcription;
• normalized or explanatory notes.

Do not silently “correct” the source.

Separate masters from derivatives

Preservation masters should remain stable.

Create derivatives for:

• sharing;
• crops;
• web use;
• restoration;
• OCR;
• transcripts.

Do not let a photo editor become the only place where the archive exists.

Record provenance

For each item, record how it entered the collection.

Examples:

• inherited from a named relative;
• found in an album;
• scanned from a borrowed original;
• downloaded from a repository;
• copied from a newspaper;
• created by the family.

Without provenance, later researchers cannot judge the evidence.

Store uncertainty explicitly

Do not invent precision.

Use:

• ca. 1914;
• 1910–1920;
• before 1932;
• possibly Anna Smith.

Do not create 1914-01-01 merely because a database wants a complete date.

That converts uncertainty into false fact.

Protect private information

Family archives can contain information about living people.

Separate material involving:

• financial data;
• health records;
• identification;
• current addresses;
• private correspondence.

Create public derivatives intentionally rather than publishing the preservation archive wholesale.

Plan for software failure

If you use genealogy or archive software, periodically export:

• metadata;
• relationships;
• notes;
• media references.

Keep original media outside the application too.

The collection should survive the disappearance of one vendor.

For digitization, see How to Digitize and Preserve Old Kirksville Family Photographs.

For repository donation, see How to Prepare a Digital Kirksville Local-History Collection for Donation to an Archive.