UC AWOB PM 17 SPEC Make ePublication

MPDL,GAVO

PM_17_Add_ePublication_To_Project_ePublications =R1.0=

PM_17_06_Make_Product_Publicly_Available

 * R1.0
 * Make a product site publicly available. (Read-only for public)
 * Provide an option to review 'public page'.
 * [JK] Is this agreed on?
 * Public view should not display navigation info(like breadcrumbs, horizontal navigations, etc)
 * NO need to distinguish 'Public' vs 'Working' version of a product site:
 * Implement with 'View/Representation' instead of 'Copying' of 'Working' site.
 * For a product of which visibility is 'public' if the product site changes then the change is immediately available to the public.
 * Actor can change its visibility so that the product site is not publicly available.
 * If so on public site show 'Temporarily unavailable' or 'Under construction' or something equivalent.

Actor

 * 1) If a product belongs to a project
 * 2) Project Lead of the project to which a product belongs
 * 3) Product Creator  who is
 * 4) project manager
 * 5) If a product doesn't belong to a project
 * 6) Product Creator 

Preconditions

 * 1) The system status of the selected project is open if a product belongs to a project

Steps

 * 1) Actor chooses an option to change the visibility of a product to 'Public'
 * 2) Alternatively, have a separate action to publish product.
 * 3) Actor is asked for confirmation of the action.

Post conditions
If actor confirms positively the system does the following


 * 1) Make all the content publicly available(Read-Only) except
 * 2) Adding editors to the product but display the list of editors.
 * 3) Progress
 * 4) Setting its visibility
 * 5) Log the change in what’s new/progress of the project.
 * 6) Announce/notify : None

=R0.9=

PM_17_01_Add_Publication_To_ Project_Publications

 * R0.9


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

Actors

 * 1) Project Lead
 * 2) Project Manager

Steps

 * 1) 	The actor selects an option to add Publication from Publications and is brought to a form with
 * 2) Title
 * 3) Abstract
 * 4) 	The system creates a Publication site which consists of
 * 5) WIKI : Child pages allowed.
 * 6) Attachment? No
 * 7) Publication and its metadata
 * 8) title of publication
 * 9) abstract of publication
 * 10) authors of the publication
 * 11) contact including his/her e-mail address
 * 12) creator(Publication lead)
 * 13) editors
 * 14) expected date to finish
 * 15) Actor is given an option to specify whether there is a real paper. If true
 * 16) status of publication(Status)
 * 17) N/A
 * 18) Submitted
 * 19) Accepted
 * 20) Rejected
 * 21) Published
 * 22) Withdrawn
 * 23) submission status comment
 * 24) simple text field
 * 25) all editors can edit this field
 * 26) read-only to any user who can view a publication
 * 27) publication type: its enumeration list is
 * 28) Refereed paper
 * 29) Non-refereed paper
 * 30) Conference proceedings
 * 31) Technical paper
 * 32) Book
 * 33) Posters
 * 34) Presentations
 * 35) Ph.D thesis
 * 36) Online publication
 * 37) White paper
 * 38) Internal report
 * 39) Other
 * 40) Link to a remote paper or PDF
 * 41) ADS
 * 42) arXiv
 * 43) other
 * 44) Designated resource folder for data
 * 45) All resources in this folder will be visible to the same group(s) as the whole Publication.
 * 46) Add Editors of Pub
 * 47) Identify the creator of a Pub: Publication lead
 * 48) Internal has
 * 49) Option to set the visibility
 * 50) Available to Project Lead, and ePub creator only
 * 51) the possibilities are
 * 52) Publication  (default)
 * 53) Project members only
 * 54) Group
 * 55) Consortium
 * 56) Public(World) - TBD
 * 57) 	Actor enters the information
 * 58) All fields are optional except title, creator, the visibility setting.

Post conditions
For ‘save’
 * 1) 	Log changes in Publications of what’s new/progress of the project.
 * 2) 	Notify - none

