Scheduled DB Maintenance: January 21st - 8:00 AM to 10:00 AM. Confluence will be unavailable during this time.

Navigation:
Documentation
Archive



Page Tree:

Child pages
  • Major Areas of Work v0.2

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 Phase 1 (24 months) of a Bamboo Implementation Proposal.

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 implementation phase. The intent of this document is to solicit community input toward the ongoing development and revision of the implementation proposal. As this is an early draft, it is not yet a commitment to carry out all or any of this work.

Please note that we are updating this document frequently based on wide ranging input from the Bamboo community. These updates will occur periodically and will be indicated as ".1", ".2", ".3", etc updates. In addition, we will occasionally make major document revisions. These are noted as "1.X", "2.X", and so forth. Between major document revisions there may be some inconsistencies in language used between the sections of the document.

4 - Major Areas of Work

Table of Contents:

In the current draft, this document section is a high-level summary of the major areas of work the Bamboo Project is considering carrying out over the first two years of implementation (2010-2011). This summary was derived from the Bamboo Community's discussion of and voting on the 7-10 year Program Document at Bamboo Workshop 4 (April 16-18), and further discussion with the Bamboo Leadership Council. In this document the eleven areas of work presented in the 7-10 year Bamboo Program Document have been combined and narrowed down into three areas work for the first two years of implementation. The table at the end of this introduction explains the the relationship of Program Document to this first draft of the Implementation plan.

Three major areas of activity are described for the initial implementation phase of Bamboo. In combination, and at levels of investment to be determined in conversation with institutions navigating toward participation in the implementation phase, these areas aim to realize the Bamboo vision articulated in the Program Document of a "Forum" across disciplines and communities concerned with the humanities and digital humanities; as well as that of building the "Cloud" - a shared and sustainable infrastructure for digital scholarship across institutions and organizations in higher education. Each of these areas of work contain a number of "Bamboo Labs" - that is, teams made up of multiple institutions engaged in exploring, planning, building, and sustaining core components of Bamboo. An additional area of work over the next two years are activities and environments that sustain the "Bamboo Community" as a whole, described in the Community and Governance section of the proposal, which follows this one.

It is important to note that this draft includes early examples of work plans for several major areas and is far from definitive. Program Staff will use this evolving document as a framework for several rounds of discussions with institutions participating in Bamboo, and as a core of the Bamboo Implementation Proposal.

Mapping Areas of Work: Program Document Discussion Draft to Bamboo Implementation Proposal

Program Document Discussion Draft 1.0

 

Bamboo Implementation v0.2

3.1 Scholarly Network

maps to

4.1 - Scholarly Networking

4.2 Bamboo Exchange

maps to

4.1 - Scholarly Networking

3.2 Scholarly Narratives

maps to

4.2 - Bamboo Atlas

3.3 Recipes (Workflow)

maps to

4.2 - Bamboo Atlas

3.4 Tools & Content Guide

maps to

4.2 - Bamboo Atlas

3.5 Education & Curricular Materials

maps to

4.2 - Bamboo Atlas

4.1 Services Atlas

maps to

4.2 - Bamboo Atlas

4.4 Tool and Application Alignment Partnerships (TAAP)

maps to

4.3 - Bamboo Services Platform

4.5 Content Interoperability Partnerships (CIP)

maps to

4.3 - Bamboo Services Platform

4.3 Shared Services Lifecycle

maps to

4.3 - Bamboo Services Platform

3.6 Bamboo Community Environment(s)

maps to

5 - Community and Governance

4.1 - Scholarly Networking

"Scholarly Networking" in the Bamboo Implementation Proposal blends elements from the "Scholarly Network" and "Bamboo Exchange" sections of the Program Document (cf. full mapping table for more complete information).

4.1.1 Summary

The Scholarly Networking area of work enables people to discover resources, build relationships, and connect with others across the Bamboo community and beyond. Within this area a number of labs will focus on developing individual Bamboo "Gadgets" to provide specific scholarship-centric networking and/or resource exchange functionality. "Gadgets" refers here to software that exposes a single service or an aggregate of several services within the virtual research environments and/or social networks in which researchers, scholars, and/or students collaborate, learn or conduct research.

The first year of work will focus on discovering, exposing, and/or creating relationships among individuals and/or projects. These relationships will interface with and contribute toward the efforts around the development and deployment of the Bamboo Atlas (see the next major area of work, below).

