AWOB Concepts Project

MPDL,GAVO

= Introduction = A scientific project can be described as a number of typical scientific tasks resulting in products that are to be published to the communinity in various forms. In most of scientific projects scientists collaborate.

The AWOB proposal focuses on projects in which users collaborate. An AWOB project represents a real scientific collaboration, originally with the purpose of writing a paper (publication). The idea behind using a publication as goal of a project was that it gave us a framework to organize and design the AWOB project: AWOB projects need to support all(or many?) aspects of projects leading to a paper: collaboration, discussions, writing, creation of images/plots from underlying data etc. Here we try to formalise this concept by listing individual components of the project that should be represented (made visible/editable/managebale/shareable/...) in AWOB. (See the diagram [[Media:Awob_project_concept.jpg|Awob project concept.jpg]].)

An AWOB project has project overview which describes project and two main functional components: organization and resources. The former deals with managing lifecycle of a project, organizing work over collaborators, calendars, meetings etc. The latter deals with managing actual artefacts used/produced during the by the project. This includes data products (files, databases etc), bibliographic references, plots, texts written for a publication or proposal, etc.

For details the image and the file located at the links provided in section Documentation on this page.

= Documentation =


 * Generated document [[Media:AwobDM.doc|Awob project concept.doc]]: generated from a model diagram. Therefore its content is always in sync with the diagram.

The following sections describe general description of main concepts in the diagram.

= Project = Represent an awob project. It has attributes identifying and describing projects and contains various collections of classes, each class represents a specific concept like task, resource, meeting, etc.

Project Organization
A project organization consists of the following concepts

Related Project
...

TODO list, Tasks
Within the context of a given Project, one must be able to add tasks to a "TODO list" (i.e. a Project contains a TODO list).

A Task represents a scientific task performed by 1 or more members of the project (Marat: possibly specially an external collaborator added to Project for this task). It has a description, a start date, provisional end date, status, list of members assinged to it etc. It can have input data (INPUT), represented as a set of resource(/resource links) and a set of output resources (OUTPUT). A Task might be seen as a mini project.

The TODO list must be visible on the main Project page. Members assigned to a Task must see this task show up in the TODO list on their personal dashboard. End dates associated to the tasks SHOULD show up on the Calendar associated to the project, and to the user's dashboard Calendar.

Tasks can form the link between OUTPUT data and input data, providing part of the provenance metadata of the output.

In the long run it should be possible to sort tasks. (Tree view).

Examples of Tasks:
 * from a given FITS file create a publication ready plot of a contained image/spectrum/...
 * calibrate/clean a particular raw input FITS file to provide ouptut that is (A Bongiorno)
 * extract spectra from a Grism observation represented as a FITS file (Overzier)
 * from a given simulated light cone create images in particular bands (Overzier & Lemson)
 * cross-match a given input source catalogue with one or more existing reference catalogues (SMC)

Meetings, Calendar Items
List of project meetings both upcoming and in the past, and items which appear on in the project calendar. A meeting is one of telecon, videocon, f2f meeting. Also provide an easy and simple way to schedule meetings. In the calendar mark any deadlines including todo items, meeting dates, conference dates etc.

Any conference which might be an interest to the project members could be announced and displayed in the project calendar.

Project members
List of all the individuals and organizations(?) participating in the project including their roles. Each individual could either be a registered user(RU) or an email user(EU).

In general the project roles varies project by project except PI and Co-I. (See awob project role.) The default project roles could be
 * PI
 * Co-I
 * Project Member
 * External Collaborators/Guest
 * Referee.

Invitation of collaborators
Group all the information related with inviting collaborators. (cf Invite_Collaborators) In some cases an invitee accepts the invitation but wants to play a different role from proposed one.

Mail Items
Archive of all the mails exchanged for the project. ...

Project Events/What's new? Recent changes/activities
This could be a 'view' of all the changes made in an awob project. ...