...
Here it is shown, whether the integrity of all packages is OK or not. Also an overview table is shown, containing numbers of packages in different states from the date integrity point of view. These states have the following meaning:
Total | The total number of packages with data in the SOFiE application. Packages without files do not count (eg. shredded packages). |
|---|---|
OK | The number of packages with completed integrity check where integrity is OK. |
Corrupted | The number of packages with completed integrity check and corrupted data. |
Inaccessible | The number of packages for which the integrity check could not be performed because some or all of their files are inaccessible. Most likely indicates a problem with datastore. |
Unchecked | The number of packages for which the integrity check was not performed at all yet. |
The data integrity checks settings
...
If this function is enabled, the users can themselves run an integrity check of packages and files.
(default: enabled)
Periodic data integrity check
If the periodic data integrity check is enabled, the application will automatically periodically (according to schedule below) verify the checksums of the stored data.
(default: enabled)
Schedule of the periodic data integrity check
The cron string for setting the schedule of periodic data integrity checks. The string must be in the "UNIX CRON" format and the UTC time zone. You can test the string for example here: https://crontab.guru/ .
(default: 0 2 * * SAT)
Check packages in state of
The scheduled automatic, or manually run by the administrator below, check will verify only the packages in the states selected here. If there are a lot of packages in the application, this could significantly speed up the check, if run e.g. only for active packages.
(default: active/quarantined)
Cancel the check / Run the check / Save
...