Overview
MediaVerify can detect different errors and will inform you about them. In addition, the creator info may provide helpful information for contacting the data manager to find possible solutions.
The errors that may occur are explained below.
Missing files
Fig. 1: The Quick Scan Detected Missing Files
Files that are referenced in the history but not present in the file system are considered missing. Missing files are errors indicated by a red color in the user interface. Click on one of the files to open the file info box on the right, where you can find information about its missing state.
Potential solutions:
- Request the missing files from the data manager
- Create a new history that does not reference the missing files (e.g., with Silverstack).
New files
Fig. 2: The Quick Scan Detected Unregistered Files
Files not registered in the history but present in the file system are considered unregistered or new. These new files are not treated as errors and will be included in the new generation. Before the verification, the history does not contain hashes for these new files. Therefore, they cannot be verified and are labeled as not verifiable. After the verification, the state of new files is “original” compared to “verified” since an initial hash value was calculated.
Potential solution:
- If you do not want to include the new files in the history, remove them from the managed data before you proceed with the verification.
Hash mismatch
Fig. 3: Hash Mismatch
A hash mismatch occurs if the comparison between the recorded hash in the history and the newly calculated hash fails. This error means that the file has changed since the last time the history was created. MediaVerify shows the old and new hash values (hash types) in the file’s info box.
Potential solutions:
- Request the unchanged files from the data manager that sent you the dataset.
Renamed files
Fig. 4: MediaVerify Detected A Potential Renaming Scenario
If files were renamed, the quick scan detects the previous names (or paths) as missing and the current names as new. Therefore, renamed files result in an equal amount of missing and new files. MediaVerify can detect renamed files by comparing the hash values of the missing and new files and storing the information in the history through an attribute called previous path. This feature can be enabled in MediaVerify’s settings. If enabled, the application will inform you about potential renaming scenarios. Please note that renaming detection can increase the processing time.
Ignored files
Fig. 5: MediaVerify Lists All Ignored Files
Ignored files are not errors and are only displayed for information purposes. MediaVerify allows you to define custom ignore patterns in the settings. Files and directories matching the defined patterns will be ignored in the ASC MHL history. The patterns will only be stored in newly created histories. Once a pattern has been added to the history, it can no longer be removed. Individual patterns must be separated in the settings’ text field by a comma to take effect.
The post How to identify issues appeared first on Pomfort Knowledge Base.