University of Maryland Land Cover ESIP

INTERFACE DESIGN

Interim report for June 1st, 1998 Milestone Report

Catherine Plaisant, HCIL
University of Maryland - College Park
College Park, MD 20742

 

Introduction

 

Based on the results of the users needs assessment we have started to prototype some elements of the ESIP user interface. We have focused on 2 tasks of the task taxonomy: 1) Getting an overview of the site and 2) locating datasets of interest.

 

Getting an overview of the site and locating datasets of interest

 

1. Interface challenges

 

A challenge for the user interface of digital libraries is to provide users with an adequate overview of what the site purpose is, and what type and volume of material it contains. Once users have been able to decide that they in fact have reached a potentially useful site, users will need to search or browse the available materials (here data and services).

Today's Land Cover ESIP is still in its infancy and only contains a few datasets, making lists appropriate to browse the datasets, but as the number of datasets grows, other techniques will be needed. We propose to highly interactive graphical interfaces to browse the available datasets. The first one is a dataset browser in which each dataset is described individually. The second version proposes a initial preview step where numbers of datasets are given in response to users selections for 3 three datasets attributes.

 

  1. Dataset browser for early ESIP (i.e. few datasets)
  2.  

    In the ESIP dataset overview users can see the list of datasets. They can see on the map the overall geographical coverage of the data in the ESIP and its time coverage. Samples representative of the whole ESIP are given. Next to each dataset is given the maximum resolution, and the type of processing: none (raw data) , fixed (processing has been done and is available "as-is"), or on demand (request for processing is possible).

    As users select a dataset the map, time line and samples are updated to reflect the geographical and temporal coverage of the dataset. Samples of the selected dataset are shown.

    Figure 1: The user has clicked on a dataset (Atlantic coast marsh data), the map is updated to show the rough geographical coverage. The timeline shows that data is only available for 1993, and a sample map showing gridded index data and the legend. A selection of a smaller area in the gridded map would further narrow the timeline coverage; and a selection on the timeline would update the geographical coverage.

    Figure 2: The user has now selected another dataset, the map, timeline and samples have changed to refelect the attributes of the selected dataset.

    Figure 3: The user has now selected another dataset, the map, timeline and sample have changed to refelect the attributes of the selected dataset.

     

  3. Dataset browser for future ESIP (i.e. hundreds of datasets and services)
 

In the future the number of dataset will increase significantly and users will have to query the ESIP to locate datasets or services ofinterest.

Query languages are effective for frequent users who are also willing to take training, but more robust querying interfaces are needed for a system that supports intermittent users, from scientists to high school teachers, with extensive or limited computer experience. Classic form fill-in interfaces for EOSDIS exist, but zero-hit queries are a problem as well as queries returning too many hits. It is difficult to estimate how much data is available on a given topic and how to refine or relax a query to return a useful set of hits.

The Land Cover ESIP will make use of the dynamic queries and query preview techniques that have been shown to alleviate some of those problems.

Our initial design is closely related to our existing design for the NASA global change master directory. Three attributes are chosen and a number of available datasets is given next to each attribute values. The choice of attributes has not been fixed yet and will probably depend on the type of datasets that will populate the ESIP. For example resolution, or projection type could be used as well as a selecting attribute.

Figure 4: Here users have to choose among thousands of datasets. The intreface provides an overview of all the datasets and allow users to select rough values for area location and years. As users select values, the preview bars are updated to reflect the effect of the query. When the number of datasets has been sufficiently reduced the list of datasets can be explored with an interface similar to the version one, or submitted for inspection in the dataprocessing service.