Hyrax Admin Interface: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
No edit summary
Line 1: Line 1:
This is a place to start discussing peoples desires/needs for a Hyrax Administrators Interface.
This is a place to start discussing peoples desires/needs for a Hyrax Administrators Interface (HAI).




==Requirements==
= <Project name> =
 
== Background ==
 
The Hyrax Administrators Interface allows the ''administrator'' to perform debugging,
 
== Definitions ==
 
; ''Administrator''
: The ''administrator'' is the human that operates the HAI.
 
; ''User''
: The ''user'' is a human that uses client software such as Kepler, Matlab OPeNDAP Ocean Toolbox, a web browser, and others to make requests (HTTP, SOAP, etc.) of the Hyrax server. 
 
== Use Cases ==


# Secure (SSL?)
The ''administrator'' uses the HAI to:
# Turn on/off OLFS debugging and view/save(/stream?) the output.
# Turn on/off BES debugging and view/save(/stream?)  the output.
# Compare Server output with debugging associated with the request.
# Check logs.
#
#
#
#
#
#
= <Project name> =


== Use Cases ==
 
== Design ==
 
 
 




== Definitions ==
=== Required features ===


# Secure (SSL?) login and sessions.
# Log viewing.
# Debug control.
# ''User'' access control? What does that look like?
#


== Background ==
=== Desired features ===


== Design ==


== Deliverables ==
== Deliverables ==

Revision as of 23:02, 28 April 2009

This is a place to start discussing peoples desires/needs for a Hyrax Administrators Interface (HAI).


<Project name>

Background

The Hyrax Administrators Interface allows the administrator to perform debugging,

Definitions

Administrator
The administrator is the human that operates the HAI.
User
The user is a human that uses client software such as Kepler, Matlab OPeNDAP Ocean Toolbox, a web browser, and others to make requests (HTTP, SOAP, etc.) of the Hyrax server.

Use Cases

The administrator uses the HAI to:

  1. Turn on/off OLFS debugging and view/save(/stream?) the output.
  2. Turn on/off BES debugging and view/save(/stream?) the output.
  3. Compare Server output with debugging associated with the request.
  4. Check logs.


Design

Required features

  1. Secure (SSL?) login and sessions.
  2. Log viewing.
  3. Debug control.
  4. User access control? What does that look like?

Desired features

Deliverables

Period of use