Quality Control
From UA Libraries Digital Services Planning and Documentation
| Line 24: | Line 24: | ||
[[QcReporter.rb details]] Follow link for complete usage of this scripts reports | [[QcReporter.rb details]] Follow link for complete usage of this scripts reports | ||
| - | ===Derivatron | + | ===Derivatron=== |
This script will run on command or will run every evening, and creates a set of low resolution .jpg derivatives for fast visual quality control checking of a collections image files. | This script will run on command or will run every evening, and creates a set of low resolution .jpg derivatives for fast visual quality control checking of a collections image files. | ||
| - | [[Derivatron | + | [[Derivatron details]] Follow link for complete usage of this script |
Revision as of 21:24, 2 March 2010
Preparation for Check Phase (as needed)
During the Check Phase (Weekly)
Determining what to do with weeded image files (as needed)
Contents |
Quality Control scripts
Per collection
see: http://www.lib.ua.edu/wiki/digcoll/images/0/0a/General_QC_guidelines.docx
This document covers script usage for individual image collections as well as guidelines for spot-checking and notation of issues discovered during Quality Control.
Across multiple collections
These scripts are written in Ruby and can be found in the c:\portableruby directory
QcReporter.rb
This script runs automatically every evening and creates a report of all the files that do not meet our standard file and folder naming conventions.
QcReporter.rb details Follow link for complete usage of this scripts reports
Derivatron
This script will run on command or will run every evening, and creates a set of low resolution .jpg derivatives for fast visual quality control checking of a collections image files.
Derivatron details Follow link for complete usage of this script
