ALRS Implementation

From PTAGISWiki

Contents 1 Objectives 2 The Road Map to Implementation 2.1 Identify Location definitions 2.1.1 Tag/Release/Recovery Sites 2.1.2 Interrogation Sites 2.2 Identify definition anomalies and ambiguities 2.3 Resolve definition anomalies and ambiguities 2.4 Identify dependent functions 2.4.1 P3 Validation 2.4.2 FDVL Validation 2.4.3 IDL Validation 2.4.4 IDL Operations/Scheduling 2.4.5 Other Interrogation Processes 2.4.6 Other Interrogation activities 2.4.7 QB Drop-down menus? 2.4.8 SiteScape Site menus? 2.5 Populate ALRS 2.6 Incorporate functionality 2.7 Transfer functionality 2.8 Uncouple existing structures (xfer to backup tables) 2.9 Verify functionality 2.10 Remove backup tables 3 See Also

Objectives

• Consolidate all PTAGIS activity location definitions in a common set of database structures.
• Use a standard set of tools and conventions to populate and maintain the location definitions.
• Use the ALRS data definitions to support all existing location-related functions and references in the PTAGIS database.
• Develop new or expanded funtions and references to the ALRS data definitions in the PTAGIS database, through the PTAGIS Web Portal, and in the various PTAGIS client software applications.

The Road Map to Implementation

Identify Location definitions

Tag/Release/Recovery Sites

     ptagis3.rkm
     ptagis3.valid_tbl (domain='HATCHERY')
     ptagis3.master_intra_dam_release_sites (contains the templates used to flesh out new definitions)

Interrogation Sites

     ~pittag/etc/sites
     ptagis3.site
     ptagis3.valid_tbl (domain='OBS SITE')
     ptagis3.Obs_Site_Definitions (subset of sites active on or after 1/1/1998)

Identify definition anomalies and ambiguities

Resolve definition anomalies and ambiguities

Identify dependent functions

P3 Validation

     Hatchery Domain
     Tag-only Sites
     Fixed Release Sites

FDVL Validation

     data from rkm.ptagis3
     data from valid_tbl.ptagis3???

On Tuesday, you asked if I'd look at FDVL and determine what use(es) it
makes    of the 'rkm' and 'valid_tbl' tables. A quick review of the code
turned up the following: 

1. fdv_checkConformity.pl reads a number of flat-files to obtain validation data

2. The validation flat-files are generated by util_genInitFile.pl

3. The following are retrieved from the 'valid_tbl' table
   CaptureMethodCodes.txt (CAPTURE METHOD domain)
   Coordinator_ID.txt (TAG COORD domain)
   HatcheryCodes.txt (HATCHERY domain)
   MonitoredReleaseCodes.txt (MONITORED RELEASE domain)
   OrganizationCodes.txt (ORGANIZATION domain)

4. The following is retrieved from the 'rkm' table
   RelSite_RiverKM.txt

IDL Validation

     ?

IDL Operations/Scheduling

     ?

Other Interrogation Processes

     MiniMon
     MultiMon
     CEA
     ADE
     DGE
     TASS
     STA

Other Interrogation activities

     ptagis3.Obs_Site_Dates
     ptagis3.Obs_Site_Interruptions
     ~pittag/etc/sites
     Event logs

QB Drop-down menus?

SiteScape Site menus?

Populate ALRS

Incorporate functionality

Transfer functionality

Uncouple existing structures (xfer to backup tables)

Verify functionality

Remove backup tables

See Also

Alrs
ALRS_MR_Site_Categories