Laserfiche WebLink
Susan Lesovsky will provide technical support for linking the web application to the CWCB <br />document management system LaserFiche. <br />Priorities for data collection should account for software development dependencies, i.e., if <br />development of a specific feature requires specific data for testing, the data should be available at <br />the time the feature is implemented to avoid the need to generate fake data. <br />Sharing data between the Flood DSS Map Viewer and the CDSS Map Viewer may be difficult <br />because each application is implemented with a different server technology (ArcGIS Server and <br />ArcIMS, respectively), the data are stored on two separate servers, and the servers exist on <br />different network domains. <br />Task 10 -Training and Documentation <br />Riverside recommended that perhaps a smaller group of users could be trained with an <br />early version of the system to accelerate adoption of the system into operations for a core <br />group, thus allowing for feedback and ultimately facilitating sign-off on deliverables. <br />CWCB staff supported the recommendation, but this will be revisited later in the project. <br />The point was made again by Ray Alvarado that clear documentation needs to be <br />provided to facilitate maintaining and operating the system. Steve mentioned the <br />Instream Flow DSS documentation, which provides detailed information on setting up the <br />system and updating system components, including data layers. <br />Susan suggested that on-line help be considered for Flood DSS. <br />Task 11 -Evaluation <br />It was agreed that ongoing evaluation is important and will help resolve system issues <br />(e.g., differences between development and deployed environments, CWCB network <br />problems). <br />Interim review meetings could occur via conference call, in conjunction with progress <br />meetings, or visits to Denver. <br />Feedback to Riverside is welcome at all times and will be categorized and prioritized <br />relative to the scope. <br />Performance Measures <br />Project team needs to develop and provide quantitative performance measures. <br />For example, to evaluate usability, pick several key users and indicate the system is <br />"highly usable" when the users provide feedback that it is so. Although this is subjective, <br />it narrows the feedback. <br />