You run the 'Issue labels' update for an audited publication exactly as you would for a non-audited publication. Click here for instructions on the 'Issue labels' update.
For an audited publication the 'Issue labels' update automatically reclassifies non-paid qualified subscribers who are more than three years old. For ABC or BPA-audited business publications they are changed to "Nonqualified other". For VAC-audited publications they are changed to "Non-paid association". ABC audited magazines have slightly more relaxed rules: only verified individual request subscriptions (VI with request type INR), and NPI (non-paid individual), NPL (non-paid list source), NPA (non-paid association) and NPM (non-paid club membership) subscriptions are subject to reclassification under the three year rule. QuickFill determines the qualification age of a subscriber based on the difference between the calendar date of the current issue and the subscriber's qualification date. Click here for more information on the qualification date.
For BPA and VAC audited publications QuickFill does not serve grace issues to controlled subscriptions or PB (Paid Bulk) subscriptions. For ABC audited publications it does not serve grace issues to controlled subscriptions, PB (Paid Bulk) subscriptions or PS (Paid Sponsored) subscriptions.
The labels produced by the 'Issue labels' update for an audited publication are the same as for a non-audited publication with one exception. Even if you choose to include the expiration date on the publication definition issue labels tab, the labels for controlled subscriptions do not include the expiration date because you don't want controlled subscribers to know when their subscription expires. If subscribers know that a subscription won't expire for another two years, they are less likely to respond to your requalification efforts.
In addition to producing labels, the 'Issue labels' update also produces a galley data file for each audit issue. The galley file's name is made up of the database name, publication code, and issue number. For example, if your audit issue for publication code WIDGET in the standard QuickFill database (that is the database files are named QFWDB*.QFDAT) was issue #144, the galley data file would be named QFWDB_WIDGET_0144.QFDAT.
The galley data file is located in the database directory. This file should not be deleted. If it is, you will not be able to run the 'Audit issue galley' report for the issue associated with the file; this file makes it possible for a test selection to be created for your auditor. (Click here for details on the 'Audit issue galley' report. )
QuickFill does allow you to generate a galley file in case of loss or damage to the original file, but it is always best to work with the original. Any changes in the database since the audit issue was run may be reflected in the reconstructed galley data file. In the event that the galley data file is lost or damaged, you should first back up your current database, then restore your database and galley data file back to a point before the galley data file was deleted or damaged.
The 'Issue labels' update also uses the "last update" date and time in the issue table to ensure that the audit issue galley data file matches the database. If you serve additional copies for an audit issue after the initial update, the 'Issue labels' update scans the galley data file to make certain that the number of copies reported therein matches the number of copies reported in the issue table.
QuickFill will automatically resynchronize and truncate the galley data file if the 'Issue labels' update fails and you restore your database, but do not restore the galley data file. (This assures that the contents of the galley data file return to what they were before the failed update.)
On rare occasions the 'Issue labels' update will refuse to run and the label update report will contain a message to the effect that the galley data file does not match the database. The following situations could cause this to happen: the galley data file has been altered or deleted; the galley data file was created from a prior version of QuickFill and was not updated to the version you are currently running; you restored your database and for some reason only a partial restore was done or you restored from a bad backup; your database is corrupt; or there is a bug in QuickFill. In the event that the galley data file does not match the database, contact Technical Support for instructions.
Click here for information on audit system procedures.