Hyrax Admin Interface: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
| Line 43: | Line 43: | ||
# Secure (SSL?) login and sessions. | # Secure (SSL?) login and sessions. | ||
# Log viewing. | # Log viewing. | ||
# | # control and view debugging information. | ||
# ''User'' access control? What does that look like? | # ''User'' access control? What does that look like? | ||
# | # | ||
=== Desired features === | === Desired features === | ||
Revision as of 23:08, 28 April 2009
This is a place to start discussing peoples desires/needs for a Hyrax Administrators Interface (HAI).
Background
Members of the Hyrax users community have asked for an administrators interface that will allow them to control, reconfigure, and debug the Hyrax server. This page is the starting point for organizing the design work for the Hyrax Administrators Interface (HAI).
The Hyrax Administrators Interface allows the administrator to:
- control and view debugging information.,
- .
- .
- .
- more!
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:
- 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.
Design
Required features
- Secure (SSL?) login and sessions.
- Log viewing.
- control and view debugging information.
- User access control? What does that look like?
