Navigation:
Documentation
Archive



Page Tree:

Child pages
  • v.0.1 - Bamboo as a Facilitator and Developer

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

Skip to end of metadata
Go to start of metadata

WORK IN PROGRESS

This is an outline for a possible 7-10 year vision for the Bamboo Community. The purpose of this document is to provide information to institutions and organizations participating in the Bamboo Planning Process so that they can help determine (1) the long term future of Bamboo and (2) define what activities Bamboo will carry out in its first, 3 year Implementation Phase (from 2010-2012).  This document is designed to solicit community input, and is a draft in progress. It is not yet a commitment to carry out all or any of this work.

4. Bamboo as a Facilitator and Developer of Shared Technology Services (Cyberinfrastructure Ring II)


Note: by "services" in this section we refer to the technical and more narrow definition of a "web service."

4.1.  Services Atlas

The Services Atlas presents community input (Scholarly Narratives, Recipes, Activities, Tool examples, Content/Resource examples, Service Families, Service Candidates, Service Contracts, and extant Services) in easily updated, hyperlinked, annotatable forms that may be mixed, matched, categorized, and re-categorized in order to render the community's understanding of scholarly practice accessible from the multiple perspectives of diverse stakeholders native to Bamboo. Dynamic ability to incorporate and view evolving input and analysis, and quickly and clearly draw connections to broader context, will benefit faculty, librarians, funders, institutional leaders, technical architects, and service developers. These varied views of a changing landscape will enable informed governance by key stakeholders in arts, humanities, and qualitative social sciences scholarship.  Included in the Atlas is core "service registry" functionality.

4.2.  Marketplace of Services

The Bamboo Marketplace of Services will serve as a focal point for information about services, including but not limited to services incorporated in the Service Atlas; and as a venue for exchange between marketplace participants. Incentives to participate in this marketplace will include channels of communication to and feedback from the community of institutions and disciplines participating in Bamboo, as well as an avenue for access to Bamboo's experimental "incubator" service-deployment platform (cf. Local and Incubator Services, below).

4.3.  Local and Incubator Services

Working services that are not yet refined and offered as "common" may be provided from local or regional deployments by Bamboo institutions, and listed with appropriate descriptors of service quality (SLA, Service Level Agreement) in the Bamboo Marketplace. A deploying institution or group of institutions would be wholly responsible for availability and maintenance of such services; Bamboo as a consortium would make no guarantee regarding these limited or experimental deployments. Services deployed in Local and Incubator Deployment contexts are considered to be potential candidates for refinement, standardization, and adoption as "Common Services."  Services deployed in these contexts may originate in the work of Bamboo member-institutions, or in the broader universe of service builders; it is the latter case that comprises Bamboo Incubator Service deployments, which will generally be segregated into a separate and parallel deployment context from services that originate in the development efforts of Bamboo members.

4.4.  Common Services

Services of foundational or broad utility may become candidates for refinement into "Common Services."  Service interfaces that have been refined through a process of architectural modeling, design, alignment to applicable standards, and coordination to maximize interoperability, then developed as reference implementations, will be considered "Common Services." As such, they can and will be deployed for use by the global community of scholars by Bamboo member institutions in a redundant, distributed network of Bamboo Appliances that comprise a Bamboo Cloud. These services will include those that enable core digital infrastructure of the Bamboo Community (the Services Atlas and its component entities; and the Bamboo Marketplace, including its elements). Additional services will deliver direct support to scholarship by automating workflows (recipes) that add value to the arts, humanities, and qualitative social sciences. Some classes of service will provide resources delivered directly from servers operated by Bamboo member institutions; while others will wrap (call) or refer to compute, storage, and/or service-delivery resources operated by others. Service Level Agreements for services offered from the Bamboo Cloud, as well as those for underlying services hosted elsewhere, will be clearly articulated to service consumers.

4.5.  Architectural Alignment Partnerships

Bamboo will partner with interested tool and application projects and developers to wrap and/or deliver functionality (automation capabilities) as services that can be deployed alongside, and interoperate with, Bamboo Common Services. By exposing capabilities from other projects and providers as Bamboo-affiliated services, broader and more diverse uptake of those capabilities is more likely; such exposure will also enrich the pool of service candidates being considered for refinement into Bamboo Common Services. These partnerships will deepen and broaden the Bamboo ecosystem with expertise and experience rooted in domain- and function-centric communities.

4.6.  Content-Services for Interoperability

Bamboo will partner with interested content (digital resource) providers to enable Bamboo Common Services to discover, search, and appropriately operate on their diverse and distributed holdings. Similarly, partnerships with interested repository platform providers will enable Bamboo Common Services to discover, search, and appropriately operate on resources hosted on platforms of strategic value to communities of arts, humanities, and qualitative social science scholarship. These efforts will likely take the form of modeling, implementing, and deploying service interfaces to expose strategically identified content stores and platforms. Bamboo-facilitated exposure of content via service interfaces will broaden uptake and trans-disciplinary opportunities for scholarship, as well as suggest additional candidates for refinement into Bamboo Common Services.

1 Comment

  1. Unknown User (pearce.judith@gmail.com)

    Re the note at the top: by "services" in this section we refer to the technical and more narrow definition of a "web service."

    Technical services may not necessarily be web services. For example, not all authentication and authorisation services are web-based. Email is not a web service but sending and receiving messages are important scholarly activities. Many scholars still use word processing software and might benefit from a workflow that, for example, allowed a verified citation from a library catalogue to be imported into a bibliography maintained in MS Word. 

    I recommend removing the word 'web' and taking time to explain in an introductory paragraph exactly what is meant by shared technology services and their relevance to the automation of scholarly practice. For instance, one could explain that the term 'service' is used in a broad sense to describe a general operational capability (a social bookmarking service, an interlibrary loan service) but that it is used in the section that follows in a technical sense, as a resource characterised by the functionality (performance of tasks) it provides. (These definitions are both from the e-Framework glossary.)