Add versioning support to papers (DOI per version)

[yattias]

• model changes
• Allow users to specify a "version commit message"
• api changes (create version, associate pdf to version)

API Changes

• Create DOI when creating new version
• Associate PDF to version

Upload PDF version

• Two endpoints: One for initial PDF (Upload endpoint), and another for version
• Allow uploading of PDF via chunks/parts (Gregor)
• Endpoint in paper view for uploading a new version, description message (Gregor)
• Should we upload files directly to AWS in a pre-signed way? If so, can we leverage the ref. manage upload mechanism?

Open questions / Research

• Should we create a DOI if the paper already has an existing DOI - Yes
• How should we store different versions in the database?
• Can we modify the DOI ? e.g. suffix at the end of DOI
• Can we leverage existing storage mechanism on AWS
• How do we make others aware that a DOI has been updated? e.g. new version on ResearchHub

Frontend

• Dropdown for different versions
• Upload PDF version component w/commit message

Additional Changes

• Send notification to peer reviewer(s) when a new version is submitted

[yattias]

1. Upload paper blob; step 1:

POST /api/blob => Parameters: filename

=> Create signed S3 URL => Return signer S3 URL to caller

2.1 Create new paper; step 2

POST /api/paper

• createPaper => paper_ID
• createDOI(paper_ID) => doi
• updatePaper(doi)
• createNextVersion(paper_id, message) => (version_id, version_number)

=> Return paper

2.2 Create new paper version; step 2

POST /api/paper//version

• createPaper => paper_ID
• createDOI(paper_ID) => doi
  • look up base_doi from initial version
  • createVersionDOI(base_doi) => doi
• updatePaper(doi)
• createNextVersion(paper_id, message) => (version_id, version_number)

=> Return paper

TODO ++++

• Add (current) version to paper serialization
• Add (all) version list to paper serialization