Goal

Use this page as full project overview that introduces the PIP phases, provides a project checklist, and shows how working directories hand off finalized files into a dedicated Preservation folder to reduce project-folder bloat.

All PIPs at a glance

PIP means Preservation Intervention Point: a specific stage where key preservation decisions should be made and documented. Hover a phase for the quick summary, then click it to jump to the full section below.

PIP 0: Build the rules before the files arrive

Set the repository shape, IDs, rights baseline, workflow standards, and metadata expectations before scanning starts.

Main folders: Documentation/, Metadata/, Projects/

PIP 1: Protect raw capture

Copy source files into managed storage, keep them unchanged, and record capture method, device, settings, and date.

Main folder: 01_raw_scans/

PIP 2: Create the preservation master

Process the data, retain milestone versions, and document the decisions that produced the authoritative master package.

Main folders: 02_processing/, 03_preservation/

PIP 3: Make access copies and hand off the package

Create access derivatives, move the raw package and preservation package into repository storage, and keep working folders lean.

Main folders: 04_access/, Preservation/

PIP 4: Sustain it over time

Apply multi-copy storage, copy validation, policy confirmation, and DOI/publication tracking so the package stays understandable and usable.

Main layers: local, offsite, repository, logs

Checklist by phase

Use for mental checking of your own project

Before scanning

Set structure, IDs, and governance

Make the rules visible before the project produces files.

After capture

Secure raw data and capture context

Protect the source files before cleanup or export work begins.

During processing

Retain the story behind the master

Keep milestone exports and write down the decisions that shape the model.

After processing and ongoing

Hand off, store, and maintain

Move final packages into preservation storage and keep publication status synchronized.

Preservation Intervention Points (PIPs)

Use the dropdowns for more information on each PIP.

PIP 0

Repository setup and before scanning

Establish structure, naming, workflow standards, rights, and metadata expectations before capture.

Steps

  1. Create repository and project folder structure.
  2. Assign project ID and naming pattern.
  3. Write or adopt Documentation/workflow_standards.txt and apply it.
  4. Set rights and access level baseline.
  5. Define required metadata and registry fields.
After this PIP you will have: a ready repository, a project ID, and clear governance before scan day.

Folder focus for this stage

Documentation/
Metadata/
Projects/[Project_ID]/

Main setup work

Create folders, name the project, write workflow standards, and start the project registry.

What to record

Rights baseline, access expectations, required metadata fields, and naming rules.

Good

  • Folders and IDs exist.
  • Basic rights note exists.

Better

  • Workflow standard file is documented.
  • Project registry record is created.

Best

  • Naming/version rules are enforced consistently.
  • DOI plan is defined early.

PIP 1

After capture

Secure raw capture data immediately and preserve enough context to trust it later.

Steps

  1. Copy raw captures into 01_raw_scans/.
  2. Record device, settings, operator, and date.
  3. Keep source data unchanged and track file location in documentation.
This is the stage where capture method and device history matter most. If you miss them here, they are hard to reconstruct later.
After this PIP you will have: preserved raw data with enough context to trust and reuse it.

Folder focus for this stage

Projects/[Project_ID]/[Object_ID]/
  01_raw_scans/
  documentation/

Main setup work

Copy raw capture data into managed storage and keep the source files unchanged.

What to record

Capture device, settings, operator, date, and any deviations from the planned workflow.

Good

  • Raw files copied the same day.
  • Short capture note written.

Better

  • Capture context is complete.
  • Raw folder follows naming standard.

Best

  • Second person confirms completeness.
  • Capture protocol deviations are logged.

PIP 2

Processing and preservation master

Create the authoritative master and document the decisions that shaped it.

Steps

  1. Process scans in 02_processing/ and save major milestones.
  2. Export high-fidelity preservation master files in 03_preservation/.
  3. Write object metadata and paradata notes for key decisions.
This is where provenance and paradata become essential. If a model is filtered, smoothed, or decimated, record it here.
After this PIP you will have: a traceable preservation master that can be interpreted later.

Folder focus for this stage

Projects/[Project_ID]/[Object_ID]/
  02_processing/
  03_preservation/
  documentation/

Main setup work

Process the model, save milestone versions, and export the high-fidelity preservation master.

What to record

Registration, cleanup, smoothing, decimation, export settings, and software/version information.

Good

  • Final master export is saved.
  • Basic processing notes exist.

Better

  • Milestone versions are retained.
  • Paradata includes key parameter choices.

Best

  • Full provenance trail is captured.
  • Master quality check is documented.

PIP 3

Access derivatives and preservation handoff

Produce delivery copies and move final packages into repository preservation storage.

Steps

  1. Create access derivatives in 04_access/ for web, teaching, or outreach.
  2. Copy raw package, preservation package, and metadata file into Preservation/<project>/<object>/.
  3. Keep only active working files in project processing folders.
Before you consider the handoff complete, reopen the package after transfer so broken paths or missing sidecars are caught early.
After this PIP you will have: usable public-facing outputs plus a clean preservation copy separated from active project folders.

Folder focus for this stage

Projects/[Project_ID]/[Object_ID]/
  04_access/

Preservation/[Project_ID]/[Object_ID]/

Main setup work

Create access derivatives and copy the raw package, preservation package, and metadata into the repository.

What to record

Which derivative came from which master, and whether the packaged files reopen correctly after transfer.

Good

  • At least one access copy exists.
  • It is separated from the master.

Better

  • Preservation folder handoff is complete.
  • Metadata links each derivative.

Best

  • Access performance is tested.
  • Working directories are kept lean after handoff.

PIP 4

Storage, policy checks, and maintenance

Place preservation packages in reliable storage tiers, validate governance, and maintain publication records.

Steps

  1. Apply the three-copy model to the repository Preservation folder package.
  2. Update project registry metadata with policy and publication status.
  3. Set DOI status and confirm access/policy language before release.
This is the maintenance stage: copies, policy confirmation, DOI tracking, and link checking all need recurring attention.
After this PIP you will have: distributed storage for preservation masters and a clear DOI publication path.

Folder focus for this stage

Preservation/[Project_ID]/[Object_ID]/
Preservation_Logs/
Metadata/project_registry.json

Main setup work

Distribute copies, confirm policy values, and keep DOI/publication records synchronized.

What to record

Storage locations, validation checks, DOI status, landing page links, and maintenance actions.

Good

  • Master has working and backup copies.
  • DOI planning status is tracked.

Better

  • Master has offsite copy.
  • DOI is reserved before publication.

Best

  • Storage and DOI records stay current.
  • Access links and metadata stay synchronized.