Creating a new batch job (Production Mapping)
Batch jobs can be created in the Batch Job Manager. You can create groups in which you can store checks that apply to different aspects of your database. For example, in one group, you can have checks that are used to validate the domains and subtypes for a specified feature class, and in a different group, checks for geometry that overlaps. Checks and check groups can be reordered by clicking and dragging the check names.
Checks can be duplicated so you do not need to individually configure a check if you want to include it more than once in a batch job. This allows you to easily choose the feature classes on which to run the check.
You can also insert a batch job into another one. This can be accomplished by opening one check and inserting another.
- Start ArcMap.
- On the main menu, click Customize > Toolbars > Data Reviewer.
-
Click the Reviewer Batch Job Manager button on the Data Reviewertoolbar.
The Reviewer Batch Job Manager dialog box appears.
-
Right-click the Batch Job Contents area and click New Group.
A new group appears in the field.
- Click the group name to make it editable.
- Type a new name for the group and press ENTER.
-
Right-click the group, point to Add Check, point to the category that contains the check to be added, then click the check name.
The check's properties dialog box appears.
- Configure the parameters for the check.
- Click OK.
- Repeat steps 7–9 for each check to be included in a group.
- Repeat steps 4–6 for each group to be added for a batch job.
-
When you are finished creating groups and adding checks, click Save As.
The Save As dialog box appears.
- Type a name for the batch job in the File name text box.
-
Click Save.
The Reviewer Batch Job Manager dialog box appears.
- Click OK.
If you configure your session to use default checks, such as Invalid Geometry, do not manually add those same default checks to your batch job.
It is recommended that you validate a selection set or current extent when the number of features to validate in that set or extent is much smaller than the total number of features in the containing feature class. If the selection set size or current extent encompasses or nearly encompasses the entire feature class, it is more efficient to validate using the full database option.
Duplicate checks judiciously. The Duplicate Check Generator validates neither WHERE clauses nor the error conditions.
When updating a batch job using the Set Data Source dialog box, the Apply to all matching datasets option only updates those that have a valid matching dataset in the new workspace. Thus, if the new workspace lacks a particular table, the check referencing that table will not be updated.