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.
