Skip directly to searchSkip directly to the site navigationSkip directly to the page's main content

Data Administration System - System Information Overview

The IBIS-PH Data Administration System Information section provides general information about this application and is intended for project managers, system administrators, content managers, and application developers. The goal of this section is to provide a high level view of the application. This includes the system architecture, system requirements, basic design, and a history on what decisions went into the system.

The Data Administration System provides three basic services:

  1. Centralized, private, web based intranet application interface which allow various organization offices to access and maintain their Indicator Profile data. These data are currently stored in a Relational Database Management System (RDBMS). The application can be setup to limit indicator profile owners and editors so that only those individuals are able to modify their data.
  2. Mechanism to publish indicator profile data to the public IBIS-PH View System internet application.
  3. Mechanism for the IBIS-PH View System to save IBIS-PH View System survey responses in the admin database.

Data Administration System's High Level Features:

  • Allows the maintenance of Indicator Profile data to be dispersed across a variety of organization offices. These data are centrally stored in a modern relation database.
  • Allows the maintenance of the indicator profile data to be performed using a minimal client toolset (internet browser).
  • Allows the access of this data from any computer that has a browser and an internet connection.
  • Able to limit certain users to only work on and see specific data records
  • Able to run on all modern hardware and operating systems
  • Designed and built to be 508 compliant

Basic Overview of How the System Works

The IBIS-PH Admin application consists of a set of database tables and a series of JSP pages that correspond 1:1 with the data maintenance pages that can be requested. When a request is made for a page, a Java servlet receives the request and determines if the user has the needed privileges for that request. If they do the request is then sent to a Java controller which queries the database and puts the data into Java objects. These Java objects are then put into the user's session and the associated JSP view is invoked. The JSP then looks into the user's session object and grabs the Java data object(s) placed there by the Java request controller. The JSP then builds the requested HTML page with that data and the server streams the content back to the user.

When data are modified by a user, a similar request path is taken. The data are HTTP POSTED to the servlet which then calls the appropriate Java controller object. The data are then parsed then parsed and inserted/updated into the appropriate database table(s).

Page requests are defined within the REQUEST database table. This table contains the request name, the privileges needed by a user to be able to access that request, and the JSP used to build the HTML page to be presented to the user.

System Information Documentation Section Overview

The Data Administration System's Information documentation section includes the following pages:
The information provided was retrieved on: Mon, 18 November 2019 3:57:05.

Content updated: Wed, 4 Nov 2015 09:26:28 MST