UC4: Client Search Metadata

Back to the Transverse Technology Use Cases list.

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 as registered in the GEOSS Clearinghouses and Community Catalogs. This use case is a pre-condition to the Presentation of Reachable Services & Alerts in the clients.

Basic flow of events


 client Search Metadata



 Actors and Interfaces

  • GEOSS user
  • Client application (GEO Portal, Community Portal, Desktop Application, portlet, etc)
  • GEOSS Clearinghouse provider(s)
  • Community Catalog provider(s)

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 (through Registry populated with available resources references)
  • Resources' metadata has been successfully registered in Community catalog(s), available either directly or via the GEOSS Clearinghouses


(basic flow steps)

  1. Client application requests capabilities of catalogs of interest (GEOSS Clearinghouse and/or Community Catalogs) to determine the protocol needed to search for resources (CSW 2.0.2, Z39.50, etc) and the queryable elements for each as needed.
    • Alternatively, the client application knows a-priori the protocol needed to interact with catalog(s) of interest
  2. Client application presents user with search criteria based on queryable properties of selected catalogs
    1. Simple keyword and Area of Interest/bounding box search
      • This could be done via mapping window or virtual globe
      • Options may also include select results that are fully contained or overlap with area of interest
    2. Advanced parameter searches such as
      • Organization
      • Time of data publication/coverage/harvest date
      • Location/region/place of interest
      • Catalogs to be searched (e.g. community catalogs)
      • Societal benefit area (and subtopics)
      • Keyword search in abstract, title and/or full text
      • Resource type (e.g. service, workflow, document, client app, portlet, alert, etc)
      • Other
    3. More specific Earth-Observation criteria such as
      • Row/path of sensor
      • Collection
      • Cloud cover parameters
      • Subsetting, ordering and/or delivery mechanism
    4. Value-added and/or domain/community-specific search capabilities such as
      • Thesaurus-matching (e.g. Client uses thesaurus published as OWL to support user search)
      • Cluster matching
      • Pattern matching
    5. As a reference, the GEOSS Clearinghouse common search facility currently supports
      • Title
      • Record type
      • Full text
      • Abstract
      • Identifier
      • Bbox
      • Return format
  3. Based on user selections. client application constructs query to each selected catalog
  4. The resultSet is returned and presented to the user with options to
    • Display total number of results
    • Display basic information about each result (e.g. thumbnail, title, abstract, organization, etc)
    • Expand results to display additional information (e.g. full metadata record)
      • This may require another query to the underlying catalog(s)
    • Group or sort results in categories (e.g. by type of resource, by SBA, etc)
    • Select 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 user search criteria for further evaluation and/or use.

Alternative flows of events


Special Requirements