Data Integrity

In ROPARC, Git is the source of truth — every item, document, and link lives as a file in the workarea’s repository, and the database is a derived index used for fast queries. The Settings → Integrity tab is a read-only diagnostic that verifies the index still matches the repository.

Running a scan

Click Run scan. The scan reads every item and document in the workarea from git and compares it field-by-field against the database index. Larger workareas take a few moments.

• No drift detected — the index matches git at HEAD. This is the expected result.
• Drift entries — rows whose database state diverges from the YAML in git. This is phantom state: it exists only in the index and will disappear on the next full reindex. Each entry shows the entity, field, both values, and the last commit that touched the file.

The report also lists uncommitted writes — audit-log entries for writes that never produced a matching git commit — with links to the affected entities.

Interpreting drift

Drift normally indicates a bug or an interrupted write, not user error. Because git is authoritative, the remedy is a reindex (which rebuilds the database from the repository) rather than manual correction. Use the audit log to trace when and how the divergence happened, and report reproducible drift to your administrator or support.

Long values in the report collapse behind a show toggle, and values that look identical but differ in whitespace are rendered with visible whitespace markers and byte counts — a leading space is a real difference even when you can’t see it.