Development of improved Hyrax User Interfaces - Revision history

EvanKroske: /* Implementation Plan */

2010-04-13T02:47:26Z

Implementation Plan

← Older revision		Revision as of 02:47, 13 April 2010
Line 37:		Line 37:

	== Implementation Plan ==		== Implementation Plan ==
	[[~~Creating OpenDAP~~ Data Request Form]]		[[Javascript Data Request Form]]

	[[Category:Google Summer of Code]]		[[Category:Google Summer of Code]]

EvanKroske: Added link to implementation plan.

2010-04-12T21:51:55Z

Added link to implementation plan.

← Older revision		Revision as of 21:51, 12 April 2010
Line 35:		Line 35:
	* Expanded server-side functions will simplify writing complex Constraint Expressions. Much of the data served by DAP is geospatial data but its storage precludes easily using it as such. The new server-side functions will provide a new interface which greatly simplify this use		* Expanded server-side functions will simplify writing complex Constraint Expressions. Much of the data served by DAP is geospatial data but its storage precludes easily using it as such. The new server-side functions will provide a new interface which greatly simplify this use
	* Aggregation will enable the server to collapse certain operations that used to take several ‘trips’ to the server into a single request which makes a form interface, which is fundamentally non-interactive, easier to use.		* Aggregation will enable the server to collapse certain operations that used to take several ‘trips’ to the server into a single request which makes a form interface, which is fundamentally non-interactive, easier to use.

			== Implementation Plan ==
			[[Creating OpenDAP Data Request Form]]

	[[Category:Google Summer of Code]]		[[Category:Google Summer of Code]]

Ndp at 20:32, 2 April 2010

2010-04-02T20:32:28Z

← Older revision		Revision as of 20:32, 2 April 2010
Line 1:		Line 1:
	~~Development of Improved User Interfaces for Hyrax~~

	The Hyrax data server provides one of the simplest User Interfaces (UIs) that OPeNDAP supports. While it has not undergone any significant change in almost a decade, that interface remains one of the most widely used with which to access data using our server. In the intervening time since it was first implemented, many new technologies have emerged which greatly expand the capabilities of a web-based UI. In this proposal we outline the enhancements possible to this popular interface (known as the ‘HTML form interface’ as well as more colorful names) and the benefits those enhancements would bring to users.		The Hyrax data server provides one of the simplest User Interfaces (UIs) that OPeNDAP supports. While it has not undergone any significant change in almost a decade, that interface remains one of the most widely used with which to access data using our server. In the intervening time since it was first implemented, many new technologies have emerged which greatly expand the capabilities of a web-based UI. In this proposal we outline the enhancements possible to this popular interface (known as the ‘HTML form interface’ as well as more colorful names) and the benefits those enhancements would bring to users.

Line 10:		Line 8:
	== Features ==		== Features ==
	What features are proposed for the interface?		What features are proposed for the interface?

			=== Geo-Data Awareness ===
	* The interface (UI) will recognize geo-referenced Grid variables; present a map, a time line and use geogrid() functions when building requests		* The interface (UI) will recognize geo-referenced Grid variables; present a map, a time line and use geogrid() functions when building requests
	* The UI will also recognize geo-referenced Arrays and enable Grid-like selection capabilities using values gleaned from DAP attributes		* The UI will also recognize geo-referenced Arrays and enable Grid-like selection capabilities using values gleaned from DAP attributes
	* UI will use ~~AJAX~~ where ~~it can to be more interactive~~
			Requires the ability to interpret metadata in the DDX. I think James' idea is a heuristic, but we might consider code that can process CF-1.0 as a starting place. That won't get bounding box, but if UDD-1.0 is added then it could work. We might involve the semantic engine work that has been going in the WCS to get the CF and UDD metadata explicitly (Java/OLFS). We might just leverage the code associated with geogrid() and use that to identify the geo-metadata (C++/BES).

			If certain features exercise logic about geo-location (like checking for the extents of Map vectors, applying metadata convention semantics, etc) then we would want to think carefully about where that happens.

			=== Time Awareness ===
	* Add time as a recognized type in the UI (at least)		* Add time as a recognized type in the UI (at least)

			=== Server Analysis ===
	* The UI will examine a server and suggest using an aggregation if the data set currently viewed is part of one hosted by that server (does not check for an aggregation managed by a remote server).		* The UI will examine a server and suggest using an aggregation if the data set currently viewed is part of one hosted by that server (does not check for an aggregation managed by a remote server).

			This would need to happen in the BES, or the BES would have to able answer the question via the BES XML API, or the BES would have to embed that information in the DDX.


			=== Structural Content Improvements ===
			* UI will use AJAX where it can to be more interactive
	* The UI will reduce clutter to improve the display of large data sets (using AJAX) and other techniques.		* The UI will reduce clutter to improve the display of large data sets (using AJAX) and other techniques.

	New server features will further increase the interface’s usefulness
			== New server features will further increase the interface’s usefulness ==
	* The netCDF file output means that the UI can deliver data in a form that is more easily used. Currently the data are delivered in DAP binary form, something that only a handful of clients can use. The netCDF file response will expand the set of ‘clients’ to all of the software that can read netCDF files (this was added and released as part of Hyrax 1.5 in early April 2009).		* The netCDF file output means that the UI can deliver data in a form that is more easily used. Currently the data are delivered in DAP binary form, something that only a handful of clients can use. The netCDF file response will expand the set of ‘clients’ to all of the software that can read netCDF files (this was added and released as part of Hyrax 1.5 in early April 2009).
	* Expanded server-side functions will simplify writing complex Constraint Expressions. Much of the data served by DAP is geospatial data but its storage precludes easily using it as such. The new server-side functions will provide a new interface which greatly simplify this use		* Expanded server-side functions will simplify writing complex Constraint Expressions. Much of the data served by DAP is geospatial data but its storage precludes easily using it as such. The new server-side functions will provide a new interface which greatly simplify this use

