add information about repeat/related submissions

[danielskatz]

When a new submission happens, JOSS systems could check to see if it is a resubmission, or perhaps list other submissions from the same submitter, or even use ML to list closely related previous submissions, and present this on the JOSS submission page (visible only to editor). Once a pre-review starts, perhaps this would also be added to the pre-review issue, though I'm less sure if this is a good idea.

[agahkarakuzu]

Resubmission exists as a submission option. But when this option is selected, the form does not ask about the DOI of the existing submission, based on which a previously closed issue could be re-opened and a versioning logic could be implemented. I am not sure how DOIs are currently managed for multiple versions of the same content.

[agahkarakuzu]

I started implementing a versioning workflow, which is frequently needed in our platform as we publish preprints. Now on the form, when "resubmission" is selected, the user is prompted to provide the DOI to the already published version:

On the editorial dashboard, this appears as:

after ensuring that this is an iteration of an already existing publication and consistency of other fields (e.g., the same author, repository etc), issue can be reopened:

depending on the versions available in the parent directory of the respective preprint, a version tag is determined to update the issue body (in this case, Preprint version: v2):

With this version information available in the issue body (and not v1), draft generations will use a version-suffixed branch and version-suffixed files:

Upon publishing, the parent file (i.e., 10.55458.neurolibre.00041.pdf) will be replaced by the latest, while versioned files (i.e., 10.55458.neurolibre.00041.v1.pdf and 10.55458.neurolibre.00041.v2.pdf) coexist under the same directory.

Once new version is published, the resubmission (of model paper ) can be withdrawn, as new-version relevant operations take place under the parent publication's issue.

Multiple versions then can be displayed on the DOI landing page, with new depositions incorporating isVersionOf field.

[agahkarakuzu]

To update if there is any interest on versioning,

After adding version and parent_paper_doi columns to the paper model, Paper.find_by_review_issue_id_and_version enables locating the correct paper to deposit/update.

I followed this convention as review_issue_id was already serving as a unique constraint, which now can be also used to define sub-papers of a paper.

Example (WIP) page is at https://staging.neurolibre.org/papers/10.55458/neurolibre.00041, where you can use the dropdown to shuffle between the versions.

Version-suffixed URL routing is also enabled for doi purposes:

• https://staging.neurolibre.org/papers/10.55458/neurolibre.00041.v1
• https://staging.neurolibre.org/papers/10.55458/neurolibre.00041.v2

with the canonical URL always pointing to the latest.