We've looked at OJS in the past and not been happy with it, we're pretty
happy with WordPress, and not really looking to migrate all our
operations to different software.
But thanks for the suggestion.
(I do think there are probably ways we could keep using WP without a
custom codebase, which I personally would prefer, but it's all tradeoffs.).
On 12/5/2012 5:05 PM, Ed Sperr wrote:
> Instead of maintaining a custom codebase to try and force WP to do what you want, why not just use a tool purpose-built for this kind of job? The open-source, "Open Journal Systems" from PKP might be a good fit: http://pkp.sfu.ca/?q=ojs
>
> Ed Sperr, M.L.I.S.
> Copyright and Electronic Resources Officer
> St. George's University
> [log in to unmask]
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
>
|
