AWOB Meeting 2011-12-16

MPDL,GAVO

General Information

 * Date: Fri, Dec 16, 2011; 10 h
 * Place: MPE/Garching
 * Partcipants
 * Natasa Bulatovic
 * Matthias Egger
 * Jaiwon Kim
 * Gerard Lemson
 * Andreas Vogler

Scope of the Meeting
Focusing on AWOB Tasks 003, 006, 007, 017 (cf. AWOB_Tasks)

Agenda
[JK]


 * Discuss conceptual model.
 * GL and JK will explain the model once more, focusing on the main concepts, Task in particular.
 * There are some updates on AWOB_Task_007
 * For overall conceptual model see Concepts Overview
 * Roles/privileges
 * We think it would be good to then also come to an understanding how we want to deal with privileges in AWOB.
 * It seems clear that a few simple roles will be insufficient.
 * We should look at Liferay's support for this as much as possible, though tuned to the AWOB concepts as defined in the model.

Minutes
[JK] The remark 'In general, tasks should get visible in the end, not only the results - so that the "making of" is available. ' is not quite correct. It depends on project, and its policy. Figure 1 Figure 2
 * Conceptual model see Concepts Overview
 * Task needs: Upload, work space(s), permissions. Work space: Share, code repository, wall
 * NB: is everything related to the project?
 * GL: A project is a work space as a task or the dashboard are work spaces. Hierarchy. A work space here is an AWOB request independend of the LR implementation. The folder of the task is under the root folder
 * NB: Thus: Project contains folder, web content, memebers etc. A project also contains a task, which is again made up out of folder, web content, members.
 * Who can see the task? Who has the lead? Correct permissions/privileges should be assigned when creating the task. There will be a task list, visible for all memebers. But not everybody can look inside. In general, tasks should get visible in the end, not only the results - so that the "making of" is available. It may be possible, however, to hide the wall.


 * NB: Problems to assign Wiki Pages automatically, LR only offers roles & groups. For permissions, liferay distinguishes between roles (correlated to actions), objects and users (+use-groups, communities, organizations)
 * GL: Tune roles & actions - what are you allowed to do at the task level?
 * GL: Extra Wiki for task
 * Closer look to the wall as known from facebook, two implementations in LR 6.1: The wall and message board. Advantage of both vs. Wiki: Time ordered
 * Message board looks more promising. However, it has a more complicated editor. Simplify the editor?
 * Possibly usrs with permission to add entry to wall/message board but read only for web contents
 * Meetings etc.: Also with work space addedf to a meeting? Add agenda?
 * Question: What kind of roles, permissions/privileges, actions
 * Use AWOB matrices, use simple terms like task lead to describe roles
 * GL: What does it mean to do something in the content of pojetcs and tasks? Look at the table "existing roles".
 * GL: Task creator as a role?
 * Finally, we come up with the following roles: task lead and task member. The task lead creates and starts the task
 * Roles in general within AWOB: Project lead, project manager, project member. Task lead, task member. AWOB user, AWOB administrator.