Skip to end of metadata
Go to start of metadata

Overview of "Manage Resource Metadata" Use Case

*Edit (add, deprecate, improve) metadata of a resource*

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|,+status+DESC]   •   [All|,+priority+DESC,+status+DESC]


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

Actors Integrated Observatory Operator, Resource Operator,
any user (Anonymous Guest), Register User
Uses UC.R2.20 Annotate Resource in Registry
Is Used By  
Is Extended By  
In Acceptance Scenarios AS.R2.01B Define Marine Observatory Policies, AS.R2.02C Instrument Life Cycle Support, AS.R2.04A Data Product Leads Drive Core Data Product Creation, AS.R2.04B Curate Data Products
Technical Notes This use case applies to any resource in the Integrated Observatory.
Lead Team DM
Primary Service OOI Common Data & Metadata Model Part 2
Version 2.5
UC Priority 5
UC Status Mapped + Ready
UX Exposure EUC


This information summarizes the Use Case functionality.

For any resource, provide the following functions: Edit metadata of a resource. Add non-system metadata to a resource. Add system metadata to the resource*. View the resource's metadata and changes to it.
(* = Integrated Observatory Operator only)


  • The object's identity (unique identifier) inside the Integrated Observatory is core to the object itself, and is not editable metadata. Identity attributes that apply to other systems are metadata and therefore editable.
  • Some or all resource types must support ISO 19115 metadata (basic metadata in R2, more advanced in R3).
  • Some metadata may be kept as fields of the object, while others will be maintained as a sequence of associations. This affects the use case minimally; in particular resource versioning is affected if it is handled differently for the two cases.

Initial State

A resource has been identified and brought into view by an operator or user.

Scenario for "Manage Resource Metadata" Use Case

  1. An OOI user views metadata of the resource
    1. On selection of any resource, all the associated metadata for that resource can be viewed.
    2. User viewing the metadata sees only the most recent valid metadata, and at first only the most significant metadata; further metadata is exposed on request.
    3. Anticipated that in most cases there will be far more information than can be displayed in a single view; a hierarchy of information is displayed.
  2. <3> Integrated Observatory Operator adds metadata field to a resource
    1. Integrated Observatory Operator selects any resource and, through an editing interface, adds necessary fields to the resource
  3. Resource Operator edits any (editable) existing metadata of a resource
    1. Resource Operator selects any metadata of a resource to be edited, and through an editing interface edits the metadata information.
    2. The previous metadata information is preserved; it is deprecated but not lost.
    3. Depending on rules for versioning this resource type, the edit likely updates the resource version.
  4. <3> An OOI user views the changes of a resource's metadata
    1. Ideally a user could view the change history of values for any specific metadata, inspecting the history of changes by clicking on the appropriate link.

Final State

The resource metadata is 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.