Page Tree:

Child pages
  • W4 Action Plan - 4.5 Content Interoperability Partnerships

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

Skip to end of metadata
Go to start of metadata

What should be the qualities of a project in this area?

The  success of the content interoperability model will be measured by the degree to which it reduces friction and lowers barriers to content access, transport (if needed), and readiness for scholarly use, analysis, synthesis, and sensemaking.  Specific qualities that Bamboo needs to promulgate here include:

  • Coherent end-user access experience, with openness to centralized, decentralized, and hybrid repository approaches on the backend
  • Full leveraging, and further coordination of instantiated repositories (note: there are questions about whether it is necessary or wise for Bamboo to build out discovery services)
  • Versatility of format concerns (text, images, audio, video)
  • Standardized data formats
  • Content/data that is available or packaged in the way that it is needed (e.g., viewing, extraction, computational access, etc.)
  • Access security through cross-institutional authentication model
  • Well-understood rights/permissions framework

What could be done in one year?

  • Assimilate content and interoperability requirements determined through Bamboo assessment and service definition efforts.
  • Synthesize published assessments and surveys of relevant content providers and forge mutually beneficial partnerships that will commit to interoperability development and testing
  • Explore Shibboleth as a technical solution to authentication across Bamboo content provider partners

What could be done in two years?

  • Produce multiple proof-of-concept builds for support of higher impact use cases (determined by assessment and requirements process), involving multiple data types
  • Produce Shib-based authentication method as proof-of-concept.  If successful, consider setting a requirement for institutions to join InCommon to be eligible for use of Bamboo API services
  • Model scaled-out interoperability architectures (e.g., grid model)
  • Set initial requirements for institutions to be open to the Bamboo "pipeline"

What may be the dependencies or necessary relationships?

  • Strong partnerships needed with existing repositories for content provision and search utilities for discovery services
  • Key inputs from scholarly narratives and other analyst activities that define interoperability requirements related to data access, acquisition, and use
  • No labels

1 Comment

  1. Unknown User (

    InCommon seems to be a framework which is restricted geographically to the USA. We would need to also seek relationships with initiatives and frameworks in other countries and regions, such as EduGain in Europe.