Add records to calculate readiness.
Local-first preservation workspace
Keep the context, not just the files.
Build a rights-aware continuity plan for the stories, events, posts, and notes your community values. Track provenance, permission, checksums, and backup health without uploading a single file.
Collection coverage
See what is documented and what is fragile
Coverage insight will appear here.
Readiness signals
Strong archives explain themselves
Audit has not been run yet.
Records with a source URL and context note.
Local files with a recorded checksum.
No duplicate signals detected.
Metadata catalog
Every item should have a story of origin
Fictional examples are included to demonstrate the workflow. Replace them with lawful records from your own preservation project.
| Record | Rights | Completeness | Copies | Priority | Actions |
|---|
No matching records
Adjust the filters or add a new metadata record.
3-2-1 backup planner
Three copies, two media types, one off-site
Batch preservation checklist
Prepare a collection before a platform changes
Portable manifest
Your metadata should outlive this browser
Export a JSON working backup or a CSV catalog. Importing JSON validates its shape before replacing local data; no file content leaves your device.
Preservation practice
Archive with care, context, and consent
A durable archive is not a content dump. It is an accountable record of what an item is, where it came from, why it may be retained, and how future readers should interpret it.
Start with official archives and platform terms
Check publisher archives, downloadable account data, terms of service, and announced preservation plans before creating copies. A source URL and access date preserve context even when you do not retain the media itself.
Respect copyright, creator consent, and takedowns
Ownership and access are different. Record permission status, avoid redistributing protected media, seek creator consent for fan works, and maintain a process for honoring takedown requests.
Use durable formats and integrity checks
Prefer open, well-documented formats where lawful. Record a SHA-256 checksum after acquisition so later copies can be compared without exposing file contents.
Test redundant backups, not just copy counts
Follow the 3-2-1 pattern, encrypt sensitive collections, keep recovery instructions, and periodically restore a sample. A backup that has never been tested is only a hypothesis.
Preserve metadata when media cannot be retained
A lawful metadata-only record can still preserve title, date, creator, source, synopsis, rights state, and relationships. It can point future researchers toward authorized copies without redistributing content.