Resources · 74

Social content: prepare a usable and proportionate archive

Retain necessary context, versions and media and test what an export actually reconstructs.

· 3 min

Empty archive room with document cases and digital evidence storage AI-generated editorial illustration

What this guide helps achieve

  • Limit the necessary scope
  • Retain context
  • Verify exports
  • Prepare use and removal

Quick check

  • Does purpose justify each retained field?
  • Are media and corrections included?
  • Can someone read the archive off-platform?

Step-by-step method

  1. 01

    Limit the necessary scope

    Separate brand publications, public exchanges and private messages. Define purpose, access and duration. Full exports may contain unnecessary data; do not collect third-party profiles merely because a tool allows it.

    Deliverable: scope and retention rules.

  2. 02

    Retain context

    Link native identifiers, URLs, language, dates, author, text and media. Keep corrections and publication status. Observed counters need observation dates; screenshots may omit links, captions and alternatives.

    Deliverable: dictionary and file inventory.

  3. 03

    Verify exports

    Open a sample off-platform: a simple post, thread, video and corrected item. Check encoding, order, media and relationships. Activity Streams supplies an activity vocabulary; it does not guarantee full feature exports by a platform.

    Deliverable: reading results and losses.

  4. 04

    Prepare use and removal

    Define who can search, correct or remove records. Test reconstruction in an independent tool and removal under retained rules. Document limits: an archive file does not restore followers or platform reach.

    Deliverable: consultation and removal procedure.

Acceptance case to reproduce

Fictional example: these inputs describe no customer or observed result.

View case inputs
{
    "objects": [
        {
            "id": "post-1",
            "reply_to": "post-0",
            "attachment": "media-7"
        }
    ],
    "exported_ids": [
        "post-1"
    ],
    "exported_media": []
}

Expected decision

The referenced reply and media are missing. Document these losses before calling the archive reusable.

Fictional variations to test

Two platforms use the same local identifier 42.

Use a key including the platform or a global URI. Do not merge two posts using only their local number.

The archive hash is valid but a media file remains external.

The hash checks bytes present, not export completeness. Check the manifest and open expected attachments independently of the platform.

The export contains creation, update and deletion events.

Reconstruct the chronology and final state. A deletion marker does not justify redisplaying deleted text; apply the retention policy.

Evidence to retain

  • Platform, global identifier and retained relationships.
  • Manifest, hashes and attachment test.
  • Event order and deletion rule.

Additional reference : W3C — Activity Vocabulary, Tombstone [EN]

Verification procedure

  1. Inventory exported posts, replies and attachments.
  2. Reconstruct a reply and its media outside the platform.
  3. Keep missing-object records and reuse limitations.

W3C — Activity Streams 2.0

Reusable worksheet

Complete with your authorised observations. These fields are a working template, not observed results.

FieldInformation to record
ScopePurpose, content and excluded data
ItemIdentifier, language, date, version and media
ReadingIndependent tool, relationships and observed losses

Worked example

Illustrative situation

Fictional example: a team exports a campaign before closing an account.

Decision and expected evidence

It discovers missing videos and corrections, completes permitted records, documents losses and tests reading without social-platform login.

Distinguish the mechanisms

MechanismPurposeCheck or limitation
ScreenshotRetain a visual stateMay omit context and accessibility
Structured exportRetain fields and relationshipsCoverage depends on the supplier and needs testing

Management indicators

IndicatorWhat it measuresFirst action
Readable recordsItems opened off-platformComplete or document omissions
Retained contextItems linked to dates and versionsFix missing links and fields

Common pitfalls

  • Store private exchanges without a defined scope
  • Check only the number of exported files

Frequently asked questions

Does an archive prove content is true?

No. It documents retained material and context; factual accuracy needs separate verification.

Can an export migrate a whole community?

No. Identifiers, relationships, features and audiences may not be transferable.

Must all private messages be retained?

Scope depends on purpose and applicable rules. Limit content, access and duration to justified needs.

Further reading and tools

Editorial resources to extend the method.

Official references

References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.