PM_17_02_Change_ePublication_Visibility

 * R0.9
 * To a larger scope

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 a Publication
 * 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 project if visibility = project
 * 5) 	All content of the Pub site is visible (read-only) to all members of project
 * 6) For consortium project if visibility = consortium
 * 7) the link to the Pub appears on the consortium project list.
 * 8) All content of the Pub site is visible (read-only) to all members of consortium.
 * 9) For group project if visibility = group
 * 10) the link to the Pub appears on the group project list.
 * 11) All content of the Pub site is visible (read-only) to all members of group
 * 12) For group project if visibility = consortium
 * 13) the link to the Pub appears on the group project list.
 * 14) the link to the Pub appears on the consortium project list if the project is announced to consortium project list.
 * 15) All content of the Pub site is visible (read-only) to all members of group.
 * 16) All content of the Pub site is visible (read-only) to all members of consortium.
 * 17) Log the change in what’s new/progress of the project.
 * 18) Announce/notify the selected user group  as follows:
 * 19) Visibility = group notify
 * 20)  by
 * 21) Email: sender = actor
 * 22) Internal awob notification
 * 23)  whom: all members of the relevant group
 * 24)  what: publication '$title' is available to $group_shortname
 * 25) Visibility = consortium notify
 * 26)  by
 * 27) Email: sender = actor
 * 28) Internal awob notification
 * 29)  whom: all members of the relevant consortium
 * 30)  what: publication '$title' is available to $consortium_shortname.

PM_17_02_a Change_Publication_Visibility_To_Smaller_Scope

 * R0.9

Actor

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

Preconditions

 * 1) 	The visibility of a given publication is larger than project if publication belongs to project.
 * 2) 	In R0.9 deal with the case that the visibility = consortium

Steps

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

Post Conditions

 * 1) 	If there exists a project which owns the publication(i.e., project publication) and it is linked to a consortium publication archive
 * 2) 	The link to publication in the publication archive becomes inactive.

PM_17_03_Add_Editors_to_Publication

 * R0.9
 * Similar to the use case which adds members to group or task.

Actors

 * 1) Pub 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 a Pub.
 * 2) Log the change in What’s new/progress of the selected project.
 * 3) Notify
 * 4) Whom: the members who are added to the Pub
 * 5) By
 * 6) email: sender = actor
 * 7) Awob internal notification

PM_17_04_Link_to_Publication_from_Publication_Archive(Add product to Featured products)

 * R0.9
 * This use case is for adding a product to 'Featured Products'.

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) Pub creator and
 * 6) project manager and either
 * 7) Consortium lead or
 * 8) Consortium manager or
 * 9) Consortium project manager
 * 10) Consortium lead
 * 11) Consortium manager

Pre conditions

 * 1) Publication visibility is at least consortium

Steps

 * 1) Actor navigates to consortium publication list(i.e., 'products' list of consortium) which shows all publications(i.e., products) of which visibility = consortium
 * 2) publication9i.e., product) site
 * 3) products list on 'projects and products'.
 * 4) Actor is given an option to ‘Link Publication’(i.e., add to featured products) or something equivalent.
 * 5) Actor can link Publications(i.e., Add to Featured products) which satisfy the following conditions
 * 6) its visibility = consortium AND
 * 7) belongs to a project in which actor is either project lead OR  Pub creator
 * 8) Actor chooses one from the list.

Post conditions
The system does the following
 * 1) An entry appears on the archive(i.e., Featured products) providing info on the Pub(i.e., product) with link to Pub(i.e., product) overview.
 * 2) The entry is now listed on both 'products' of 'projects and products' and 'Featured products' of consortium
 * 3) On publication archive(i.e., Featured products) tabular view displays
 * 4) Group name (if publication belongs to a project which belongs to a working group), title, abstract, contact, authors, publication archive status, type, modified date, expected date to finish
 * 5) Log the changes consortium what’s new.
 * 6) Notify
 * 7) Whom: all consortium members
 * 8) By
 * 9) email: sender = actor
 * 10) By internal AWOB notification

PM_17_05_Edit_Publication

 * 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.