4.1.2 Activities

  • Explore: The Explore activity will identify opportunities, share concepts, and articulate community value for candidate gadgets.
  • Plan: In the initial year, Plan activity will involve selecting a subset of candidate gadgets that minimizes duplication of existing work, leverages existing and/or forthcoming Bamboo services, realizes intended community value, and be deliverable in a first release within three to six months of development. Plan will then establish a Bamboo Lab for each gadget that includes specifications, gadget interoperability criteria, and human interface requirements. For each lab, appropriate liaison activity with other organizations will be both promoted and encouraged.
  • Build: The Build activity will involve developing the initial round of Bamboo Gadgets as selected by Plan. These Bamboo Gadgets will plug into a subset of virtual research environments, social networking platforms, and/or portals using established specifications and standards such as OpenSocial, Facebook Connect, and/or JSR-168. Initially, these gadgets will be instantiated outside of the Bamboo Services Platform (BSP) until such time as the BSP is capable of hosting gadget services. In all cases, Bamboo gadgets will be targeted for deployment in a cloud-based environment on the Bamboo Services Platform (see next area of work, below).

4.1.3 Reasoning

Throughout the Bamboo planning process many individuals and institutional teams expressed interest in using technology to track what others are doing and to connect with other scholars, technologists, and librarians within and across disciplines. Bamboo proposes to add value not by building its own scholarly networking environment, but rather by (1) finding ways to interconnect existing social networking tools and higher-education collaborative environments, (2) helping disciplinary societies and institutions to develop key data models required for exposing information about scholarly interests and activities in the humanities (e.g., biographical / CV information), (3) bringing together disciplinary societies in the humanities with key higher education technology initiatives, and (4) leveraging open standards and rapidly developing technologies in the social networking field.

4.1.4 Work Plan

  1. Invest in CV-lite gadget
    1. Develop specifications for an initial set of gadgets to ingest and express some common subset of CV data, preferably using widely-adopted standard(s)
    2. Implement minimum of two interfaces (based on OpenSocial, Facebook Connect, or JSR-168)
  2. Invest in Research Interest gadget
    1. Develop specifications for an initial set of gadgets to ingest and express research interest data, balancing rigidity of controlled vocabulary with user-adaptable synonymy capability
    2. Implement minimum of two interfaces (based on OpenSocial, Facebook Connect, or JSR-168)
  3. Another gadget [TBD]
    1. Develop specifications for an initial set of gadgets [functionality to be decided]
    2. Implement minimum of two interfaces (based on OpenSocial, Facebook Connect, or JSR-168)


4.2 - Bamboo Atlas

The "Bamboo Atlas" blends together elements from the "Scholarly Narratives", "Recipes (Workflow)", "Tool and Content Guide", "Education and Curricular Materials", "Bamboo Community Environment(s)", and "Services Atlas" sections of the Program Document (cf. full mapping table for more complete information).

4.2.1 Summary

The Bamboo Atlas will provide avenues for scholars in the arts, humanities, and interpretive social sciences to express their practice, participate in its analysis from methodological and technological perspectives, and locate community-vetted services, tools, and digital content repositories applicable to areas and practices of pedagogical and research interest. In addition, the Atlas provides a means for information scientists, librarians, museum specialists, infrastructure designers, software developers, and others developing services in the digital humanities to participate in collaborative analysis, identify cross-disciplinary activities, explore commonalites, and provide information about the evolution of services and cyberinfrastructure from disciplines inside and outside the humanities. As a dynamic and hyperlinked repository of information, relationships, and contributed metadata, the Bamboo Atlas will connect the ebb and flow of teaching and research with the constant change of technology and shifting ideas about how practices, resources, and services can and should be linked together. Dialogue generated through exploration and preserved by the Bamboo Atlas will connect scholars with technologists, researchers with content providers, students with instructors and practitioners, and domain specialists with engineers.

The API and user interfaces through which the Atlas is accessed will enable deep relationships among scholarly practices in the humanities and shared services to be discovered, mined, and exposed in relation to context, discipline, and/or technology. Ingest and expression of an array of input from scholars and technologists will be enabled, including artifacts such as scholarly narratives, recipes, activities, tool and content references, and service contracts, as well as the relationships between these artifacts, usage information, and tagging/filtering functionality that facilitates discovery.

