SPCDIS

Prior Relevant Work

This work closely relates to a number of areas in the domains of provenance and workflow research. Below, we provide a select listing of these areas:

Workflow Management Systems

In domains such as eScience, workflows are commonly used to automate the execution of task sequences. Workflows are commonly used to manage the generation of various types of data products. A variety of workflow management systems have been developed to aid users in both creating and executing workflows.

User Roles in Provenance Presentation

Motivation

One goal of provenance is to provide users an understanding of the steps a system took to generate certain data products. Here, the level of detail captured by provenance becomes an important consideration. As detail is added, more questions can be hypothetically addressed.

User-Submitted Annotations on Provenance

Motivation

Provenance can be used to answer user questions about the steps taken to generate a data product. Many eScience-based systems will generate data products for later review by end users. For these end users, establishing an understanding of how data products were created is useful for varying reasons.

SPCDIS CHIP Role View Use Case 1

Scenario

A user Alice is looking at a listing of CHIP Velocity images, similar to what is currently provided by the browsing interface at http://mlso.hao.ucar.edu/cgi-bin/mlso_data.cgi?2010&CHIP. In addition to displaying image listings, the browsing interface Alice is using provides links to provenance traces for each image.

SPCDIS User Annotation Use Case 5

Short description:

A user asks about a problem/event with one image, and gets a reply relating the problem/event to an NCAR-generated data product used to generate that image.

NOTE: Currently, there are no bug correction reports released by ACOS. Therefore, this is a hypothetical situation for CHIP.

SPCDIS User Annotation Use Case 4

Short description:

In this use case, a user wishes to filter replies made to a given request, based on facts about the replying users.

Scenario:

Here, a user Alice is looking at intensity images for 10d242, and notices the image 20100830.223717.chp.hsc.fts is assigned an ‘UGLY’ rating. Curious about why this is, user requests clarification.

Here, two users reply to Alice’s request: Bob (affiliated with ACOS) and Carol (not affiliated with ACOS).

SPCDIS User Annotation Use Case 3

Short Description:

In this use case, a user requests clarification on the description of a process used in the provenance of an image, and receives an response clarifying the original description. In turn, the clarification becomes applicable to alternate references of that process (i.e. from provenance traces for other data products).

Scenario:

Here, a user Alice is looking at the provenance trace for a given solar intensity image.

SPCDIS User Annotation Use Case 2

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.

SPCDIS User Annotation Use Case 2

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.

SPCDIS User Annotation Use Case 1

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.

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.

Syndicate content