Abstract
The digital format opens up new possibilities for interaction with monographic publications. In particular, annotation tools make it possible to broaden the discussion on the content of a book, to suggest new ideas, to report errors or inaccuracies, and to conduct open peer reviews. However, this requires the support of the users who might not yet be familiar with the annotation of digital documents. This paper will give concrete examples and recommendations for exploiting the potential of annotation in academic research and teaching. After presenting the annotation tool of Hypothesis, the article focuses on its use in the context of HIRMEOS (High Integration of Research Monographs in the European Open Science Infrastructure), a project aimed to improve the Open Access digital monograph. The general line and the aims of a post-peer review experiment with the annotation tool, as well as its usage in didactic activities concerning monographic publications are presented and proposed as potential best practices for similar annotation activities.
Highlights
From Print to Digital AnnotationAnnotation has roots that stretch back far into the history of the written word itself, as scholars and readers added notes and interpretations to the Talmud and other texts more than a thousand years ago
Ubiquity works with the Book Management System RUA, an Open Source application developed by Ubiquity to assist with the monograph publishing life cycle, from submission to both internal and peer review, from copy editing to production and publication
To increase discoverability and usability of open access (OA) Monographs, HIRMEOS experimented with the integration of a Named Entity Recognition and Disambiguation (NERD) for visualizing key words and disambiguating concepts in the full text
Summary
Annotation has roots that stretch back far into the history of the written word itself, as scholars and readers added notes and interpretations to the Talmud and other texts more than a thousand years ago. In 1993, when Marc Andreessen and Eric Bina were building Netscape, they included a feature called “group annotations” to complete this missing piece envisioned by Bush almost 50 years before This functionality was short-lived, as the team was not able at the time to build a server adequate to store those user-generated annotations [4]. There is clearly a need for both human readable and machine readable annotations as infrastructure, enabling deep dives into author credentials, methods, lab equipment, and identifiers. Depending on their needs, readers will select which channels or layers to monitor.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
