AnnotumAn open-source scholarly authoring and publishing platform based on WordPress

New models of scholarly communication

2

New models of scholarly communication

3

PLoS Currents: Key features

• Registration• Articles are date-stamped and citable

• Certification• Reviewed by expert researchers

• Dissemination• All content is open access

• Preservation• Archived at PubMed Central

knol.google.com

Knol authoring features

PLoS:Currents – review workflow

PLoS:Currents – review workflow

1. Editor selects reviewers 2. Reviewers enter comments

3. Approved content published to Knol and PubMed Central

PLoS:Currents limitations

• DTD/Structural conformance has been a challenge

• No import of existing content (compilations, re-use)

• Single-source hosting – features, workflow, etc. cannot be brought in-house or modified

• Limited output/formatting options

9

Annotum: goals for v1.0

• Replicate the basic Knol / PLoS:Currents feature set • Address limitations of Knol toolset

• DTD conformance (enforcement) and import/export• Support for rich designs and additional output formats• Provide flexible hosting options via open source code

• Out of scope: • Replace all print/online journals, tools, systems• Solve all issues raised at #beyondthepdf

10

Annotum: v1.0 key features

• Based on WordPress• Rich network of designers, developers, and add-on services• Simple to self-install and administer• Stable, scalable, wide adoption – many millions of blogs

• Authoring tools: tables, equations, citations, figures• Simple review workflow with pre- and post-review comments (public and non-public)

• “Beautiful” templates for presentation (web, pdf, txt)• “Round-trip” import and export via NLM XML

11

Timeline (tentative)Task Jan-11 Feb-11 Mar-11 Apr-11 May-11 Jun-11 Jul-11 Aug-11 Sep-11

Task 1: Setup

Task 2: Requirements

Task 3: Implementation(2-week sprints)

Task 4: Launch

Task 5: Support

12

Kickoff

Detailed Requirements Complete

1 2 3 4 5 6 7 8

Beta VIP Migration

Ongoing

Walk-throughs

Mid-project Review

Wrap-up

Annotum: issues for v1.0 and beyond

• Who defines document structure? • A human must be involved – author, editor, or repository

owner. Annotum asks the author/submitter to do this.

• What workflow/review models are needed beyond PLoS:Currents quick-review use case?

• Support for new data formats and elements?

13

Thank you!

Many thanks to: Google/Knol, PLoS, NIH/NLM/NCBI, WordPress.com, Crowd Favorite

Carl Leubsdorf, Jr.

annotum@solvitor.com

http://solvitor.com

Special thanks to Mark Patterson, PLoS for several slides used in this presentation.

14

Appendix

WordPress supports rich designs

16

vs.

Use case – small group

A group of collaborators use a local installation to author and collaborate on a series of articles, which are then published on the web or printed (PDF) for distribution to their friends and colleagues

17

Author / Invite / Edit

PDF/RTF

XML Export

CoauthorsWeb Publish

Annotum

Use case – online journal

• Submissions via XML import or authored on-site• Approved articles published or exported

18

Reviewers

Invite / Review

PubMed Central

Author / Invite / Edit

Coauthors

PDF/RTF

XML Export

Web Publish

XML Import

Annotum

Annotum vision: a “knowledge ecosystem”

19

Invite / EditExport PDF

Export XML

Invite / Edit

Local independently-produced print journal

Reviewers

Invite / ReviewAdditionalCoauthor

Publish to Web

Export XML

University Journal sharing content with PubMed Central

Invite /

Review

Publish to Web

Large open-access eJournal

Export XML

PubMedCentral

XML

PublishCoauthors

Reviewers

Invite / Edit

Invite / Edit

XML

Invite /

Review

“Freemium” Open Journal Hosting Network

MultipleReviewerGroups

MultipleCoauthorGroups

Coauthors

Annotum

Annotum

Annotum

Annotum