Versions Compared

Old Version 1

changes.mady.by.user Christopher Lynnes

Saved on

compared with

New Version Current

changes.mady.by.user Valerie Dixon

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note that these categories occur along a continuum requiring some judgement to classify the tool or service. For example, OPeNDAP services provide both API access and a web form interface. However, the web form is typically used for inspecting data and troubleshooting, not routine access. Most access is via scripts and Opendap-enabled clients such as Panoply, IDV, ArcGIS and nco, putting OPeNDAP  closer to the Headless Service than Full Stack Service.

Service / Tool Type

HTTPS API

Web UI

Headless Service

Yes

No

Full Stack Service

Yes

Yes

Web Tool

No

Yes

Local Tool

No

No


We will use this classification to show how a given tool or service class maps to the Use Cases envisioned for UMM-S.

...

With prevalence of API-based data formats in EOSDIS,  many users would like to save time and effort by using off-the-shelf tools. However, determining which tools can correctly read ,and process a given dataset is not always inferrable from the data format.  Small deviations from standards and conventions can render datasets unreadable by the tools that rely on them. One use case envisioned for UMM-S is to record the known associations between data collections and the tools that are known to work with them. The tools known to work for a given dataset would be presented in the dataset landing page and dataset info pages. Enabled by UMM-S, a preliminary smart-handoff capability has been demonstrated with Web Tools (Giovanni, SOTO) allowing the user to transition from Earthdata to the Web Tool with their data search criteria intact.

Legacy SERF Hosting:  Correct and Complete SERFs satisfying one of the above use cases

...

  1. For Headless or Full Stack Services, is the information quality high enough for use in Services Infrastructure?

  2. For Local Tools, Web Tools and Full Stack Services, is the value to the user community high enough to warrant cleanup of the SERF for re-hosting in CMR?

Populating the

Earthdata Tools Page:  Local Tools, Web Tools and Full Stack

The Earthdata Tools Page is notoriously difficult to curate over time. it is conceivable, however, that it could be populated from UMM S, if UMM S in CMR becomes the single It is conceivable that the UMM-S can be used to help curate and maintain the EOSDIS Tools and Services Inventory over time. One or many UMM-S entries can be used to capture the various ways in which an Inventory tool/service can be applied (e.g. WMS, WCS, etc.), and while not all entries in the inventory should necessarily have a UMM-S presence, but UMM-S entries should strongly consider having an inventory entry; in this fashion, if UMM-S in CMR becomes a publicly accessible source of truth for EOSDIS Tools then periodic reconciliation of UMM-S against the Inventory could prompt inventory updates. Since the users of the Tools page are most likely to be end users looking for useful tools for working with data, this would be confined to tools with a user interface, I.e., Full Stack Services, Web Tools, and Local Tools.