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

Skip to end of metadata
Go to start of metadata

Group 1

  • Guiding principle: BROAD IMPACT
  • Accessibility
    • Accessible to many people and institutions
    • Avoid siloing projects
    • Finding way to show value to everyone
    • Ability to get a journal publication
    • Availability to move forward
    • Access to services
    • Access to decision-making process
  • Design
  • Iterative
  • Visualization
    • Make it possible for people who aren't technical to see what Bamboo is and does from the beginning.
  • Articulate Model for project
  • Legibility
    • A way into the site, a sense of what it is and does
  • Access points
    • When you go to the website, you want to know what it is and what to do
  • Dynamism
  • Feedback process
    • Testing, feedback, redesign
    • Connects back to iterative design
  • Communication
    • Esp. communication btwn. Working groups as project moves forward

Group 2

  • 4 principles
  • PB needs in teh first year to establish a core of tools, etc as a demonstration
  • Hum scholars need to be integrated into development
  • In short range: work w/ people already involved in something digital; long range - get many more humanists involved
  • "Bamboo Charter" - document that needs to address needs and points of view explicitly of different audiences - "unusual suspects", general suspects, chairs/deans/admins/CIO,

Group 3

  • Priories in terms of top of list
  • Very specific: what we need to do is select tools and services to begin
  • Set of recommendations: uses Mellon list (Chris Mackie has a chart), beginning there
  • Take this list, a set of criteria for evaluation, to see what makes sense for us to do (and early on)
  • Suggested some of the criteria we might want to use: 1) Extent to which tools/services are data-driven because that makes them more ready to use; 2) Germane-ness to humanities (if Mellon is funding, should be), 3) Zotero's much more extensive in range of applications; extensibility is important
  • Think about criteria as a way to think about our values as PB
  • Adjusting the list according to what we value - add and subtract as necessary
  • Further down road: thinking about how to incentivize development of the list by having institutions who have develop tools/services that aren't part of Mellon set to join us, build with us in the future

Group 4

  • Principles - began by thinking about what should guide PB
  • Imperative on us to move quickly for two years only
  • Get something - exemplars, prototypes, etc in first year
  • Then , populate/add to it, etc. during 2nd/3rd years
  • Use extensible, build it up
  • Problem: criteria for membership for PB?
  • Institutions have signed up because we want to benefit from other people and exchange what we have

Group 5

  • Urge community to not think of this as a proof of concept - need a long-term vision and build out the real thing
  • Need to jump in and build the real thing instead of a prototype
  • Leverage the exiting body of work (not just not reinventing teh wheel, but showing what relationship is between what PB wants to do and what others are doing/have done
  • No better way to actually have it clear that we ant to be a partner, than to be a partner
  • Short timeframe - could shift emphasis on building to a small group of people (heads down, get it done)
  • But can't lose overall community design/development/outreach, including notion of professional development/outreach that we articulated early on
  • Make sure we create opportunities for contribution for non-build institutions
  • Learn from mistakes and successes (our own, others')
  • More visible connections to what's gone before

Group 6

  • Need to see sensible and useful things coming out of it
  • Iterative processes, rapid testing; working towards the real thing
  • Collaboration is key
  • Communication

Group 7

  • Opened up with "focus focus focus, concrete concrete concrete"
  • Tangible
  • Ended up with a possible definition of what PB is: there are a lot of projects that go through R&D phase, but this is like getting to market - 10x cost of R&D
  • Organization that helps rally institutional resources to deliver, necessary to provide value in some way
  • Making it more affordable, by spreading cost across institutions
  • Number of ways to organize this at the moment
  • I regret I still don't know what PB is.

Virtual comments from Tom Knab (Case Western)

  • I'd like to say that it is important in year1/2 to think about strategic connection of PB with certain their consortia, initiatives and appropriate Societies – as a way to quickly add value, without duplication of effort – and to address the question "why do we need another consortium now and I thought that "X" already did this , or could do this", in a time of very tight resources and focusing of resources for all.
  • No labels