I am glad to announce the public availability of rchiveit, a Web application with the aim to quickly deliver the answer to the question
What am I allowed to do with my scientific paper?
Three days ago, I played with Bootstrap for the first time. Yes, I have background in Web Engineering but I have never played with Bootstrap before.
Playing with bootstrap for the first time, and building something good for #openscience.
— Daniel Graziotin (@dgraziotin) September 15, 2013
While Open Access begins to be well known and widely adopted in Life Sciences, I could perceive this is not the case for Computer Science. Especially, I deal with many researchers in Software Engineering and Information Systems. The majority of them do not even know that they can self-archive their papers.
Even worse, most of those who aware of self-archiving blatantly admit that they do not have the time to understand whether they are allowed or not to do that. Therefore, they don’t self-archive. Sure, publisher’s copyright transfer agreements are long, tedious and difficult to understand. For this reason, SHERPA/RoMEO was born. SHERPA/RoMEO collects and lists publishers’ copyright agreements & retained author rights. Unfortunately, its outdated interface still offers too many details. Scientists need a fresh website that delivers a strong, immediate message. Therefore, I developed rchiveit.
Researchers input the name of the journal or the conference proceedings book in rchiveit. The system looks in SHERPA/RoMEO database, eventually help to disambiguate the given text, and then deliver an icon-based answer, in a 4+1 View of green Open Access.
This is what researchers see if preprinting is not allowed.
On the other hand, this is what researchers see if preprinting is not allowed:
In addition to listing the preprint permissions in a straightforward way, rchiveit already suggests where to upload them. Unfamiliar names such as self-archiving, preprint, and postprint have associated explanations that appear on mouse hover. Where possible, Wikipedia links are also provided.
As publishers often impose limitations and general conditions to the granted rights, rchiveit presents them after the permissions.
An rchiveit entry somehow mimics a Creative Commons page. It strives to deliver the most essential information with the links to expand the knowledge, if needed.
rchiveit is how I imagine a better SHERPA/RoMEO to be. But it is far from being perfect. I kindly ask the scientific / technological community to spread the tool but also to contribute to the project. Every small help counts, even correcting the English of the Why self-archiving a paper? section.