LOCAL PROJECTS · V0.8.0

Turn separate tools into a repeatable workflow.

Bundle profiling evidence, cleanup recipes, data contracts, import mappings and migration presets into a reusable local project — without storing the source datasets in RowMend.

✓ Browser-only persistence✓ Exportable project JSON✓ No account required

Select or create a project A project becomes the local container for a recurring RowMend workflow.

ACTIVE LOCAL PROJECT

Run project

Project name

Description

Workflow configuration

01 · PROFILE

Data profile

Keep a structural snapshot of the dataset you profiled, without raw row contents.

Open Profiler

02 · CLEAN

Cleanup recipe

Attach reusable transformations for recurring files.

Open Clean & Transform

03 · CONTRACT

Data contract

Keep schema and data-quality expectations with the workflow.

Open Data Contract

04 · IMPORT

Validation & SQL setup

Store target mapping, validation rules, SQL dialect and merge key.

Open Import Checker

05 · RECONCILE

Migration preset

Keep source-to-target mapping, comparison flags and key selection.

Open Migration Check

Project portability

Exporting a project creates a JSON file with configuration and profile summaries. It intentionally excludes CSV/Excel row data, generated SQL and migration issue rows.

Delete this local project

This removes only the project container. Standalone recipes, contracts and import profiles remain in their existing local stores.

WHY PROJECTS

Move from one-off fixes to repeatable local operations.

The same monthly or weekly file usually needs the same cleanup, schema expectations, validation rules and downstream checks. Local Projects keeps those decisions together so the workflow is easier to repeat.

Projects can now be executed locally as a pipeline with privacy-minimized run history. The future cloud/Team layer can add synchronization, schedules, permissions and audit trails without taking away the free local runner.