Page Tree:

Child pages
  • Tele-forums of 12 May - Report Out

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

Skip to end of metadata
Go to start of metadata

These are report-out notes from two calls held on Tuesday 8 May 2009.

Participants were invited via a general invitation extended via a wiki comment to v0.2 of the Major Areas of Work section of the Bamboo Implementation Proposal, and e-mail to contacts from each institution that had (by 8 May) expressed interest in areas of work discussed at Workshop Four.

The discussion in these calls was focused around the v0.2 draft of the Major Areas of Work, which was not altered in v0.3 of the Bamboo Implementation Proposal (BIP); because these notes are being published directly following publication of BIP v0.3, they are added to the wiki as a child of the more current version of the draft implementation proposal.

Comments are always welcome, whether to this page or to the parent page (Major Areas of Work v0.3).

Tele-forums report-out: Atlas and Service Platform

Two "tele-forum" phone calls were held on Tu 5/12 to discuss the Bamboo Atlas and the Bamboo Service Platform areas of work. The two calls combined were attended by participants from five institutions. Here are the major points raised in each call:

Bamboo Atlas

  • Attention to participation incentive (e.g., Atlas contributions as artifacts suitable for publication in journals focused on digitally-enabled methods of humanities scholarship) is critical to success.
  • Making pedagogical narratives an explicit part of the Atlas is a positive development.
  • Working forward from work done to date by Working Groups (esp. Narratives, TCP, Shared Services), and continuing that work in some way and to some degree, will best equip Bamboo to model and populate the Bamboo Atlas. Multi-person teams of narrative gatherers & analyzers has been suggested in the working groups; could this be a funded/supported effort?
  • A suggestion that the July-December 2009 period be used to create an Atlas Proof-of-Concept (PoC) in the context of continued pre-W4 efforts was well-received.
    • Models and function developed for the PoC ought to be incomplete and informal (otherwise it's too far a reach); a more formal and complete effort is properly part of Bamboo Implementation.
    • Even a PoC ought not be a technologists-only affair: humanist participation/critique is necessary if it is to prove anything more than aspects of the technical implementation problem.
  • Some suggested values and characteristics of the atlas:
    • adds information to the discovery and exploration part of the work of service creation for scholarship
    • provides a forum/mechanism for critique of plans as they are being formulated
    • provides a forum/mechanism for response to preliminary prototypes as things are built
    • matches people and their work with tools/content/services that might help them
    • provides/enables "rich discovery tool" ... like faceted search in the library-world
    • allows users to find categorized and tagged content - tags and categories must be user-contributed and curated - multiple categorizations must be user/group-creatable and user/group-curatable
    • provides metasearch that sits on top of DiRT and other tool-cataloging sites/services, with deduplication & merging of results
    • encourages arts and humanities scholars to describe their methodologies more rigorously and regularly
  • Suggested model for a system of incentives built into a community resource such as the Atlas:
  • Is it reasonable to think about working groups for the W5 to EOY period, to accomplish work such as the PoC (assuming that goes forward)?

Bamboo Service Platform

  • Selection of partnership projects will shape the BSP significantly (i.e., Tool and Application Alignment & Content Interoperability partnerships).
  • Institutional interest in Bamboo is strongly tied to a wish to align ongoing and emerging work/projects to a BSP.
  • BSP should enable service delivery to support the Bamboo Atlas, as well as Scholarly Networking (and, implicitly in the current organization, some Bamboo Exchange functionality).
    • In both these cases, though not the focus of this discussion, participants acknowledged that Bamboo is well-advised to learn from what's out there already.
    • Participants advise starting with an examination of data types in the Atlas, and build BSP around support for operations on those types (as well as other data types to be initially supported).
  • General models/interfaces/services for content interoperability, such as the JCR effort, ought to be part of the supported services early on.
    • BSP should enable content from diverse sources to be used by a personal profile of tools that any given scholar is interested in
    • IP is a hard problem in content interoperability. Bamboo must address IP, at least to the extent of describing IP constraints in a way that is less cumbersome for scholars to manage.
    • A group of tele-forum participants will work on developing some expression of how content interoperability services / technologies ought to be included in the BSP, targeted for publication to the community in late May
  • No labels