ALRS MR Site Categories

From PTAGISWiki

This document describes the various format constraints and business rules for each of the categories of PIT tag Mark/Recapture locations defined in the ALRS schema. In this context, "Recapture" includes mortality events, but excludes interrogation (passive detection) events. If and when interrogation site locations are added to this discussion, the "Mark/Recapture" nomenclature must be modified to "Mark/Recovery".

Contents 1 General Business Rules 2 Mark/Recapture Categories 2.1 Dam 2.1.1 Format Mask 2.1.2 Business Rules 2.2 Intra-Dam Release (IDR) Site 2.2.1 Format Mask 2.2.2 Business Rules 2.3 Hatchery 2.3.1 Format Mask 2.3.2 Business Rules 2.4 Acclimation Facility 2.4.1 Business Rules 2.5 Linear Waterbody (Stream, River, etc.) 2.5.1 Format Mask 2.5.2 Business Rules 2.6 Fixed Waterbody (Lakes, etc.) 2.6.1 Format Mask 2.6.2 Business Rules 2.7 User-defined Site (e.g., instream trap, weir, etc.) 2.7.1 Format Mask 2.7.2 Business Rules

General Business Rules

• Unless explicitly noted differently, the Mark/Recapture location is a release site.
• A location denoted as 'tag-only' is not a release site.
• A location that is a release site is also a tagging site.

Mark/Recapture Categories

Dam

Format Mask

• A Dam code has a mask of exactly three (3) characters.

Business Rules

1. A Dam is a tag-only location. Any release/recapture/mortality events at a dam are tied to one or more specific Intra-Dam Release (IDR) Site codes.
2. A Dam is a fixed-site location. However, this attribute is masked by the "tag-only" status assigned to the dam.
3. A Dam has a specific Dam_ID identifier referencing a single entry in the StreamNet Dams table.

Intra-Dam Release (IDR) Site

Format Mask

• An IDR Site code has a mask of exactly six (6) characters, consisting of a 3-character dam code and a 3-character intra-dam location suffix (IDLS).

Business Rules

1. An IDR Site is derived from an existing dam definition.
2. An IDR Site is derived from an existing IDLS definition.
3. An IDR Site is a fixed-site location.
4. An IDR Site inherits its lat/lon coordinates from its parent dam. (Does it also inherit the parent Dam_ID?)

Hatchery

Format Mask

• A Hatchery code has a mask of exactly four (4) characters.

Business Rules

1. A Hatchery can be either a tag-only or a release location. (Identify the first case as 'Hatchery only'?)
2. A Hatchery is a fixed-site location.
3. A Hatchery has a specific Hatchery_ID identifier referencing a single entry in the StreamNet Hatcheries table.
4. Only an entity in the Hatchery domain can populate the hatchery field in the ptagis3.tag_hdr table.

Acclimation Facility

• An Acclimation Facility code has a mask of either five (5) or, preferably, six (6) characters.

Business Rules

1. An Acclimation Facility is a fixed-site location.
2. An Acclimation Facility has a specific Hatchery_ID identifier referencing a single entry in the StreamNet Hatcheries table.

Linear Waterbody (Stream, River, etc.)

Format Mask

• A Linear Waterbody code has a mask of either five (5) or, preferably, six (6) characters.

Business Rules

1. A Linear Waterbody is not a fixed-site location. This is the only category that allows a suffix to be appended to the Release_River_KM value associated with each location code.
2. A Linear Waterbody has a specific Location_ID identifier referencing a single entry in the StreamNet Waterbodies table.

Fixed Waterbody (Lakes, etc.)

Format Mask

• A Fixed Waterbody code has a mask of either five (5) or, preferably, six (6) characters.

Business Rules

1. A Fixed Waterbody is a fixed-site location.
2. A Fixed Waterbody has a specific Location_ID identifier referencing a single entry in the StreamNet Waterbodies table.

User-defined Site (e.g., instream trap, weir, etc.)

Format Mask

• A User-defined Site code has a mask of either five (5) or, preferably, six (6) characters.

Business Rules

1. A User-defined Site is a fixed-site location.