Specifications
Table Of Contents
- Overview
- Configuration
- Configuration Profiles
- General Profile Settings
- Configuring Devices
- Activating Tag Actions
- Validation Constraints
- Audible Alert Sound Events
- Data Collection and Validation
- Importing and Exporting
- Tools
- Tag Actions
- Tag Action Manager
- Tag Action Settings and Commands
- Tip: the Replace command will import tag codes much faster than the Import command. Use the Import command only when appending a relatively small number of tag codes (less than 25k) to a tag action.
- Tip: the Delete All and Replace commands will generate a lot of empty space in the P3 database. We recommend running the Compact and Repair utility after running any of these commands to optimize the database.
- Tag Actions and Data Entry
- Digitizer Maps
- Searching Data
- Replacing Data Values
- Merging Tag Sessions
- Dot-Out Wizard
- Remove Dot-Outs
- Duplicate Viewer
- Validation Codes
- Database Maintenance
- Tag Actions
- Appendix
- Frequently Asked Questions
- Hardware Support
- Troubleshooting Common Tag Reader Problems
- Troubleshooting Common Digitizer Tablets Problems
- Digitizer Tablet Doesn't Register Pen Clicks
- WinTab Digitizer Tablet Won't Communicate with a PC
- ASCII Digitizer Tablet Won't Communicate with a PC via Serial Port
- Digitizer Tablet doesn't Communicate with P3
- Digitizer Tablet is Sending the Wrong Commands
- Digitizer Tablet is Sending Wrong Lengths
- Digitizer Tablet Hangs P3 when Connected via Baytech Multiport
- Operating the Destron 400 kHz Benchtop Tag Reader
- Configuring Calcomp Drawing Board III
- Index
Data Collection and Validation
43
There are 50 columns available to record Text Comments, a free-form
annotation pertaining to the existing detail record. Data can be entered from
a keyboard and recurring phrases can be entered from a digitizer command.
Tag Detail Validation
P3 performs a number of validation and verification routines on every processed Tag
Detail Record. There are field-level routines that ensure that the entered data
matches the expected format, and that the content is present within domains of
values. There are record-level routines that verify that all required fields within the
record contain data values. There are also session-level routines that address
contingencies such as duplicate Tag Codes between Tag Detail Records, Variable
Release Time code declarations without corresponding assignments, and the
appearance of unexpected Tag Codes in a Tag Session. These various methods of
data validation and verification are described in the sections below.
Field-Level Validation
The following detail record fields perform field-level validation and format checking:
Tag Code
Only hexadecimal characters (0-9;A-F) can be entered into
this field, with the exception of a period in the fourth
character position (denoting a country code prefix). This
field allows two styles of tag codes to be entered: a 10-
character hexadecimal code or a 14-character hexadecimal
code with a period in the fourth position. Once a valid code
has been entered, the field is locked to prevent accidental
typos. Only a dot-out command
can overwrite a valid tag
code once it has been entered.
When a tag code is entered, either by device or keyboard,
P3 performs a lookup into any activated actions
. A device
action may also fire when a tag code is entered from a
device.
Length
Only numeric characters can be entered into this field.
Weight
Only numeric characters, and a decimal point, can be
entered into this field. The field will automatically round any
weight input to a tenth of a gram.
VRT
Only numeric characters can be entered into this field, with
values between 00-99 inclusive; input will be zero padded
to two digit values.
Conditional
Comment
This field accepts valid conditional flag codes. The codes can
be typed in or selected from the drop-down list. This field
will automatically remove duplicate flag codes and format
multiple flag codes to be delimited by a single space.