Option 1: OJS/Wordpress plugins
See this Google Doc for instructions and links to download the relevant plugins.
Content is submitted, reviewed, edited, and published in OJS, but publicized via a Wordpress install automatically, in the Wordpress install’s blog.
Published content (including article galleys, abstracts, etc., as well as article metadata for Google Scholar) are all available on the OJS install. Abstracts, titles, and author information only is available on Wordpress.
- relatively easy to configure: simply install each plugin on its respective sites and configure.
- Can use Wordpress’ themes, and other Wordpress plugins.
- Content is still published via and stored within OJS, so that external services etc. (DOI, Google Scholar, etc.) can be managed by OJS – Wordpress simply acts as a presentation layer.
- Conceivably this could be added to a pre-existing website that publishes other content (this needs to be tested);
- Can use Wordpress comment, sharing options with articles (though not directly on article galleys, which are still stored in OJS).
- Open question whether either plugin will remain up-to-date (and as of this writing, Matt’s Wordpress plugin does not work with Wordpress 3.5+, though should be noted that other partners or PKP may choose to actively support these plugins);
- Article content is still stored and effectively published in OJS, with Google Scholar metadata, reading tools available only in OJS (by default, at least), resulting in the probable main presentation layer lacking a number of typical article tools;
- Having two different sites for the same content may conceivably be confusing for eg. Google Scholar (though probably not, as WP really only acts as a presentation layer in this case), or for users wrt comments (NB: commenting should definitely be turned off on OJS side);
- May have to investigate specific configuration parameters for WP/OJS so that they play nicely with one another.
Option 2: Use OJS as submission/review/editing only; use Wordpress to publish
OJS instance would disable content publishing from Journal Setup (step 4.1); Authors would submit content to OJS instance, where review and editing workflows would also be used; final article galleys would be manually moved to and formatted in Wordpress, and published there.
- The final publication and display location would be the same (in Wordpress);
- No confusion on where to comment, or for eg. Google Scholar on where the canonical article version is;
- Would be able to use Wordpress’ extensive HTML/multimedia authoring tools;
- Would be able to use Wordpress plugins in conjunction with published content.
- Would not be able to use OJS’ plugins or presentation options, incl. Crossref export; Google Scholar; etc.;
- Would have to evaluate available Wordpress plugins to compensate.
Option 3: Use Wordpress’ RSS feed widget to promote new content available from journal
OJS’ Web Feed plugin is activated; the TOC RSS feed then added to an OJS RSS Feed widget, and TOC entries are displayed in the Wordpress sidebar.
- doesn’t need special plugins to work – plugins are already available natively in OJS and Wordpress, and are actively supported;
- can specify whether title, date, author are displayed (currently doesn’t appear that author is);
- easily promotes article content in Wordpress, leaving all other publication issues to OJS
- Can’t use Wordpress’ HTML/media tools;
- RSS metadata isn’t (currently) rich enough for scholarly metadata
- Content isn’t published as blog posts – only as sidebar content – meaning that anyone who subscribes to the blog/Wordpress site won’t get notification regarding new articles;
- Likewise, commenting and other typical blog sharing tools probably aren’t usable.