we’re looking to update to 3.2.X and are currently doing test runs on our demo server. One problem we’ve come across is that assigning an article to an issue that is already published (a back issue), the article is published as soon as the assignment has taken place, with no way to edit metadata etc in between the assignment and the publication - unless we unpublish the article, which unassigns the issue.
This is mainly a problem because it makes DOI assignment really hard. I’ve seen this topic which suggests that removing all issue data (such as volume number) from the DOI scheme solves this problem, but several of our journals have such data in their DOIs and use the method of publishing to back issues, and we’d hate to ask them all to change their DOIs.
The only workaround I’ve been able to come up with is to give the articles a future publication date, then assign the issue, then set up the DOI, then change the publication date to today, then unassign/reassign the issue. It works, but it’s pretty annoying.
So I’m asking if there’s already a way to solve this problem, and we just haven’t been able to find it, or, if there isn’t, to please make assigning an issue and publishing an article two separate steps (hence the Feature Request tag)!