This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.
PAIR is a sequence aligner, which means it does an automated scan of a digital text and executes a comparison against other texts, with an emphasis on finding common substrings within or between the texts. This kind of analytical routine is useful for tracking citations and quotations among different texts, detecting plagiarism, and discovering named entities or idioms. The algorithms used are similar to genomic sequencing. PAIR is part of Philologic, an environment for interacting with documents which are part of ARTFL, a collection of text databases. The PAIR demonstrator will help us in further analyzing some of the ideas discussed in the original planning proposal. In particular, what happens when you create a shared service as part of an existing digital humanities project? What do central IT staff need to learn about working on digital humanities projects, and vice versa? Can the service be made sufficiently agnostic to be useful to a variety of scholars, in a variety of disciplines?
NYX uses formatting stylesheets prepared using the XSLT language to format XML-encoded documents, particularly TEI documents, into human-readable and useful HTML documents. TEI encoding presents a particular challenge for a generic service because the standard is very flexible. This demonstrator is, potentially, an example of a truly generic service, and will be available as a standalone service as well as part of a standalone web applications and as part of the SEASR tool platform. Is a service at this scope too generic to be useful? Too specific to be implemented by non-Humanities specialists? Or is it "just right" for collaboration between IT/Humanities/Library? What might this tell us about assessing future services for their suitability to a Bamboo services community? Can services of this type make manifest the benefits of a shared services approach? What sort of API might a shared service offer in order to be useful?