Search the catalog
Point Of Contact: James
Description
Give a short descriptive name for the use case to serve as a unique identifier.
Search00
Goal
The goal briefly describes what the user intends to achieve with this use case.
A user wants to find data so they search a given catalog and are shown a set of URLs which reference data sets that have metadata records matching the search parameters.
Summary
Give a summary of the use case to capture the essence of the use case (no longer than a page). It provides a quick overview and includes the goal and principal actor.
A user is working with the Kepler system (a client from the perspective of a DAP server) and wants to search for data (i.e., for data sets that contain data from a certain time or range of times, location or within a bounding box and/or that are described by one or more keywords). Since Kepler already is designed to search over EML records stored in one or more Metacat servers, that search system will be used by this system.
Need to add information about:
- How Kepler should provide an interface for this; and
- How we're going to look for satellite data given that Kepler does not currently search over geo-spatial EML records
Actors
List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.
- The user searching for data
- Kepler and its search interface, modified to work with metadata records that contain SpatialRaster elements
- Metacat
- DAP servers
- NcML files
Preconditions
Here we state any assumptions about the state of the system that must be met for the trigger (below) to initiate the use case. Any assumptions about other systems can also be stated here, for example, weather conditions. List all preconditions.
- The NcML for a group of datasets has been written and those datasets have been crawled and cataloged by some Metacat server.
Triggers
Here we describe in detail the event or events that brings about the execution of this use case. Triggers can be external, temporal, or internal. They can be single events or when a set of conditions are met, List all triggers and relationships.
- The user wants to find data.
Basic Flow
Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)
Alternate Flow
Here we give any alternate flows that might occur. May include flows that involve error conditions. Or flows that fall outside of the basic flow.
Post Conditions
Here we give any conditions that will be true of the state of the system after the use case has been completed.
Activity Diagram
Here a diagram is given to show the flow of events that surrounds the use case. It might be that text is a more useful way of describing the use case. However often a picture speaks a 1000 words.
Notes
There is always some piece of information that is required that has no other place to go. This is the place for that information.
Resources
In order to support the capabilities described in this Use Case, a set of resources must be available and/or configured. These resources include data and services, and the systems that offer them. This section will call out examples of these resources.
Other Resources
| Resource | Owner | Description | Availability | Source System |
| name | Organization that owns/ manages resource | Short description of the resource | How often the resource is available | Name of system which provides resource |
