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.
The Open Journal Systems users use embedded TinyMce editor to enter various information during publishing their articles in journals. Some users may need for various reasons spellcheck in order to make sure that texts they enter are spelled correctly. TinyMce developers developed one very simple spellchecker plugin that is not configured by default in the Open Journal Systems. There is free version and Spell Checker Pro version. TinyMce developers stated on the web page for Spell Checker pro that: A TinyMCE Enterprise subscription includes the ability to download and install a spell check as-you-type feature for the editor.
If you are editor, editorial board member or administrator of the site of your journal various payment schemes for spellchecking might not be affordable.
For general purpose texts you can use spellcheck capability of your browser.
But, if you need free, easy to install TinyMce spellchecker capable to spellcheck medical, scientific and legal terms you can consider using Nanospell spellchecker. The developers of Nanospell stated on their site that: It is perfect for secure applications and websites where user experience counts:
- Guaranteed dictionary availability across all browsers, including medical, scientific and legal words.
- Never sends your secure data to any remote servers: everything is done locally.
- Works in older browsers which do not have spellchecking capabilities of their own.
- No popup Ads
I supported some members of editorial boards to install it and configure properly in their Open Journal Systems installations. That is very easy and straightforward process which should not last more than 5 minutes and its icon should appear in toolbar of TinyMce editor in your Open Journal Systems installation. It is easy to install its dictionaries which can meet your editorial and authoring needs. However, please be aware of their licensing policy.
I have been recently invited by high level officials of one institution to help them to publish several journals on line. Indeed, I recommended them to use Open Journal Systems which they gladly accepted.
They showed me their server, but one of high officials said: “You know, we do not have anyone who knows Linux. We heard that you know it. we have on our server several installations for different web platforms, but we do not have idea how to fix several small issues and how to make everything work smoothly.” I looked at each of those GNU/Linux installations and realized that many of them are installed as desktop machines with some additional applications such as web server, PHP, MySQL etc. But, many of those installations were lacking several dependencies resulting that some modules in web applications did not work. People who installed them were elsewhere and they did not have any documentation on settings, active services, software package versions and other important information related to virtual machines with operating systems and web applications installed on them.
I suggested to them that is necessary somehow to standardize those installations and choose GNU/Linux distribution that is efficient and easy to administer and migrate web applications to newly installed virtual machines and create documentation with precise information on operating system version, versions of important applications and infrastructure requirements. Those specifications will help administrator to manage backups, upgrades, maintenance, testing instead of guessing where is which application and with what other application is or is not compatible. They were scared since they were not sure how to do that and how many work hours is needed for that. Well, that will save a number of work hours of saving damaged or corrupted data, misbehaving applications or consequences of compromised virtual machines due to software packages that were not upgraded when needed.
Thanking to experience and knowledge of free software developers and users of GNU/Linux and many other free software applications it is possible to plan, project and implement whole infrastructure and web applications in a way that can assure users and administrators that everything will work smooth.
It is needed to take care on:
- easy of use
- ease of quality administration
We can add more criteria and discuss all of them which is beyond scope of this post. But, I want to stress importance that free software, open access are not just sandbox for benevolence and good will. It is rather, very serious activity and require a lot of work in order to make sure that users of information and knowledge we publish on web applications designed for open access publishing will have positive experience that will help them to learn.
I prepared myself to do training for the members editorial boards of two journals issued by one institute of economic sciences.
I came to the premises where I was supposed to do training, but I noticed that people who entered data in the system dedicated to on line publishing were shocked and confused. “Everything is gone!”, said one of them. “What has gone?”, I asked. “The data we entered in the last two months!”, she replied sadly. I started to examine what has happened and discovered that some bad backup was restored over our virtual machine hosted on their server. “Hmm, did anyone restored some wrong backup?”, I asked. ” I do not know how to do that and even our administrator is away. He left a couple of weeks ago.”, she sad hopelessly. Well, another person was invited to examine what has happened and we determined by checking logs and possible scenarios and we have found that former system administrator assumed that so-called bare-metal backup was sufficient. In addition, he did not check whether back was complete or not and what software vendor suggests to perform backup of guests on Hyper-V. Well, too much mistakes resulted in complete loss of data that two persons entered in the period of two months.
So, when you plan hosting and backup of your data please check carefully documentation, test your methods of backup and after checking of various possible disaster scenarios implement it on production (virtual) machine with open access application and samples of data entered.
Journal of Science Communication published in their special issue (Issue 03, 2017) articles on history of science communication.
Authors from various countries wrote articles and essays about history of science communication in thier respective countries. Readers can learn about history of science communication in Japan, Australia, New Zealand, Spain, United Knigdom, Estonia, Mexico, South Africa.
Authors of editorial emphasized that: “The papers published in this issue are organized in three groups, though with diffuse boundaries: geography, media, and discipline. The first group contains works that deal descriptively and critically with the development of PCST actions and either general or specific public policies for this area in specific countries. A second set of papers examines aspects of building science communication on TV or in print media. The third group of papers presents and discusses important PCST cases in specific areas of science or technology at various historical moments.”
I strongly recommend all readers of this blog to read those articles and follow study in this are since this will help authors, editors, reviewers, system administrators to collaborate efficiently and make informed choices that put forward advancement of science communication in theory and everyday practice.
In my work with editorial boards of scholarly journals I found often that they support idea of open access in general. But, it is not clear always that licensing itself from the legal point of view may be quite complex. Heads of scientific libraries and editorial boards sometimes discuss for long time issues related to licensing issues. Sometimes that takes too much time since their lawyers sometimes say: “That license gives you framework for implementation of open access ideas, but in our legislation it will be hard to make defense at the court. ” Well, it might be quite useful to have close cooperation with lawyers, NGOs and other people involved in the development of legislative efforts and translate Creative Commons license and do necessary steps so it can be accepted and accepted in legislation in your country.
In some countries people register their work in national copyright agencies, but absence of registration does not imply absence of protection and copyright.
One of successful and viable licensing practices is to choose appropriate Creative Commons licenses for article, data set, images or other article components. Scientists who would publish source code of software used and created in research may use free software licenses. Please note that license does not relate to the content on images, video in terms of privacy and other potential legal issues. For example, video showing a woman doing breast self-exam can be from the point of video authoring protected by Creative Commons. But if video shows face of the woman showed in video recording her privacy is violated if she had not given clear consent for that previously.
Editorial boards and librarians should often visit the website of EIFL. They made very useful Handbook on Copyright and Related Issues for Libraries. Those who would like to learn more on use of Creative Commons and what users can do with Creative Commons licenses please visit page with information on webinar related to that topic. Knowledge acquired from those resources can help you to be more efficient, productive and safe in your publishing efforts. Your administrator can insert appropriate licensing information in published content.
The Open Journal Systems can insert licensing information in the article metadata automatically and save your effort and time.
If you work a lot with web applications that you use to publish your journal, repository of scholarly publications you probably heard about web security, certificates, eavesdropping.
If you are scholar or member of the board being much more involved in social sciences, arts, culture all those technical terms and theories may be quite confusing for you.
I have got recently message from one faculty member that study political sciences that their site is not accessible due to security certificate issue. “I use Firefox”, he said and I have got warning message about certificates and it does not allow me to see my site.
Well, in majority of cases such warning message is not necessarily bad nor it does prevent you from seeing your site. Indeed, it is good to learn more about web site certificates. A good resource of information is here.
The Firefox team published their own article about web site certificates and relations with Firefox browser.
In additional article about technical error and message “Your connection is not secure” Firefox team explained possible reasons.
In the case of journal published in the Open Journal Systems there was not issue with the Open Journal Systems web application. Actually, their certificate expired as on image below:
Since they are sure that they trust their site they added exception to their browser. They contacted their hosting company, checked certificates and solved issue. That is not hard. Your administrator can keep notes on certificates and remind you on renewals and keep communication with hosting company and/or other certification authority and renew certificates in a timely manner.
Many people from editorial boards asked me various questions about registering their journal with CrossRef. What is DOI? Is that XML thing too complicated? Do we need someone with PhD to do that?
CrossRef is a not-for-profit membership organization for scholarly publishing working to make content easy to find, cite, link, and assess. We do it in five ways: rallying the community; tagging metadata; running a shared infrastructure; playing with new technology; and making tools and services to improve research communications. The Digital Object Identifier, DOI is special number assigned uniquely to publications such as article, issue, galley, dataset, book, database etc. There is interesting Wikipedia article about DOI for those who do not have much time to go into details.
People from CrossRef created a series of training materials which you can find on their Youtube channel.
I found very useful to watch their training on content registration and maintaining metadata information. You can find a lot of useful information in that video training. If you prefer slide presentation CrossRef published on Slideshare presentation about the same topic.
I always suggest to those who do not want to spend a lot of time in technical work in process of metadatadeposit and xml formatting to use the Open Journal Systems.
It is very easy to use Open Journal Systems and assign DOI numbers. Easy to use interface and pretty automatized process of metadata deposit save you a lot of time and effort. There is special plugin for DOI assignment to your articles or other article/publication components. The users of 2.4.x branch of OJS can find information on assigning DOIs here.
The users of 3.x branch of OJS can do that even easier in less than 2 minutes configuration of plugin. Huh, you will see that DOI and XML exports are not so hard thing. After using OJS you can ask yourself why you have had a lot of anxiety while thinking on things that are so easy to do.
Many times, I have experienced situations where people try to draw
lines between authors, editors, and system administrators. True, they
do have very different roles. But they should understand each other
beyond awareness of their role differences. Technically speaking,
system administrators do not care whether an author makes spelling
mistakes or not. Editors do care about spelling and grammar errors,
but they do not know much about server infrastructure.
If we really want to be productive, then we have to go beyond
polarized communication. Working together, authors, editors, and
technical people can create articles with clarity, cohesion,
concision, and precision. The more they understand the basics of
communication, the faster and smoother the process of creating a
quality document is.
I came across a very interesting book that will be helpful to authors
and editors, and will make life easier for system administrators too.
Roy Jensen, M.Sc., Ph.D., is a chemistry instructor and author of
Communicating Science and Exploring Chemistry. It is Communicating
Science that I recommend to authors here so they can acquire skills
that will help them to convey messages efficiently. His book is an
introductory communication guide that provides learners with a
foundation for writing, reviewing, and presenting technical
information to academic and public audiences.
His site, Rogue Publishing, contains useful information on these and
The secretary of one association that is publisher of four journals asked me to install the Open Journal Systems and to train their staff member to upload articles.
I have installed OJS on their local machine since they were not clear about hosting they would like to use. I met their staff member and showed how to enter data in the forms for metadata, how to create journal, sections, users and other details.
He looked quite confident and confirmed my instructions using phrases: I will do that easily. I will manage that somehow.
After a couple of days their secretary called me and said that the Open Journal Systems messed up all information entered.
I was confused with what they said and I came to inspect what was going on. I noticed that some titles are written in capital letters, some are not, there is very noticeable inconsistency in typographical presentation of all information, numerous spelling mistakes, missing commas, periods.
Some references had number only associated to one reference, order was not good.
I was sure that this was not technical issue. The system cannot mess up entered information in that way.
Their staff member was looking at wrongly completed forms and he did not react much. When I asked details about entered data I realized that he entered them in that way.
I was more and more sure that he is person with dyslexia and that he was not aware on textual inconsistencies, fields in forms that are not completed, inaccurate years of journals etc.
I reported the secretary of that association on my opinion and that there is no magic software that will easily correct all mistakes in titles, subtitles, references, abstracts, numbering of references.
My suggestion was that their staff member is person with dyslexia. They expressed that they have had already some difficult misunderstandings with that person.
A couple of weeks later they said that their board is not against him. Well, it should not be against him, but it is questionable that being “for him” assumes that he can do work that is extremely hard.
From my point of view, that person should undergo medical examination and if the board decided to keep him involved in on-line publishing that is fine, but he must have personal assistant or to do some other work that is less difficult for him.
Persons with dyslexia should not be excluded, but we have to create relationship that is based on informed and scientifically supported decision making process that will make sure that there is no discrimination against that person and too great expectations.
Many people with dyslexia are never diagnosed and consequently not supported properly. When we notice that there is person in our working environment that does often spell-check errors or have had great difficulty reading texts. That person can be quite intelligent. Some important guidelines and explanations about dyslexia can be helpful to develop strategies that will not hurt a colleague with dyslexia. Even more, we can come up with solutions that can be very supportive for that person.
There are people who have had similar issues and they made a lot of effort to find solutions. Good resource about typefaces for dyslexia is worth reading. Some others developed special fonts that can help person with dyslexia to read better. Dr. Robert Hillier’s site offers useful information about his efforts confronting such issues.
Editors and administrators of the Open journal Systems can add information related to dyslexia in the information block for librarians, authors and readers. Sharing of good practice cases can multiply success in treating that phenomena.