shared open source infrastructure in...

5/22/2019

1

Shared Open Source

Infrastructure in workflowCouncil of Science Editors Annual MeetingColumbus, OHMay 7, 2019

Infrastructure: Shared or Owned

● Acquisitions and Consolidation continue to affect publishing and library

services.

● A few companies may have the potential to “own” the research lifecycle.

● More university-created and community-owned projects are appearing on the

scene

● More funder and institutional mandates around open access and open data

● Increase in interest around reproducibility, reuse, data portability, and user

control.

5/22/2019

2

Sustainability

● The 2 ½% Project: Mellon-funded “inventory of infrastructure.” Would a

percentage of library budgets ($150-200M per year) sustain and preserve

open infrastructure?○ Michael Roy (Middlebury), David Lewis (formerly IUPUI), Katherine Skinner (Educopia)

● SCOSS (Global Sustainability Coalition for Open Science Services): Global

network of institutions committed to securing the future of OA.○ Current Appeal: DOAJ and Sherpa/ROMEO

● MIT undertakes environmental scan of open source authoring and publishing

platforms○ Mellon-funded

○ Results to be discussed at the Society for Scholarly Publishing Annual Meeting in June

Speakers

Heather Staines, MIT Knowledge Futures Group (moderator)

Maël Plaine, eLife

Andrew Smeall, Hindawi

Jennifer Regala, American Society for Plant Biologists

5/22/2019

3

Shared Open Source Infrastructure in workflow

Shared Open Source Infrastructure in workflow

Why eLife is building open source technology for publishing

Shared Open Source Infrastructure

5/22/2019

4

What is eLife?

● A non-profit backed by research funders to drive

reform in research communication

● We invest heavily in open-source technology

development and innovation on behalf of the

community

Libero Publisher

5/22/2019

5

eLife’s motivations

● Leverage the power of web technology to accelerate

research and discovery

● Support open-access publishing

● Build a community-owned infrastructure for research

communication


What are the infrastructure options for a publisher?

5/22/2019

6

Buy an

infrastructure

Buildyour own

infrastructure

Buy a proprietary solution

● You risk a strong dependence on a single provider

● There is reduced competition for feature

customisations

● There can be a lack of transparency

5/22/2019

7

If you build your own solution

● Requires a big upfront investment

● Maintenance and keeping up with the standard can be

difficult

● Need to keep up with fast moving technology

Shared open-source infrastructure

5/22/2019

8

Libero Reviewer Libero Publisher

Building an end-to-end solution

Submission Peer review Typesetting Hosting Publishing

Libero Producer

Today I will talk about

● eLife’s journey towards open-source infrastructure

● How do we build open-source technology

● How you join the conversation and use the open-

source tools that we are building

5/22/2019

9

eLife’s involvements in the open-source world


eLife’s development community

5/22/2019

10




Libero Producer

eLife’s Libero Reviewer collaboration

5/22/2019

11




Libero Producer

eLife’s Libero Producer collaboration

5/22/2019

12




Libero Producer

eLife’s Libero Publisher collaboration

5/22/2019

13

How do you build open-source software?


We listen to content providers

● A strong need for cost-effective solution

● Desire for a modern user experience (UX/UI)

● A need for more flexible, modular options

5/22/2019

14

How do we build tools that are easy to use?

● Workshops: we run with users and stakeholders

● Short feedback loops: we iterate on feedback and

adapt our design

● User tests: we make sure that our solution works wellWe run workshops with usersand stakeholders

...to build user interfacesthat are intuitive and

save time

5/22/2019

15

How can you join the conversation and get started with your open-source projects?


Talk to the community

https://libero.pub/join-slack/

Or contact us by email: [email protected]

5/22/2019

16

See our product roadmap

https://elifesci.org/roadmap

Accessing the code now

● Libero Publisher code:

https://github.com/libero

● Other products’ code:

https://github.com/elifesciences

5/22/2019

17

● We’re constantly evolving https://libero.pub with new guides and

links to the relevant repositories

Visit our product website

Join our events

● Open-source technology in publishing Community Call

● Open-source Community Sprints

● Subscribe to our technology and innovation newsletter and

follow us on Twitter: @eLifeInnovation

5/22/2019

18

I do not have a tech team, can I still use your tools?


Options

● Libero is developer-friendly which means you can easily find

software professionals to help get you set up

● Will be supported by an ecosystem of open-source service

providers that can provide turnkey implementations of our

platforms

5/22/2019

19

Libero Community

ServiceProvider

Univ

ers

ity

Pre

ss

Publis

her

Publis

her

Univ

ers

ity

Pre

ss

Publis

her

Socie

ty

Socie

ty

Socie

ty

ServiceProvider

Service provider model

ServiceProvider

Implementation, customisations &customer service

Libero Suite users

Code base maintenance

Our conclusion to this approach


5/22/2019

20

Benefits of a community-owned approach

● Future-proof: No one is dependent on any one

organisation

● Customer-owned: Your instance of the platform

belongs to you; you can change it any time

● Best of both worlds: You can adapt the code, and

have plenty of qualified support available

[email protected]

https://libero.pub

https://libero.pub/join-slack/

https://elifesci.org/roadmap

Thank you

5/22/2019

21

Implementing Open Source Publishing ToolsCouncil of Science Editors Annual Meeting

Andrew SmeallChief Digital [email protected]@mynameissmeall

Hindawi publishes 232 Open Access journals across STEM, Biology, Medicine.

