AWOB Task 031

MPDL,GAVO

General Information
Grouping: Short description: Continued from Task 006

Member title

 * Support to enter "title" in awob?
 * [AM] For supporting publication archive it is not necessary. But for supporting consortium management, yes.
 * Should support a predefined list of titles (defined by scientist, eg Andrea, or by system (which list? PI, Co-I, Project Scientist, …)?)
 * [AM, FH] Preferable to user defined enumeration list. But free text string is fine in the beginning.
 * For eROSITA consortium titles are PI, Project Scientist, Working Group Chair, Steering Committee, Senior Scientists, Member Scientists.
 * Features to support regarding titles?
 * create a mailing list, eg, mailing list for working group chairs, one for steering committee.
 * identify titles in consortium member list.
 * Should privilege assignment to a member dependent on "title"
 * [AM] title is related w/ privileges. But the system doesn't need to assign automatically what privileges to give to each title. In current eROSITA consortium wiki there are two types of user groups
 * admin group: Consortium members whose titles are PI, project scientist, members of steering committee, senior scientist, read/write access privileges to all working group pages. can invite his/her phD student in the consortium.
 * any group: the rest of the members, read/write access to the working groups that she/he is a member of. Read only for the rest working group pages.
 * Support for creating custom "member groups" to independent of title
 * examples :'Task force' like 'Tiger group' (in ivoa). Specifically in eROSITA task force group are 'simulation', 'mission strategy committee', etc. these groups mainly investigate subjects across working groups, short-term activities. These groups are formed to organize internal activities. These groups do not appear in organizational structure description of consortium public page.
 * If the task force group wants to produce a paper of its own it is more than likely to propose such a paper on a working group which is mostly related.
 * Therefore for such a task group it is sufficient in AWOB to provide a place which has a member list including inviting members to a group,  resources, discussion thread and to define tasks. In AWOB it would be sufficient to allow to create a project in a consortium level rather than in a working group.

Question on Liferay Permission System

 * [JK] Suppose that project lead wants to publish results to all consortium members using ePublication. And she/he wants to share some files uploaded in project resources using 'Related Assets'. Assume that these files are accessible by the project members only.
 * if these files are linked to ePublication by related assets, is it possible for consortium members who are not a project member to access them?