Data organization

CryoMaestro presents data through scientific relationships rather than requiring users to navigate an implementation-specific directory tree.

Logical hierarchy

• Project — ownership, collaborators, samples, grids, and analysis workspaces
• Session — one instrument run with a grid, operator, plan, and captured calibration context
• Target hierarchy — atlas, square, square map, cluster, hole, and exposure targets
• Artifacts — movies, micrographs, metadata, previews, masks, particles, maps, and reports
• Jobs and results — workflow version, parameters, inputs, outputs, status, and provenance

Storage responsibility

Administrators map this logical record to institution-controlled storage during deployment. Users should not rename, relocate, or edit managed artifacts behind the application. External data should be registered through an approved import workflow so identity and provenance are retained.

The facility deployment guide defines actual storage locations, permissions, backup scope, retention, and recovery procedures.