This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.
Each main section (an H2 in the current draft, and included in the ToC below) will be given a section on this 'front page' of final documentation (pages in this hierarchy will be moved or copied to the target space on the UC Berkeley wiki – in the page hierarchy titled Documentation – after they are assembled; the UC Berkeley wiki will be the long-term host of archived Project Bamboo wiki materials).
The short overviews, drafted and to be further edited to provide context as plainly as possible in language understandable by the target audience and others will be included in this 'front page.' The enumerated outline included in this draft of the front page will NOT likely be included (to keep the documentation clean) but will become the sections or top-level links of the page(s) that correspond to each section of documentation that corresponds to the ToC at the top of this page. The enumerated-outlines on this page are provided as a conceptual map to the hierarchy of documentation wiki pages.
Current "assignments" of responsibility for these elements of [in square brackets] are current as of 19 February, are based on consultations including Steve Masover, Quinn Dombrowski, Noah Wittman, Tim Cole, Bill Parod, and Bruce Barton. In some cases they describe lead responsibility and only imply consultation with other team members.
View access to some pages linked from this one are currently restricted, but can be assumed to be accessible to the parties responsible for the corresponding section of documentation.
[QAD and SJM to handle this section]
An overview of Project Bamboo's eighteen-month planning phase (April 2008 - September 2010) and two-year technology implementation phase (October 2010 - September 2012). The planning phase brought together over 650 participants from 114 institutions and organizations, to address the question “How can we advance arts and humanities research through the development of shared technology services?” In the technology implementation phase, ten institutions were involved in technical development work around cataloging digital tools, interoperability of digital collections, proxied access to remotely hosted tools for scholarship, identity and access management, research environments, and curation of digital materials.
Bamboo DiRT is a directory of digital research tools, particularly targeting those tools relevant for humanities scholars. Developed by Project Bamboo in response to strong interest expressed by scholars, librarians and IT staff during the Bamboo Planning Phase (April 2008-September 2010), Bamboo DiRT expands on the longstanding DiRT (Digital Research Tools) wiki, providing an interface that facilitates task-oriented browsing and searching (e.g. “I need a research tool to manage bibliographic information”). Tools range from content management systems to music OCR, statistical analysis packages to mindmapping software.
Scholars who work with digital content from multiple repositories identified the heterogeneous formats used by those repositories as a barrier to efficient research workflows. This drove Bamboo’s efforts to develop a model for ‘normalizing’ the presentation of content from diverse repositories-- without sacrificing the formats and detailed metadata specific to any given repository-- in order to facilitate scholars’ use of digital tools for collecting, analyzing, and manipulating that content.
(cf. WIP wiki page Collection Interoperability - Documentation Summary 2013)
Using a common RESTful service interface with a shared Identity and Access Management framework for a variety of distinct tools, computation resources, and storage services simplifies the process of integrating those functionalities into new applications and virtual research environments. Bamboo developed such a service interface, and implemented it for a small number of tools for textual analysis.
Bamboo's Identity and Access Management infrastructure outsources authentication (login) to institutional Identity Providers (IdPs) (e.g., campus authentication systems based on Shibboleth), and/or to social media Identity Providers (such as Google). A Social/SAML gateway normalizes the data returned to applications and platforms by social media IdPs. Authorization (permission) to access services or resources is effected via definition, decision, and enforcement of policies that allow or deny service and resource access based on factors that include institutional affiliation; membership in groups managed independently of individual applications; resource ownership; and/or the identity of a client application from which a user issued her/his request.
Bamboo's centrally-hosted services include an IAM (Identity and Access Management) suite, Collection Interoperability Hub, and proxy services to remotely-hosted tools for scholarship. This set of services runs on FUSE ESB, an enterprise distribution of Apache's open-source ServiceMix (acquired in 2012 by RedHat). A number of additional, open-source technologies are required to support these services, including Apache Web Server (httpd), and Grouper.
Team members conducted usability studies, extended, and integrated open-source platforms built to manage and/or manipulate digital content. These platforms included HUBzero, Alfresco ECM, Drupal, and the OpenSocial framework. Integration with centrally-hosted BSP services was pursued atop the HUBzero and Drupal platforms; integration with an institutional archive (the California Digital Library's Merritt Repository) was pursued atop Alfresco ECM; and the OpenSocial framework was explored in conjunction with SURFnet. These efforts resulted in production of significant bodies of reusable code, such as a CMIS interface atop Fedora, and implementation of the ACL (permissions) aspect of the CMIS specification atop Apache Chemistry. In addition, usability studies at UC Berkeley led to production deployment of Alfresco ECM as an institutionally-supported production service, dubbed Research Hub. The term "Work Spaces" was used within the Bamboo Technology Project to name this broad area of software development and integration.
A faculty-led thread of work during the phase of the Bamboo Technology Project funded by the Andrew W. Mellon Foundation was charged with setting direction for future development atop the successful products of the initial phase of work. The proposed direction, which was not ultimately funded, focused on support for collaborative curation of digital materials using shared identity and access management (IAM) services, and aggregation of textual content from multiple, heterogeneous repositories. During planning work for this activity, it was referred to as "CorporaSpace". The documentation in this section gives a conceptual overview of how the project team intended to move forward had funding been granted.
[QAD to handle this section]
Final and funded proposals to the Andrew W. Mellon Foundation for the Bamboo Planning Project and Bamboo Technology Project are included here for reference. These were publicly-released scope-setting documents during the respective projects whose work they proposed.
[QAD to handle this section]
Links to related sites and material outside this wiki-hosted set of documentation are included for reference and convenience.
[QAD to handle this section]