Page Tree:

Child pages
  • Defining Project Bamboo Success

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

Skip to end of metadata
Go to start of metadata

This page holds high level descriptors of what constitutes success for Phase 1 Bamboo. There are sections for the project overall and for each of the major work areas and, for Work Spaces, the individual deliverables. This material, as well as pages linked from it, will be presented and discussed during the January 2011 Partner Meeting.

To prepare for the Partner Meeting please review this page as well as the linked pages. This activity is essential to the success of our Partner meeting.

We have also created a PDF of the material which you can download here .

The early thoughts that were on this page are now deprecated to a child page, Defining Bamboo Success - Early Notes.


Thoughts on success criteria to include when defining success:

  • Definition of success provides value to the humanities community beyond what is already available, moving humanities and? digital humanities forward
  • Definition of success describes a realistic goal
  • Definition of success is in alignment with Project Bamboo's vision/mission
  • Definition of success is in alignment with the participating institution's goals for participating in the Bamboo effort

Comment about Overall Success: As we examine project scope and available resources once again, we will be forced to consider the tradeoffs between laying a solid foundation for the broader vision (difficult to restrain scope here) and enabling future development vs. getting some short term wins via focused proof-of-concept projects that demonstrate value to scholars and other stakeholders in tangible ways but may not be fully implemented (a kludge or inelegant solution).  We will look to Bamboo leadership for guidance on striking the right balance here. (NW 12.10.10)

Work Spaces

Work Spaces success is measured in four areas:

  1. software implementation to adapt the Alfresco ECM and HUBzero platforms as Bamboo Work Spaces, integration of Work Spaces into the Bamboo Ecosystem, and user engagement and piloting, and preparations for Phase 2 adoption projects?;
  2. development and deployment of the Tools and Services Registry (TSR), with extensibility for future use cases/requirements;
  3. porting of Oxford's VRE for the Study of Documents and Manuscripts to OpenSocial and experiments to determine the suitability of OpenSocial as a tools integration strategy both for scholarly tools and for services user interfaces;
  4. platform and TSR deployment and business models to support future Consortium planning.

A fuller description of success is available on the Work Spaces' Work Spaces High Level Objectives page and on the supported pages liked to from that page.

Collections Interoperability

The Collections Interoperability (CI) team’s focus is on the following areas of development during Bamboo Phase One.

  • Candidate Collections I: Identify and qualify a prioritized list of important humanities collections to use for the Collections Interoperability demonstrations (better term, implementations?) of Phase One. These collections should not only provide a thorough test of collections interoperability profiles, but they should be able to put to early, beneficial use by scholars using Bamboo Work Spaces deployments during 2011. The Candidate Collections should help drive interest and confidence of the larger humanities community to the benefits that Bamboo will deliver to the humanities profession. It would be ideal if several of the CI candidate collections coordinated well with the first work from the Corpora Space team.
  • Candidate Collections II:Successfully mine existing scholarly narratives, engage scholars, talk with collection creators of collections that are being used (e.g., cited frequently in published literature) to identity additional collections and prioritize collections with which Bamboo needs to interact.
  • Bamboo Collections Interoperability Standards Profile: Develop a successful and useful CI profile for object-level metadata, including HTTP-based identifiers, object type, and rights management obligations. Identify a successful and useful CI profile for supported descriptive and packaging schemas, such as MODS, OAI-ORE, METS, RDF and other useful standards.
  • Bamboo Collections Interoperability Standards Profile II: Develop and test a CI metadata profile for collection-level description and decide how/if collection level description information needs to be included in TSR, including links between collection-level description and collection-related service descriptions in the TSR. DECISION FROM 1/27/2011 MORNING: STANDARDS PROFILING FOR COLLECTIONS AND FOR OBJECTS WILL MERGE THEIR WORK INTO A SINGLE WORK GROUP
  • Content Interoperability and Management: Identify and deploy an effective Content Interoperability specification across Work Spaces, the Bamboo Services Platform, CI and CS. The most promising, forward-looking candidate for this standard is Content Management Interoperability Specifications (CMIS). Build efficient CMIS connector services to the top candidate collections being used in Bamboo Phase One.
  • CI-based operations supporting scholarly activities: Identify CI-related operations implicit in important scholarly use cases, in order to assure maximum benefit of Bamboo’s CI profiles and services. Identify critical gaps in existing collections interoperability standards and profiles.  [What will we do with these identified operations?  Will they inform tools and services delivery within WS, BSP, CS?]
  • Corpora / data set maintenance: Complete experiment / demonstration of an approach and one set of technologies that could be used to automatically refresh items brought into Bamboo and from which new derivatives have been made.

