OJS has no automatic way to create galleys (OJS 2.x has no REST at all, OJS 3.5 has no galley route). Studio Galley Bridge adds one: a tiny plugin for OJS 2.4 through 3.5, one click in Studio, three galleys ready in Production.
v1.1.0 · 13 KB · SHA-256 92b0caf95dd8… · Author: Ruang Ide · GPL v3
The plugin is free to install. Sending galleys from Studio uses 1.75 credits per send (PDF + HTML + XML together).
From the author’s DOCX, Studio builds full JATS: front (journal, ISSN, authors, affiliations, bilingual abstracts), body (sections, tables, figures, MathML + TeX equations, footnotes) and back (references). A built-in validator points at problem lines before you send.
One Send to OJS button builds the PDF (A4 in the journal profile), standalone HTML and JATS XML, then creates or replaces the PDF, HTML and XML galleys on the OJS submission. No more Add galley → Upload file → Continue → Save, three times per article.
The plugin only adds {journal}/studioGalley/ping, /upload and /token. It changes no OJS tables and runs no outside code.
Created by the journal manager on the token page, only its SHA-256 hash is stored, replaceable any time. Without a valid token everything is refused (401).
Published publications are rejected (409). To change one, Unpublish or create a new version in OJS.
File extension and content are checked. Anything else is refused.
Click Download free above. You get studioGalley-1.1.0.tar.gz. Do not extract it.
OJS 3.x: sign in as administrator → Website → Plugins → Upload A New Plugin → choose the file → Save. OJS 2.4: copy the folder to plugins/generic/ (see manual install below).
In the Generic Plugins list, tick Studio Galley Bridge.
Sign in to OJS as journal manager, open https://your-site.org/index.php/journal/studioGalley/token, press Create token and copy it (shown once). No api_key_secret or REST needed.
Connections menu: paste the journal URL (OAI mode is enough) → Connect & sync → on the journal card click Set plugin token and paste the token.
Open the manuscript in the editor → File → Export → Send to OJS → enter the OJS submission ID → OK (1.75 credits). Check in OJS: Workflow → Production → Galleys.
If you cannot upload through the panel (or on OJS 2.4), copy the folder to the OJS server and register it:
cd /var/www/html/plugins/generic tar xzf studioGalley-1.1.0.tar.gz chown -R www-data:www-data studioGalley cd /var/www/html php lib/pkp/tools/installPluginVersion.php plugins/generic/studioGalley/version.xml
Then enable it under Website → Plugins. With Docker, run the commands inside the OJS container. OJS 2.4 has no installPluginVersion.php: add one row to the versions table (product studioGalley, class StudioGalleyPlugin, type plugins.generic) and enable it; details are in the plugin README.
curl -H "X-Studio-Token: YOUR_TOKEN" \
https://your-site.org/index.php/journal/studioGalley/ping
# {"plugin":"studioGalley","version":"1.1.0","ojs":"3.3.0.14", ...}| 3.5.x | Tested on 3.5.0.5 |
| 3.4.x | Tested on 3.4.0.9 |
| 3.3.x | Tested on 3.3.0.14 |
| 3.2.x | Tested on 3.2.1.4 |
| 3.1.x | Tested on 3.1.1.1 |
| 3.0.x | Same code as 3.1, not tested (the official 3.0 images are incomplete) |
| 2.4.x | Tested on 2.4.8.5 |
| 2.0 – 2.3 | Not tested |
| Studio | A StudIO RuangIde account and the plugin token under Connections; an OAI-only connection is enough |
| Plugin "Studio Galley Bridge" is not installed | The plugin is not enabled for that journal, or the journal address is wrong. Run the ping above. |
| Plugin token rejected | The token is wrong or was replaced. Create a new one on the studioGalley/token page and save it again under Connections. |
| sign in as a journal manager first | The token page is for signed-in journal managers only. |
| This publication is already published | OJS locks galleys after publication. Unpublish or Create new version in OJS, then retry. |
| Not enough credits (402) | Send to OJS uses 1.75 credits per send. Buy credits under Settings → Billing. |
What is free is the installation: the plugin can be downloaded, installed and modified freely (GPL v3), with no galley limit on the OJS side. Sending galleys from StudIO RuangIde uses 1.75 export credits per send (PDF, HTML and XML together). Downloading files and uploading them by hand still follows the normal export quota.
1.75 credits per Send to OJS press, however many formats you pick, and only if at least one galley was created. A total failure takes no credits. Admin accounts are not charged.
Yes, the upload page is open to any script holding the plugin token (a curl example is in the README). Its main job is serving Studio.
OJS’s JATS plugin (3.5) manages one JATS file per publication. The Bridge creates galleys (PDF, HTML, XML) that readers see, stored at the Proof stage, on every OJS version.
Not through the plugin: OJS locks published publications and the plugin respects that. Create a new version in OJS first.
No. Studio sends the files straight to your OJS with your token. The plugin only stores the files in OJS.
OJS 2.4 through 3.5, one package for all. Tested on 2.4.8, 3.1.1, 3.2.1, 3.3.0, 3.4.0 and 3.5.0; OJS 3.0 uses the same code as 3.1 but is untested.
Install the plugin, connect Studio, send.