AWOB Meeting 2011-07-04

MPDL,GAVO

General Information

 * Date
 * Mon, July 4, 2011; 14.00 h - 17.45 h
 * Place
 * MPDL, room 213
 * Participants
 * Bulatovic, Natasa
 * Kiefl, Rupert
 * Kim, Jaiwon
 * Lemson, Gerard
 * Makarenko, Vlad
 * Voges, Wolfgang
 * Vogler, Andreas

Agenda

 * Scope
 * Review the use case(s)
 * Preparation read:
 * Demonstrator release scope
 * Project management use cases
 * User management use cases
 * AWOB Actors
 * AWOB concepts Project
 * Conceptual model
 * Review/revise mockups
 * see Mockups, black books only (there shall be 5 black books shown to you), log-in with your email (if not possible, check with Rupert)
 * Review demonstrator state
 * go through Liferay to see which of above use cases are supported
 * Define ToDos
 * based on what is already possible and what is to be done

Scope

 * We agree to freeze the scope as defined here until implementation phase of the demonstrator is finished
 * user management
 * only 1 e-mail adress, no rule based authorization and automatic role assignment
 * user registration: first name and last name only (no middle name, no organization)

Administrative

 * JIRA is set up to take issues that need to be followed up (Improvemnts, Bugs, Tasks)
 * AWOB mailing list with messages containing 'Implementation highlights' in subject header, to inform on progress

What should be on the startpage?

 * AWOB project which is public.
 * Latest news about AWOB.
 * Document about awob.
 * do not remember "document about AWOB" discussion, can someone precise?
 * Andreas: As far as I remember, a short version of the actual AWOB info. I'll have a look to the actual Liferay viea and then I try to compile a new intro and send it to NB...


 * Menu items: Welcome, Documentation, News

Liferay AWOB create user

 * email is created by system and is sent to user by email.

Liferay invite collaborators

 * this portlet is visible only to PI of the project.

project public page url

 * could based on Project shortName
 * liferay provides a way to set the url.

project's visibility

 * private: MUST not appear on any project list except on its project member's dashboard.
 * public: closed but publicly available.
 * no 'restricted' implemented in demonstrator.

project page

 * Needs navigation on the left handside (open/close if necessary).
 * Navigation should be drilled down to subpages.

=TODO =
 * What should be on start page?
 * GUI:
 * Finalize the gui on balsamiq(0) - Rupert/Jaiwon clean up some pages
 * Rupert - create an alternative project page/dashboard(1)