Starting from Manovich’s (2007) statement that “a prototype is a theory”, Galey and Ruecker (2010: 406-07) argue that design can become “a process of critical enquiry itself”, a “thinking through making” pursuit allowing the combination of digital prototyping with critical analysis. Furthermore, Pierazzo (2011: 466) brings into discussion the theoretical assumptions that may underpin the decision making process in building an edition as an “interpretative scholarly product” based on the “selection of features transcribed from a specific primary source”.
The Transviewer concept consists of building a framework for the publication of European history documents on the CVCE’s Website, from treaties, official declarations and meeting reports to letters and interview transcriptions. In a first phase, a pilot testing set for the prototype (Figure 1) has been encoded in XML-TEI P5, including a selection of 55 documents on armament issues within Western European Union (WEU), from 1950’s to 1980’s.
In line with Booth et al. (2008), Galey and Ruecker (2010: 412-13) consider that a prototype can be the embodiment of an argument (or more), with all the key components of a “good thesis topic”: to be “contestable”, “defensible”, and “substantive”. This refers to how a prototype includes old affordances in a new way or proposes something new, to its potential of convincing people to accept it, or finally, to its intellectual and practical value.
Our idea in designing the Transviewer has been based on the following “arguments”:
A number of features to be encoded and rendered via the interface have been considered after consultations with the users (CVCE's researchers):
|Documentary||Ink colour of stamps (red, black)||Ink colour of handwritten text|
|Topology||Document layout (position and alignment of headers/footers/ headings)|
|Writing||Capitalisation and punctuation||Empty lines and exact vertical spacing on the page|
|Handwriting||Handwritten elements from header/headings||Handwritten fragments, sometimes not legible, from the body of the text|
|Textuality||Paragraphs and structural divisions|
|Semantics||Named entities (e.g. names of persons/ organisations/places/functions/events/ products, dates)|
The current version of the prototype supports functionalities such as side-by-side view of digital facsimile and transcription, page-by-page navigation, zoom-in/out, vertical scrolling, search (by names of persons/places/organisations, dates).
Although the direct adaptation of EVT was considered from the beginning, different requirements for EVT and Transviewer project have been identified.
|General architecture||Project-oriented (Vercelli Book manuscript)||Multi-project-oriented (documents/collections in European integration history)|
|XML-HTML transformation granularity||Page-oriented (one HTML file per page/manuscript image)||Document-oriented (one HTML file per XML document)|
|XML-HTML transformation process||HTML generation||XML transformation on the fly, in the browser, and XHTML generation|
|Transcription||Line-oriented||Structure-oriented (divisions, paragraphs) with semantic annotations (named entities).|
|Navigation||Page-by-page (supported by a single HTML file per page implementation)||Page-by-page and vertical scrolling (applied to a whole document)|
|Image management/loading||One by one||Images for a whole document|
Therefore, the EVT concept of side-by-side view of digital facsimile/transcription has been combined with the integration of third-party libraries (BookReader, Saxon-CE) and in-house development. The first one has been chosen for enabling on the fly loading of images, the second for supporting XSLT 2.0 transformations in the browser.
The in-house development mainly comprised modules for the implementation of a core/project specific architecture including elements of configuration, frames and buttons layout/actions, XSLT transformation and transcription rendering.
A simplified diagram of the decisions points in the first development cycle of the Transviewer is shown in Figure 4.
As illustrated, the prototyping process can imply multiple iterations. Once a functional prototype is built, the decisions on further development may reiterate similar phases of conceptualisation, search for solutions, implementation, evaluation and decision making. In this respect, our theoretical approach could be framed at the crossroad of “iterative prototyping” (Buxton and Sniderman, 1980; Buchenau and Suri, 2000; Lucena and Astua, 2012), “user-centered design” (Shneiderman and Plaisant, 2009; Warwick et al., 2009; Gibbs and Owens, 2012), and scholarly digital editions (Pierazzo, 2011; Rosselli Del Turco, 2011).
Although partial evaluation had been carried out throughout the prototyping cycle, a more formal testing and evaluation phase has been conducted on the first functional version of the Transviewer. Several facets of assessment have been taken into account:
|Facet||Short description||User group/stakeholders|
|Technology||Technical issues have been identified and worked upon (e.g. non-uniform support for Saxon-CE in different browsers and the use in BookReader of an older version of the jQuery library). Another evaluation aspect, related to argument 2, consisted of proving the scalability of the framework by testing it with different projects samples.||CVCE's development team|
|User||The prototype functionalities and argument 1 have been evaluated via usability tests (Nielsen, 2000; Lund, 2001) mainly enquiring on the ease of use, ease of learning, usefulness and user satisfaction (on a scale from 1 to 5), and on suggestions for potential improvement.||Internal/external researchers as end-users of the Transviewer|
|Impact||Beside the impact on the final product (e.g. how many/in what proportion the functionalities/features/arguments of the prototype are reflected in the final product), another point of interest concerns its impact on other products, in particular, the initial models having inspired it.||Cooperation partners, research infrastructures|
As an outcome of the analysis on the first prototype cycle, a new iteration and development reassessment is currently ongoing. The analysis helped us to: (1) identify and amend technical (see Table 3) and design issues (e.g. functionalities not quickly accessible or requiring extra-effort, unclear terminology or functionalities hierarchy, simplification); (2) adapt the encoding to support a larger variety of objects to be visualised (e.g. transcription only, facsimile only, transcription and audio/video); (3) better understand the needs of the users while dealing with historical documents (e.g. “trust” and “contextualisation” seem to play an important role).
Moreover, the development of new technical tools poses not only challenges to the process itself and the methods it introduces or refines but it also raises the question of sustainability: project based funding stimulates the development of new tools between different entities but far too often, this development stops once funding runs out. In the context of the informal and not project-funded cooperation between the CVCE and the EVT team, we therefore want to explore the trials and tribulations of building and maintaining a shared codebase that would be beneficial for both entities even though our specific use cases differ. As a result of the experiences made in this ongoing process of building the new version of the EVT framework, we will take the opportunity to discuss the practical challenges, opportunities and limitations of open-source development models for digital humanities projects as an approach to achieve sustainability.
In other words, we are not just testing an application but a development framework which implies considering complex theoretical-practical elements: Human-Computer Interaction (HCI) aspects, Information Technology (IT) methods and tools, specific types of documents to be published, projected audience, collaborative strategies and sustainability, etc.
The article proposes an analytical approach to the prototyping of a visualisation framework for historical documents. Its main assumption is that a critical perspective can be applied not only to a finished digital artefact but also to the process of its creation. In line with more traditional methods of criticism from the Humanities, a "thinking through making" viewpoint may bring into light theoretical and practical aspects related to the construction of digital tools and to the mechanisms of the "laboratory". A prospect that, by its nature, positions itself at the crossroad of the old and the new, of the past and the future.