UC AWOB CM 06 SPEC Manage Consortium Publication Archive

MPDL,GAVO

=R0.9=

UC_AWOB_CM_06_1_R0.9_Add_Publication_To_Archive
Change:
 * Status
 * Its enumeration (See also use case UC_AWOB_PM_17_SPEC_Make_ePublication)
 * In progress
 * Draft uploaded
 * Submitted
 * Accepted
 * Rejected
 * Published
 * Withdrawn
 * Added a text field 'Comment'
 * Free format text field: Eg., submitted to MNRAS on 2013-10-11, received referee report on ...
 * Who can edit: All editors of pub
 * Read only for any users can view a publication.

Actors

 * Consortium Lead
 * Consortium Manager
 * Consortium Project Manager

Pre Condition

 * The system status of consortium is 'open'.

Steps

 * Actor is in consortium publication archive page.
 * Actor "clicks a button" to "add a publication".
 * Actor is given an option to specify status
 * In progress
 * Draft uploaded
 * accepted
 * rejected
 * Published
 * Withdrawn
 * an actor can specify a (working) group name if a publication belongs to a (working) group of a consortium. Alternatively, system extracts it and displays it on the publication archive tabular list.
 * A page is given an option to enter information required to create a publication site(SEE UC_AWOB_PM_17_SPEC_Make_ePublication)
 * Actor submits.

Post conditions

 * The system creates a consortium publication site.
 * Notify
 * Whom
 * All consortium members
 * By
 * AWOB notification
 * Email

Future developements

 * If document is extracted from remote repository, some of metadata may be automatically filled in.
 * --Jkim 18:26, 23 November 2012 (CET) moved to future release (agreed on Nov 23, 2012 by AV, NB, JK)

Actors

 * Consortium Lead
 * Consortium Manager
 * Consortium Project Manager
 * Consortium Member

Steps
There should be a page with a table with all publications that have been added.
 * url to paper or something equivalent
 * title
 * abstract
 * 'contact'
 * authors
 * ';' separeted list. Display first 5 authors followed by 'and N more coauthors?'
 * expected date to finish
 * 'status': enumeration values
 * In progress
 * Draft uploaded
 * Submitted
 * Accepted
 * Rejected
 * Published
 * Withdrawn
 * type: enumeration
 * Refereed paper
 * Non-refereed paper
 * Conference proceedings
 * Technical paper
 * Book
 * Posters
 * Presentations
 * Ph.D thesis
 * Online publication
 * White paper
 * Internal report
 * Other
 * related project: the link to the AWOB project which produced the publication
 * working group: if a project which led to publication is proposed and accepted within a specific working group (only appears on publication list on the archive)
 * Last modified: date time

For a selected publication different options are available depending on actor's role.
 * for consortium lead
 * download/view
 * edit if consortium lead is a publication editor
 * remove
 * for consortium manager
 * download/view
 * edit if consortium manager is a publication editor
 * remove
 * for consortium project manager
 * download
 * edit if consortium project manager is a publication editor


 * for consortium member
 * download/view
 * edit if consortium project member is a publication editor

UC_AWOB_CM_06_3_R0.9_Update_Publication_In_Archive
See UC_AWOB_PM_17_SPEC_Make_ePublication

UC_AWOB_CM_06_4_R0.9_Mark_Publicaiton_As_Withdrawn(Soft delete)
Able to mark a selected publication as removed by add ‘Withdrawn’ to publication archive status enumeration. ''No workflow related. ''
 * R0.9
 * Since 'Consortium archive' is replaced by 'Featured products' this use case is deprecated.

Actors

 * 1) Project lead of the publication if applicable(i.e., for project publication).
 * 2) publication creator.
 * 3) Consortium lead

Steps

 * 1) Actor is given an option to select ‘Withdrawn’ from publication status enumeration.

Post conditions

 * 1) The publication still appears on the list and still readable.
 * 2) Log in What’s new of consortium
 * 3) Notify
 * 4) Whom: all consortium members
 * 5) By:
 * 6) Email
 * 7) AWOB internal notification

