As the developers of Open Journal Systems, Open Conference Systems, Open Harvester Systems, and Open Monograph Press, the PKP team are experts in helping journal managers and conference organizers make the most of their online publishing projects. PKP Publishing Services offers support for:

As a customer of PKP Publishing Services, you will not only receive direct, personalized support from the PKP Development Team, but will be contributing to the ongoing development of the PKP applications. All funds raised by PKP Publishing Services go directly toward enhancing our free, open source software. For more information, please contact us.

Forum rules
This forum is meant for general questions about the usability of OJS from an everyday user's perspective: journal managers, authors, and editors are welcome to post questions here, as are librarians and other support staff. We welcome general questions about the role of OJS and how the workflow works, as well as specific function- or user-related questions.

What to do if you have general, workflow or usability questions about OJS:

1. Read the documentation. We've written documentation to cover from OJS basics to system administration and code development, and we encourage you to read it.

2. take a look at the tutorials. We will continue to add tutorials covering OJS basics as time goes on.

3. Post a question. Questions are always welcome here, but if it's a technical question you should probably post to the OJS Technical Support subforum; if you have a development question, try the OJS Development subforum.

Some people at QUT are interested in using OJS for managing the review of theses/dissertations for post-gradate students. The workflow for examination of theses here is similar to the journal review and acceptance workflow. In particular, a thesis has a number of reviewers who provide feedback, resulting in a decision of acceptance, acceptance with changes, or re-examination. Access controls are important and OJS implements these in the appropriate way for this use case. Obviously the OJS workflow goes further than reviewing and the additional steps are not required, nor would the majority of the website functionality. Also, I think significant customisation would be needed to create a seamless thesis-oriented user experience rather than confusing thesis/journal experience.

Is anyone using OJS for thesis/dissertation examination? We'd be very interested in hearing you experiences.

We are using OJS to register AND publish IBICT personnel's participation in events.This is a bit different than OCS as it refers to meetings, going to outside events not necessarily hosted or organized by IBICT, presentations, visits from other organizations and other internal employee events.We want to register (all), store (all) and publish (selected) media from each event. For example, IBICT every year participates in the Week of Science and Technology Fair, with a stand presenting its services and promoting workshops in many areas. These events are recorded, but not accessible, so we want to provide that access.

OJS was the software of choice because we want a repository to store this data, and had many issues with DSpace.

I personally think a CMS, in our case would be a simpler and faster solution, but OJS is promoted by the institution, so it's being customized to fit the needs.

Each "event" is set as a Journal, and each area is testing it to identify what customizations they want. Then, these will be analyzed to see if they are feasible.

I'm working on implementing a JWPlayer or other Lightbox/Media Gallery plugin to simplify the viewing of the published event media.We'll also need to customize each "event"'s translation to remove all calls to "journal" and related terms for something else.

It's still under work and it's not high priority, but it's an interesting case.