Section 11.1.1.5 Errors

Section 11.1.1.5 Errors


Section 11.1.1.5             Errors

Sessions and/or boxes with errors that prevent the ingestion of the images in the workspace are shown in the error grids. Sessions that have not received a log file will be listed in the sessions grid, and those boxes without a box log file will be listed in the boxes grid. Radix Data support will monitor any errors created by an operator error. Some operator errors include, but are not limited to, exiting the Capture Program before all content is uploaded or shutting down the WIB™ Unit while the Capture Program is still running.

Section 11.1.1.5.1                 Set Expected Box Count

Setting the expected box count allows for reconciling sessions that have a deleted box, sessions where the box barcode was scanned more than 1 time in the session (before Release 1.0.11 Nov-27-2024), corrupt zip files that require reprocessing, etc.

Section 11.1.1.5.2                Resolve Errors

The ‘Resolve Errors’ function allows the reconciliation of sessions that are missing zip files. This static table has new records written in the table, but requires a support technician to resolve. This allows the support technician to update the item(s) as resolved by setting the status and removing them from the list of errors.

Section 11.1.1.5.2.1                        Sessions without Log Files

A complete session should always include a log file. Sessions that are in progress will not include a logfile until they are completed. Sessions Missing Zip files

Section 11.1.1.5.2.2                        Sessions Missing Zip files

A complete session should always have a zip file count that matches the number of zip files reported in the session's logfile.

Section 11.1.1.5.2.3                     Exception Zip files

The scanner apparatus will upload zip files that it has identified as having issues.

Section 11.1.1.5.2.4                     Loose Zip files

Something may go wrong during the initial cataloging of an uploaded zip file. Those zip files will show up here.

Section 11.1.1.5.2.5                     Empty Boxes

The scanner apparatus will upload zip files that it has identified as having issues. Empty Boxes are automatically resolved. This is to clear any historical boxes that may have been uploaded without images.

Section 11.1.1.5.2.6                     Solr Missing Records

Boxes that exist in SQL but have records missing from the Solr search index. Expand a box to see which images are missing. You can select each record individually or all the boxes missing a record in the Search Database (Solr) and ‘Rebuild Attributes’ to get the missing records into the Search Database. This table is populated nightly. If you are looking for missing records on the same day of capture, you can ‘Check for Missing Records’.

Section 11.1.1.5.2.7                     Box Zip file Pipeline Stuck

Boxes where a pipeline step started but never completed. Select rows and use Re-run Selected to restart from the stuck step. This table is populated nightly. If you are looking for missing records on the same day of capture, you can ‘Refresh’.



    • Related Articles

    • Section 11.1.1.2 Boxes

      Section 11.1.1.2 Boxes The Boxes Section gives management a high-level view of boxes uploaded to the workspace in a grid. The following information is available for each box: Identifier – unique identifier for the box, usually the barcode Project ...

    • Section 10.2.4 Workflow

      Section 10.2.4 Workflow The production Workflow is a structured sequence of tasks designed to ingest, organize, and manage incoming sessions of boxes and the content into the WIB™ Review Web Application. WIB™ Review organizes the tasks into Modules ...

    • Section 11 Data Management

      Data Management Data Management allows administrators to watch sessions and keep data synchronized with changes to the configuration by rebuilding data at various levels. Section 11.2 Data Management Monitoring Levels Data Management is organized by ...

    • Section 11.1.1 Monitor Upload Status

      Section 11.1 Data Management Monitoring Levels Data Management is organized by Levels in a Workspace. In a Workspace there are Project, Collections, Sessions, Records, Images and lastly attributes that make up the index of a record. Data Management ...

    • Section 6.9 Action Feature Set - QC Tags

      Section 6.9 Action Feature Set Action features either elicit an action or call for an action to be taken. Elicit actions include tags and notes, where a QC Tag is a call to action. There are two (2) types of QC Tags: automated and user-defined tags. ...