Simple API Guide for "no review publications"?

Software Support
1

Hello,

I am interested in using this tool for an in-house preprint server (publishing “memos” between groups). We have an information collection system in house, so we would like to relay this information directly into our private server. No issue about review, etc.

Does anyone have a guide for choosing the correct API calls? There are a large number of them and ultimately I think that we would need very few.

Thanks

2

Hi @rictuar,

Our API guide can be found here: https://docs.pkp.sfu.ca/dev/api/

-Roger
PKP Team

3

Thanks for the product and the response.

The API does describe all of the endpoints. However, sewing them together requires a LOT of trial and error. I was hoping that someone might have already tried this and could share the minimal API call sequence required to publish. (lots of moving parts like different roles, awareness of the “stages” of publication, etc. make this non-trivial)

4

Hi @rictuar,

Thanks for clarifying. Hopefully someone will come along and weigh in if they have some experience with this.

Best regards,

Roger
PKP Team

5

Hi @rictuar,

This might be off-topic, but have you considered OPS for preprints (rather than OJS)? It’s very similar to OJS, but without the review toolset, issue management, and a few other things that are specific to journals. It might be a better fit.

For the API question, can you describe the interactions between the two systems that you envision? It might help me direct you to specific resources.

Regards,
Alec Smecher
Public Knowledge Project Team

6

Thanks for the response. We are definitely going to go with the preprint server. We want this to be fairly minimal. Unfortunately, it seems like there is only API documentation for OJS. It is good to learn that some aspects like stages are not a concern with OPS.

We envision the interactions looking very simple. Using some in-house (because of integrations with other internal tools) form, people would generate 1) .pdf of their manuscript 2) basic metadata like Author, Title, etc.

This in-house tool would then automatically do the proper sequence of API calls. Ideally, people wouldnt even have their own account. There would maybe be an admin and a user account that the API roleplays as.