AWOB Scope AWOB 0.5

MPDL,GAVO

About this Page
Summarizes actually the view of the implementation group on the scope of AWOB 0.5. The page is open for discussion and these remarks might vanish as soon as the page has been discussed by the entire team. See here for further discussion/testing/detected bugs etc.

Scope AWOB 0.5
 LINKS WILL BE ADDED ASAP 

Task 002, AWOB resource Management (FITS Files)
Scope 0.5: Recognize by extension and allow for files to be opened with Aladin

Status: OK

Task 003, AWOB Wiki
Scope 0.5: What means AWOB Wiki in the context of AWOB?

Status: As this has not been specified or precised, we will provide default Wiki component with only revision of the name of the Front page. We define "Overview" as default name of the WIKI for the project/task wikis

Jkim 10:18, 13 February 2012 (CET) The current way that wiki is implemented at the project level does not conform to the design mock ups [TBD add link] as they have been around since before the demonstrator. At the minimum we should discuss whether that can be fixed.

Task 004, AWOB invite collaborators, registered users
Scope 0.5: Invitation shall be fulfilled by e-mail to any recipient or by invitation of the AWOB users. Use case descriptions UC_AWOB_PM_02_Invite_Collaborators, mockups are [TBD] Status: Invitor can see and update the default text from the Invitation form. Current invitation notification will be extended to contain the role in which user was invited. We use default roles (Project Lead, Project Member, Project Manager) - we will not use any other field for additional "scientific roles" in this release. This can be provided in the text of the default message by the invitor. Sent invitations feature will not be implemented in 0.5

Jkim 10:23, 13 February 2012 (CET) Default text must be slightly updated since the invitations are now going to registered users as well.

Jkim 10:23, 13 February 2012 (CET) Invitee must be able to see the invitation text on his/her dashboard.

Jkim 10:23, 13 February 2012 (CET) Strictly speaking Project Lead is not a role that can be assigned. It is the "role" that the Project Creator "plays".

Task 006, AWOB Roles
Scope 0.5: Understand and model AWOB roles (project creator, project member, PI, CoI...)

Status: Some roles important for project management will be re-labeled or newly defined such as: Project Lead, Project Manager, Project Member Task Lead, Task Manager, Task Member

Jkim 10:27, 13 February 2012 (CET) We ask for Project Manager to be added to the Project Member role supported in Demonstrator. As mentioned above, Project Lead is (for 0.5 at least) not an assignable role, as Project Creator is the one leading the Project.

Jkim 10:27, 13 February 2012 (CET) Similar for Task Lead. The creator of the task has this role, which is (in 0.5) not assignable. We need Task Manager and Task Member.

Jkim 10:27, 13 February 2012 (CET) Privileges corresponding to these roles are defined in AWOB_Task_006.

Task 007, Task management
Scope 0.5: ???

Status: Create task : Jkim 10:29, 13 February 2012 (CET) In our opinion visibility is well enough understood to be able to be supported in 0.5. It is not related to larger workflows.
 * visibility will not be implemented as it is related to a bigger workflow modification which is not yet fully understood, however in 0.5 we will prepare specification and implementation concept.
 * task creation notification will not be implemented, we will prepare specification and implementation concept in 0.5  (we would like to check the overall notification implementation in AWOB - e.g. via activities or assets publisher portlet (add additional customization options)
 * task workspace will be lazy created by invocation of the task-link after task is created
 * task site template has to be created that contains: task metadata, wiki, message board (acting as a "task-wall" with 1 default category e.g. General and 1 default thread e.g. public discussion), document library folders for input/output resources Change task status:
 * pending->in progress: user will change the task status and system will "lock" message board (public wall) from further editing; system will switch all wiki pages as "read-only" for project members.
 * --Jkim 12:36, 13 February 2012 (CET) Task wiki page becomes 'read-only' for project members only if visibility = 'project' while 'in progress' status. See post conditions UC_AWOB_PM_09_Change_Task_Status.


 * in progress->completed or in progress-cancelled: user will change the task status and system will set the task workspace as read only for project members  http://colab.mpdl.mpg.de/mediawiki/AWOB_Task_007#Implementation_Model_Description
 * --Jkim 12:39, 13 February 2012 (CET) Once 'complete/cancelled' the task workspace becomes read only for all project members including task lead, task manager, task members.

Task 010, AWOB dashboard
Scope 0.5: What shall be in the AWOB Dashboard

Status: We provide Personal Site template and will be refined by GUI

Task 011, Layout issues - GUI
Scope 0.5: ???

Status: Document library, refinements of CSS provided by the LR 6.1 Themes, merging so-theme and astro-theme

Related to Task 011
Scope 0.5: Revise the GUI for Document library to show smaller document icons

Status: OK

Task 014, Liferay social side
Scope 0.5: ???

Status: Already chat, messaging provided for 0.5

Task 017, AWOB comments
Scope 0.5: Use cases, model, implementation

Status: AWOB Comments will not be explicitly provided as separate feature as these are enabled for each LR resource already - We would like to learn from users how they would use the comments first.

Task 018 Upgrade to LR 6.1
Scope 0.5: From 6.0.6 to 6.1 new portlets, hooks, themes, social office

Status: The basic upgrade is done, but makes no sense to use old custom portlets as social office features offer more functionality which we will customize - projects, invitations and tasks

Task 019, Task management implementation
Scope 0.5: TM implementation

Status: See comments on Task 007

This might be a new entry in the task table: Task 020, AWOB projects
Scope 0.5: AWOB Projects - upgrade to 6.1 and reimplementation in SO portlets

Status: Sites shall be customized to behave as Projects or Tasks

This might be a new entry in the task table: Task 021, AWOB release procedure
We shall prepare a release procedure which clearly tags AWOB code and generates properly documentation from one release to another

This might be a new entry in the task table: Task 022, AWOB content deployment
Deployment of templates and content; Site templates and web content have to be archived and prepared for deployment automatically and included in the AWOB bundle