The -log.txt file present in your downloaded folder gives you information related to the creation of your archive in Reveal, and is used during the quality control check (see our Archives Quality Control Checks article).
.png)
Log.txt Expected Value Count
The values for each of these lines is described below:
Total Files Succeeded: The number of successfully archived files.
This should equal the number of files in your project, unless there are bad/corrupt or failed files.
Total Dup Files in Archive: The number of dup files in your archive.
A dupe file is created when a file experiences a problem during the archive process. The file that experienced the problem will remain in your downloaded archives as a dup and represented in Total Dup Files in Archive. Reveal will try two more times to archive the file:
If any of the retries succeed, it will be represented in Total Files Succeeded, and the retries (up to 2 for a single file) will be represented as dupes.
If both retries are unsuccessful, the file will be represented in Total Bad/Corrupt Files in Archive (third and final unsuccessful retry), and the first 2 retries represented as dupes.
No dupes will be present when extracting your archives, because they will all be overwritten by either their successful file or the bad/corrupt file counterpart during the extraction process.
Total Bad/Corrupt Files in Archive: The number of bad/corrupt files in your archive.
A bad/corrupt file is created when the third time trying to archive a file is unsuccessful. If you have any bad/corrupt files in your archive, contact customer support.
Total Files Failed: The number of failed files that could not be archived.
A failed file occurs when there is an issue with the file even before the archival process, for example if the file is in a bad state in Reveal. Failed files do not generate dupes. If you have any failed files in your archive, contact customer support.
Total Files Referenced but Not Generated (Informational): Number of files with an additional file path that does not lead to a file. This does not mean Reveal couldn’t find your file, rather Reveal designated an additional space for your file to exist in the database, but that space was not generated with that file.
Total Files in Archive: Total file count of all files in your archive; includes successful, dup, and bad/corrupt files. Reference this number when you’re using the Test function in the Archive Extractor.
Total Files in Archive = [Total Files Succeeded] + [Total Dupe Files in Archive] + [Total Bad/Corrupt Files in Archive].
Total Files Unique Files in Archive: Total file count of just successful and bad/corrupt files. Reference this number when you have actually extracted the files.
Total Files Unique Files in Archive = [Total Files Succeeded] + [Total Bad/Corrupt Files in Archive].
Total uncompressed size of dup files in archive: Total size of dup files.
Total uncompressed size of bad/corrupt files in archive: Total size of bad/corrupt files.
Total uncompressed size of valid files in archive: Total size of the successful files in the archive.
Total uncompressed size in archive: Total size of all files in your archive; includes successful, dup, and bad/corrupt files. Reference this number when you’re using the Test function in the Archive Extractor.
Total uncompressed size in archive = [Valid files size] + [Dup file size] + [Bad/corrupt file size].
Total uncompressed size of unique files in archive: The total size of just successful and bad/corrupt files. Reference this number when you have actually extracted the files.
Total uncompressed size of unique files in archive = [Valid files size] + [Bad/corrupt file size].
When to Contact Support
If your archived project has any Bad/Corrupt files or Failed files, or the numbers do not add up correctly as detailed in this document, contact customer support by emailing support@revealdata.com.