|
Revision 15
(checked in by graybeal, 3 years ago)
|
Augmented and added new workflow (reworded existing numbered items to be textual scenarios).
|
- Property svn:eol-style set to
native
|
| Line | |
|---|
| 1 |
Use Case 11: Learn about data context from sensor information. |
|---|
| 2 |
|
|---|
| 3 |
This use case has two distinct circumstances. Both start with the user having access to a dataset, and wanting to learn contextual information about that dataset. Both involve learning about the instrument used to collect the data. |
|---|
| 4 |
|
|---|
| 5 |
In the first situation, the user wants to use the knowledge about the instrument to better evaluate or process the data. For example, the user may want to know expected accuracy and resolution of the instrument's measurements, or the appropriateness of the calibration status that has been provided. |
|---|
| 6 |
|
|---|
| 7 |
In the second situation, the user wants to know what related data parameters are likely to be available for this dataset. One way to discover additional metadata is to find what other data can be collected by the instrument that collected this data. (Another way, learning what other devices were deployed with this one, is outside the scope of this project.) |
|---|
| 8 |
|
|---|
| 9 |
The workflow is something like this: |
|---|
| 10 |
|
|---|
| 11 |
1. User has data set of interest. |
|---|
| 12 |
2. User goes to provider of data set and looks up the data set and its metadata. |
|---|
| 13 |
3. User finds metadata describing the metadata used to collect the metadata. |
|---|
| 14 |
4a. User obtains device metadata directly from the metadata description, or |
|---|
| 15 |
4b. User learns the type of device (manufacturer, model, and in some cases serial number is needed) used to collect the data, and does additional research on that device to learn the necessary information. |
|---|
