CURATION AND ORCHESTRATION

Curate the files that matter. Automate what happens next.


Data orchestration in Diskover: cleanup policies select files by catalog query, such as file type, age, project, or tag, then delete, move, or copy them, and a legal hold tag keeps files out of every query

Why it matters.

Less manual work.

Scheduled policies replace scripts and ticket-driven cleanup, so your team spends time on real projects.

Lower storage spend.

Cold, duplicate, and temporary data leave premium tiers on a schedule, freeing capacity you already own.

Traceable runs.

Every run is logged, with the files it processed, which supports audits, retention questions, and policy reviews.

Clean inputs for AI.

Curated files are tagged in the catalog, so you can always see which files went into each model or pipeline.

From scattered files to decisions that run themselves.

Data orchestration workflow in Diskover: select files, tag them, approve, and act by policy

Built-in safeguards.

Approval tags.

Destructive actions can require an approval tag, such as approved_delete, so they run only on files marked as ready.

Dry run first.

A dry run lists every matching file and logs what would happen, without changing anything.

Edited files wait.

If a file changed since the last scan, the policy leaves it for the next run, to protect recent work from mistakes.

Every run logged.

Each run logs the files and sizes processed, with warnings and errors, and scheduled reports can email the results.

Curation and orchestration in action.

Workflow orchestration in Diskover for a localization services company: launch GLIM and Telestream Vantage as file actions, then move source files to preservation and delete them 7 days after delivery by policy
Data orchestration automates what happens to files after you decide about them: copy, move, archive, rename, or delete, on a schedule and by policy. Diskover runs it from the metadata catalog, so each action follows a catalog query, which can include tags.
Data curation selects and labels the files that belong in a set, such as a training set, an archive, or a cleanup list. In Diskover, curation uses catalog queries, filters, and tags.
Only if you set it up that way. A policy can require an approval tag, such as approved_delete, before it deletes anything, and a dry run shows the matching files first.
Yes. A policy can run after each scan of a location or on a schedule your team sets, and each run is logged.
The AI Connector finds files and recommends a tag in plain language. A person approves the tag, and the policies on this page act on it.
Scroll to Top