eLife Lens - HW publishers meeting

Transcript

1. Ian Mulvany - head of technology @IanMulvany i.mulvany@elifesciences.org eLife Lens Highwire publishers meeting May 2014
2. Why did we build Lens?
3. Articles online are designed with print constraints HTML can do things print can’t
5. How did we build Lens?
6. Ivan Grubisic Michael Aufreiter Graham Nott Concept, prototype testing, development front end, javascript, interface, development xml workflows and back end, image processing
9. What does it do?
11. Demo
12. How does it do that?
13. In NLM XML most links are one-way
14. In Lens-JSON we make two-way links explicit
15. XML JSON HTML This conversion happens in the browser, client side, no server needed!!
16. How can you deploy it?
17. 1 - Call the Javascript 2 - Point it at your XML file
18. EJP zip AWS EC2 AWS S3 article xml AWS S3 image optimisation AWS S3 lens index.html HW article page Amazon web services
19. Does it work?
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.
23. What’s next?
24. NOW NEXT Peer Review?
25. XML JSON HTML edit in browser
26. EJP TNQ submissions system typesetters 80% XML 80% XML + lens.js = Awesome reviewing experience
27. http://substance.io/composer/
28. Landes Biosciences, PeerJ also interested are PLOS, Dove Press and a project from the University of California Davis
29. - tracking of in-lens interactions - extend lens to support more “resources”
30. Finally, why is it called Lens?
31. Altreader Anableps Glance Kaleidoscope Lens Mix Obake Panorama Panoreader PaperView Parallax Quarto Reader Savvy Scope Sense Spectare Telescope Vision Visum Wafer eLluminate
32. https://vimeo.com/67254579 http://lens.elifesciences.org/manual/ Resources https://github.com/elifesciences/lens/