Accountability 

 

Where data is kept

 

md5sums.txt, sha1sums.txt sha256sums.txt

 

This file is placed in each RDC folder and copied with copy process to each destination. This file contains a listing of files in that folder, the checksums for each file, and a unix timestamp of when that checksum was done. These would be the master checksums for each checksum type

 

md5sums-xxxxxxxx.txt

 

After each file is copied, the checksums are checked and referenced to the master file (md5sums.txt). The checksum of the file at the destination is then written to this md5sums-xxxxxxxx.txt file. The file contains a checksum for each file in the folder, in the same format as md5sums.txt. This file is never referenced by R3D Data Manager, but becomes your audit trail. From these files, you can tell what the MD5 sum for each file was after every copy process. So if there is ever an error, you can see on what date it happened and from there determine the source.

 

ProjectInformation.txt

 

This file is placed above the RDM folders (RED camera build 15 and above) or the RDC folders (RED camera build 14 and below), in the root of each destination. This file contains all the project, shot, and RED media information. In addition, it contains info about every folder transferred, each file in that folder, and all the checksums for that file. So this can then become a master list of everything that was transferred to that destination. From here, if you are looking for if a specific shot or file was transferred, you can search this text file and find the time it was transferred and the original RED Media