Differences
This shows you the differences between two versions of the page.
— |
phelp:helpbatchreports [2021/12/29 16:21] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | BATCH REPORTS | ||
+ | The 'Batch Reports' | ||
+ | |||
+ | Notes | ||
+ | |||
+ | In version 247, a number of options were added requiring the addition of a second options form for batch mode. This form is launched by pressing "More display/ | ||
+ | |||
+ | Also in 247, the following three options previously found on the main Batch option page have been moved to the new 'More options' | ||
+ | Include Tag Occurrence numbers, | ||
+ | Add Message Ids to Notes, and | ||
+ | Show Full Pathnames of ' | ||
+ | |||
+ | |||
+ | REPORT ORGANIZATION | ||
+ | |||
+ | There are two ways to organize a Batch Report: 'By Record' | ||
+ | |||
+ | 'By Record' | ||
+ | |||
+ | 'By Problem' | ||
+ | |||
+ | REPORT DISPLAY OPTIONS | ||
+ | |||
+ | There are three types of displays that are available in a Batch Report: ' | ||
+ | |||
+ | ' | ||
+ | |||
+ | 'Brief Message' | ||
+ | |||
+ | 'Full Message' | ||
+ | |||
+ | CONTROL NUMBER | ||
+ | |||
+ | In the ' | ||
+ | |||
+ | Note: If this field is set to a tag that is not present in a record, the program will (attempt to) display the contents of the 001. Also, if you specify a variable field and forget to specify a subfield (i.e. ' | ||
+ | |||
+ | DISPLAY MARC FIELD | ||
+ | |||
+ | The default is to not display MARC data. To display the data from the MARC field that is being reported as a problem, check the ' | ||
+ | |||
+ | TAG AND MESSAGE FILTER | ||
+ | |||
+ | This filter is applied against the brief messages that the program returns when it validates a record. It behaves in exactly the opposite way as the Cancelled Message feature--it returns only messages that MATCH the filter, and discards all others. | ||
+ | |||
+ | The purpose of this filter is to make it easy to target specific problem areas without having to perform major surgery on the cataloging check options--whether the objective is simply to review/ | ||
+ | |||
+ | In its simplest case, if you specify a single tag (for example, ' | ||
+ | |||
+ | LIST OF TAGS | ||
+ | |||
+ | In addition to single tags, this filter also accepts multiple tags separated by commas: | ||
+ | |||
+ | Example: 600, | ||
+ | |||
+ | Do not enter a blank space after the commas. | ||
+ | |||
+ | This filter also accepts tag ranges, and XX-tag specifications: | ||
+ | |||
+ | Example: 600-651 | ||
+ | Example: 6XX | ||
+ | | ||
+ | And you can bundle all of the above in a single filter: | ||
+ | |||
+ | Example: 1XX,700-710 | ||
+ | |||
+ | MESSAGE STRINGS | ||
+ | |||
+ | The ' | ||
+ | |||
+ | 100: Subfield $e value is not RDA | ||
+ | 700: Subfield $e value is not RDA | ||
+ | 700: Subfield $i value is not RDA | ||
+ | 710: Subfield $e value is not RDA | ||
+ | etc. | ||
+ | |||
+ | This makes it easy to find all messages with the same problem, even though they are in different tags. | ||
+ | |||
+ | Another good example of this type of filter would be to find all messages reporting a problem with character encoding; to achieve this objective, one would simply enter the phrase ' | ||
+ | |||
+ | Strings are not case-sensitive, | ||
+ | |||
+ | Occurrence specifications are ignored when matching brief message strings. So if you enter | ||
+ | 700: Subfield $e value is not RDA | ||
+ | it will match the following brief messages | ||
+ | 700-01: Subfield $e value is not RDA | ||
+ | 700-02: Subfield $e value is not RDA | ||
+ | but not this one: | ||
+ | 710: Subfield $e value is not RDA | ||
+ | |||
+ | Beginning in version 250, multiple strings can be combined if they are separated by a fill character, eg.: | ||
+ | needs matching 00|needs matching 33|value is not rda | ||
+ | |||
+ | MESSAGE IDS | ||
+ | |||
+ | Also, beginning with version 246 of MARC Report, the ' | ||
+ | 47000002, | ||
+ | This makes it possible to target a very specific error message or messages. | ||
+ | |||
+ | NOTES | ||
+ | |||
+ | If you want to mix message Ids and message strings in the same filter, be sure to use ' | ||
+ | 47000002|value is not rda|47600004 | ||
+ | |||
+ | It is easy to set up something like this in the options and later forget that you have done so. For this reason, when you start a Batch Mode run and the program finds a 'Tag filter' | ||
+ | |||
+ | The functionality of this filter is also available inside an Edit session--for more information, | ||
+ | |||
+ | MARC FILE OUTPUT | ||
+ | |||
+ | There are two types of MARC file output available in a Batch Report run: 'Write records with errors', | ||
+ | |||
+ | Click 'Write Records With Errors' | ||
+ | |||
+ | MARC FILENAMES | ||
+ | |||
+ | Default names for each of these two MARC files described above can be specified in the edit boxes below. The program will write these files in the Batch Reports directory (which is set under the File and Directories tab). | ||
+ | |||
+ | ASSORTED PROCESSING OPTIONS | ||
+ | |||
+ | IGNORE RECORDS WITHOUT ERRORS | ||
+ | |||
+ | Check this box if you do not wish the reports to list records without errors. | ||
+ | |||
+ | NOTE: This option affects only the report itself. Checking this option will not affect the statistics produced by MARC Report, nor will it cancel the writing of good records to a MARC file when running the Split Option for MARC Output. | ||
+ | |||
+ | AUTOMATICALLY GENERATE REPORT FILENAME | ||
+ | |||
+ | If this option is selected, which is the default, the program will automatically generate a unique filename and proceed directly to the Batch Mode task. When the run completes, either the name of the report file, or the report itself, will be displayed, depending on the setting of the next option. If you want to set the name of the report file before Batch Mode begins, then disable this option. | ||
+ | |||
+ | NOTE: The format of the automatically generated filename is as follows: | ||
+ | |||
+ | marcrept-771701.txt | ||
+ | |||
+ | where ' | ||
+ | |||
+ | AUTOMATICALLY SHOW REPORT ON COMPLETION | ||
+ | |||
+ | If this option is selected, which is the default, the program will automatically try to open the report when Batch Mode completes. The report will be opened in whatever program you have associated with the .txt file type (Notepad by default). If this behavior causes problems, then you should disable this option and see if the problems go away. | ||
+ | |||
+ | AUTOMATICALLY GENERATE REPORT SUITABLE FOR EXCEL | ||
+ | |||
+ | If this option is selected, a second version of the report will be created using the row and column format generally associated with programs that support tables, like Excel, but equally amenable to any SQL software. For details on configuring this output, vist the "More display/ | ||
+ | |||
+ | |||
+ | LIMITATIONS AND SUGGESTIONS FOR VERY LARGE FILES | ||
+ | |||
+ | In 'By record' | ||
+ | |||
+ | In 'By Problem' | ||
+ | |||
+ | When the program reaches the point where all memory is exhausted, it should display an exception message that tells the user the number of the last record that was validated. If this happens, split the file into smaller pieces--using the Split utility--and then run batch mode on each piece. | ||
+ | |||
+ | Also note that--even in 'By Record' | ||
+ | |||
+ | Therefore, when running batch mode on very large files, turn off messages for problems you are not interested in, because the configuration of the validation and cataloging checks have a direct impact on the number of messages generated. For example, start a batch mode run on your file, then interrupt after processing 100,000 records or so, and look at the results. There are probably large numbers of items that you are not interested in (such as obsolete indicator messages, local tag conventions, |