The next time you feel moved to comment on an article in the open-access online journal eLife, be prepared for a different user experience. On 31 January, eLife announced it had adopted the open-source annotation service, Hypothesis, replacing its traditional commenting system. That’s the result of a year-long effort between the two services to make Hypothesis more amenable to the scholarly publishing community.
NEW: Applications are now open for the Innovation Sprint on May 10 and 11, 2018 — a two-day challenge to prototype new ideas to bring cutting-edge technology to open research
Find out more & apply now https://buff.ly/2DKjPnG
#Product manager, apply by Feb 14 – see below
#Marketing assistant, apply by Jan 31: https://elifesciences.org/jobs/86a1a482/marketing-assistant …
Highly recommend this place as an employer & can vouch for the heads of both teams (my current and my previous). Hit me up if you’ve Qs 🙂 https://twitter.com/augmentl/status/951099077592256512 …
Introducing ScienceFair, a new way to stay up-to-date with science from your desktop @sciencefairapp #eLifeLabs https://elifesciences.org/labs/88b45406/sciencefair-a-new-desktop-science-library … pic.twitter.com/iUCEN8uQs5
An Unpaywall tab is prominently visible on @eLifeInnovation‘s screenshots of their redesign. #thisBringsMeJoy https://elifesciences.org/labs/c8e0dddf/welcome-to-elife-2-0 …
We’re moving the online journal forward, and we hope you’ll join us on our journey.
Why do we need an eLife 2.0?
When I joined eLife just short of two years ago, I moved from a long stint in the corporate high-tech space into the scientific publishing realm, and got a serious taste of professional culture shock. Having spent much of my career as a user experience practitioner, I was taken aback at the state of online science journals when compared directly against the well-established standards of usability, accessibility and design that have become commonplace in the online services, retail, technology and social media spheres.
Responsive design, the ability for content to adjust its presentation seamlessly from one device to another, is still a rarity in the journal space. So are applied UX design principles, affordances for multiple reading and browsing behaviours, offline reading and performance optimisations, and a number of other practices most of the rest of the web takes for granted.
The eLife website did many of these things right, but it was still far from ideal. Born of a need to get up and running quickly in the fledgling days of the organisation, and tasked as an effective delivery vehicle for an innovative peer-review process, the site followed the standard online journal practice of displaying as much information about the article as possible, without a great level of care about whether, and how, this information should be prioritised.
The result, again typical of many online science journals today, was a somewhat cluttered article view brimming with seldom used links and metadata, a sub-optimal visual hierarchy, and an overall presentation that most users found less preferable than the stalwart format for research consumption, the venerable PDF.
The observation that the PDF, a proprietary legacy of the printed page era, still represents the dominant form through which the latest research is accessed, suggested that we as a journal had a real opportunity to look closely into what we could do to help our users transition towards more dynamic, rich, and interactive research artefacts that can more fully and faithfully convey the nuances of scientific discovery.
Thus began the effort that became eLife 2.0, a user-centred, bottom-up overhaul of our online journal aimed at delivering three key goals: deliver the best article reading experience, highlight content that enriches the research, and make it all easy to find. All while setting down a modern foundation for future innovation in the research publishing space.
Goal 1: deliver the best article reading experience
In an era of dynamic web content, open data, and increasingly powerful browsers, the PDF still rules supreme as the primary form through which new research is read. This is a shame, because it means fewer researchers are taking advantage of opportunities to more fully convey the full, reproducible narrative of their research through tools like interactive figures, executable code, and live data visualisations.
Our user research indicated a number of rather predictable reasons for PDF’s continued dominance as a research consumption format, including portability, offline reading use cases, and good old fashioned familiarity. But one of the most prevalent reasons given by our users for preferentially using PDF really surprised us: “because it looks nicer”.
Aesthetics are easy to underestimate in the realm of reason and scientific rigour, but even the most analytical mind is still human after all and, whether consciously or not, appreciates reading experiences that minimise visual noise, reduce distractions, and therefore limit sources of cognitive load beyond what’s needed to interpret the content being read. In the case of research articles, “looking nice” is in fact a proxy for some important aspects key to an article’s readability:
- A clean layout, with a clear visual hierarchy
- No intrusive sidebars, calls to action, thumbnails or adverts
- A legible, high-contrast font
- Good-sized figures that can be consumed alongside the article text
These aspects formed the basis of eLife 2.0’s article page design, and went on to influence every major design decision throughout the rest of the site.
Inspired in part by research into reading behaviours, as well as reading-focused platforms from Medium to the Amazon Kindle, the new article page in eLife 2.0 provides a clean, distraction-free layout with a flexible navigation structure that supports how reading and skimming behaviours vary across desktop and mobile. In addition, eLife 2.0 article pages more seamlessly embed our signature Lens view (for simultaneous text and figure browsing), which is now accessible by selecting the Side by Side option alongside the traditional Article and Figures views.
The new article pages are also optimised for reading across a wide range of devices and screen sizes, and should load significantly faster than our previous site thanks to a streamlined page asset budget and our new IIIF-enabled figures. Standing for International Image Interoperability Framework, IIIF allows us to more efficiently serve the large images behind our figures by efficiently delivering only the bare minimum image data needed to render an image at any given screen size.
IIIF also forms the basis of further enhancements to the site. Shortly after launch, we will be deploying an enhanced asset viewer that will take full advantage of IIIF’s feature set. This new viewer, which we’ll also release as a standalone open source component, will allow figures viewed in full screen, and all their supplements, to be zoomed with very fine granularity thanks to OpenSeaDragon. This will let users interact with very large, highly detailed images with no performance penalty on almost any device. In the future, IIIF will also allow us to explore the ability to let users annotate our figures, as well as a number of other interesting use cases.
And what about offline reading? We’ve now laid the groundwork for the implementation of Serviceworker, a technology that will soon let eLife 2.0 articles cache locally on your machine, so that once you’ve browsed to an article you can go offline, reload it from your browser history or a bookmark at a later date, and it will still be there waiting for you. Or, you could download the article into ScienceFair and take advantage of its powerful manuscript management functions while enjoying your papers though our eLife Lens view.
Goal 2: highlight content that enriches the research
eLife’s in-house teams generate a large amount of content, such as Insights, Feature Articles and Editorials, that add both context and perspective to the science we publish. These articles also appeal to a broader, less specialised audience, and promote a shared understanding of scientific discoveries across disciplines.
In eLife’s previous iteration, this content could be quite difficult to find (Some users didn’t even know we had a regular podcast), so we wanted to make sure that all this content had a proper home, a portal where readers could more easily access this material.
The Magazine section of the site was created as just such a portal, showcasing everything from our latest Insights, Feature Articles and Editorials to subject-specific Collections, our Podcast and a range of content for and about early-career researchers.
It is our hope that the Magazine will establish itself as an alternative entry portal to eLife’s content that appeals both to specialists who are keen to read about developments in other fields, and to non-specialists looking for a perspective on the latest research across the life sciences.
Goal 3: make it all easy to find
Search was never a strong use case for the eLife website, given the majority of our visitors originate from search engines such as PubMed and Google Scholar, and enter our site directly at the individual article level.
But search is not the only way to find relevant content, which is why we have completely overhauled both the site’s navigation as well as its content recommendations infrastructure. What this means, is that specialists can jump directly into their subject of interest from the home page without having to so much as scroll, or get there directly from an article by clicking the appropriate tag.
In eLife 2.0, research categories are now treated like mini home pages in their own right, presenting relevant, up-to-date Research and Magazine content in a single organised view — allowing users so inclined to bookmark their research category of choice and streamline their browsing experience.
Finally, when you’re done reading an article in eLife 2.0 you will be discreetly introduced to a set of closely related articles, to help you discover more relevant science, or to more easily follow the full narrative of a discovery without leaving the article page.
And yes, we have also overhauled our global search capability to cover all content types across the site and provide more intuitive filtering, so you should always get the most relevant results whether you’re searching for an author name or a model organism (or anything in between).
Performance, patterns, and giving it all away
eLife 2.0 is the result of roughly eighteen months of user-centred design, development and testing, with many key site features having seen dozens of iterations as a result of direct user testing and performance optimisations. And while we’ve made every effort to ensure the site serves as a good example of UX and accessibility best practices, we know others can do even better.
To that end, we will soon be releasing all the UI patterns, style guides and key visual and code assets developed for eLife 2.0 under a CC-BY license as part of eLife’s Continuum publishing platform, in the hope that they will lower the barrier to entry for other publishers to use what we learned in the making of eLife 2.0 to improve their own user experience.
By using these assets, other publishers will also be able to take advantage of the substantial performance gains delivered by our minimalist design patterns, while making their own sites substantially more maintainable by adopting our novel approach to the use of PatternLab for the modular implementation of the site’s front-end (a post on the subject will follow soon).
We have worked hard to make sure that eLife 2.0 brings across-the-board improvements to our users, and now that the site is out we have many new features in the pipeline, to be announced in the coming months. We will be measuring the success of the project not only by its impact on the usual visitor metrics, but also on whether and how the assets and resources we release to developers are used, and whether they are judged as helpful by the community.
Thanks for joining us on the next phase of our journey.
When we set up the eLife journal in 2012, we knew datasets were an important component of research content and decided to give them prominence in a section entitled ‘Major datasets’ (see images below). Within this section, major previously published and generated datasets are listed. We also strongly encourage data citations in the reference list.
Major Datasets for “Structural basis of protein translocation by the Vps4-Vta1 AAA ATPase” by N. Monroe, H. Han, P. Shen, et. al.
Almost five years on and I feel we have still not cracked it! We have signed up to the Force11 data citation principles, which were published three years back; we have been actively involved in working groups of Force11 and others, for example the Data Citation Roadmap for Scientific Publishers and the JATS XML data citation recommendation of JATS4R. I am also currently working with other publishers to come up with recommended JATS XML tagging for data availability statements, which is easier said than done considering the nuances of dataset uses and also how different publishers approach this.
Added to this, there is still significant push-back from authors about putting all dataset citations in the reference list (for example, authors are concerned about self-citing by citing a dataset created as part of the research article; “dataset citations” that are in effect a link to a search results page on a database; and the necessitation of hundreds of reference entries if an author has used a large base for the research).
While eLife is very active in this space, and aims to arrange and mark up the datasets and citations produced by our authors in line with recommendations, the recommendations still have some gaps and the complete picture is not yet clear.
In late 2014, we brought in-house the process of depositing Crossref metadata (previously our online host did this for us). It gave us control of our processes and, at the time, we sent all the information we could to Crossref and have ensured our references are open and available in the Crossref public API. The code for this conversion process is all open-source and available for reuse. It can be found on GitHub (https://github.com/elifesciences/elife-crossref-feed). Since then, besides small improvements to the code and troubleshooting problems, we’ve not updated the code. I have been keeping a list of Crossref features and new deposit metadata we can add to our deposits, and now is the time for us to start working on this again.
One of the items we’ll be addressing is data citations.
The Crossref reference schema does not cater well for non-book or -journal content, and if an item does not have a DOI, the “reference” is not very useful because of the few tags available in the Crossref schema.
However, Crossref have introduced the relationship type to their schema, so data references can be well linked and mineable. As I see Crossref as a potential broker between publishers and data repositories in the future, using the relationship-type deposit for all datasets will assist this and also allow these data points to more easily be seen within the article Nexus framework (see the recent blog post, How do you deposit data citations?).
At eLife, we already distinguish between Dataset generated as part of research results (relationship type in the Crossref schema: “isSupplementedBy”) and Dataset produced by a different set of researchers or previously published (relationship type: “references”). Therefore, it will not be hard for us to convert all the information about data referencing that is within the dataset section into a relationship-type deposit in the conversion to Crossref XML.
We have also recently gone through an exercise of defining a set of rules for all our references and, of the 12 allowed types, one is data. The rules for Schematron (a rule-based validation language for making assertions about the presence or absence of patterns in XML trees; see also this useful article about Schematron on the JATS4R learning centre) have been written for the eLife ‘business’ rules. Subject to final testing, these will be integrated into our workflow (the Schematron is open source and available for reuse on GitHub, and we will also build an API for people to use the Schematron direct). This will allow us to easily identify all data references and convert them into relationship types in the XML delivered to Crossref. This way, they will not be lost in the references section of our deposits, but properly identified.
However, we do appreciate this will become harder for us as authors become more familiar with datasets as references, because we will not be able to identify the difference between generated and analysed datasets so easily.
The code developed and used to complete these conversions will, again, be on Github and open source, and we actively encourage the reuse of this.
While the industry is still working on the best way to deal with data and ensuring it is given the prominence it requires, we feel this is the best approach we can take. Nothing is forever and we can still change what we do in the future. The beauty of open-source code also means that if there is an alternative approach now or in the future, the code we wrote at eLife can be developed by someone else in the future and we can all benefit.
If you have any questions, please do not hesitate to contact us.