Page Tree:

Child pages
  • Bamboo Documentation FAQ

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

Skip to end of metadata
Go to start of metadata

Major deliverables of the Bamboo Technology Project

What ever happened to the Bamboo Commons or the Bamboo Atlas?

See the wiki page Cataloging Digital Tools for Humanities Scholarship - Bamboo DiRT.

What progress was made in improving access to digital content from multiple, heterogeneous repositories?

See the wiki page Interoperability of Digital Collections.

Work Spaces – general support for managing digital content – were a key element of Bamboo's roadmap. Where can I learn more about that?

See the page Research Environments to Store Manipulate and Manage Digital Content.

Work under the heading "Corpora Space" was meant to set direction for the second phase of the Bamboo Technology Project. Where can I learn more about the results of that effort?

See the page Curation of Digital Materials - planning for future development and the child-pages linked from that one.

Curation was a core aspect of Bamboo's roadmap. Where can I learn more about that?

See the page Curation of Digital Materials - planning for future development and the child-pages linked from that one.

Authentication, Authorization, Shibboleth, and Identity & Access Management (IAM) were a core focus of the Bamboo Technology Project. Where can I learn more?

See Identity and Access Management - Authentication and Authorization, and pages linked from that one.


Picking up where Project Bamboo left off

I want to develop services for deployment on the Bamboo Services Platform. How do I get started?

Functional context is given in the overview pages Proxied Access to Remotely Hosted Tools for Scholarship and Identity and Access Management - Authentication and Authorization.

A comprehensive architectural overview can be found on the page Architectural Overview of the Bamboo Services Platform.

Service APIs of extant services can be found in the pages linked from Service APIs - Centrally-Hosted Bamboo Services.

Instructions for setting up a development environment can be found at Developer Workbench Environment for BSP Service Developers.

Where can I learn more about Bamboo's CMIS interface for the Fedora Commons repository?

See the page Bamboo Book Model - CMIS Binding and Fedora Repository Implementation.


Bamboo materials not found in this documentation

Where is the code produced by Project Bamboo?

See the wiki page Links to Project Bamboo on-line artifacts.

Links to specific elements of the code base are included at contextually-relevant locations throughout the documentation.

Is there a project Issue Tracker?

See the wiki page Links to Project Bamboo on-line artifacts.

Where is the project wiki archived?

See the wiki page Links to Project Bamboo on-line artifacts.

Where can I find Project Bamboo in social media space?

See the wiki page Links to Project Bamboo on-line artifacts.


Credits and contacts

Which organizations and institutions of higher education participated in Project Bamboo?

The first phase of the Bamboo Technology Project included teams from the University of California, Berkeley; the Australian National University; Indiana University; Northwestern University; Tufts University; University of Chicago; The University of Illinois at Urbana-Champaign; University of Maryland; University of Oxford; and University of Wisconsin, Madison.

