SPCDIS User Annotation Use Case 2

Printer-friendly version

Short description:

In this use case, a user asks about a problem/event with one image, and gets a reply relating the problem/event to MLSO-generated data products used to generate that image, as well as other images.

Scenario:

A user Alice is looking at intensity pictures for 10d242, and notices the entry 20100830.223717.chp.hsc.fts is assigned an ‘UGLY’ rating. Curious about why this is, Alice submits the following request: “Are there any known events which caused this image to be assigned an ‘UGLY’ rating?” Following this, a link is made from Alice’s clarification request to the data product.

Next, an alternate user Bob (affiliated with ACOS) replies through establishing a link from a piece of data representing the statement:

WEATHER COMMENT: Mon Aug 30 22:39:13 GMT 2010 Clouds clouds everywhere. Insturments have been idled

To three places:

  1. Alice’s request
  2. A surrounding sequence of BAD/UGLY images
  3. The raw data files from MLSO used to produce the image from Alice’s request, as well as the surrounding sequence of BAD/UGLY images

Scenario Aftermath:

For any future users (including Alice) looking at the provenance for the entry 20100830.223717.chp.hsc.fts (and 15 subsequent entries), a flag will be raised that the image quality has been impacted by weather, based on the information provided by Bob.