UC_AWOB_CM_06_5_R0.9_Remove_Publication_From_Archive

 * Remove a publication from publication archive list. The use case doesn't require to delete hard delete it.
 * Since publication archive and publication are changed to ''Featured products' and 'Products', respectively, this use case is 'Remove product from Featured products'.
 * R0.9

Actors

 * 1) Consortium lead
 * 2) consortium manager

Steps

 * 1) Actor is given an option to remove a selected publication.
 * 2) Actor submits.
 * 3) The system asks for confirmation of the action.
 * 4) Actor confirms it.

Post conditions

 * 1) The publication is removed from the archive list.
 * 2) If the removed publication is consortium publication
 * 3) the removed publication is still available from publication drop down menu in horizontal navigation.
 * 4) Log in what’s new of consortium that the publication is deleted.
 * 5) Notify
 * 6) Whom
 * 7) The creator of the publication
 * 8) Consortium lead
 * 9) By:
 * 10) Email
 * 11) AWOB internal notification

=R0.8=

UC_AWOB_CM_06_1_R0.8_Add_Publication_To_Archive
Add the following to the postconditions
 * Notify
 * Whom
 * All consortium members
 * By
 * AWOB notification
 * Email

=R0.7=

Actors

 * Consortium Lead
 * Consortium Manager

Pre Condition

 * The system status of consortium is 'open'.

Steps

 * Actor is in consortium publication archive page.
 * Actor "clicks a button" to "add a publication".
 * A page opens offering various options for identifying the actual document.
 * Options for document are
 * Upload a document (eg PDF).
 * Provide a plain URL to a document inside AWOB, or external.
 * Enter a link or something else identifying a document in an external, known repository.
 * E.g. an ADS bib code, an arXiv id, ....
 * Actor submits.
 * The system shows a page (or on same page) for entering metadata.
 * List of metadata is TBD (similar to pubman).
 * If document is extracted from remote repository, some of metadata may be automatically filled in.
 * Actor can edit or provide additional metadata for a given document.
 * title
 * abstract
 * 'contact'
 * authors
 * expected date to finish
 * 'status': enumeration values
 * 'In progress': a temporary solution since there is no support for consortium managed projects. In progress has only rought abstract, title
 * Draft uploaded
 * Submitted
 * Accepted
 * Published
 * type: enumeration
 * refereed paper
 * non-refereed paper
 * conference proceedings or refereed proceedings
 * version:
 * last changes:
 * Temporary solution: date for each status change should be properly stored

Future developements

 * If document is extracted from remote repository, some of metadata may be automatically filled in.
 * --Jkim 18:26, 23 November 2012 (CET) moved to future release (agreed on Nov 23, 2012 by AV, NB, JK)

Actors

 * Consortium Lead
 * Consortium Manager


 * Consortium Member

Steps
There should be a page with a table with all publications that have been added.
 * url to paper or something equivalent
 * title
 * abstract
 * 'contact'
 * authors
 * ';' separeted list. Display first 5 authors followed by 'and N more coauthors?'
 * expected date to finish
 * 'status': enumeration values
 * 'In progress': a temporary solution since there is no support for consortium managed projects. In progress has only rought abstract, title
 * Draft uploaded
 * Submitted
 * Accepted
 * Published
 * type: enumeration
 * refereed paper
 * non-refereed paper
 * conference proceedings or refereed proceedings
 * version
 * last changes:

For a selected publication different options are available depending on actor's role.
 * for consortium lead
 * download
 * edit
 * delete
 * for consortium manager
 * download
 * edit
 * delete
 * for consortium member
 * download

Actors

 * Consortium Lead
 * Consortium Manager

Pre Condition

 * The system status of consortium is 'open'.

Steps

 * Actor is in consortium publication archive page.
 * Actor selects a publication in archive.
 * Actor 'clicks a button" to "update a publication".
 * A page opens a page allowing updating a selected document.
 * Options for update are
 * Update metadata fields listed in Add publication spec.
 * New upload of PDF
 * Actor submits.
 * The system keeps track of old versions.
 * use feature provided by LR