For multimedia archives, the resulting files can be significant in size. A 4K video file of about 1 hour requires around 10 GBytes. Thus it makes little sense to store this data directly in the database. If the files are stored externally (as recommended), the corresponding files are given the name of the database as well as the document number (file) and the corresponding file extension. Here is an example: moviestar-15.mp4
.
In order to later ensure that the corresponding file is in its original state, so-called MD5 keys are created from all externally stored files. The entire file is read to create a check digit, which is saved in the database. With the check program 'Check external contents' it can be determined whether to the seized files effectively the suitable externally stored files are present.
The name of the database must be entered when calling up the program. Optionally, the number of documents to be checked can be limited accordingly with 'First document' and 'Last document'. After the call, the corresponding files are logged in the ArchivistaBox log file. To do this, the system switches directly to the 'View system files' form when the process is started. It should be noted that the corresponding system messages are only updated when 'View system files' is clicked. In order to determine whether the check program has been processed, you must click on 'View system files' again to check whether the program has been processed. The check program itself logs each checked file. Either a 'sucessfully' (successful) or an 'ERROR' message is displayed. At the end of the check program all errors are displayed again 'bundled'.
When calling this program all files must be read. Depending on the number of files, it may be necessary to read a high volume of data, so that the check process can take several hours up to several days.