Skip to end of metadata
Go to start of metadata

Overview of "Reacquire External Data" Use Case

Re-obtain data requested by user but no longer in ION


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 Anonymous Guest
References  
Uses UC.R2.01 Acquire Data From External Dataset
Is Used By  
Extends  
Is Extended By  
In Acceptance Scenarios None
Technical Notes  
Lead Team EOI
Primary Service IOOS Integration Package 2
Version 1.1.1
UC Priority 3
UC Status Mapped + Ready
UX Exposure EUC

Summary

This information summarizes the Use Case functionality.

User makes a request for data that is no longer in the system (been dropped from the back-end of the data cache). The request is submitted to the External Data Provider via the appropriate Data Agent and the returned data is transformed (if necessary), added into the data cache, and returned to the user.

Assumptions

  • Integrated Observatory keeps the catalog metadata for all the data that has passed through its portals.
  • Original data provider is still online at original location.

Initial State

User has a unique identifier for, or finds in a catalog, external data that is no longer in the ION system.

Scenario for "Reacquire External Data" Use Case

  1. Any OOI user requests externally originated data that is no longer maintained in the Integrated Observatory system.
    1. This would be data from an external provider that ION has dropped from its cache.
  2. Integrated Observatory system uses metadata about the data's original provider to re-request the data from that provider.
  3. Data is reacquired from the data provider and ingested into the system.
    1. If the data provider doesn't have that data any more, an error results.
  4. Upon completion of ingestion, Integrated Observatory routes the data to the requesting user.
    1. Possibly should occur as ingestion proceeds, rather than upon completion.

Final State

Data has been retrieved from original source (if still available) and routed to user.

Comments

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

This is a case where, aside from caching the data for a little while per our caching policy) the data is really a "flow through" — we're essentially just reposting the request to the originator and funneling the reply back to the user.

(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.