Laserfiche WebLink
Active Server Pages (ASP). The existing CWCB web site uses a simpler implementation <br />with static HTML pages. Links to the Content Manager system are available from the <br />CWCB system, using a variety of combinations of user input. It is understood that the <br />CWCB is planning to update its web site but RTi is not aware of details. It is envisioned that <br />non - spatial data will be accessible via one or more of the following options: <br />• "Simple" static links on the CWCB web site pointing to content on the web server. In <br />this case pages will need to be enabled to list available data and data will need to be <br />organized on the web site. This approach may be appropriate in some cases but will not <br />be appropriate for a large number of documents. This approach may be appropriate for <br />the prototype if the other options cannot be implemented using available tools. <br />• Use a database to help manage content, similar to the DWR site. This approach is <br />desirable because content can be added to the database without updating static pages. It <br />is not clear whether the DWR site could also serve CWCB flood documents or whether <br />the DWR design could be adapted for the CWCB web site. This approach should be <br />discussed during the kickoff meeting. <br />• Utilize Content Manager or other document management software for all or the majority <br />of non - spatial data. The existing CWCB web site has an interface for the Content <br />Manager and RTi has implemented a link from the ISFDSS software to Content Manager. <br />The inventory task of the project will identify the amount of non - spatial data that is <br />available in Content Manager. <br />RTi will evaluate whether one of the above approaches can satisfy the requirements of the <br />Flood DSS and will implement access to enough data suitable to demonstrate the prototype. <br />The web site will allow direct access to documents and other files, without the map interface. <br />Deliverable Non - spatial data necessary to support the Flood DSS will be organized in a file <br />or database structure available on a web site, as necessary to support the prototype. All or a <br />subset of non - spatial data in the inventory will be used, based on initial review and in order to <br />demonstrate prototype features. All files necessary to support the web site will be provided <br />to the State as part of the prototype delivery. <br />Implement Map Links to Non - Spatial Data. The existing CDSS Map Viewer provides <br />links to secondary data by embedding hotlink information in spatial data attributes. This is an <br />effective way to link the map to other web site pages. Currently, links from the map point to <br />ASP pages with dynamic content that is formatted on the fly. For example, links to stream <br />gage data contain the gage identifier, which is used to query the database and format pages. <br />The previous item listed several options for managing and accessing non - spatial data on the <br />website. To provide a link from the map interface, some unique identifier must be available <br />to find the documents. Typically this identifier is a location identifier. RTi will evaluate the <br />link between the spatial data layer and secondary data for each major data type and will <br />implement features at a prototype level to illustrate how the link could be implemented for all <br />data in an operational system. If spatial data are not available for some data types, layers will <br />be created showing locations of studies and other data. Links to static data products (e.g., <br />reports, floodplain model data sets) will be provided as hotlinks from map layer attribute <br />data. The number of layers that are linked in this way will be evaluated during the inventory <br />task. <br />Deliverable The ArcIMS web site application and related data will be configured to <br />demonstrate links to non - spatial data, as defined in the data inventory. All files necessary to <br />support the web site will be provided to the State as part of the prototype delivery. <br />