Beta testing results: part II
In an earlier blog post, Cynthia York addressed and summarised the invaluable comments we received from the 34 beta testers who willingly devoted some of their precious time to play around with the AOR1 viewer and answer a number of questions we had formulated. These questions covered various aspects of the viewer, including its functionalities and design, as well as of the AOR website itself. In this short blog post, I will reflect upon some of the suggestions which appeared more frequently and the subsequent actions we will take or already have taken to address them. But before that, we again want to express our heartfelt gratitude to our beta testers: thanks ever so much, you rock!
Pinning a page
Several beta testers expressed the wish to be able to ‘pin’ or freeze a page, ensuring that subsequent actions in the viewer (searching, browsing) do not result in the ‘loss’ of that particular page. We thought this to be an important feature too, since one can easily lose important research findings when going down the rabbit hole of (early modern) marginalia. Hence one of our programmers, John Abrahams, created a button which enables one to pin the page, making it impossible to move to another image (via the browse buttons) or to open another image in the same work space. It still is possible to conduct searches and to open a search result in another workspace, however. Research thus can continue, but without the risk of losing the pinned page. There is one small glitch which remains to be solved: opening several other workspaces through the ‘change layout’ button unpins the page.
The desire to return to the gallery of books (the AOR corpus) in a simple and straightforward manner was also voiced by several beta testers. Luckily, this request turned out to be pretty easy to fulfill as the new version of Mirador (2.1) included such a home button, further improving the ease with which one can navigate.
Transcription/search panel icon
Various testers mentioned that it was not easy to find the icon to open the transcription and search panel. Although it turned out to be difficult to change the icon, we have changed the accompanying tooltip text to ‘View Transcriptions & Search’. As the real meat of the AOR content can be accessed in this panel, we might arrange that this panel automatically opens after having selected a book.
The need for (better) documentation was mentioned frequently as well, and over the last month or so of the project the whole team has been working hard on generating documentation covering various aspects of the project, including its technical infrastructure and the functionalities of the viewer. In addition, two wonderful contextual pieces, a biography of Harvey and a short introduction to the history of reading, have been included as well. We aim to add another piece, this time on Harvey’s library, soon. All the documentation can be found here.
Various testers expressed the wish to be able to search for, for example, all instances of underscored text in a particular book or, indeed, all instances of a reader intervention in a book. This is a search functionality I have always been interested in myself, in particular because it’s fairly annoying to have to scroll through lightly annotated books in order to find a page which has been annotated by a reader. Including such a functionality provided to be impossible before the end of AOR1, but this is high on the to-do list of AOR2.
Highlighting the coordinate region of a specific annotation
When browsing heavily annotated pages, it sometimes is not immediately obvious where to locate a particular annotation. One way to indicate the location is to highlight a coordinate region in which the annotation ‘sits’, as done, for instance, by Annotated Books Online. However, there are a number of annotations, such as the ones who snake around a page or even across pages – as frequently happens in the heavily annotated books from the Folger, the Domenichi and Guicciardini – which can’t be captured in a system of polygons based on coordinates. Moreover, the XML transcriptions do not contain any spatial data related to the position of the annotations (and manually including these would take ages). We do describe the location (or position) of annotations on the page in the XML transcription and, realizing that some form of indication regarding the position of annotations is helpful, we have included a set of icons in the transcription panel which points at the location of a marginal annotation.
People mentioned in marginal notes as hyperlinks
Some testers would appreciate that the people mentioned in marginal notes (and which are broken out individually in the transcriptions) become hyperlinks which initiate a corpus-wide search (i.e. returning all the instances in which this person appears). Already when developing the AOR1 XML schema and, at a later stage, the document relating to the transformation of the data in the XML transcriptions to HTML in the transcription panel, we thought about this functionality. However, this proved to be quite a tricky feature indeed, so we were not able to implement it. However, this feature will be discussed for possible technological development and implementation in AOR2.
There are certainly more desiderata to be mentioned, and it was interesting to see how several comments of our beta testers overlapped with our own ideas regarding further improvement of the AOR viewer. Rest assured that we will do whatever we can to maximize the functionalities of our viewer and to further enhance the research environment AOR envisages!