ALRS meeting
From PTAGISWiki
December 7, 2005
PSMFC Headquarters
Attendees: Doug, Dave, Ryan
Contents |
Agenda
- Powerpoint overview
- remind us about what ALRS is
- application walkthrough
- what the prototype webapp looks like and how to use it
- legacy maintenance
- how do we get the older apps that use valid_tbl and rkm to use ALRS?
Powerpoint overview
Looked at Doug's G2_ALRS_Overview from the PTAGIS forum. These tables are in every PTAGIS application: PTAGIS domain domain enumeration
Application walkthrough
Dave was unable to log in to the webapp. Firefox kept offering to download a weblogic internal mimetype. Have to manually switch to this URL after login and after some bad links
The code to guarantee referential integrity of the domains is not in place yet. The app consists of 9 java files and 5 jsp pages and is autogenerated from Ant and the meta-data tables. SpringMVC is also helpful. Searches are case-sensitive. We may want to define domains for several fields, including LatLongSource. This would make searching those fields easier. Some fields are too small for the data and would truncate existing data if an update were done.
Break for lunch
Add WFF Site
Walked through steps to add site with webapp to sockeye.
- Search to see if a site exists that can be modified for WFF
- one doesn't exist. Although the location for the midpoint of the
river segment is close. We'll create a new one.
- added location entry
- there are issues of precision and data type
- there are issues of field size and truncation
- added a new site type: ADULT FISHWAY
- added a location_in_segment entry
- question about the km_total field: is it a dotted-triplet or a single
integer representing distance to the mouth of the columbia? The metadata says single integer from segment base...
- added activity_location entry
- an issue with ActivityLocationDescription
Determined where the descriptive text for sites in the Flash menu comes from: activity_location:site_description. It would be nice if there was a short site descriptor field in this view that can be used for brief descriptions in the Flash menu.
Discussion of legacy issues
Maintenance of and sync with rkm table
- Who are the consumers of this information?
- What processes will need to be updated?
- Flash, P3, FDVL, MiniMon, MultiMon, CEA, ADE, DGE, TASS, STA
The fact that we are generating flat files from RKM makes it easy for us to migrate to ALRS for the data source.
Maintenance of valid_tbl
=== Maintenance of and sync with site configuration management schema
