|
Event Types |
|
The Event Type field must be completed for each record in a session and is required to be completed during data entry before the record can be saved. Records with different Event Types have different requirements for what makes a complete record. Please see the MRR Field Definitions and Requirements table for a complete list of P5 data fields and their requirements by each Event Type. Alternatively, you can view the requirements for each event type by following the hyperlinks in the table below.
|
The event during which a fish is initially marked with a PIT tag and released (or planned to be released). Only one mark event is allowed for each PIT tag code. If additional mark events are submitted for the same PIT tag code, they will be categorized as Mark Duplicates during the loading process. |
|
|
The event during which a previously PIT-tagged fish is recaptured, scanned by hand, handled and released (or planned to be released). Multiple recapture events are allowed for each PIT tag code as long as the Event Dates are different. If an additional recapture is reported with the same Event Date of a previously reported recapture for the same tag, it will be categorized as a Recapture Duplicate during the loading process. |
|
|
The event during which a previously released PIT tag is recovered from or detected in a dead fish, or is recovered or detected as a bare tag, or is removed from the possibility of being recaptured or detected in the future. Multiple recovery events are allowed for each PIT tag code as some PIT tags, while obviously no longer in a living fish, may be detected multiple times without a physical recovery (e.g. carcass surveys, avian nesting sites). A recovery event that is reported for the same PIT tag with the same Event Date as a previously reported recovery event will be classified as a Recovery Duplicate during the loading process. |
|
|
The event during which a previously PIT-tagged fish is detected by unattended or remotely operated detection equipment at a location other than an interrogation site and is not handled. It differs from a Recapture event in that the fish is not handled, only detected. It differs from an interrogation record in that the detection occurs opportunistically in a location that is not a registered interrogation site. Multiple passive recapture events are allowed for each PIT tag code as long as the Event Dates are not the same. |
|
|
The event during which an un-tagged fish is sampled or counted without being marked with a PIT tag. Tally events must have 10 dots as the PIT tag code and will be ignored when submitted to PTAGIS for loading. |