eLife Lens - HW publishers meeting

Transcript

1. Ian Mulvany - head of technology
   @IanMulvany
   i.mulvany@elifesciences.org
   eLife Lens
   Highwire publishers meeting May 2014
   

   View Slide

2. Why did we build Lens?
   

   View Slide

3. Articles online are designed with print constraints
   HTML can do things print can’t
   

   View Slide

4. View Slide

5. How did we build Lens?
   

   View Slide

6. Ivan Grubisic Michael Aufreiter Graham Nott
   Concept, prototype
   testing,
   development
   front end, javascript,
   interface,
   development
   xml workflows and
   back end, image
   processing
   

   View Slide

7. View Slide

8. View Slide

9. What does it do?
   

   View Slide

10. View Slide

11. Demo
    

    View Slide

12. How does it do that?
    

    View Slide

13. In NLM XML most
    links are one-way
    

    View Slide

14. In Lens-JSON we
    make two-way links
    explicit
    

    View Slide

15. XML JSON HTML
    This conversion happens in the browser, client side,
    no server needed!!
    

    View Slide

16. How can you deploy it?
    

    View Slide

17. 1 - Call the Javascript
    2 - Point it at your XML file
    

    View Slide

18. EJP
    zip AWS
    EC2
    AWS S3
    article
    xml
    AWS S3
    image
    optimisation
    AWS S3
    lens
    index.html
    HW article
    page
    Amazon web services
    

    View Slide

19. Does it work?
    

    View Slide

20. View Slide

21. average time on lens article : 3:12
    average time on html article : 3:34
    need to do some more investigation, and
    segmentation, for me it’s an encouraging start.
    

    View Slide

22. View Slide

23. What’s next?
    

    View Slide

24. NOW
    NEXT Peer Review?
    

    View Slide

25. XML JSON HTML
    edit in browser
    

    View Slide

26. EJP TNQ
    submissions system typesetters
    80% XML
    80% XML + lens.js
    =
    Awesome reviewing experience
    

    View Slide

27. http://substance.io/composer/
    

    View Slide

28. Landes Biosciences, PeerJ also interested are PLOS,
    Dove Press and a project from the University of California Davis
    

    View Slide

29. - tracking of in-lens interactions
    - extend lens to support more “resources”
    

    View Slide

30. Finally, why is it called Lens?
    

    View Slide

31. Altreader
    Anableps
    Glance
    Kaleidoscope
    Lens
    Mix
    Obake
    Panorama
    Panoreader
    PaperView
    Parallax
    Quarto
    Reader
    Savvy
    Scope
    Sense
    Spectare
    Telescope
    Vision
    Visum
    Wafer
    eLluminate
    

    View Slide

32. https://vimeo.com/67254579
    http://lens.elifesciences.org/manual/
    Resources
    https://github.com/elifesciences/lens/
    

    View Slide