Ndp at 20:20, 2 April 2010

2010-04-02T20:20:54Z

← Older revision		Revision as of 20:20, 2 April 2010
Line 7:		Line 7:
	* It can work with any data served: It is the LCD of UIs		* It can work with any data served: It is the LCD of UIs


			== Features ==
	What features are proposed for the interface?		What features are proposed for the interface?
	* The interface (UI) will recognize geo-referenced Grid variables; present a map, a time line and use geogrid() functions when building requests		* The interface (UI) will recognize geo-referenced Grid variables; present a map, a time line and use geogrid() functions when building requests

Jimg at 19:10, 25 March 2010

2010-03-25T19:10:18Z

← Older revision		Revision as of 19:10, 25 March 2010
Line 19:		Line 19:
	* Expanded server-side functions will simplify writing complex Constraint Expressions. Much of the data served by DAP is geospatial data but its storage precludes easily using it as such. The new server-side functions will provide a new interface which greatly simplify this use		* Expanded server-side functions will simplify writing complex Constraint Expressions. Much of the data served by DAP is geospatial data but its storage precludes easily using it as such. The new server-side functions will provide a new interface which greatly simplify this use
	* Aggregation will enable the server to collapse certain operations that used to take several ‘trips’ to the server into a single request which makes a form interface, which is fundamentally non-interactive, easier to use.		* Aggregation will enable the server to collapse certain operations that used to take several ‘trips’ to the server into a single request which makes a form interface, which is fundamentally non-interactive, easier to use.

			[[Category:Google Summer of Code]]

Jimg at 23:15, 9 March 2010

2010-03-09T23:15:44Z

← Older revision		Revision as of 23:15, 9 March 2010
Line 1:		Line 1:
	Development of Improved User Interfaces for Hyrax		Development of Improved User Interfaces for Hyrax
	~~James Gallagher~~
	~~17 April 2009~~

	The Hyrax data server provides one of the simplest User Interfaces (UIs) that OPeNDAP supports. While it has not undergone any significant change in almost a decade, that interface remains one of the most widely used with which to access data using our server. In the intervening time since it was first implemented, many new technologies have emerged which greatly expand the capabilities of a web-based UI. In this proposal we outline the enhancements possible to this popular interface (known as the ‘HTML form interface’ as well as more colorful names) and the benefits those enhancements would bring to users.		The Hyrax data server provides one of the simplest User Interfaces (UIs) that OPeNDAP supports. While it has not undergone any significant change in almost a decade, that interface remains one of the most widely used with which to access data using our server. In the intervening time since it was first implemented, many new technologies have emerged which greatly expand the capabilities of a web-based UI. In this proposal we outline the enhancements possible to this popular interface (known as the ‘HTML form interface’ as well as more colorful names) and the benefits those enhancements would bring to users.

Jimg: New page: Development of Improved User Interfaces for Hyrax James Gallagher 17 April 2009 The Hyrax data server provides one of the simplest User Interfaces (UIs) that OPeNDAP supports. While it ha...

2010-03-09T23:04:56Z

New page: Development of Improved User Interfaces for Hyrax James Gallagher 17 April 2009 The Hyrax data server provides one of the simplest User Interfaces (UIs) that OPeNDAP supports. While it ha...

New page

Development of Improved User Interfaces for Hyrax
James Gallagher
17 April 2009

The Hyrax data server provides one of the simplest User Interfaces (UIs) that OPeNDAP supports. While it has not undergone any significant change in almost a decade, that interface remains one of the most widely used with which to access data using our server. In the intervening time since it was first implemented, many new technologies have emerged which greatly expand the capabilities of a web-based UI. In this proposal we outline the enhancements possible to this popular interface (known as the ‘HTML form interface’ as well as more colorful names) and the benefits those enhancements would bring to users.

Why the ‘HTML Form Interface’ is so important:
* Ubiquitous: The interface is part of the server so it is always present
* It can work with any data served: It is the LCD of UIs

What features are proposed for the interface?
* The interface (UI) will recognize geo-referenced Grid variables; present a map, a time line and use geogrid() functions when building requests
* The UI will also recognize geo-referenced Arrays and enable Grid-like selection capabilities using values gleaned from DAP attributes
* UI will use AJAX where it can to be more interactive
* Add time as a recognized type in the UI (at least)
* The UI will examine a server and suggest using an aggregation if the data set currently viewed is part of one hosted by that server (does not check for an aggregation managed by a remote server).
* The UI will reduce clutter to improve the display of large data sets (using AJAX) and other techniques.

New server features will further increase the interface’s usefulness
* The netCDF file output means that the UI can deliver data in a form that is more easily used. Currently the data are delivered in DAP binary form, something that only a handful of clients can use. The netCDF file response will expand the set of ‘clients’ to all of the software that can read netCDF files (this was added and released as part of Hyrax 1.5 in early April 2009).
* Expanded server-side functions will simplify writing complex Constraint Expressions. Much of the data served by DAP is geospatial data but its storage precludes easily using it as such. The new server-side functions will provide a new interface which greatly simplify this use
* Aggregation will enable the server to collapse certain operations that used to take several ‘trips’ to the server into a single request which makes a form interface, which is fundamentally non-interactive, easier to use.