Skip to end of metadata
Go to start of metadata

Overview of "Browse to Get Data Product" Use Case

Browse data products using metadata, select one, and access its contents.

Tip: Key Points
UC Priority= 4 or 5: Critical, is in R2
Only boldface steps are required
<#> before a step —> lower priority
(optional) —> run-time option

Related Jira Issues:   Open   •   All


Refer to the Product Description and Product Description Release 2 pages for metadata definitions.

Actors Any user (Anonymous Guest)
Is Used By  
Extends UC.R2.21 Transform Data in Workflow
UC.R2.26 Navigate Resources and Metadata
Is Extended By  
In Acceptance Scenarios AS.R2.03A Modelers Integrate External Model with OOI, AS.R2.04B Curate Data Products
Technical Notes Data Products are all those data resources made available by OOI to users (not just the core Data Products specified by Data Product Specifications).
Lead Team SA
Primary Service Data Product Catalog & Repository Services
Version 2.2
UC Priority 5
UC Status Mapped + Ready
UX Exposure EUC


This information summarizes the Use Case functionality.

Present aggregated information about a collection of data products. Allow users to navigate through the collection of information. Request more metadata (such as provenance) for a particular data product. Explore metadata in more detail by following links. Select one or more of the data products, or a subset of a data product, and request it be downloaded. Receive the requested data.


  • Metadata about the data products already exist (are associated with each data product).
  • The collection of data products can be ordered along some axis (and this is the axis by which the view is ordered). The axis might be 2-D (spatial) or of higher dimensions, but then navigation becomes quite challenging.

Initial State

User has arrived at a screen which presents a large collection of data products.

Scenario for "Browse to Get Data Product" Use Case

  1. User sees a partial view of a collection of data products
    1. The exact format of the collection is not defined, but a list is presumed because it provides certain navigational capabilities.
  2. User uses cues to navigate across collection of data products.
    1. Should include navigating in at least two directions (e.g., forward and backward), and being able to go to either end of the collection.
  3. User selects any specific data product(s) on the browsing page
    1. The user sees the collection of information associated with the selected data products(s).
    2. The associated information shall be organized into different categories.
  4. User navigates across collection of information
    1. The displayed information shall not be only text. These information shall be navigable. Users can select any piece of information, and if that information has additional information (or metadata) about itself, the user shall be able to navigate to that additional information (metadata).
  5. Find specific metadata of a data product
    1. There shall be a mechanism (e.g., searching on the content of the visible page) to enable to user to find specific metadata (e.g., provenance) for the data product being examined.
  6. The user explores more metadata of a data product
    1. As stated above, all the metadata shall be navigable, and explorable.
    2. The user shall be able to explore the metadata of data products to any depth (as long as the selected item contains its own metadata)
  7. The user accesses contents of any specific data product, a collection of data products, or a subset of a data products
    1. Once the user has browsed the metadata to find specific data of interest, he or she can choose to access a data product's contents.
    2. The user can also select a collection of data products to be accessed all at once.
    3. The user can also select to retrieve the data product in its precise current state (a URL pointing to time-invariant contents); at this moment this URLs will retrieve the same data as the default one, but once supplements to the data product arrive, the standard URL will include those in the returned data.
    4. Accessing data product contents requires obtaining an access URL that pointing to an Integrated Observatory data server (e.g. DAP server).
    5. The data product access URL remains valid any time in the future
    6. The data product access URL may be accessed by a tool such as Matlab
    7. Having a data product access URL enables the user to repeatedly access the latest state of the data product, for instance in user side tools.
    8. The user interface may provide a direct function to download the data product contents via the browser.

Final State

The user has access to the data product(s) contents.


These comments provide additional context (usually quite technical) for editors of the use case.

This is a mix of multiple functions: search (actually browse and explore), select, download. The emphasis is on being able to obtain and explore metadata for a data product, and on exploiting the ecosystem of Integrated Observatory resources to enable a more holistic browsing experience.

The default collection of data products one might see on first visit is only the OOI core data products, possibly just Level 1 and Level 2 collections. This is closest to what a science user might be looking for to evaluate the credibility of the system. Other preset filters (only raw, include all types of resources, etc.) should be readily available.

(click on # to go to R2 use case)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
61     27B


r2-usecase r2-usecase Delete
usecase usecase Delete
productdescription productdescription Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.