5/22/2019

22

Distribution PlatformPeer ReviewSubmission

Acceptance

Invoicing Production

Publication

Distribution PlatformPeer ReviewSubmission

Acceptance

Invoicing Production

Publication

Quality Screening

Workflow Customization

Content Ingestion

Reporting and Audit

Collection and Couponing

Online Proofing and QC

Staff and Vendor Manager

Reporting and Audit

A & I Delivery

Marketing and Blogging

ALMs, Text Mining

SEO and Analytics

5/22/2019

23

Building a metadata review process for repository ingestion using Pubsweet

Building a simple, single-blind peer review workflow using Pubsweet

Building a multistage, collaborative peer review process using Pubsweet

Building an HTML-first, open review process using Pubsweet

Build vs. Buyanalysis

Start development

Second journal release

White label version

First Pubsweet meeting

First journal release

Full portfolio release

2017 2018 2019 2020

5/22/2019

24

Build vs. Buyanalysis

Start development

Second journal release

White label version

First Pubsweet meeting

First journal release

Full portfolio release

2017 2018 2019 2020

Ingredients we needed in 2018

• 4-5 Javascript developers • 1 tester• 1 designer• 1 product manager• Hosting costs

Image: Flatiron Building Construction, New York Times - Library of Congress, 1901-1902 crop.jpg (Public Domain)

5/22/2019

25

What’s already sitting in the pantry

• All the work done by Coko, UCP, eLife, Hindawi, and EBI

Fresh ingredients you might need today

• 1 Javascript developer • 1 designer• Hosting costs


Fresh ingredients you’ll need next year

• Hosting costs


5/22/2019

26

Review Demo

Take a copy for yourself!https://gitlab.com/hindawi/xpub/xpub-review

Get in touch!

Andrew [email protected]@mynameissmeall

5/22/2019

27

ASPB and Hypothes.is

Jennifer Regala ([email protected]; @Jregala_ASPB)

Managing Editor, The Plant Cell and Plant Physiology

Yay! We just signed with

Hypothes.is!

5/22/2019

28

Should We Use Hypothes.is at ASPB?

There Are Many Questions To Ask…1. What are the costs involved?

2. What will be required of our pubs staff?

3. What will our journals’ editorial boards think?

4. How can our authors, readers, and members of our

community at large use this tool?

5. Are there other departments/missions in our

organization that will be well served by this tool?

6. What are our competitors doing?

7. The hardest question of all: WHERE DO WE START?

• The Plant Cell, ASPB’s flagship journal,

publishes novel research of special

significance in plant biology, especially in

the areas of cellular biology, molecular

biology, genetics, development, and

evolution

• Top primary research journal in plant

biology

• The Plant Cell celebrates its 30th

anniversary this year

5/22/2019

29

• The Plant Cell announced its decision to adopt a form of open peer review in

an October 2016 editorial by Editor-in-Chief Sabeeha Merchant: “The Plant

Cell Begins Opt-in Publishing of Peer Review Reports”

• From the editorial: “Reviewer anonymity will be strictly maintained. The

reports will include the major comments from reviewers and the editors’

decision letters along with the authors’ response to reviewers for each

submission of the manuscript (including original, revised, and previously

declined versions), as well as a timeline documenting the path of the

manuscript from submission to publication. The decision letters typically

include the substance of comments from any post-review consultation among

editors and reviewers.”

• We decided we needed a way to highlight these important reports

HOW Does The Plant Cell Handle Open Peer Review?• Invitations to review a manuscript include information about the peer review

report

• Reviewers remain anonymous in peer review reports (the editorial board

believes that anonymity is integral to this process)

• After manuscript acceptance by the reviewing editor, a peer review report is

prepared by the science editor handling the paper (WITH author approval).

Science editors are paid per report (compilation, formatting, posting of

report)

• Reports follow a standard format and are lightly edited (to remove

miscellaneous correspondence, for instance); authors APPROVE their reports

• To be added to August 2019 Editorial Board Meeting discussion: publishing

peer review reports for ALL articles

5/22/2019

30

What Does a Peer Review Report Look Like in The Plant Cell?

What Does a Peer Review Report Look Like in The Plant Cell

(continued)?

5/22/2019

31

The Plant Cell Includes Peer Review

Reports with Supplemental Data

https://hypothes.is/groups/qYmBjYvN/tpc-reviews

5/22/2019

32

CHALLENGES

• Staff time and buy-in

• Ed Board time and buy-in

• Creative and useful ways to implement

Hypothes.is

• How to market the tool

LOOKING FORWARD

5/22/2019

33

The Plant Cell is considering using

Hypothes.is during the peer review process

The Plant Cell will participate in a pilot

program with bioRxiv

5/22/2019

34

• Plant Physiology is a monthly journal

• ASPB’s largest publication (volume)

• Most frequently cited plant biology journal

• Plant Physiology will be the next place where

we roll out the Hypothes.is tool

• NOTE: This journal does not publish peer

review reports, so the bioRxiv pilot program

will not apply to this journal

5/22/2019

35

We also plan to implement Hypothes.is with our digital ecosystem, Plantae, to allow for

enhanced community conversation and more cross-talk between our journal sites and this

network.

https://plantae.org/

ANY QUESTIONS?

I’m Jennifer’s new puppy, Scotty!

Let’s talk about me instead of you

all asking any questions! Ruff ruff!

shared open source infrastructure in...

Documents