Corpora Space

  1. A clearly defined description of, and rationale for the building of at least two Corpora Space applications and a supporting architecture of widespread use to humanities scholars, with a carefully constructed road map for implementing it in the second 18-month phase of the Bamboo Technology Project 
  2. A design process that through well articulated workshops and agile development of prototypes produces that road map, with a concomitant recognition of constraints in terms of resources, access, and audience
  3. A design process whose roadmap includes a well considered plan for sustainability
  4. A design process that while emphasizing functionality for primary data in textual form is open to such media as sound, images, and video
  5. A design process and project governance mechanism that takes strategic advantage of the services and outcomes of the other BTP technology groups and services as well as the research agendas of the Bamboo Partners.
  6. A design process that genuinely involves other infrastructure initiatives outside of Bamboo (e.g. HathiTrust, EEBO, ARC?).
  7. A design process that develops an open architecture for Corpora Space capable of bridges to key online datasets of use to researchers
  8. A design process that produces an architecture enabling developers and content providers from outside of Bamboo to contribute tools and content
  9. A design process that will result in widespread international buy in and advice from key content providers, tool builders, and user groups

Links to more detailed discussion related to Corpora Space success

Scholarly Services on the Bamboo Services Platform

Success measures for the BTP Area of Work Scholarly Services on the Bamboo Services Platform are divided into three groups, corresponding to the three sub-areas of work described in the BTP Proposal to the Mellon Foundation of Summer 2010: Scholarly Services, Bamboo Services Platform, and Shared Services Lifecyle. A set of success measures addressing the integration role of this area of work is also included. The detailed pages to which the more... links refer also includes a brief Introduction / Overview that contextualizes these success measures.

  • Scholarly Services success will include:
    • version 1.0 release of access and/or transformation services that enable access to and/or processing of content from at least two collections independent of Project Bamboo. more...
    • version 1.0 release of one candidate set of Scholarly Services developed by each of at least two BTP Partners. more...
  • Success for the Bamboo Services Platform (including core and utility services) will include:
    • selection and successful deployment of platform infrastructure technology; more...
    • development and provision of core and utility services. more...
    • deployment of services contributed by two or more Partner teams. more...
  • Shared Services Lifecycle success will include:
    • publication of guidelines for development of services to be deployed on the Bamboo Services Platform (BSP). more...
    • deployment of QA and Production instances of the Bamboo Services Platform (BSP) serving requests from authenticated and public clients. more...
  • Integration success includes:
    • one or more Scholarly Service hosted on the BSP integrated by Bamboo Work Spaces built on the HUBzero and Alfresco platforms;
    • one or more Core or Utility services hosted on the BSP integrated by Bamboo Work Spaces built on the HUBzero and Alfresco platforms ;
    • one or more Core or Utility services hosted on the BSP integrated by the Bamboo Tool and Service Registry;
    • guidelines drawn from lessons learned by multiple institutions developing Scholarly Services during BTP Phase One included in Shared Services Lifecycle processes and criteria;
    • guidelines applicable to software development and technology adoption across multiple ecosystem platforms (beyond BSP) included in Shared Services Lifecycle processes and criteria.


[Note:  red italicized comments above from JDM review prior to Berkeley workshop, added 2/21/11]

This right-side column is an artifact of "old-style" navigation. Please remove sections, columns, and content of the right-side column when this page is next edited. Cf. the Wiki navigation changes - July 2011 page for a 'how-to' on removing old-style page markup.