Talk:UC AWOB PM 17 SPEC Make ePublication

MPDL,GAVO

PM_17_Add_Publication_To_Project_Publications =OLDER VERSION of R0.9=

PM_17_01_Add_ePublication_To_ Project_ePublications

 * R0.9


 * 1) ePublication has
 * 2) WIKI: allow child pages
 * 3) ePub’s metadata
 * 4) title, abstract, authors(contributors to the content of the ePublication,, may be different from editors)
 * 5) Publication (eg., paper) & its metadata
 * 6) Reference to the paper if published in  a journal already
 * 7) Designated resources folder for data
 * 8) ePublication Editors
 * 9) creator: the user who creates of an ePublication
 * 10) Internal has
 * 11) Option to set the visibility
 * 12) Available to Project Lead, and ePub creator only
 * 13) the option possibilities are
 * 14) Project members only (default)
 * 15) Group
 * 16) Consortium
 * 17) AWOB-TBD
 * 18) Public(World) - TBD

Actors

 * 1) Project Lead
 * 2) Project Manager

Steps

 * 1) 	The actor selects an option to add ePublication from ePublications. Its metadata are
 * 2) Title
 * 3) Abstract
 * 4) Authors
 * 5) 	The system creates an ePublication which consists of
 * 6) WIKI : Child pages allowed.
 * 7) Attachment? No
 * 8) Publication and its metadata(the same metadata as in publication archive except group)
 * 9) title of publication
 * 10) authors of the publication as appear in the publication
 * 11) contact including his/her e-mail address
 * 12) abstract of publication
 * 13) status of publication submission
 * 14) publication type
 * 15) Link to publication
 * 16) ADS bibcode
 * 17) arXiv
 * 18) other
 * 19) Designated resource folder for data
 * 20) All resources in this folder will be visible to the same group(s) as the whole ePublication.
 * 21) Add Editors of ePub


 * 1) Internal has
 * 2) Option to set the visibility
 * 3) Available to Project Lead, and ePub creator only
 * 4) the possibilities are
 * 5) Project members only (default)
 * 6) Working group
 * 7) Consortium
 * 8) Public(World) - TBD
 * 9) 	Actor enters the information
 * 10) All fields are optional except the visibility setting.

Post conditions
For ‘save’
 * 1) 	Log changes in ePublications of what’s new/progress of the projec.
 * 2) 	Notify
 * 3) 	Whom: project members excluding the actor
 * 4) 	By
 * 5) 	email: sender = actor.
 * 6) 	AWOB internal notification

PM_17_02_Change_ePublication_Visibility

 * R0.9

Actor

 * 1) Project Lead of the project to which an ePub belongs
 * 2) ePub Creator who is
 * 3) project manager

Preconditions

 * 1) The system status of the selected project is open.

Steps

 * 1) Actor chooses an option to change the visibility of an ePublication
 * 2) Actor is asked for confirmation of the action.

Post conditions
If actor confirms positively the system does the following


 * 1) Make all the content available to the selected user group except
 * 2) Adding editors to the ePublication
 * 3) Setting its visibility
 * 4) For consortium project if visibility = consortium
 * 5) the link to the ePub appears on the consortium project list.
 * 6) All content of the ePub is visible (read-only) to all members of consortium.
 * 7) For group project if visibility = group
 * 8) the link to the ePub appears on the group project list.
 * 9) All content of the ePub is visible (read-only) to all members of group.
 * 10) For group project if visibility = consortium
 * 11) the link to the ePub appears on the group project list.
 * 12) the link to the ePub appears on the consortium project list.
 * 13) All content of the ePub is visible (read-only) to all members of group.
 * 14) All content of the ePub is visible (read-only) to all members of consortium.
 * 15) Log the change in what’s new/progress of the project.
 * 16) Announce/notify the selected user group  as follows:
 * 17) Visibility = group notify
 * 18)  by
 * 19) Email: sender = actor
 * 20) Internal awob notification
 * 21)  whom: all members of the relevant group
 * 22) Visibility = consortium notify
 * 23)  by
 * 24) Email: sender = actor
 * 25) Internal awob notification
 * 26)  whom: all members of the relevant consortium

PM_17_03_Add_Editors_to_ePublication

 * R0.9
 * Similar to adding members to group or task.

Actors

 * 1) ePub creator

Steps

 * 1) Actor is given an option to add members from the list of project members.
 * 2) There is no role assignment option.

Post Conditions

 * 1) The system shows the added members to the editor list of an ePub.
 * 2) Log the change in What’s new/progress of the selected project.
 * 3) Notify
 * 4) Whom: the members who are added to the ePub
 * 5) By
 * 6) email: sender = actor
 * 7) Awob internal notification

PM_17_04_Link_to_ePublication_from_Publication_Archive

 * R0.9

Actors

 * 1) Project Lead of the project to which the ePub belongs and either
 * 2) Consortium lead or
 * 3) Consortium manager or
 * 4) Consortium project manager
 * 5) ePub creator and
 * 6) project manager and either
 * 7) Consortium lead or
 * 8) Consortium manager or
 * 9) Consortium project manager

Steps

 * 1) Actor navigates to consortium publication archive.
 * 2) Actor is given an option to ‘Add ePublication’.
 * 3) Actor is given a list of ePublications
 * 4) Of project in which actor is project lead OR
 * 5) In which actor is epub creator and project manager
 * 6) Actor chooses one from the list.

Post conditions
The system does the following
 * 1) An entry appears on the archive providing info on the ePub with link to ePub overview.
 * 2) If a “real” publication exists in ePub also a direct link to the Publication page of the ePub pages.
 * 3) On publication archive list display title, abstract, authors as follows:
 * 4) If a "real" publication exists in ePub display the title, the abstract, the authors of the real publication.
 * 5) Otherwise, display those of the ePub.
 * 6) Status should refer to real pub only
 * 7) Log the changes consortium what’s new.
 * 8) Notify
 * 9) Whom: all consortium members
 * 10) By
 * 11) email: sender = actor
 * 12) By internal AWOB notification

PM_17_05_Edit_ePublication

 * R0.9

Actors

 * 1) All of ePub editors

Steps

 * 1) Actor selects an option to edit ePublication.
 * 2) Actor edits the content.
 * 3) Actor clicks save.

Post conditions

 * 1) The system saves the change.
 * 2) Log the change in project’s what’ new/progress.