Quality Control

From UA Libraries Digital Services Planning and Documentation
(Difference between revisions)
Jump to: navigation, search
(Commercial QC Software)
Line 1: Line 1:
[[Checking Work By Object|As Students Work (Daily)]]
+
There are 2 major steps in the Quality Control process, the QC script and spot-checking.
  
[[Checking Work Daily|At Shift's End (Daily)]]
+
==QC Script==
 +
The script we use in QC can be found on the Share drive here:
 +
S:\Digital Projects\Administrative\scripts\qc
 +
filenamesAndDupes.pl
  
[[Determining what to do with weeded image files (as needed)]]
+
This program will check for correct and sequential filenames per the collection number in a Scans folder and its corresponding Transcripts folder (if there is one) as well as check for duplicate filenames. It will print out a report in the “output” folder. If it shows errors, please rename the files accordingly and also check the metadata and trackingFiles to make sure the filename is OK in those spreadsheets. When you are done with the report file this script created, please delete it.
  
 +
You should be able to run this program by double clicking on it. You might need to first associate the file type with Perl the first time you use it.
  
  
<!--=Quality Control scripts=-->
+
==Spot-Checking==
 +
Once you've run the programs and fixed any problems, please spot-check images.
  
==Folder QC==
+
*Open every object folder with Adobe Bridge.
see: [http://www.lib.ua.edu/wiki/digcoll/images/0/0a/General_QC_guidelines.docx http://www.lib.ua.edu/wiki/digcoll/images/0/0a/General_QC_guidelines.docx]
+
*Verify what you see against what's in the Metadata and the number of scans recorded on Tracking files.  
 +
*Check general image quality (cropping, alignment, colors, etc.)
 +
 
 +
 
 +
'''If you are working on a collection in collaboration with someone else or are working on an ongoing collection, mark the items that have been QCed on the QC tab of the Tracking Files sheet.'''
  
This document covers script usage for individual image collection folders as well as guidelines for spot-checking and notation of issues discovered during Quality Control.
 
  
 
==Commercial QC Software==
 
==Commercial QC Software==

Revision as of 11:55, 25 June 2012

There are 2 major steps in the Quality Control process, the QC script and spot-checking.

Contents

QC Script

The script we use in QC can be found on the Share drive here: S:\Digital Projects\Administrative\scripts\qc filenamesAndDupes.pl

This program will check for correct and sequential filenames per the collection number in a Scans folder and its corresponding Transcripts folder (if there is one) as well as check for duplicate filenames. It will print out a report in the “output” folder. If it shows errors, please rename the files accordingly and also check the metadata and trackingFiles to make sure the filename is OK in those spreadsheets. When you are done with the report file this script created, please delete it.

You should be able to run this program by double clicking on it. You might need to first associate the file type with Perl the first time you use it.


Spot-Checking

Once you've run the programs and fixed any problems, please spot-check images.

  • Open every object folder with Adobe Bridge.
  • Verify what you see against what's in the Metadata and the number of scans recorded on Tracking files.
  • Check general image quality (cropping, alignment, colors, etc.)


If you are working on a collection in collaboration with someone else or are working on an ongoing collection, mark the items that have been QCed on the QC tab of the Tracking Files sheet.


Commercial QC Software

Click here to access a quick guide to settings/preferences for Adobe Bridge.

Other QC Documents

File:Box and folder check procedure.docx

Personal tools