Navigation:
Documentation
Archive



Page Tree:

This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.

Skip to end of metadata
Go to start of metadata

From the beginning, Project Bamboo planned to propose a second phase of technology development and integration to extend infrastructure built in the first phase of the Bamboo Technology Project (October 2010 through March 2013, including extensions) in support of humanist scholarship. Phase one effort emphasized fundamentals such as shared identity and access management (IAM) services, and aggregation of textual content from multiple, heterogeneous repositories. Application of digital tools to aggregated content was demonstrated, but was not organized into processes that constituted a complete, coherent scholarly workflow. Research Environments (a.k.a. "Work Spaces") were piloted as clients of the centrally-hosted infrastructure services, but were not tailored to the research needs of particular communities of scholarship.

From October 2010 through June 2011, the "Bamboo Corpora Space" design process conceptualized a set of applications that would be developed during phase two, which would allow scholars to work on dispersed digital corpora using a broad range of powerful research tools and services. These applications would facilitate the modeling and tracking of the artifacts and processes connected with digitally-facilitated research in the humanities, including both curatorial and analytical activities. The Corpora Space workshops sought input from a broad range of tool developers and disciplines, and identified common needs and issues. Martin Mueller's essay "Collaboratively Curating Early Modern English Texts" provides a narrative description of the curation process; based in part on this essay, developers discussed curation workflows, capabilities and integration patterns and from this an overview of Bamboo's proposed curation application emerged.

Later plans for phase two narrowed the scope of "Corpora Space" vision to focus on providing additional infrastructure and effect integrations with key tools used by the Classical philology community, rather than build full user-facing applications

Bamboo's expanded infrastructure would include:

  • Extension of the phase one "book model" used to package content from heterogeneous repositories. The extended model would encompass a wider range of textual objects of scholarship -- beyond books -- that can be exchanged between independent tools. It would also encapsulate a normalized model of annotations based on Open Annotation Collaboration (OAC) standards to store, manipulate, and expose assertions made by individuals (researchers, students, community-curators) on textual objects and other media (see Scholarly Data Management, next bullet-point). This model of scholarly annotation would be designed to support interdependent curatorial and analytical scholarly research.
  • Development of a model for Scholarly Data Management in which annotations and the provenance of persons and tools involved in their creation could be expressed and consumed. This model would enable documentation of scholarly workflows by recording metadata harvested when producing or procuring an object (content provenance); the tool(s) that was (were) used to create it; the objects that were inputs to the tool(s); tool settings, versions, and so on. This applies both to the production of curated manifestations of a text and to the generation of derivative objects, manually or with analytical tools.

This infrastructure would be integrated with a set of tools already used by Classics scholars, including the Perseus Son of Suda OnLine (SoSOL) and Alpheios Treebank Editor, with the goal of demonstrating the direct application of Project Bamboo models and infrastructure to Classical scholarship. The Classics use case for curation of digital materials was intended to shape this "reference implementation." The Classics Capabilities Map was developed on the basis of the Classics use case. It delineates work required to effect the reference implementation.

The integration of extant tools with Bamboo-built infrastructure would have supported:

  • identification of scholars (faculty and students) participating in use of phase two reference implementations in support of Classics scholarship;
  • authorization of scholars to view, propose, evaluate, accept, and/or publish annotations on primary and secondary sources;
  • citation of scholars (faculty and students) in provenance records of annotations they have proposed, evaluated, etc.
  • No labels