The Bamboo Atlas:

  1. continues, preserves, and surfaces dialogue around the evolution of scholarly practice in conjunction with or as impacted by technology;
  2. distills practice into "recipes" that reveal workflows, opportunities for adopting or exposing shared services, and interoperable content repositories;
  3. shares digital methods and techniques of scholarship with researchers, scholars, students, librarians, technologists, and others, to enhance or build new research programs and/or curricula; and
  4. provides domain, field, project, service, practice, and technical data essential to discovery and exploration activity that will integrate Bamboo shared services in scholarship across institutional and disciplinary boundaries.

Narrative, recipe, and activity data are primarily based on narrative contributions by faculty, students, and other members within and outside of the Bamboo Community, and analyses derived therefrom. In order for this contribution model to succeed, appropriate incentive mechanisms that fit existing and accepted practice (such as a reviewed journal) must be established; merely submitting practices or analyses to a registry or database is not enough. Scholarly narrative submission can be one form of publication, distillation of the narrative into a recipe can be a form of review, and affirmation of a recipe and/or practice can be potentially recorded through a scholar's direct interaction with a recipe itself. All of these connections populate the Bamboo Atlas, enriching the description of shared services and increasing the Atlas's utility to the community.

With the appropriate design at both the technical (e.g., data models, API, gadgets) and socio-cultural levels (e.g., incentives, connections to existing and new journals, partnerships with disciplinary societies), the Bamboo Atlas is a living and growing body of data across disciplines and communities. This data can then serve as a fundamental source of manipulable information from which various views and interfaces can be designed for different communities of practice, disciplines, and/or institutions. The Atlas might, to name only a few examples, be a source of data and views from which to explore and present emerging trends in the pedagogy of the digital humanities; new curricular practices in language education; or cross-disciplinary methodologies and services. The Atlas is expected to serve a foundation from which distributed projects across Bamboo and the humanities develop particular interfaces, views, and gadgets.

The first year of Bamboo Atlas activity will focus in two primary areas:

  • Establishing and initiating the narrative-gathering and recipe-distillation processes, and developing a core set of pedagogical materials that advance a shared services model for arts and humanities research and learning.
  • Establishing a data model for narrative, recipe, and related information elements, and a set of services to support ingest, recording of relationships between elements, recording of metadata (e.g., tagging), and exposure of data via a well-defined, easily "mashed" API.

4.2.2 Activities

  • Explore: The Explore activity will establish one or more labs to collect and distill narratives into recipes. This activity will not stand alone as a separate data gathering process, but rather will be integrated with the work of a reviewed journal or other similar scholarly communication mechanisms. Explore will create and share pedagogical materials, programs, etc. which both share and demonstrate practices and methodologies that take advantage of shared services, content, and other service-based resources hosted by providers or provisioned through a cloud. Explore will refine the incentive and curation models for the Bamboo Atlas; the connection of Atlas data to tool and academic portfolio applications; and participate in defining and refining interfaces to the Atlas.
  • Plan: The Plan activity will select and establish standards for narratives, recipes, and activities, and incorporate those standards, including interoperability requirements, into the Bamboo Atlas. If a Bamboo-specific system for storing and sharing scholarly narratives, recipes, and activities is required, then Plan will develop specifications for such a system. Plan will determine the detailed data models, metadata standards, and semantic functions of the Atlas; the interoperability mechanisms and APIs between the Atlas and tool / content partners; and how the Atlas will be deployed on successive generations of the Bamboo Services Platform. These initial Plan activities will be undertaken with attention to the anticipated integration of a services registry as a critical mass of services are available for registration.
  • Build: The Build activity will create and maintain a narrative and recipe collection, storage, and sharing system (if required); as well as build, test, and refine the core services of the Atlas through fast prototype to long-term delivery stages in the Bamboo Shared Services Lifecycle.

4.2.3 Reasoning

The investment in an Atlas by Bamboo is meant to generate several major areas of value for humanities scholars and content and technology partners. First, it is means to reach out to the broadest range of humanities scholars (students and faculty) who may not be deeply immersed in digital technologies, by offering an easily accessible avenue to see what scholars across the humanities are doing (narratives) and how they are doing it (recipes, activities, tool and content references). Second, the Atlas becomes a living library to help track and chart the developing course of digital scholarship in the humanities. Third, the Atlas serves as a fundamental source of unified data from which information scientists, academic technologists, and content stewards can carry out activity and workflow analysis, community design and modeling, and service implementation. Fourth, recipes and narratives serve as a body of data from which particular disciplines and faculty can build more specialized curricula and publications focused on deep investments in pedagogy and interdisciplinarity.

