For Quality Control
Jlderidder (Talk | contribs) |
Jlderidder (Talk | contribs) |
||
| Line 24: | Line 24: | ||
== On Linux Server, the Storage Archive == | == On Linux Server, the Storage Archive == | ||
| − | Checking the MD5 checksums of content stored prior to each full-tape backup: [[Image:Dirs.txt]] (as described in [[Watching Our Backs]] | + | Checking the MD5 checksums of content stored prior to each full-tape backup: [[Image:Dirs.txt]] (as described in [[Watching Our Backs]]) |
Revision as of 15:45, 30 July 2010
Quality Control checks happen in multiple parts of the work flow pipeline.
File:Filenames.txt is a Windows Perl script for locating badly formed and mislocated file names. This version of the script is also known as 'filenamesAndTranscripts' as it checks transcript directories also, if they exist.
File:Numfiles.txt is a Windows Perl script that looks through scans directories in a selected collection directory, counts up all files of input extension chosen, and outputs txt file tab delimiting item number followed by number of files
On Linux Server, for Web Delivery
Once content is uploaded to the Linux server for archival storage, one of the scripts we run to verify that all the archival filenames are correct and in the right directory, and no sequences are missing, is File:TestIncoming.txt
To test content online in Acumen, and locate items that have no derivatives or no MODS record, use this Linux Perl script: File:FindMissing.txt
For Cabaniss, this one checks the content in the web directory (in Acumen) against what's in the storage archive, to make sure nothing is missing: File:FindMissingFile.txt
On Linux Server, the Storage Archive
Checking the MD5 checksums of content stored prior to each full-tape backup: File:Dirs.txt (as described in Watching Our Backs)
