The current MRR data model was implemented for production data submission in September 2016. The data model is centered around four types of potential data collection events: Mark, Recapture, Recovery, and Passive Recapture.
Event Definitions
|
Mark |
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. |
|
Recapture |
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. |
|
Recovery |
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. |
|
Passive Recapture |
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. 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 |
Data collection events are grouped together in a session which acts as a logical container for a set of records. All records in a session must be collected for the same PTAGIS MRR project and same purpose or scope, as described in the Session Message. A session could represent all fish encountered at a single site on a single day, or all fish encountered at multiple sites over any period of time, as best determined by the data collection and management protocols of each project. When a session is submitted to PTAGIS, it is transformed into a data file with a specific format and requirements. Once that file is processed, it is archived and retained in perpetuity as the base data source for the records in the PTAGIS database.
Within each session/file are one or more event records. Event records include the PIT tag code and set of data associated with the fish in which that PIT tag was implanted. Some fields are required, depending on the type of data collection event, and some are optional. Many of the fields have a controlled domain of values, called Validation Codes, to ensure that data collected across the Columbia basin region are compatible regardless of the organization collecting the data. Data collection event and release locations are also standardized across the basin and maintained in the MRR Site code domain. Validation codes and MRR sites are reviewed by the PIT Tag Steering Committee before being implemented in PTAGIS.
Version: 1.08
Published: 11/12/2024