The Bamboo Atlas records and delivers community input (Scholarly Narratives, Recipes, Activities, Tool examples, Content/Resource examples, Service Candidates, Service Contracts, and extant Services - including community-contributed references to information outside the formal bounds of Bamboo) in easily updated, linked, 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. The dynamic capability to incorporate and view evolving input and analysis, and quickly and clearly draw connections to broader context thus enabled will benefit faculty, students, librarians, funders, institutional leaders, technical architects, and service developers. These varied views of a changing landscape will enable informed governance by key stakeholders in the arts, humanities, and interpretive social sciences.

4.2.4 Work Plan

  1. Develop contribution and analytical models
    1. Define and develop narratives as a form of Scholarly Communication
    2. Define and develop recipes as Scholarly Analysis
      1. Content (ingredients)
      2. Activity definitions (steps)
      3. Tools (utensils)
    3. Narratives/Recipes/Activities populate the Atlas
    4. Narratives/Recipes/Activities tie to research, pedagogy, and curriculum
  2. Develop data models and technology services to support contribution, analysis, and discovery of Atlas elements, relationship, and metadata
    1. Develop data model and API for Narratives/Recipes/Activities and metadata (e.g., tags)
    2. Identify or sketch a service registry model with APIs, for future integration in the Bamboo Atlas
    3. Develop repository for Atlas data
    4. Develop specifications for an initial set of Atlas gadgets (views into the Atlas)
      1. Universal gadget: minimum of two interfaces (based on OpenSocial, Facebook Connect, or JSR-168)
      2. specialized-perspective gadget 1: widget interface (based on OpenSocial or JSR-168)
      3. specialized-perspective gadget 2: widget interface (based on OpenSocial or JSR-168)

4.3 - Bamboo Services Platform

The "Bamboo Services Platform" blends together elements from the "Shared Services Lifecycle", "Tool and Application Alignment Partnerships", and "Content Interoperability Partnerships" sections of the Program Document (cf. full mapping table for more complete information).

4.3.1 Summary

Major investment in this area will deliver the technical infrastructure that permits humanities projects to transition from project-specific applications to longer-lived, more broadly supported, more efficiently operated, and more widely useful services, setting the stage for a future in which many scholars, content stewards, and technologists can easily discover, combine, re-mix, and share content and technology to create new forms of digital research and teaching. A "Bamboo Services Platform" (BSP) will include platform technology elements (e.g., service container; message mediation, transformation, and routing; service orchestration) on which services for scholarship will rely, and from which such services will be made available for consumption.

The BSP shall be developed as a standardized (and in all likelihood, virtual) server. Hosting strategies will cluster around the "cloud" and appliance paradigms; alternatives to be explored here may include institutional deployments, commercial vendor deployments, and/or consortial hosting, with close attention to evolving commercial models and widely adopted university strategies (e.g., those developed and articulated by participants in the Common Solutions Group). Finally, work in the BSP will actively draw from, and contribute to, other cyberinfrastructure, e-research, and shared infrastructure initiatives internationally and from disciplines outside of the humanities.

While the term 'service' may be used to describe a broad or general operational capability (e.g., a social bookmarking service, an interlibrary loan service, an e-mail service, an academic computing support service, or other forms of technical expertise), the term is used in a narrower sense here. Services, in the sense intended here, are relatively small units of software that deliver a set of capabilities grouped to most flexibly facilitate (a) interoperability with other software and/or digital content; and/or (b) combination and recombination with other services in support of multiple tasks or workflows.

The earliest services built or adopted for deployment on this platform in years 1 and 2 of Bamboo will comprise two major categories:

  • Services that instantiate components of Scholarly Networking and the Bamboo Atlas (Scholarly Narratives, Recipes, and the Services Atlas).
  • Services that directly address scholarship, factored out of extant humanities projects focused on tools (functionality) and content (objects of scholarly interest).

