Over the course of two days in San Francisco, about 20 of us put our heads together to talk about upcoming features in PubSweet 2.0, Coko’s platform-building toolkit. (If you want to get up to speed on the 1.0 release, more on that here.)
The first day covered PubSweet 1.0. Jure Triglav, lead developer for PubSweet started by running through where PubSweet is now, we also looked in detail at Editoria and xpub the book and journal platforms constructed from the PubSweet ecosystem.
Editoria has been released as a version 1.0 and xPub is in early development so this was a great time to get input from journal publishers who can shape how xPub will meet their needs for manuscript submission, peer review and article production as well as back-end functions in conversion and enrichment.
On day two, we split into two groups: one to look at the PubSweet 2.0 request for comments and the other to think through some use cases. The RFC process was extremely interesting and useful. We slimmed down and prioritized the 2.0 features and made some enhancements.
The final list is as follows:
- Add a missing test for the production pubsweet-cli
- Write a getting started guide for component development
- Authorization support for filtering
- Replace bespoke ORM Code
- Implement GraphQL
- Simplify Project Structure (if necessary) (waiting for code review)
- Double check terminal colors
- Replace bespoke CLI code
- Extend CLI
- Automatically write routes based on added/removed components
- One-line publishing platform installs, e.g. “pubsweet install editoria” or “pubsweet install xpub-journal”
- Process management (daemonize, kill, ps)
- “pubsweet updated”
- “pubsweet upgrade”
- “pubsweet backup & pubsweet restore”
2.0 – Remove REST endpoints
Towards the end of the meeting, the group broke down several common journal components and worked out requirements for them. We covered everything from submission to configurable HTML-first workflows.
A diverse set of journal publishers were represented and, interestingly, were able to design several important common components. We’ll begin building these immediately!
We also talked about what being part of an open source community means in terms of business models and sustainability, the need for new types of service providers to step up and how our relationship to technology is changing in the publishing industry.
Next up: we’ll continue to build out components for a journal and preprint production platform, xPub. Because of PubSweet’s flexible content model, xPub is suitable for other forms of data and content, too.
We’ll be expanding our community to gather more input, so get or stay in touch!