Section 9.2.6 New Collection

Section 9.2.6 New Collection

Section 9.2.6                  Collections (Owned by Project Name)

It is suggested you create a Taxonomy before creating a Collection for a Project. Collections require a taxonomy before they are available for production. Please Refer to Configuration Management, Automation, Taxonomy for instructions on setting up a Taxonomy.

Section 9.2.6.1              Collection Name

Give your collection a name. It is best to make the name descriptive. For example, a department name or record type. This will make it easier for production personnel to select the correct collection.

Section 9.2.6.2             Project

The Project is selected by default when you create a collection from within a Project.

Section 9.2.6.3             Taxonomy

Select the Taxonomy you want applied to the records in the Collection.

Note: Regular expression rules and data extraction rules are now applied directly to the collection in Pipeline Settings or Workflow Settings (Section 9.2.6.7 and Section 9.2.6.8), not through the taxonomy. The taxonomy continues to apply Lists, Prompt Quality Issues, and PII Entities for Redaction. Regular expression and data extraction rules are defined in Section 10 Configuration Management, Automation.

Section 9.2.6.4             Description

Adding a description to your project is optional but does supply more information that could be helpful in the future.

Section 9.2.6.5             Hidden

You can hide a collection from production. This is useful when setting up a collection that you do not want users producing records in. You can complete the setup and when ready make the collection visible to end users

Section 9.2.6.6              Workflow

Select a workflow to assign to this collection. The Workflow field determines how image processing is organized and controls which settings tab appears on the Collection page.

When Workflow is set to — None —, the second tab on the Collection page reads Pipeline Settings. Images are processed automatically through all configured pipeline steps from ingestion through completion without pausing for operator review at any stage.

When a workflow is assigned, the second tab reads Workflow Settings. Processing pauses at each module defined in the workflow, requiring operators to review images before processing advances to the next stage.

Note: Workflows are configured in Section 10 Configuration Management. A collection can operate without a workflow assigned — the pipeline continues to function as it did before workflows were introduced.

Section 9.2.6.7              Pipeline Settings

The Pipeline Settings tab is available when no workflow is assigned to the collection. Use this tab to configure the processing functions that run automatically on all images in the collection.

Detect Barcodes — Reads barcodes optically from the captured image, as an alternative or addition to reading barcodes with the hardware scanner. Enabled by default; can be turned on or off.

Automatic Image Rotation — When enabled, WIB™ Review performs a best guess at which direction an image needs to be rotated based on the direction of the majority of the text on the image.

Rotation Text Percentage — The percentage of text on a page required to consider that text direction to be the orientation of the page. Default is 80.

Automatic Image Deskew — When enabled, straightens images that were scanned at a slight angle.

Identify Forms — When enabled, any forms present in images of the selected types will be identified.

Available Regular Expressions / Applied Regular Expressions — Assign regular expression rules to this collection. Move rules from the Available list to the Applied list using the arrow controls.

Available Data Extraction Rules / Applied Data Extraction Rules — Assign data extraction rules to this collection. Move rules from the Available list to the Applied list using the arrow controls.

Select Save to apply changes.

Section 9.2.6.8              Workflow Settings

The Workflow Settings tab is available when a workflow is assigned to the collection. Settings can be configured in either Design View or Wizard View — select Switch to Wizard View or Switch to Design View in the upper right to toggle between them. Design view displays all sections on a single scrollable page. Wizard view steps through each section individually using Back and Next controls. The wizard displays only the steps corresponding to the modules enabled in the assigned workflow.

Settings are organized into six sections:

1. Detect Barcodes

Reads barcodes optically from the image captured during collection, as an alternative or addition to reading barcodes with the hardware scanner. This step runs immediately before the Quality Compliance step. Enabled by default; can be turned on or off.

2. Quality Compliance


Automatic Image Rotation — When enabled, WIB™ Review performs a best guess at which direction an image needs to be rotated based on the direction of the majority of the text on the image.

Rotation Text Percentage — The percentage of text on a page required to consider that text direction to be the orientation of the page. Default is 80.

Automatic Image Deskew — When enabled, straightens images scanned at a slight angle.

Auto-Accept QC — When enabled, images with an AI quality score at or above the threshold are auto-accepted. Users only review images below the threshold.

Threshold — Sets the quality score cutoff for Auto-Accept QC. Range is 0–100.

3. Form Identification

Identify Forms — When enabled, any forms present in images of the selected types will be identified.


4. Index


Available Attributes / Attributes Requiring Data Entry — Move the attributes operators must enter by hand while indexing into the Attributes Requiring Data Entry list, using the arrow controls.

Image Types Requiring Data Entry — Select which image types require manual data entry during indexing. Leave this empty, or select All, to require data entry on every image type. Images of any other type are filtered out of the Index step entirely and are never presented for manual entry.

See Section 8.3 Index Module for the Batch Manager screen operators use to complete indexing.


5. Verification

Available Regular Expressions / Applied Regular Expressions — Assign regular expression rules to this collection. Move rules from the Available list to the Applied list using the arrow controls.

Available Data Extraction Rules / Applied Data Extraction Rules — Assign data extraction rules to this collection. Move rules from the Available list to the Applied list using the arrow controls.

Auto-Accept Verification — When enabled, images whose worst per-attribute extraction score is at or above the threshold are auto-accepted. Users only review images with at least one attribute below the threshold.

Threshold — Sets the extraction score cutoff for Auto-Accept Verification. Range is 0–100.
















6. Export

Export is always enabled.

Select Save to apply changes.


Section 9.2.7                          Add Tags to a Collection

After a collection is created, you can add tags for the Review process. Select the Tags tab, then click the Add Tag button to add a user-defined tag. Tags consist of a name, description, Tag Color, and Text Color. These tags are then available to users as a drop-down menu on the Tag Tile during Review. Tags will appear in Review with the same tag color and font color defined under the Collection.











Section 9.2.8                 Add Attributes to a Collection

Add the attributes for the Collection. Attributes can be filtered to include only those applicable to the Collection. Go to the Attributes tab on the Collection Page and select Add Attributes. Select each attribute that will be used for the collection of data extraction.


Section 9.2.9                 Define Hierarchical Capture

Hierarchical Capture allows the export to identify images that are associated. There are 3 levels available: Container, Parent, and Child. Drag images are associated with the Container to the Container level, images that are Parents and their associated Child images. Below is a typical Hierarchical Capture definition.

Content Type Definitions allow for identifying the Hierarchy for exporting the Metadata in XML format. For each image type, the user can define the Content Type, which is included in the XML at the Container and Parent nodes. Below is a standard Content-Type Definition.

      

Section 9.2.11                 Reference Collections (Roadmap)

Reference collections managed by another project can be added to any project. The billing is associated with the original Project. This allows departments and later projects access to records without exporting, importing or reprocessing records.