A key "bootstrapping" activity in realizing sharable services for scholarship in arts, humanities, and interpretive social sciences will rely on partnerships with existing projects, tool, and content providers. Identifying sharable components built into these existing resources, factoring them into functionality deliverable as scalable, reliable, and always-available shared services, and deploying those services on the BSP will drive adoption of a shared services model as 'contributing' partners evolve their offerings to rely on 'contributed' services deployed and maintained in a Bamboo environment. These partnerships will draw from established disciplinary and interdisciplinary digital humanities and related projects, including collaborative environments (Virtual Research Environment initiatives, etc.), content providers and repository technologists interested in solving interoperability issues, and tool & application builders whose direction converges with Bamboo's shared services trajectory. Partnerships will invest in:

  1. selecting and promoting interoperability standards
  2. identifying and implementing sharable services
  3. refactoring existing projects to rely on services deployed on the Bamboo Service Platform

Service development and refactoring efforts will focus on implementation-agnostic interfaces, and on enabling service uptake across initial (disciplinary or other) boundaries of the contributing projects.

4.3.2 Activities

  • Explore: The Explore activity will establish labs to explore and define which existing virtual research environments, content tools and digital corpora, and/or digital humanities initiatives are interested in and and capable of a interoperability and refactoring partnership with Bamboo, as well as identify a number of scholars whose use of these tools / content partnerships will be captured in narratives and recipes. The Explore activity will work closely with Plan to identify how standards-selection and architectural choices intersect with substantive elements of scholarship.
  • Plan: The Plan activity will define common standards and processes for interoperability; select initiatives or projects from which an initial set of sharable services can be externalized in a short timeframe; identify an architecture and technology elements of the Bamboo Services Platform; and work closely with other University and cyberinfrastructure initiatives to learn from and help to define the best trajectories for "cloud" or "above the campus" service provision (with respect to financial, legal, and policy issues in additional to technical considerations).
  • Build: The Build activity will implement the Bamboo Services Platform, instantiate it in one or more "appliance" forms, and deploy early ("incubator") services on the BSP.

4.3.3 Reasoning

By partnering closely with key content, tool, and cyberinfrastructure projects, and by using a strategy that stresses interoperability and deriving services from existing applications, Bamboo can accomplish several things key to its core approach and philosophy.

  • help to bring together sharable aspects of important tool / content projects in a common technical framework;
  • add value to and, in some cases, help to transition to and sustain existing projects at the next level of technical evolution;
  • identify key technical functions built into certain projects and develop these as web services that can be supported in a shared, cloud-based infrastructure;
  • build long lasting partnerships based on trust and short cycles of demonstrated, incremental success; and,
  • help to create an ecosystem of projects that can work together, and whose value and interrelationships can be portrayed, via the Bamboo Atlas, in a manner accessible to many scholars in the humanities.

The core of Bamboo's approach to sharable services centers around services and a "cloud" model of delivery. Conceiving a Bamboo Services Platform "in the cloud" introduces more than simply an approach to sharing services, gadgets, or resources; it expresses an infrastructure direction that minimizes risk to any one institution, is inherently redundant, has the potential to be of low cost to maintain, and introduces the potential for broad adoption across institutions, organizations and geographical boundaries in a sustainable and reliable manner.

4.3.4 Work Plan

  1. Identify an initial set of common standards and practices for service development, deployment, and interoperability, balancing inclusion and consultation with key international and sciences-centric cyberinfrastructure initiatives against concrete deliverable schedules
  2. Identify and refactor services from selected, existing projects for inclusion (deployment) on the Bamboo Services Platform, focusing on loose-coupling and other best practices in service design
  3. Model a Shared Services Lifecyle, made up of three phases:
    • Local and Incubator Services - early phases of discovery, adoption, or development of services of interest to the Bamboo Community
    • Common Services - a phase of service refinement that addresses concerns like sustainability, standards-compliance, and reliability
    • Ubiquitous Deployment - services deployed and reliably available via a Bamboo Service Platform deployment realized in a "cloud" model
  4. Deploy sharable services on a Bamboo Services Platform.

As a preliminary phase of work, Bamboo proposes to carry out a "proof of concept" (PoC) in the latter phase of the Bamboo Planning Project (that is, to be accomplished before the Implementation Phase begins). The goal will be to scope the following steps with sufficient narrowness to enable delivery by the end of 2009, yet conceptually prove the complete set of deliverables proposed in this area for the Bamboo Implementation Phase. Activity steps in this set include:

  1. Define the core architecture and elements of the first generation Bamboo Services Platform and its relationship to other key infrastructure initiatives
  2. Define first and second year hosting and funding strategies for the Bamboo Services Platform
  3. Define a light weight version of the Shared Services Lifecycle to be used across multiple aspects of Bamboo effort in years 1 and 2.
  4. Build and test a PoC implementation of the Bamboo Services Platform
  5. Model and build a lightweight (incomplete) set of services supporting the Bamboo Atlas in a PoC implementation
  6. Deploy the PoC services described above on the PoC Bamboo Services Platform
  7. Identify candidate partners and a preliminary set of scholarly and interoperability services to be built/adapted and deployed on the Bamboo Services Platform in years 1 and 2
  • No labels

