Skip to end of metadata
Go to start of metadata

Overview of "Navigate Resources" Use Case

Use resource associations and links in metadata to find related resources and obtain more information about them


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

Metadata

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

Actors Any OOI user (Anonymous Guest)
References UC.R1.22 Present as Catalog
Uses  
Is Used By  
Extends  
Is Extended By UC.R2.04 Browse to Get Data Product
In Acceptance Scenarios AS.R2.01A Operate Marine Observatory, AS.R2.01B Define Marine Observatory Policies, AS.R2.04A Data Product Leads Drive Core Data Product Creation, AS.R2.04B Curate Data Products
Technical Notes Wikipedia is an excellent example of well-linked information.
Lead Team DM
Primary Service Search & Navigation Services
Version 1.7
UC Priority 2
UC Status Mapped + Ready
UX Exposure EUC

Summary

This information summarizes the Use Case functionality.

As a principal, metadata must be offered in linked data form, so that references to another resources can be moused over and clicked on to see more information about that resource. In practice, this will be visible (for an example) as embedded links in data provenance, referencing the specific instrument that produced the data. On visiting that instrument resource in the system, addition metadata are provided pointing to the following viewable resources: OOI Sensor Type, Sensor Manufacturer, Sensor Calibration, Sensor Parent Platform, and Sensor Description. (This example assumes the resource was data produced by a instrument. If the resource was, say, an error message produced by the system, the additional metadata might point to the code that generated the error, and other triggering data.)

Assumptions

  • Any resource in the system will have metadata that represents other resources, inside or outside the system.

Initial State

Resources are registered in the system and properly attributed with metadata and cross-referenced with other resources.

Scenario for "Navigate Resources" Use Case

  1. User accesses an Integrated Observatory capability to navigate or browse resources
  2. User is presented with set of resource types to browse
    1. The resources should be organized in views that are oriented to the selected resource type and the user role
  3. Selecting one or multiple resource types shows navigable lists of instances with summary metadata.
    1. Filters can be added or removed from list criteria to refine the result list
    2. The summary metadata contains embedded links to other resources or terms where appropriate
    3. Where possible, a link to a resource or term incorporates a reference to a globally unique identifier for the entity
  4. User selects one or more instances to show details of that instance, including metadata with links to associated resources
    1. Associated resources are both internal and external
    2. An ability to ask for 'more like this' (to get a list of resources that are similar to the present resource, e.g., of the same type) could prove helpful
  5. The Integrated Observatory presents all resources that are directly subordinate to one resource instance and user can navigate to any of these
    1. Example: the platform for an instrument; the Data Product for a specific version
  6. The Integrated Observatory presents all resources that are directly associated to one resource instance and user can navigate to any of these
    1. Example: the owner of a resource, the instrument that produced the data found in a Data Product
  7. User follows links to explore resources and related information, such as annotations, life cycle events, and provenance
    1. Links to resources outside the system open a new browser window, or a panel within an OOI browser window.
    2. Links to resources inside the system travel to a view of that resource.

Final State

User has found information of interest by following a path of interest through Integrated Observatory resources.

Comments

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

(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

Labels

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.