IBIS-PH Documentation - View System Introduction
The IBIS-PH View System is the application that provides the public access to health data which includes static content, health indicator profile reports, and an interface which allows custom queries of SAS public health datasets. It is the system that is not grayed out in the System Architecture figure. Following the Architecture Figure the main categories of IBIS-PH View system documentation are listed.The View System documentation includes information on high level view of the IBIS-PH View System's architecture, System Design (goals, Features, History), Requirements, How HTTP Requests Flow, URL Mapping to the associated XML/XSLT files, Files, Dependencies, Artifacting of transformations, installation, configuration, customization, Tomcat Setup, how to build the deployment package, query interface/response page customization, XML content management and data files element descriptions, XML Tutorials, HTML page design (508 Compliance, Javascript menus, scaleable fonts), CSS, XSLT Page Design, API Docs (for Java, XSLT, and XML files), user preference Cookies, Javascript, Adobe SVG Viewer Browser Plugin, URL Options, Java servlet code architecture, Spring Framework, and Java Servlet filters.
System Architecture Figure
Main Categories Index
- Introduction
-
System Information
System Information
Includes high level architecture showing all parts of the IBIS-PH View System, features, design goals, decisions, requirements, naming conventions, basic list of files, and the application's history -
Installation / Configuration
Installation / Configuration
This section of the documentation covers how to setup Tomcat the open source Java application server, how to install the application, how to configure the application for different enviorments, and special issues/topics that could be of interest to system administrators. -
Content Management
Content Management
Covers topics related to how to maintain and manage web site content. This includes how to deal with XML elements in general, how to maintain static "HTML Content" type content, the indicator profile reports, the PHOM report, and how to work with the query builder/module files to control the query builder interface pages. -
Appendix A: Implementation Detail
Appendix A: Implementation Detail
This section provides specific detail oriented pages which describe how certain sections of the application work. These topics are meant for application developers and possibly system administrators. -
Appendix B: XML Elements
Appendix B: XML Elements
Documents all the different XML files and their elements. This reference section is designed for application developers and content managers. -
Appendix C: Web Interface
Appendix C: Web Interface
This portion of the documentation provides specifics about how the HTML pages are built and work. The XSLT directory and file structure is defined as well as an XSLT documentation index API. The CSS and javascript are also described in more detail with several reports that show which CSS classes are used by which XSLT files. This reference section's content is consumed by application developers and possibly content managers. -
Appendix D: Java Reference
Appendix D: Java Reference
This section of the documentation described the Java control code. Specificially, the application specific Spring framework and the gateway into the "org.ibisph" Java code/packages. These pages will be used primarily by application developers. -
Appendix E: Reports
Appendix E: Reports
The last section of the View Documentation contains a list of special Query Module XML related reports which can help query module content managers maintain the XML files.