Allow manual ordering of articles for browseIssue.action

[rcave]

Current functionality

The articles are currently sorted within browseIssue.action in the following order: a) Issue Image (if exists) is always the first article b) Article type (e.g. editorial, research article, etc.) <article-categories>

<subj-group subj-group-type="heading">

<subject>Research Article</subject>

</subj-group> …

</article-categories>

c) Publication date, most recent first

<pub-date pub-type="epub">

<day>24</day> <month>6</month> <year>2005</year>

</pub-date>

d) DOI ascending order

<article-id pub-id-type="doi">10.1371/journal.pcbi.0010002</article-id>

New functionality

Sort articles by: a) Issue Image (if exists) is always the first article b) Article type c) By the "Articles" text string in admin/manageVolumeIssues.action.

The web team will add articles to this array of URIs in the "Articles" text string. When this field is updated, the BrowseCache? will need to be cleared to display the new article ordering.

Questions

a) Can a "manual" type be added to the Issue model without requiring a data migration? This will allow the web team to specify if the articles should be displayed dynamically in browseIssue.action based on current functionality or by the manual text string.

[wtoconnor]

(In [7422]) Make changes to admin panel to allow the ordering of articles within issues. The admin panel interface was updated to allow the ordering of articles and increase the usability and reduce errors in certain task.

Additional Management Panels/Actions

1. Cross Publishing
2. Volume Management
3. Issue Management

Panels Changed

1. Manage Virtual Journals

Panels Deleted

1. Manage Volumes/Issues and its Templete ftl

New AdminService? provides functionality that can be used by all the admin panels.

The Issue.java model has been changed so that simpleCollections are not used and ordering of articles is maintained in a separate list. This will be refactored out into a separate PloS issue and volume classes in the next development cycle so that PloS specific concerns are removed.

Addresses #1109

[rcave]

Closing this ticket as the feature is complete to some extent. We'll open new tickets as testing uncovers new issues in the feature.