Journals on Scholardemia run natively: submissions, peer review, decisions, and publishing all happen on the platform. The OJS bridge exists for journal teams who also operate an Open Journal Systems installation and want the two to stay in step, rather than retyping issue and article metadata in both places.
What the bridge does
- Verifies the connection to your OJS installation with a health check.
- Creates issues in OJS from Scholardemia, including issue cover images.
- Uploads issue galleys (the published files) to OJS.
- Pushes article metadata into OJS for existing submissions: keywords, references, page ranges, author affiliations, and countries.
Journal managers work with the bridge from their journal’s admin tools, where the connection status, issue creation, and issue assets live together.
Setting it up
The bridge is configured server-side for each journal: your OJS base URL, an OJS API token for a user with the Manager or Site Admin role, and an optional shared secret that hardens the connection. A small companion plugin must also be enabled on the OJS server. Because these credentials live in server configuration rather than in your account settings, setup is arranged with the Scholardemia team; email support@scholardemia.com with your OJS address to get started.
Do you need it at all?
If your journal lives entirely on Scholardemia, you do not need the bridge; publishing, DOIs, and archiving are handled natively. Scholardemia journals do not charge article processing charges (APCs). See Journal no-APC policy. The bridge is only for keeping an existing OJS presence synchronised during or after a migration.