Manuals for Open Journal Systems

I have found that many editorial boards struggle with a lack of concise instruction materials and a lack of people who can train them with hands-on approach.  They usually find some solutions in on-line forums, but it is time consuming for editorial boards to spend so much time and look for partial information. Sometimes people who write manuals do not explain each step.  Several people contacted me and asked: “What I have to do now?  Something is missing.”

System administrators, software developers assume that what is easy to them it should be easy to everyone.  They plan training to be done in one evening because “It is easy. ” In my experience, I often found out that such practice leads to misconfiguration of application, underuse of its features,  mistakes in performing workflow tasks and procedures.  Work with applications as the Open Journal Systems is not hard but it is complex and it takes some time until user is familiar with its functionality and simple procedures for configuration and efficient use.

I wrote manuals for authors, editorial boards and reviewers for scientific journals according to their needs.

You can find here manual for authors, editorial boards, and reviewers.

I will publish here soon manual that puts together some basic administrative and editorial functions aimed to successful configuration of your Open Journal Systems application for your journal.

 

My server exploded. Everything is gone! Aaaarghhh!

I guess many times administrators, people involved in technical support on forums have been faced with such outbursts of despair and anger.

Well, it is stress to everyone. But, server never exploded and it is very rare that everything is gone forever.  Appearance of blank screen, error message or that program is stuck does not mean that your server exploded or that you lost your work.

When you experience that kind of difficulty it is important to stay calm and to have handy information that will help your administrator, hosting company/IT department people, community support participants on support forum to look for solution.  Well, often solution is correction of code, adjusting settings on server, but in any case your work is the most probably neither damaged nor gone.

You should always have handy information on your infrastructure, browser, operating system of your server and context within which issue happened.  People who want to help you often free of charge need to reproduce the problem in order to identify the point at which problem occur.

Support people at ATutor set up their forum in  a way that the user is by default provided with hints that will help to write post in a way that will be helpful.  We have to be oriented towards solution! So, do not panic! Be calm, concentrated and focused on providing sufficient information in order to find solution. It is not shame to describe sincerely and completely what you have done. That will help you and many others. Asking for help is support to yourself and to many others.

I found helpful hints on support pages of several OA software packages.

The rule is: Do backup often, be calm, sincere and helpful to yourself, people who want to help you and others who might be in trouble as you are now.

Here it is how people from ATutor made it:

  • Beginning of message:

If you are asking for help, provide lots of detail so problems can be reproduced.

Things to describe:
Operating system ATutor is installed on –
ATutor version –
Patch #s applied –
ATutor theme name –
PHP version –
MySQL version –
Webserver & version –
Copies of error messages –
Changes to default settings –
Web browser being used –
…and anything else relevant –

  • End of message.