How to scale to a large number of journals

From PKP Wiki
Revision as of 07:26, 21 December 2010 by Mvluijt (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

As open source software goes, OJS is very customizable. You can choose your theme, add header graphics and apply your own stylesheet. OJS also allows you to host a number of journals in one OJS installation, which makes management very efficient. But organisations that host OJS journals, seem to end up with one OJS for each client or even for each journal.

The main reasons for this are:

  • Modifications in templates can't be avoided. Templates are shared between all journals in an installation.
  • Userdatabases are shared among all journals in a certain installation (John indicated in Athens there is a solution for this. Anyone?)

(any more?)

This increases the cost for daily management somewhat and the cost for patching and upgrading a lot. Can this be improved?