Allow the creation of custom, issue-specific arbitrary groupings or section headings

[pgoussy]

Is your feature request related to a problem? Please describe. Janeway's current method of ordering articles in an issue--i.e., displaying each Article Section in the order that they appear in the Section Manager, and displaying all articles within that section in the ordained order--isn't ideal for all journals.

For instance, PTPBio is a rolling publication that just has a single volume for the whole year, and they add articles throughout the year. Currently, that volume page lists all of the Research Articles, followed by all of the Special Issue articles. They would prefer that those articles display on the TOC in order of publication, regardless of whether they're categorized as a Research Article or a Special Issue.

For another example, for GS 1.1, Janeway currently displays the articles in Section order: all of the Letters, followed by all of the Research Articles, followed by all of the Short Essays, etc. However, in the print edition of this issue, these articles were displayed in a completely different order--it was divided into issue-specific groupings based on theme/subject, and within each of those groups, you might find articles of multiple different types (some Research Articles, some Short Essays, etc.). So not only are the articles not appearing in the same order as the print edition, there's also no way to render the issue-specific section titles on the Janeway TOC (unless we sacrifice the article types currently identified in the Article Section field).

Describe the solution you'd like In short: most journals have been treating the Article Section field less as a way of organizing an issue, and more as a tool for labeling the type of each individual article. We would like to stop using Article Section as the default organizational structure for issues, but we'd still like each article's assigned Section (that is to say, its "type") to be easily identifiable.

Per our discussion on Discord several months ago, there are a few separate features that would need to be developed in order to achieve this. This ticket is specifically for updating the Issue Management page: we would like to create custom, issue-specific article groupings that are not dependent upon Article Section.

Describe alternatives you've considered We discussed a few potential approaches for creating these custom article groupings. Here is a screenshot of a current Issue Management page, for reference:

Option 1 would look similar to this current implementation, with the following changes:

• Next to "Add Article" at the top, there would be a new option to "Add Group/Section/Part/whatever-we-want-to-call-it".
• This button would create new issue-specific structural groupings (similar to the current presentation of Practice and Article here) that could be renamed as needed, rather than automatically using the Article Section metadata field to determine which groupings appear.
• Once created, these issue-specific groupings/section headings could be dragged-and-dropped into a particular order, or could be renamed if necessary.
• Articles could be dragged-and-dropped from one grouping into another if need be, in addition to dragging-and-dropping to reorder within each individual grouping.

Option 2 would abandon the entire premise of "grouping" the articles structurally/organizationally, and simply allow us to add section titles.:

• All articles in an issue would appear in a single unified list that could be reordered by dragging-and-dropping.
• Next to "Add Article" at the top, there would be a new option to "Add Group/Section/Part/whatever-we-want-to-call-it".
• This button would create an arbitrary, issue-specific "Section Title" item that would appear in the list of articles. Content-wise it would need nothing more than a text string in the Title field, but it would look and function similar to other articles on the list of articles in the Issue Manager.
• Once created, this item could be dragged-and-dropped anywhere on the list of articles, or could be renamed if necessary. In practice, you would simply drag it to appear before the first article in an issue-specific grouping. Then, on the issue page/TOC, the text string would be rendered as a heading/title (styled the same way that Article Sections are currently styled on TOCs)
• As long as someone looking at the TOC can tell where each group/section/part is meant to begin and end, there's no specific need to have quantified groupings of articles in Janeway, so it should be sufficient to visually display a custom "section heading" title, followed by the articles associated with that theme.

Both of these approaches assume that the Article Section metadata field (perhaps renamed to Article Type) will be retained and displayed as a label/tag next to each article, so that this information isn't lost once they're sorted into custom groupings.

See also: #3079 #3080