5 Comments

  1. Unknown User (masover@berkeley.edu)

    Bamboo "Tele-forums" on Atlas & Services Platform

    The Bamboo Program Staff is eager for the community's feedback and suggestions in any & all forms: comments to this wiki page, e-mail to any or all of the Berkeley and/or Chicago teams, ongoing conversations Chad & David are scheduling with institutional teams, blog posts, tweets, etc.

    My own next phase of activity on the Bamboo Implementation Proposal will orbit around initial, provisional identification of appropriate, valuable, and achievable deliverables during the 24-month period of the implementation proposal (2010-2011).

    With that focus in mind, I'm seeking participants in phone conversations on each of two of the currently-proposed Major Areas of Work:

    • Bamboo Atlas; and,
    • Bamboo Services Platform

    My initial idea is to schedule two conversations for early next week (we're on a tight timeline...), one on each of these topics, but we'll see who expresses what interests and availability, and also how time-zone differences figure in.

    Please write to me directly - masover@berkeley.edu - if you're interested in participating in such a call (or calls) early next week - Tuesday or Wednesday, 12-13 May [my hope is we'll settle on times between 6am and 9pm PDT (UTC -7 hours)]. I'll be checking e-mail periodically through the weekend.

    - Steve

    1. Unknown User (masover@berkeley.edu)

      Tele-forums for Atlas & Services Platform: Tu 12 May

      The calls described above have been scheduled based on feedback from those who wrote to me over the past three days. Both "tele-forum" calls, one hour each, will take place Tuesday 5/12:

      • Atlas: 11 am - noon PDT (UTC -7 hours) [1-2pm CDT, 2-3 pm EDT]
      • Services Platform: 1-2 pm PDT (UTC -7 hours) [3-4 pm CDT, 4-5 pm EDT]

      It's not too late to participate! Please write to me directly (masover@berkeley.edu) for call-in information. For each of the two calls, the preliminary agenda will be:

      Agenda


      • Intros / late start / call context [DELIVERABLES, but not details] (5 min)
      • Questions/general comments (10 min)
      • Round-robin: each participant's ideas re: deliverables (20 min)
      • Free-for-all (until 5 min before end of hour)
      • Close

      The assumption is that everyone on the call will have read the wiki page to which this comment thread is attached...

      Steve

  2. Unknown User (jim.muehlenberg@doit.wisc.edu)

    Here are a few comments or questions on this excellent first discussion draft.

    Section 4 Mapping Table:  Based on the definition of Program Document section 3.6 Bamboo Community Environment(s), it seems this might have been mapped to 4.2 Bamboo Atlas and perhaps also to 4.1 Scholarly Networking.  It seems surprising to map it to 5 Community and Governance?

    Section 4.1 Scholarly Networking:  In the statement "The first year of work will focus on ... relationships among individuals and/or projects. These relationships will interface with and contribute toward the efforts around the development and deployment of the Bamboo Atlas ..." - how does the work plan in this section relate to the Atlas work plan?  It seems the Atlas work plan includes its own gadgets that provide views into the Atlas.

    Also, who is coordinating the next stage of work planning for this section?  I'd like to connect some Wisconsin people to that effort, if possible.

    Section 4.2 Bamboo Atlas:  Is it clear enough that if we build it, the content will come?  Will the suggested incentives actually bring in rich and varied narratives and recipes?  Maybe as a second path forward, is there any practical way to "harvest" any such content from previous studies and surveys of scholarly practice?  (And this reminds me, is there still going to be a report on "Scholarly Practices and in the Arts and Humanities" as outlined in the Mellon proposal?)

    A second general question here is where do Education & Curricular Materials fit with the Atlas?  None of the specifics seem to include this mapped section from the Program Document.

    Section 4.2.2 Activities:  Could we define what "academic portfolio applications" are (under Explore)?

    In the statement "If a Bamboo-specific system for storing and sharing scholarly narratives, recipes, and activities is required, then Plan will develop specifications for such a system." it seems that tool and content references should be included here.  Also, it seems that we would need to develop specifications (or at least requirements) even if we look to adapt an existing system for Bamboo's repository needs. 

    Section 4.2.4 Work Plan:  It seems we could have a "preliminary phase of work" here, as in section 4.3.4, that would be aimed at enriching the current collection of narratives, recipes, activities, and tool & content references in the current planning wiki setting, while getting enough of a feel for their ultimate data and metadata needs to make some concrete progress on Atlas content data modeling and ideas about APIs/services during 2009.  This would in fact contribute to the 4.3.4 preliminary work aimed at modeling a set of services supporting the Atlas.  I'll save the details of this proposal for our next phone call.

    Also, for the initial set of Atlas gadgets (views into the Atlas), would we not go so far as to implement them in the first two years?  And what about any views for people who don't normally "live" within something like Facebook?  Would there be a generic gadget that stands alone in a web browser?

    Section 4.3 Bamboo Services Platform:  In the description of "bootstrapping" where it refers to driving adoption of shared services as partners evolve their offerings to rely on these services, what is the motivation for those partners to rework their offerings once such services are established?  Can we articulate some incentives here?

    Section 4.3.4 Work Plan, preliminary step 5:  It seem that Atlas content data models and some work on ideas for APIs/services by the Atlas team must feed into this work (an argument for having a preliminary phase of work for the Atlas effort as well).

    1. Unknown User (masover@berkeley.edu)

      Jim,

      I won't try to give a comprehensive set of responses, but I will acknowledge that your thoughts on a preliminary phase of work involving the Atlas is indeed on (my conception of) the table for the latter part of 2009, despite the fact that it is referenced only in Sec 4.3 ... the preliminary effort, as I conceive it, ought to be a shallow pass through both these areas, to make both conceptual and technical progress without committing ourselves more deeply than is appropriate before funders and participating institutions work out nuts and bolts of investment choices and governance/decision-making processes. Evolution of this idea for Jul-Dec '09 work will necessarily take place in parallel with evolution of the implementation proposal itself, which is (necessarily, in view of time and resource constraints) the first priority in the coming month or so.

      In general, more definition - in many of the directions you identify - should begin to emerge in subsequent drafts of the implementation proposal. Our phone conversations next week may not get us there: those conversations will focus, at what will still seem to some a fairly high level, on the broad character of what might be deliverable in the first and second years of our implementation phase ... rather than on the detailed nature of those deliverables.

      In the Bamboo Atlas work plan the numbered list (1 and 2) is not meant to imply activity in Year 1 and Year 2. There is no question that exposure/expression of the information in the Atlas - in a number of ways, almost certainly (as I conceive it) including a UI browseable outside a social/scholarly networking context - is in scope for Year 1. If we can't show the Atlas content, we certainly can't demonstrate its value ... and that would be a rather serious problem, I think!

      With regard to educational/curricular correspondence to the Bamboo Atlas, the references to pedagogically oriented data and activity are meant as a placeholder for further elaboration as we get deeper into the proposal.

      With reference to the 3.6 (PD) mapping, this is the same issue that Chad responded to vis-a-vis your comments on the Program Document Discussion Draft. We had some incompletely aligned ideas among the Program Staff in the final phases of pre-W4 editing about what that section ought to articulate, and are getting onto the same page going forward. Naturally, as nothing gets past your eagle-eyed attention, the transition (to borrow a phrase from John Unsworth) is a bit on the seamy (as in not-seamless) side ... the mapping referred to at this stage is an environment in which the Bamboo Community will do its virtual work and communication (what we'll evolve toward beyond the current web site and wiki). The UI-for-various-Bamboo-aspects, which formed the main orientation of 3.6 in the PD draft discussed in Providence, will be part of the Major Areas of Work as it evolves in Sec 4 of the implementation proposal.

      Steve

      1. Unknown User (jim.muehlenberg@doit.wisc.edu)

        Steve - thanks for the quick feedback here (midnight again! yikes!).  On the very last part, around 3.6 (PD) mapping, what puzzled me is mapping it to a section that seemed to be focused on human organizational topics and not on technical work, despite 3.6 seeming to be about technical work.  Hence the question about whether the mapping should be into a "Major Areas of Work" section rather than to 5. Community and Governance.  thanks again, Jim