The DM Presentation Services present the system's Information Resources to users in various form. Presentation includes search (aka find, discovery) and navigation (aka catalog), providing notifications to users, and providing essential data access mechanisms.
- CIAD DM Search and Navigation
- CIAD DM OV Discovery Service
- CIAD DM OV Catalog Management Service
- CIAD DM OV User Notification Service
- CIAD DM TV DAP
The figure below shows the main entities related to the DM Presentation Services and their dependencies.
Figure 1. Presentation services and lower level services overview (OV-1)
The discovery service provides a common interface for searching and navigating. With the discovery service, clients may create views which contain common parameters for which they are searching against, as well as ordering and filters. See here for details:
The Catalog management service contains the interface for creating catalog resources. The logic components for determining and selecting which indexes should be incorporated into the catalog are controlled and executed in the creation process. Indexes are intelligently selected based on the keywords chosen. Indexes are chosen based on the number of fields the entire index represents, to get better results we pick the index with the least number of fields which is a superset of the specified keywords. See here for details:
The Index management service is responsible for managing the index resources and collecting, maintaining and aggregating the metadata about the index. Indexes refer to a search space in a specific technology, CouchDB or ElasticSearch. ElasticSearch indexes maintain a context type which contains a special mapping instruction for how to map documents that are part of that context type. Most of the ElasticSearch indexes use the resource type for the context type which provides a flexible structure to map resources. The indexes are organized based on their purpose, for example; the devices indexes contains resources which are some sort of device resource. See here for details:
The ION system will generate many different events (life cycle events, data events, resource events) from many different origins (data sets, services, agents). The User Notification Service (UNS) allows a user to set up notifications which define a set of events from a set of originators for which the user wants to receive information. The notifications can be delivered in different ways, for R2 these will be primarily emails or SMS channels. When an event of interest is published the UNS will have a subscriber that will receive the event and send the user a notification.
The UNS will also implement an interface to the Event Repository for 'finding' archived events that have been logged to the repository as well as methods which allow an operator to publish an event manually.
Figure. User Notification Mechanisms
See CIAD DM TV DAP for a description of downloading scientific data from coverages via ERDDAP.