Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: data integrity slow and programmatic filters [DHIS2-16223] #1334

Merged
merged 1 commit into from
Mar 13, 2024
Merged

docs: data integrity slow and programmatic filters [DHIS2-16223] #1334

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions src/developer/web-api/data-validation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -546,6 +546,18 @@ Additional results can be filtered using a `section` parameter.

The `section` filter will return all exact matches which have the specified section.

Furthermore, to filter (select) only checks marked as `isSlow` use `slow=true`,

GET /api/dataIntegrity?slow=true

or to filter (select) only checks that are not performed via database query
(programmed checks) use `programmatic=true`:

GET /api/dataIntegrity?programmatic=true

The `slow`, `programmatic` and `section` filters can be combined in which case
all conditions must be met.

### Running data integrity summaries { #webapi_data_integrity_run_summary }

Since version 2.38, data integrity checks have two levels of specificity:
Expand Down