Using the NcML Handler to get information
The goal briefly describes what the user intends to achieve with this use case.
Virtual data sets configured by a data provider work just like 'real' data sets, but have desired metadata that the real (raw) data lack.
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.
Once a data provider has set up Hyrax with the NcML handler and configured one or more virtual data sets, a user can access a those if they have access to a URL to the .ncml file. The user sees the virtual data set as if it is real. Using the virtual data set is no different than using any other data set.
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.
- Primary actor: a downstream data-processing element (DPE)
- NcML handler
- a .ncml file (one per virtual data set)
- a client connecting to the server
- other data handlers for the BES
- 'real' data sets that work with the other data handlers loaded in the BES
In this the DPE requests data using a DAP URL that is handled by the NcML handler which then uses information in the NcML file to access some other data store (like a file) using one of the other BES handlers and merges the result with information in the NcML file itself.
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 BES, other data handlers and the matching data sets have to be appropriately configured.
- The data provider has written one or more .ncml files which reference data sets local to the BES
- We can actually handle access to remote resources, too, but there will need to be appropriate safe-guards in place to prevent client-side capabilities from being misused. In this case, the notion that the BES has to have other handlers and data is false -- there could only be the NcML handler and .ncml files that reference remote data resources.
- The client/DPE has a URL to one or more .ncml files.
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.
Using the client/DPE is the trigger for this use-case.
6 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)
- The NcML handler is passed the path name to the NcML file and one of the GetDDX, GetData, et c., entry points is activated.
- It opens the NcML file and sees which other resources to access to get the basic information
- It then examines the remaining information in the NcML file and augments the basic information given the semantics of the handler entry point (Get DDX, et c.)
- The result is returned
7 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.
- If the NcML file is not found, return a HTTP 404 error.
- If the NcML file exists but the referenced data within it cannot be found, return a 500 or a 404, depending.
- return a 500 error if the resource is local and does not exist
- return a 404, or whatever error the remote server returned, for remote resources that cannot be found (rationale: If a NcML file has a pathname wrong, that is a server configuration error but if a remote server returns an error, that could be transient - the server is down - or indicate that a document has moved).
- If the NcML is malformed, return a 500 error.
8 Post Conditions
Here we give any conditions that will be true of the state of the system after the use case has been completed.
9 Activity Diagram
Here a diagram is given to show the flow of events that surrounds the use case.
There is always some piece of information that is required that has no other place to go. This is the place for that information.
It's easiest to build this handler so that it works only with local files since that will not need to include any client code, thus eliminating any security concerns over having a server talk on the network in response to its input from a remote client. But having that additional capability will open the system to servers that only provide virtual data sets, a really cool thing. I propose that we make the NcML handler use a switch that disables this feature by default. If a site wants the extra capability, they can add it easily. Remote resources can be added to the NcML easily enough.
More: After looking at the basic use case for adding metadata for projects like REAP and IOOS, I think we need this feature, even if we do not distribute it in the first versions. See Add the NcML handler to the BES in the Notes section for more information.
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.
|(sensor name)||Organization that owns/ manages resource||Short description of the resource||How often the resource is available||Name of system which provides resource|