Skip to end of metadata
Go to start of metadata

Overview of "Display Arbitrary Resource" Use Case

Represent any class of Integrated Observatory resource in a UI

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 Integrated Observatory Operator, Any User
References See for example the nested display of the XML editor Oxygen for viewing nested data.
See also Linked Open Data for a sense of the vision.
Is Used By UC.R2.26 Navigate Resources and Metadata
Is Extended By  
In Acceptance Scenarios AS.R2.01B Define Marine Observatory Policies
Technical Notes  
Lead Team UX
Primary Service User Workflow, Interaction, and Visual Design
Version 1.3.2
UC Priority 4
UC Status Mapped + Ready
UX Exposure ONC, MNC


This information summarizes the Use Case functionality.

User displays a resource of any type, and as much information as reasonably possible about that resource is rendered in a UI. Resource details are expandable via nested operations (so as to present groups of groups of groups of variables or attributes). Common metadata for the canonical data format is presented in a consistent way. Atomic data elements are presented in consistent way for elements of that basic type. Where links to other resources appear in the metadata, active links are displayed.


  • It is assumed the user can obtain the ID of the desired resource in some way, e.g., via search.

Initial State

User has the ID of the resource he or she wishes to display.

Scenario for "Display Arbitrary Resource" Use Case

  1. User issues a command to display an arbitrary resource of the user's choosing.
    1. The mechanism for issuing the command requires some thought; a small 'display any resource by ID' button would be nice to have always available.
    2. Specifying the proper URL in a web browser, with the resource ID at the end of the URL, should also result in the following behaviors.
  2. The user sees a UI which summarizes the resource, and references further details.
    1. The summary should be common in appearance across all resource types, except for a customized section for unique resource types or unique attributes, as appropriate.
    2. Similar types of data (e.g., resource IDs, or floating point numbers) are expressed in similar ways whenever possible and appropriate.
  3. <3> To see readily accessible details about certain resource characteristics, the user clicks an icon to unfold a section of the summary.
    1. The icon may be a right-arrow/down-arrow, or other recognizable indicator.
  4. <3> To learn more about other resources inside or outside of OOI, the user clicks on the resource name or similar identifier.
    1. The name is expressed as an active link, which jumps to an appropriate descriptive page for the new resource.

Final State

Resource information has been displayed and reviewed, and user has identified other relevant resources as desired.


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


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.