AIP-3 Home

Search this site

605days since
Demo Capture

Recent site activity

Semantic Enabled Search

Back to the Transverse Technology Use Cases list.

Contents

  1. 1 Brief description
  2. 2 Basic flow of events
  3. 3 Alternative flows of events
  4. 4 Special Requirements: Ontology Engine Search

Brief description

Role and purpose: this use case describes the conditions and steps for portals and application clients to support the GEOSS user in searching for resources of interest via a combined use of GEOSS Clearinghouses (or Community Catalogs) and Ontology Engines.

Basic flow of events

 Title

 Semantics Enabled Search

 Overview

This use case describes the conditions and steps for portals and application clients to support the GEOSS user in searching for resources of interest via a combined use of GEOSS Clearinghouses (or Community Catalogs) and Ontology Engines.

 Actors and Interfaces
  • GEOSS User
  • Client Application (GEO Portal,  Community Portal, Desktop Application, Portlet, etc)
  • GEOSS Clearinghouse
  • Community Catalog
  • Ontology Engine
  • Discovery Augmentation Component

Initial Status and preconditions
  • GEOSS User is looking for information of value to task at hand
  • Client Application has been developed and is available for use
  • Resources’ metadata has been successfully harvested in GEOSS Clearinghouses (either directly or via registration in a Community Catalog)
  • Ontology Engine is available to be queried
  • Discovery Augmentation Component was successfully registered in CSR and is available to be queried

 Evolution

(basic flow steps)
  1. Client Application requests capabilities of Discovery Augmentation Component to determine the protocol needed to search for resources and the queryable elements of each as needed. Alternatively, the Client Application knows a-priori the protocol needed to interact with the component
  2. Client Application presents GEOSS User with search criteria based on queryable properties of selected catalogs:
    • Simple keyword search and area of interest/bbox search
    • Advanced search parameters such as organization, catalogs to be searched, societal benefit areas, resource type, etc
    • More specific earth-observation criteria such as sensor row/path, collection, subsetting/ordering and/or delivery mechanisms, etc
    • Value-added and/or domain/community specific search capabilities such as thesaurus matching, cluster matching, etc
    • Semantic relation (e.g. SKOS relation)Based on user selections, Client Application constructs a query to the Discovery Augmentation Component.
  3. The Discovery Augmentation Component expands the keyword with related terms (via the Ontology Engine Search UC)
  4. The Discovery Augmentation Component generates one or more geospatial queries based on user selection as geospatial constraints and as keywords the related terms from previous step (via the Client Search Metadata UC)
  5. The Discovery Augmentation Component collects the result set and sends it to the client
  6. GEOSS User selects resources of interest for evaluation and/or use. 


 Post Condition

  The Client Application has retrieved the necessary metadata to present the GEOSS User with information on discovered resources matching the search criteria for further evaluation and/or use.


Alternative flows of events

TBD

Special Requirements: Ontology Engine Search

The above Use Case makes use of the following one in order to retrieve the "related terms"


 Title

Ontology Engine Search

 Overview

This use case describes the conditions and steps for extracting terms related to a given keyword from an ontology engine

 Actors and Interfaces
  • Ontology Engine
  • Discovery Augmentation Component

Initial Status and preconditions
  • Ontology Engine is available to be queried
  • Discovery Augmentation Component was queried with semantic constraints

 Evolution

(basic flow steps)
  1. Discovery Augmentation Component requests capabilities of Ontology Engine) to determine the protocol needed to search for concepts (e.g. SPARQL). Alternatively, the Discovery Augmentation Component knows a-priori the protocol needed to interact with the component
  2. The Discovery Augmentation Component extracts from the combined query the keyword(s) to be expanded
  3. One or more cocepts (e.g. URIs) are extracted from the ontology engine for the given keyword(s)
  4. According to the relation in the combined query, the system retrieves from the ontology engine a set of terms related to the extracted concepts
  5. From the above set, the system extracts 0..N terms which will be inserted into the geospatial query


 Post Condition

  The Discovery Augmentation Component has retrieved from the Ontology Engine a set of terms to be used in subsequent geospatial query