Preprint endpoint in API

[alainna]

Is your feature request related to a problem? Please describe. It would be beneficial to external connections to have a preprint endpoint in the Janeway API

Describe the solution you'd like Preprint endpoint in Janeway API; get preprint metadata in tasty XML/Json format. yay!

Things we'd expect that the preprint API would be able to access:

• Repository_Preprint: All
• Repository_keywordpreprint: All
• repository_preprint_subject: All
• repository_preprintfile: All
• repository_preprintsupplementaryfile: All
• repository_preprintversion: All
• Repository_preprintauthor: All
• Core_Account: All (read author name, etc; create author)

Uncertain, but assuming that API may need access to some of the data:

• repository_repository
• repository_subject
• repository_repositoryfield(answer)

At this point, I would assume that, with the exception of comments and discussion, the main Repository_xxx tables would need to be accessed via the API for the POST/PUT functionality, whilst the main ones in the first chunk above may be the only ones required for the GET functionality. (This expectation may be incorrect.)

[alainna]

@ajrbyers FYI, added the tables with data I'd expect that we would wish to be accessible via API.

[hardyoyo]

@alainna I wonder if you could have a look at the API endpoint added by #3166 and let me know what's still missing? The Django REST Framework mostly adheres to the Django object models, so... getting anything more than the preprint model onto the preprint endpoint will take some creative coding.