Goal

Create a stable structure that separates repository-wide program management from project-by-project working folders, while keeping naming, documentation, and long-term stewardship consistent.

Repository level vs project level

Repository-level structure stores shared program components such as metadata standards, governance files, preservation logs, and long-term object packages across many projects. Project-level structure stores one active production workspace from raw capture through access outputs. Together they keep institution-wide continuity while preserving clear project context.

Project folders are not the repository. Projects stay active and messy; Preservation stays stable and authoritative.

1) Explore the repository root

Hover or click folders to see what each part does in a sustainable 3D repository.

3D_Repository
DIR[Project_ID]/
DIR[Object_ID]/
DIR[Project_ID]/

Documentation/

Keep repository-wide standards here: workflow rules, naming guidance, policy notes, and local documentation that should stay stable across projects.

Example file: workflow_standards.txt Supports consistency across teams

Metadata/

This is the central control layer for shared registries, schemas, and project tracking files. It helps prevent metadata from being stranded inside one project folder.

Example file: project_registry.json Can also point to shared vocabularies

Objects/

Use this area for durable object identities and optional long-term groupings. It helps separate intellectual identity from short-lived project activity.

Best for object collections that outlive one project

Preservation/

This is the long-term retention space. Store raw packages, preservation masters, and the metadata/paradata needed to interpret them later.

Authoritative package Keep linked files together

Preservation_Logs/

Track migrations, preservation actions, and major interventions over time. This folder makes stewardship visible instead of leaving it as informal memory.

Example files: migration_records.txt

Projects/

Projects are active workspaces. They can include raw capture, in-progress processing, access copies, and notes while work is still underway.

Working space, not final preservation space

View Complete File Structure

 
3D_Repository/
  Documentation/
    workflow_standards.txt

  Metadata/
    project_registry.json

  Objects/

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

  Preservation_Logs/
    migration_records.txt

  Projects/
    [Project_ID]/
      [Object_ID]/
        01_raw_scans/
        02_processing/
        03_preservation/
        04_access/
        documentation/

2) Explore the project workspace

This is the part that stays active during scanning and processing. Once the model is completed, only the preservation package moves into Preservation/.

Projects/[Project_ID]/[Object_ID]

01_raw_scans/

Store untouched source files here, such as camera images, E57 point clouds, or scanner exports. Raw data should remain identifiable and unchanged.

02_processing/

Use this folder for alignment, cleanup, intermediate saves, and milestone outputs. This is where version growth usually happens.

03_preservation/

Place finalized high-fidelity exports here before handoff. These files should be the preservation-ready package, not the whole working mess.

04_access/

Optimized derivatives for the web, teaching, or outreach belong here. Keeping them separate prevents access copies from being mistaken for masters.

documentation/

Keep object metadata, paradata, software/version notes, and validation notes here while work is active so they can move with the preservation package later.

Once the model is completed, move these from the workspace
01_raw_scans/ 03_preservation/ documentation/
Move into final package
Into repository

Preservation/[Project_ID]/[Object_ID]/

View full preservation file structure

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

3) Rules