You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Table of Contents
Purpose

This document describes the task of configuring default parameters (variables) for an ECHO form using the Data Access GUI:

  1. Prerequisites
  2. Selecting a collection-service record
  3. Choosing default parameters
  4. Choosing maximum number of parameters
  5. Expected results in Earthdata Search Client

Note: the terms variable and parameter are used interchangeably throughout this document; both terms refer to named data elements ("data objects") within a granule by which variable subsetting can be invoked.

Prerequisites

  • Latest version of the DataAccess must be installed, including:
    • AIM database patches
    • ESI*
    • DataAccess GUI
  • Invoke the appropriate mkcfgs; the corresponding web-services should begin.
  • Required information:
    • The shortname and version ID of the target collection.

Premise

ECHO forms provide spatial, temporal, and variable subsetting capabilities for collections associated with services that have said capabilities. Variable subsetting can be used to extract named attributes from a granule. The default configuration method for any given set of data objects (variables) in a collection follows:

  • enable all data objects to appear in an ECHO form
  • pre-select all data objects in an ECHO form (do not subset by variable; include all of them)

There now exist two methods of mitigating the incidence of (overly) large orders that negatively impact the system:

  • default parameter selection
  • maximum parameter selection

DAAC operators can configure a "default selection" for configure data objects–that is, they can preselect a recommended subset of those, rather than implicitly recommend that the user download everything. This is method #1 of .

Configuration


:

  • SUBSCRIPTION_ENDPOINT_URL
  • DEFAULT_FULFILLMENT_FREQUENCY

SUBSCRIPTION_ENDPOINT_URL (xs:string) allows the Data Access GUI to perform database operations using HTTP requests. The format of this value is http://x5oml01:30XX/todos

DEFAULT_FULFILLMENT_FREQUENCY (xs:integer) allows the operator to generate subscriptions without having to specify the fulfillment frequency each time. It is specified in seconds.

Note: the minimum period between subscription fulfillments is 1 hour (3600 seconds). The maximum period between them is 68 years (2,147,483,647 seconds).

 

Use Cases

Viewing Subscriptions

The "Subscription Management" tab allows an operator to view existing subscriptions.

Clicking on a subscription will reveal the details of its processing instructions in the lower half of the window in a readable format.

When no subscriptions are present in the database, a message like this might be received:

Creating a Subscription

To add a subscription, click the [Add New Subscription] button on the "Subscription Management" tab. A dialog box will appear containing several empty fields.

In the "Add New Subscription Dialog" fill in the required fields "Email" and "CMR Query" (see programmatic access or CMR pages for details on creating CMR queries).

Clicking on an item in the requests table will populate the processing options fields below with the details of the request.


Expected Result

Edit Existing Subscriptions

To edit an existing subscription, select a subscription, then click the [Edit Subscription] button on the "Subscription Management" tab. A dialog box will appear–populated with the information from the existing subscription.

 

Note that the old processing options can be overwritten with those from another request. When a subscription is edited, its ID will change.

Cancel a Subscription

Cancelling a subscription is done by selecting a subscription from the default view, then clicking the [Cancel Selected Subscription] button.

Tips & Warnings

  • If unable to connect to the database or retrieve subscriptions, relevant error messages will be shown in the table.
  • When troubleshooting, use both the firefox webpage debugger and the Data Access GUI log file (DA_Gui.log).
  • See programmatic access documentation for CMR query details.
  • No labels