The Bamboo Planning Project included participants from over one hundred institutions and organizations. Most of these are listed below, with apologies for inadvertent omissions:

  1. Albert-Ludwigs-Universität Freiburg
  2. American Academy of Religion
  3. American Numismatic Society
  4. American School of Classical Studies at Athens
  5. Andrew W. Mellon Foundation
  6. Arizona State University
  7. Arts and Humanities Research Council (UK)
  8. ARTstor
  9. Australian National University
  10. Blackboard
  11. British Library
  12. Brown University
  13. Carleton College
  14. Case Western Reserve University
  15. Chicago State University
  16. City University of New York
  17. Coalition for Networked Information
  18. Columbia University
  19. Cornell University
  20. Council on Library & Information Resources
  21. Dartmouth College
  22. Deutsche Forschungsgemeinschaft (DFG)
  23. Digital Library Federation
  24. Documents Compass
  25. Dominican University
  26. Eastern Kentucky University
  27. Eastern Michigan University
  28. Fabula
  29. Federation of American Scientists
  30. Fedora Commons
  31. Fine Arts Museum of San Francisco
  32. George Mason University
  33. George Washington University
  34. Getty Research Institute
  35. Harvard University
  36. Humanities Serving Irish Society
  37. Indiana University
  38. Institute of Museum and Library Services
  39. Intelligent Television
  40. Johns Hopkins University
  41. Joint Information Systems Committee
  42. JSTOR
  43. Lake Forest College
  44. Long Now Foundation
  45. Loyola Marymount University
  46. Massachusetts Institute of Technology
  47. Miami University of Ohio
  48. Michigan State University
  49. Microsoft Corporation
  50. Middlebury College
  51. National Endowment for the Humanities
  52. National Institute for Technology in Liberal Education (NITLE)
  53. New York Public Library
  54. New York University
  55. Northwestern University
  56. Open University
  57. Pennsylvania State University
  58. Princeton University
  59. Purdue University
  60. San Jose State University
  61. Smith College
  62. SEASR
  63. Stanford University
  64. Sun Microsystems
  65. Technische Universität Darmstadt
  66. The Open University
  67. Tufts University
  68. UC Press
  69. UCOP, California Digital Library
  70. United Board
  71. Université François Rabelais, Tours
  72. Université Paris 4 Sorbonne
  73. Université Paris X Nanterre
  74. University at Buffalo, State University of New York
  75. University of Alberta
  76. University of Arizona
  77. University of California, Berkeley
  78. University of California, Humanities Research Institute
  79. University of California, Los Angeles
  80. University of California, San Diego
  81. University of California, Santa Cruz
  82. University of Cambridge
  83. University of Chicago
  84. University of Colorado, Boulder
  85. University of Edinburgh
  86. University of Göttingen
  87. University of Illinois, Urbana-Champaign
  88. University of Iowa
  89. University of Kansas
  90. University of Louisiana at Lafayette
  91. University of Maryland
  92. University of Melbourne
  93. University of Michigan
  94. University of Minnesota
  95. University of North Carolina, Chapel Hill
  96. University of Oxford
  97. University of Pennsylvania
  98. University of Puget Sound
  99. University of Rome
  100. University of Southern California
  101. University of Tennessee
  102. University of Toronto
  103. University of Virginia
  104. University of Washington
  105. University of Wisconsin - Madison
  106. Villanova University
  107. VoxPopulis PT
  108. Washington & Lee University
  109. Willamette University
  110. William Paterson University of New Jersey

Who are the authors of Project Bamboo documentation?

Much of the documentation is culled from materials created by many authors over the life of Project Bamboo (April 2008 through Spring 2013). A number of principal authors and editors of the final documentation are credited here:

Fernando Alvarez (UC Berkeley)Principal BSP designer/developer. Author of BSP architectural overview and the bulk of service APIs.
Bruce Barton (UW Madison)Co-lead of Work Spaces team, focus on HUBzero and Drupal. Author of documentation on Fedora implementation and CMIS binding; user-experience of Collections Interoperability Hub, et al.
Quinn Dombrowski (UC Berkeley)Lead, Bamboo DiRT. Author of Cataloging Digital Tools for Humanities Scholarship - Bamboo DiRT, et al., editor throughout.
Harriet Green (U. Illinois - Urbana-ChampagneAuthor, Humanist Scholars' Use of Digital Materials.
Keith Hazelton (UW Madison)Co-architect, IAM infrastructure. Co-author and/or reviewer/editor of IAM documentation throughout.
Steve Masover (UC Berkeley)Project technical lead. Author and editor of overviews, installation and configuration, and other documentation to do with the Bamboo Services Platform; editor throughout.
Martin Mueller (Northwestern)Faculty (emeritus), co-lead in framing curation use cases driving proposed Bamboo Technology Project work in a proposed second phase of development. Author, Collaboratively Curating Early Modern English Texts.
Bill Parod (Northwestern)Architect, designer and implementer of the Collections Interoperability Hub (CI Hub). Author of Collection Interoperability Hub (CI Hub) architecture and implementation.
Noah Wittman (UC Berkeley)Co-lead of Work Spaces team, focus on Alfresco ECM. Author of documentation on Alfresco ECM Pilot and User Research, Research Hub atop Alfresco ECM at UC Berkeley, Managing digital content preservation via integration with an institutional archive, and Tool integration atop the OpenSocial API.



How can I get in touch with Project Bamboo now?

The archived artifacts of Project Bamboo, including this documentation, are maintained by a small group who were members of the project during its active period. This group is also involved in continued work on aspects of the overall project, and can provide introductions to others who are similarly involved. Please feel free to contact us at




  • No labels