AWOB Task 032

MPDL,GAVO

General Information
Grouping: Short description:

Improve default invitation text

 * 1) differentiate default text depending on
 * 2) whether it is sent to an e-mail or AWOB user
 * 3) whether it is sent in the context of consortium, working group, project.

The default text for an awob user is as follows:

Dear Colleague,

I would like to invite you to participate in my $full_name $type. A short description of the $project_full_name $type is as follows:

$project_short_description

You can accept or decline to join the $type through the invitation waiting on your AWOB personal home.

Best Regards,

$invitor_name $invitor_address

where $type is either project, working group, consortium and $full_name is title of a selected $type

The default text for an email invitation is as follows:

Dear Colleague,

I would like to invite you to participate in my $full_name $type. For this $type I have created a collaborative site in the online Astronomer's Workbench (AWOB). You will get access to this $type site if you accept the invitation.

A short description of the $project_full_name $type is as follows:

$project_short_description

If you are an AWOB user, you can accept or decline to join the $type through the invitation waiting on your AWOB personal home.

If you are not an AWOB user yet, and do not wish to participate in the $type, please notify me by email of your decision. If you wish to accept the invitation please do the following steps:

1. Please create an AWOB account at $registration_link. 2. If your account is created with this email address, you should find an invitation waiting on your personal dashboard. If not, please notify me of your new AWOB user name by email or using the AWOB messaging functionality. Once I receive your user name, I will invite you again and you can accept the invitation on your AWOB dashboard.

You can find information about the AWOB platform at $link_to_awob.

Best Regards,

$invitor_name $invitor_address

where $type is either project, working group, consortium and $full_name is title of a selected $type


 * 1) The default invitation text versus saved message
 * 2) Is it necessary to support the default text per project manager/lead or have a single default text per project
 * 3) which message should be available from 'send invitation' other than default?
 * 4) only the last one sent from project regardless who sent it.[implemented in 0.6]
 * 5) last one for each manager
 * 6) able to select from manager's previous invitations
 * etc
 * etc

Improve the list of sent invitations

 * 1) able to view sent invitations in a project
 * 2) for all project members all invitations sent from the project should be available including who/when/to whom, status for each invitation.
 * 3) for project lead make available additional information including invitation text, proposed AWOB role, comment/response from invitee for all invitations from project.
 * 4) for project manager make available the same additional information available to project lead only for his/her invitations from project.[TBD]

Enable to clean up pending invitations from the list

 * 1) an invitation which doesn't get any response from an invitee because either it being ignored or the invited person create an AWOB account using different e-mail address from what is specified in the invitation. Such an invitation remains on the list of sent invitations with pending status. It would be good to clean up those after a while
 * 2) project lead can delete any pending invitations which didn't get any responses from invitees
 * 3) project manager can delete only those invitations sent by him or her [TBD]
 * 4) Accepted invitation gets moved to the member list.
 * 5) Assuming that the member list will be enriched, once he/she becomes a member, she/he appears on the member list including the accepted invitation text, when join/leave, email, role, etc.

Invitation to a mailing list
useful to support an invitation to a mailing in particular to support custom user groups/teams in AWOB workspace like project, working group, consortium. The mailing list for a user group/team is useful not only for sending invitations but for communication in general. In order for AWOB to support this feature the mailing list must be defined in AWOB system.
 * 1) support to define  a mailing list
 * 2) what's implemented in awob0.5: upon a workspace(project, task) is created the system creates a default mailing list for the workspace. As the members of the workspace change the mailing list is synchronized automatically.
 * 3) support an option to upload an external mailing list
 * 4) eg. enter a mailing list in GUI. copy the list to GUI.
 * 5) support an option to create a mailing list in AWOB  which consists of AAWOB members or/and email members not in context of a workspace.
 * 6) eg., create a mailing list for working group chairs.
 * 7) send invitations to a mailing list which the system understands.
 * 8) each person in the list gets an email invitation.
 * 9) each invitation appears on sent invitations with status pending.

Import mailing list to AWOB

 * As of AWOB 0.5 from invitation it is possible to enter multiple email addresses to 'Add Email Address'.
 * I think that it would be useful to provide a feature to import an existing mailing list to AWOB.


 * steps
 * user selects an option to import existing mailing list.
 * enter a mailing list (eg., awob@gwdg.de)
 * copy & paste recipient email list into GUI.

request working group/project membership

 * the membership request is available in context of consortium project/working group. This use scenario can be extended to task membership request in the future.
 * there are some differences between requests to join a project and a working group. There is no status for working group itself while in project there is.
 * it requires to keep track of requests for both user and recipient sides either by supporting new types of lists or by modifying sent invitations in project collaborators and project invitations in personal home.
 * [JK] update the conceptual model to include 'request'

Request working group membership

 * actors: consortium member
 * rough steps
 * actor selects an option to request to join working group. The option may include a text area for adding comment along the request. The option is available from
 * working group list or/and working group members [TBD]
 * the request appears on received membership requests on working group workspace.
 * It also appears on actor's Personal dashboard (something like requested a working group membership  new to personal dashboard)
 * working group lead or working group manager accepts(assign appropriate role to the new member) or declines the request.
 * If accepted the actor appears on the working group member list and comments if exist
 * The request entry is removed from Received membership requests.
 * If declined the actor receives the notification to actor's personal dashboard (requested working group membership list).
 * The status of the request entry is updated to declined.

Request project membership

 * actors: consortium member
 * preconditions: project selected for membership request must be neither in 'completed/cancelled/closed'. i mentioned specifically in these terms because if the request is from working group list a project in 'pending' could solicit requests.
 * rough steps
 * actor selects an option to request to join project. The option may include a text area for adding comment along the request. The option is available from
 * managed project list of consortium
 * managed project list of working group
 * should this option available to a project in pending ?[TBD]: this should be up to project lead. Here goes the question status vs visibility.
 * the request appears on Received membership requests(TBD)on project member page w/ pending status.
 * The request appears on actor's personal dashboard (something like requested project membership which is new to personal dashboard])
 * project lead or manager(TBD) accepts and assign appropriate role to the new member, or declines the request.
 * If accepted the actor appears on the project member list along w/ the comment if there is.
 * The request entry is removed from Received membership requests.
 * If declined the actor receives the notification to actor's personal dashboard (requested project membership list).
 * The status of the request entry is updated to declined.