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

P3 Help
32
confusion about what information is saved when the Accept command is pressed
and any validation error messages will remain within the context of the Tag Session
Header.
Tag Session Header Field Reference Guide
This topic provides a reference guide for all session header fields. Please consult the
current PIT Tag Specification Document
if you have further questions about these
data fields.
Header Field Content Mandatory/Optional
Tag Date
MM/DD/YY hh:mm Mandatory
This field records the date the tag data was collected. The default value for
this field is the current system date and time.
When the tag session contains records of PIT tag releases or
recaptures/mortalities collected over multiple days then, by convention, the
Tag Date field should contain the first day of sampling effort. Under these
circumstances, the Release Date field (see below) should reference the last
day of sampling effort, the actual dates of PIT tag release/recovery should be
denoted using Variable Release Times
, and the procedure should be
documented in the Session Header Note
.
This field can be modified using the keyboard. If the field is in edit mode,
then pressing the Control and Semi colon keys simultaneously will insert
the current system date and time; pressing the F4 key will display a
calendar.
Tag File
xxxYYDDD.zzz Mandatory
This field combines the Tag File Prefix
(xxx) in the active profile with the date
from the Tag Date field, in a Julian format (YYDDD). This field can't be edited
directly, but changes in the Tag Date field will be automatically reflected in
the Tag File field.
The user must assign a one- to three-character Tag File Extension (zzz).
Extensions should be chosen and applied to ensure that Tag File names are
not duplicated anywhere within the Columbia Basin.
This value is used as the default tag session name
.
Session Message
Text Optional
The Session Message field contains an optional description or summary of
the tagging session. This information is displayed in many PTAGIS reports,
and should concisely describe the tag project.
Tag Site
[Valid Tag Site] Mandatory