UC AWOB PM 04 Create Task Usage Scenarios

MPDL,GAVO

= UC_AWOB_PM_04 Create Task Usage Scenarios =

A few usage scenarios for creating, and editing tasks.

Scenario 1

 * Provided by : Angela Bongiorno (MPE)
 * Description : task example for data reduction, eg., spectra.
 * Scenario
 * Have a project meeting to decide who wants to do what tasks: PI asks project members.
 * For Data reduction: Spectra
 * Three project members (A, B, C in different locations) are assigned to reduce the same set of observations.
 * They agree on that
 * A,B get the raw data
 * A, B do the data reduction independently, upload the results or send them directly to C.
 * C reviews the results from A and B, take the final decision and produces and uploads a FITS file containing the final reduced data
 * A message notifying the final reduced data available appears on the web site for project members only.


 * Angela's comments
 * the number of members assigned to a single task should be flexible. Some tasks require one person, some other more. Therefore, the PI should be able to decide the numbers of "persons" to which assignes the task.
 * If more than one people are assigned to a task there is agreement between them who will close the task. Sometimes, there is some one who is responsible ('C' in scenario 1), other times, the assignees agree that the task is completed, and whoever changes its status in the todo list doesn't matter(scenario 3 below).
 * The PI can decide whether there is a temporal sequence in completing a task. For example in scenario 1 when A, and B are done then C can start working. However, not all task has a temporal sequence, it can also be that all the people assigned to the same task can work in parallel and there is not temporal sequence. If there is a need to specify to such sequences for a task PI can describe them in a task note.

Scenario 2

 * Provided by : Angela Bongiorno (MPE)
 * Description: task example for the second order product, eg., derive black hole mass from the reduced spectra
 * Scenario
 * Angela volunteers to do it and gives a rough deadline
 * She downloads the final reduced spectra produced in Scenario 1
 * She measure the necessary quantities from the spectra and runs her codes to compute the BH masses.
 * She uploads the final result in the form of ascii file to a website for project members only.
 * This table can be screened via TOPCAP to get a rough and fast idea of the data.)
 * A Notification appears in the web site for project members only.
 * For example: Angela Uploaded the BH mass measurements (can be downloaded here BH_mass_v2.1.dat, see the readme file BH_mass_v1.2.readme)
 * The name Angela could be clickable (mail or instant message) to ask something.

Scenario 3

 * Provided by : Roderik, Gerard (MPA)
 * Description:
 * Scenario
 * Roderik adds astrometry to output FITS images which results in FITS images with WCS keywords. medium priority
 * Lemson, Roderik, Matthias create web application for running skymaker online. low priority

Scenario 4

 * Provided by : Andrea Merloni(MPE)
 * Description:
 * Scenario
 * Need to write a white book about scientific goals in eRosita.
 * Ask all the leaders of all the working groups to provide the goals of each working group by certain date.
 * Collect all the inputs and produces the white book.
 * Need a place where he can see who already sends it to him or not.

Scenario 5

 * Provided by : Frank Haberl(MPE)
 * Description:
 * Scenario
 * Need an optical followup observation in a certain area of sky.
 * Frank creates a task without assignees.
 * The task appears on the todo list and 'what's new in the project' page as an open task.
 * Some project members are interested in doing it, and contacts Frank about it.
 * Make an agreement b/w them and Frank or whoever is authorized adds the assignees to the task.

Scenario 6
Expected functionalities in AWOB for task definition and management.

1. Defining and starting a task.
The project managers (PMs) of a project decide to define a task. One of them clicks "Add Task" on the tasks page. A panel pops up where an initial priority can be defined, the initial goal of the task, potentially a deadline. The status will be set to "pending". This PM becomes the "Task Creator" (TC) of the new Task. Here and in many use cases we refer to this person also as the "Task Lead" (TL). On the Task's wall the TL writes some initial comments and thoughts on what should happen in the task. The TL does so on the public section of the task's Wall. Potentially one or more files are uploaded in the "Input Data" area of the task. Potentially the goal of the task is described in more detail on the "Wiki" area of the task. The TL can do all of these actions even though (s)he is not an explicitly assigned member of the task. The TL now opens up the public discussion section of the Task's wall to all project members and sends them a message asking for comments. Some project members write on the public section of the task's Wall. Some of them volunteer (by message to the TL) to participate in the task.

At some point the discussion has lead to an agreement on the contents of the task. Now project members are assigned to the task with a particular role. At most 1 can become the "Task Manager" (TM). If a member is assigned the task manager, that person will also be the contact for the Task. Otherwise the TaskLead will be the contact person. Discussions are now held on the private section of the Task Wall deciding who will do what and also proposing a schedule. This leads to the TL or the TM updating the task metadata such as deadline/due data, expected duration of work and an expiration date.
 * --Natasa 16:16, 9 February 2012 (CET) on meeting (03-02-2012) it was stated that the task creator can have all privileges on the task throughout the task cycle.
 * --Jkim 16:34, 9 February 2012 (CET) Yes. the task creator is the task lead. This use scenario was written before talking to Frank. I will update this scenario accordingly.
 * --GerardLemson 14:30, 10 February 2012 (CET) I have done so now.

The TL/TM (meaning, TL or TM) starts the task by updating the status from "pending" to "in progress". The "start date" is set automatically. The TL/TM disables the ability of non-task members to write on the "public wall". The public wall remains visible in read-only mode to all project members. No other aspects of the task are visible to non-task members.

2. work on a task
Team Members (TMb-s) can update all aspects of the task apart from metadata such as status and visibility, only the TL/TM can do so. TMb-s continue discussions on the private wall. Some of them download input data, work with it, produce results which are stored in the Task's Resource work area. Final results are loaded into the Output data area of the task. The wiki area is updated with conclusions and more formal descriptions of the work that was done.

3. reviewing results
The TL/TM opens all aspects apart from the private wall and the work area of the resources for reviewing by the project members and sends those a message asking for comments. The public wall is again opened for writing by the general project members. On the tasks list the visibility of the project is set to "project". During this time work is still possible (otherwise answering a comment would require changing visibilities again etc). After review the decisions is made that more work is required. Possibly new members are added to the task. The task is closed again for further work.

4. closing a task.
The TL/TM once more opens up the task for review. Now it is decided that the task is complete. The TL/TM gives task members the chance to clean up the Task. This may involve removing resources from the work area of the Task's Resources area that are not output data. Or unfriendly comments can be removed from the private section of the wall. That is, IF it is decided to make that visible as well; a decisions could also be made NOT to open the private wall. Once this work is finished, the TL (NOT the TM!) updates the status to "complete". The endDate is set and all (apart from possibly private wall) components are open for browsing.