UC AWOB CM 02 Manage Consortium Working Group

MPDL,GAVO

The following usecases are similar to manage consortium usecase. The main differences are:
 * actors on each use case
 * WG shortname, title: must be unique in a consortium
 * assign working group chair/deputy chairs: not described here.

=UC_AWOB_CM_02 _1 Create Working Group=

Actors
Consortium Lead

Pre-conditions
1. A selected consortium is open.

Steps

 * 1) An actor selects an option to create a new WG from a consortium workspace.
 * 2) The actor provides the following information.
 * 3) Short name( mandatory)
 * 4) Unique within a given consortium
 * 5) title(optional)
 * 6) Unique within a given consortium
 * 7) Short description/goal (optional)
 * 8) save or cancel
 * 9) the system validates the input.
 * 10) Check whether all the mandatory fields are provided by the actor.
 * 11) Apply the same validation rule as in consortium, project short name
 * 12)  Max 30 chars
 * 13) No white space
 * 14) ‘_’, ‘-‘ allowed
 * 15) Unique consortium wide
 * 16) If valid
 * 17) The system creates a new WG (see Post conditions.).
 * 18) If not valid
 * 19) The system displays the error messages: what's missing, or what's wrong with given values.

Post conditions
The system creates a WG.


 * 1) The following additional metadata are specified added to WG internally
 * 2) system create date (mandatory)
 * 3) system close date(optional)
 * 4) system status (mandatory) open(default)/close
 * 5) Displays the WG metadata
 * 6) See mockup
 * 7) Display in the category of ‘overview or WG info’ of WG’s what’s new (or change log) when and by whom WG is created.
 * 8) also the following components are created for the new WG.
 * 9) what's new
 * 10) overview
 * 11) members
 * 12) calendar
 * 13) discussion
 * 14) WG projects
 * 15) Resources
 * 16) WG publication archive(or just publications)
 * 17) the actor becomes Working Group Lead of the new WG.
 * 18) the new WG appears on consortium's working group list.
 * 19)  if restricted WG, should it be listed on the list? ASK SCIENTIST:
 * 20) the new WG appears on actor's personal workspace.
 * 21) layout [TBD]
 * 22) actor is brought to Overview of the new WG workspace.
 * 23)  Alternatively, give options to go to the new WG workspace or back to consortium's WG list.
 * 24) The following options should be available to the actor from WG workspace.
 * 25) For a full list view ‘table’
 * 26) Edit overview.
 * 27) invite WG members.
 * 28) identify WG chair/deputy chairs
 * 29) add a WG project.
 * 30) Add publication to WG publication list.
 * 31) Add an event to WG calendar.
 * 32) start discussion thread.
 * 33) upload/download resources.

Questions:

Any need for ‘restricted’ WG?

=UC_AWOB_CM_02 _2 View ‘Consortium-wide’ Working Group =

What a member can see depend on member’s role. Therefore, this use case is splitted into two parts.

This use case can be replaced by with a table.

Pre-conditions
WG visibility must be consortium-wide.

Description for any consortium member who are not a WG member
Any consortium member who is not a member of a selected working group can view the following WG components:


 * 1)  goal/title
 * 2)  overview
 * 3)  member list
 * 4)  managed project list
 * 5)  publication list [TBD]
 * 6)  calendar

Description for WG member
Who can see and do what in a selected WG.

1. For WG lead


 * 1) Edit Goal/Title
 * 2) View Goal/Title
 * 3) Edit Overview
 * 4) View Overview wiki
 * 5) View What's new
 * 6) Accept membership request
 * 7) Invite members
 * 8) View member list
 * 9) Change member role
 * 10) Create WG Projects
 * 11) Promote WG projects to consortium managed projects
 * 12) View WG projects
 * 13) Upload to WG publication archive
 * 14) View WG publication archive
 * 15) Add calendar event
 * 16) View calendar
 * 17) Start discussion threads
 * 18) View discussions
 * 19) Post on discussion threads
 * 20) Upload/Download files
 * 21) View resources/files

2. For WG manager


 * 1) Edit Goal/Title
 * 2) View Goal/Title
 * 3) Edit Overview
 * 4) View Overview wiki
 * 5) View What's new
 * 6) Accept membership request
 * 7) Invite members
 * 8) View member list
 * 9) Change member role
 * 10) Create WG Projects
 * 11) Promote WG projects to consortium managed projects
 * 12) View WG projects
 * 13) Upload to WG publication archive
 * 14) View WG publication archive
 * 15) Add calendar event
 * 16) View calendar
 * 17) Start discussion threads
 * 18) View discussions
 * 19) Post on discussion threads
 * 20) Upload/Download files
 * 21) View resources/files

3. For WG project manager


 * 1) View Goal/Title
 * 2) View Overview wiki
 * 3) View What's new
 * 4) View member list
 * 5) Create WG Projects
 * 6) View WG projects
 * 7) Upload to WG publication archive
 * 8) View WG publication archive
 * 9) Add calendar event
 * 10) View calendar
 * 11) Start discussion threads
 * 12) View discussions
 * 13) Post on discussion threads
 * 14) Upload/Download files
 * 15) View resources/files

4. For WG member


 * 1) View Goal/Title
 * 2) View Overview wiki
 * 3) View What's new
 * 4) View member list
 * 5) View WG projects
 * 6) View WG publication archive
 * 7) Add calendar event
 * 8) View calendar
 * 9) Start discussion threads
 * 10) View discussions
 * 11) Post on discussion threads
 * 12) Upload/Download files
 * 13) View resources/files

UC_AWOB_CM_02 _3View ‘Restricted’ Working Group

TBD

=UC_AWOB_CM_02 _4 Edit Working Group Metadata=

This use case is the same as Edit Project/Consortium metadata use case.

Actors
1. WG lead

2. WG manager

Pre-conditions

 * 1) The system status of a selected consortium is open.
 * 2) The system status of a selected WG is open.

Steps

 * 1) an actor selects an option to change WG metadata. The actor can change the following metadata:
 * 2) title(optional)
 * 3) goal (optional)
 * 4) submit

Post conditions
The system updates WG metadata accordingly.


 * 1) system last modified date is updated internally.
 * 2) The changes appear on what's new on the category of 'WG overview'
 * 3) Alternatively, it appears on the category of ‘WG metadata’.

=UC_AWOB_CM_02 _5 Edit Working Group Overview=

This use case is the same as Edit Project/Consortium Overview wiki use case.

Actors
1. WG lead

2. WG manager

Pre-conditions
The system status of a selected WG is open.

Steps

 * 1) an actor selects an option to edit a full description of WG in WG overview.
 * 2) actor optionally unchecks ‘This is a minor edit’ (See edit consortium overview)
 * 3) submit

Post conditions

 * 1) The system updates WG overview accordingly.
 * 2) if ‘this is a minor edit’ is unchecked
 * 3) The changes appear on what's new on the category of 'WG overview (or something equivalent)'.
 * 4) if ‘this is a minor edit’ is checked
 * 5) The changes does not appear on WG what's new