All interaction between the GSA and Gemini systems will be through the Data Ingest subsystem. The details of the interaction are described in [3].
Created:July 17, 2000 Modified:May 21, 2002
Gemini
Science
Archive
Chapter 3
User Interface
1.
Introduction
This chapter describes the conceptual design of the GSA user interface. The purpose of the user interface is to:
• Allow GSA users to view the data stored in the GSA catalogues, and to do cross catalogue queries involving data available from other archives
• Allow users to select Gemini data to be retrieved, including:
— Raw data files.
— Calibration data files.
— Meta-data such as the observing log and observing programs associated with datasets.
— Processed data, with the type of processing done selected by the user.
• Select delivery media for data requests.
• Provide preview display for datasets in the GSA archive.
• Provide links to documentation of the Gemini telescopes and instruments.
The primary interface to the GSA will be a GUI, however a batch interface which provides most of the same functionality will also be available.
1.1 Requirements on the GSA catalogue subsystem
Table 4 on page 31 lists the software requirements which apply to the GSA User Interface. The table includes a brief description of how the requirement impacts the user interface. Each description also includes the keywords “GUI”, “batch”, or “both” to indicate if the comment applies to the GUI user interface, the batch user interface, or both user interfaces. See [6] for a complete description of these requirements.
TABLE 4. User interface requirements
SR1.2 The GSA shall respect proprietary periods assigned by Gemini.
GUI: Display release dates to the user, and warn the user when he/she attempts to access data which he/she is not authorized to access. This is informative only, enforcement will be the responsibility of the Data Retrieval subsystem.
SR1.3.1 Data processing shall respect Gemini policy on proprietary periods.
GUI: Indicate which recipes cannot be executed because the user has insufficient authorization to access required input data. This is informative only, enforcement will be the responsibility of the Data Retrieval subsystem.
SR3.1 The GSA shall have an interactive user interface.
Introduction
SR3.2 Select subsets of the GSA catalogue. both: Supply the interface for this query.
SR3.2.1 Select subsets of the GSA catalogue based on coordinate region search. both: Supply the interface for this query.
SR3.2.2 GSA users should be able to select data supersets based on object descriptor. both: Supply the interface for this query.
SR3.2.3 Support cross catalogue searches. both: Supply the interface for these queries.
SR3.2.4 The GSA should support a batch mode interface.
batch: The above interfaces should be available from a batch mode interface which does not rely on a fast or reliable internet link for interaction between the GSA and the user. The batch mode inter- face may use the internet for non-interactive communication between the GSA and the user. SR3.3 View descriptors for a subset of the catalogue.
GUI: Provide an interactive display.
Batch: Allow a user to retrieve descriptor values to a file in their home computer. SR3.3.1 There shall be on-line help describing all catalogue data descriptors.
GUI: Provide interface to cause descriptor descriptions to be displayed to the user.
Batch: There will be a down-loadable source of GSA documentation which includes documentation of data descriptors.
SR3.3.2 GSA users can view a list of calibration data supersets.
GUI: Provide interface to display calibration datasets for the user, for any given science dataset. Batch: Provide an option to include information associating calibration data with science data supersets in query results (see SR3.3).
SR3.3.3 View the list of publications associated with a data superset.
GUI: Provide an interface which will allow a user to query the GSA catalogues to get a list of pub- lications associated with a data superset, and to display the list of publications.
Batch: have an option to retrieve the publications associated with the data supersets in a query result (see SR3.3).
SR3.3.4 View descriptors of objects in a data superset field of view.
GUI: Provide an interface which will display list of objects in the field of view, with the object descriptors.
Batch: Provide a batch query interface to the object table. SR3.3.5 View proposal information associated with a data superset.
GUI: Provide an interface which will allow a user to query the database to get and display public proposal information associated with any data superset.
SR3.3.6 Sort the displayed subset of the catalogue.
GUI: Allow a user to sort the displayed data supersets (see SR3.3). SR3.3.7 Sort the displayed objects.
GUI: Allow a user to sort the displayed objects (see SR3.3.4). SR3.3.8 Plot a subset of data supersets in spatial coordinates.
If this is done, the user interface should do it.
SR3.3.9 GSA users shall be able to view the electronic observing log.
GUI: Allow a user to query the database to get and display the electronic observing log entries asso- ciated with any data superset.
Batch: This information is available through a batch data request. TABLE 4. User interface requirements
Introduction
SR3.3.10 View environmental data.
GUI: allow a user to query the database to get and display environmental data associated with any data superset.
Batch: This information is available through a batch data retrieval request. SR3.3.11 Display science programs.
GUI: Provide interface elements which allow a user to query the database to get and display observ- ing programs associated with any data superset. If more than one observing program is associated with a data superset, the UI should display a list of observing programs, and allow the user to pick the one to be displayed.
Batch: This information is available through a batch data retrieval request. SR3.3.12 Display the members of association data supersets.
GUI: Allow a user to query the database to get and display members of associated data supersets. Batch: Have an option which will cause the membership information to be included with the query result (see SR3.3).
SR3.3.13 Save a set of data supersets to a file.
GUI: Allow the currently displayed set of data supersets to be saved to a file. This should not require any interaction with any other GSA subsystem.
SR3.3.14 Load a set of data supersets from a file.
GUI: Allow a list of data supersets to be read from a file. The list of data supersets will become the currently displayed catalogue subset (see SR3.3). The data superset descriptors displayed to the user will be read from the GSA catalogue, not from the file.
SR3.4 GSA users shall be able to select data for retrieval.
GUI: Provide interface elements to pick individual data supersets, or all data supersets in the cur- rently displayed subset of the GSA catalogue, and to submit a data request for processing. Batch: Provide a way to submit a list of data supersets to be retrieved.
SR3.4.1 Users shall retrieve data via Internet, EXABYTE, or CD-ROM.
both: Allow users to choose the delivery media for a data request before it is submitted. SR3.4.2 Only authorized users shall be able to retrieve proprietary data.
See SR1.2.
SR3.4.3 GSA users should be able to choose to have data processed. both: Allow user to choose to data processed.
SR3.4.4 Data processing shall not use proprietary data as input. See SR1.3.1.
SR3.4.6 Authorized Gemini staff can retrieve proprietary data.
GUI: Provide a way for authorized Gemini staff to identify themselves, and permit them to submit requests for proprietary data.
SR3.4.7 GSA users can retrieve calibration data.
both: Provide a way for users to indicate that all calibration data should be retrieved. SR3.4.8 Retrieve environmental data.
both: Provide an option to retrieve environmental data with requested data. SR3.4.9 It shall be possible to retrieve science programs.
both: Provide an option to retrieve observing program data with requested data. SR3.4.10 It shall be possible to retrieve proposal information.
both: Provide an option to retrieve proposal data with requested data. SR3.4.11 It shall be possible to retrieve the electronic observing log.
both: Provide an option to retrieve electronic observing log data with requested data. TABLE 4. User interface requirements
User interface elements