Goal

Build a storage strategy that combines local, cloud, and repository options with clear governance, documentation, and sustainability planning so 3D assets remain accessible over time.

1) Storage roles at a glance

Storage only makes sense when each layer has a clear job. Hover or click the layers below to see what they are responsible for.

Working copy

This is the active project location where people capture, process, and export files. It should not be treated as the only preservation copy.

Independent copy

A separate copy protects against device failure, accidental deletion, and corruption. Independence matters more than convenience.

Cloud collaboration

Cloud tools are useful for access and teamwork, but sync alone is not preservation because it can replicate deletions and corruption too.

Repository deposit

A repository adds governance, curation context, and often persistent identifiers. It is the best public-facing layer when long-term access matters.

Sync is not backup. The safest plans combine separated roles, not just repeated copies of the same behavior.

2) Example storage plan

Switch views to see how the same object can live across working, preservation, off-site, and repository layers without becoming a cluttered mess.

Storage layers for one object 
Projects/[Project_ID]/[Object_ID]/
  01_raw_scans/
  02_processing/
  03_preservation/
  04_access/

Primary role

Active creation, editing, and collaboration.

Main risk

Too much change happens here for this to be your only preservation location.

Preservation/[Project_ID]/[Object_ID]/
  [Object_ID]__v##_raw/
  [Object_ID]_v##_pres/
  [Object_ID]_Metadata.txt

Primary role

Authoritative local package for long-term retention.

Main risk

If it is stored in only one place, hardware loss can still wipe it out.

Independent copy/
  Preservation/[Project_ID]/[Object_ID]/
  Preservation_Logs/storage_audit_log.csv

Primary role

Protection against local disaster, theft, or media failure.

Main risk

If no one checks it, the copy may exist but still be unusable when needed.

Repository deposit/
  preservation_package.zip
  metadata record
  DOI landing page

Primary role

Long-term access, discoverability, governance, and citation.

Main risk

Identifiers only help when the repository itself has stable stewardship and funding.

3) Open each storage option

Storage option

Local Storage

Fast for active work, weak on its own.

What it does well

  • Supports active capture and processing.
  • Keeps large files close to the people using them.
Local storage should be where work happens, not where preservation stops.

Where it fits

External drives, lab servers, and departmental shares support everyday workflows, but they still need redundancy and clear documentation.

Good

  • Local storage is used for active work with at least one additional copy.
  • Copy destinations are documented.

Better

  • Local copies are distributed across independent systems.
  • Validation and restore checks are scheduled.

Best

  • Local storage is integrated with policy-driven redundancy.
  • Integrity monitoring and migration planning are tracked over time.

Storage option

Cloud Storage

Helpful for collaboration, risky if treated as backup.

What it does well

  • Makes collaboration and access easier.
  • Adds a geographically separate location.
Synchronization can spread mistakes quickly. Keep critical preservation files outside the sync-only layer too.

Where it fits

Cloud platforms improve off-site resilience and sharing, but they need governance controls and exit planning.

Good

  • Cloud space is used for access and collaboration.
  • Critical files are also stored outside the sync platform.

Better

  • Cloud workflows define versioning, roles, and retention practices.
  • Platform risks and cost growth are documented in planning.

Best

  • Cloud storage is one layer in a multi-location preservation plan.
  • Exit strategy and migration pathways are documented in advance.

Storage option

Repository Deposit and DOI

Best for long-term discovery and public-facing stewardship.

What it does well

  • Improves findability and citation.
  • Adds stewardship expectations beyond one project folder.
A DOI is a promise of managed access, not a substitute for preservation work.

Where it fits

Repositories and persistent identifiers matter most when governance, funding, and metadata quality support them.

Good

  • 3D assets are deposited in a stable repository service.
  • doi_status is tracked in project records.

Better

  • DOIs are reserved before publication.
  • Landing page and metadata links are confirmed before release.

Best

  • Repository governance and funding stability are considered in selection.
  • Identifier records stay synchronized with policy and metadata updates.

Storage option

One Combined Plan

Storage only works when the layers support each other.

What to budget for

  • Storage media and subscription costs
  • Metadata and documentation labor
  • Copy validation, migration, and user support time

Where it fits

The strongest plans combine local workflow storage, independent copies, and repository deposit with realistic staffing and cost planning.

Good

  • One local working location plus one independent copy.
  • Basic documentation of responsibilities and locations.

Better

  • Local, cloud/off-site, and repository roles are clearly separated.
  • Costs and staffing needs are planned annually.

Best

  • Storage, governance, and funding are treated as one long-term stewardship program.
  • Planned migration and continuity workflows are maintained over time.