Page Tree:

Child pages
  • Instructions for Recipes

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

Skip to end of metadata
Go to start of metadata

The key to recipes is that they are written for the users - the academics. They explain to a user how they can get things done using the technologies deployed and they connect academics to the


  • Recipes should be written with scholars in mind.
    • The title should be something they recognize as a task they would want to do in the language they would describe it.
    • The introduction should describe the task and it should end by linking to one or more Narratives from which it was drawn. That way potential users can see a concrete example.
    • The ingredients should be described so that even if they don't recognize the Tool Type they can recognize the function. Thus you should begin with a linkable functional title like "Collaborative document technology" followed by a recognizable example like "Wiki" followed by an example (Twiki). Where possible link to Tool Types that already exist even if the ingredient is a subset of the linked to Tool Type.
  • Recipes should be general so they can be used by many, not just the person whose story they are based on.
    • The Recipes draw on the specific stories written by scholars, but they should, where possible, gather similar needs under a recognizable task.
  • Recipes can contain Recipes.
    • Some Recipes will be for large complicated tasks that include smaller tasks that others would want to do by itself.
  • Recipes can follow other Recipes as Preparation and lead to yet other Recipes as Next Steps.
  • Recipes involve steps that are typically Activities with a tool.
    • However, Recipes can also include activities not assisted by computer and therefore not described further in Bamboo. The reason for this is that Recipes address academic needs that are almost never solved exclusively by technology.

How to write a Recipe

  1. Read through the How the recipes work page to make sure you understand the role of Recipes.
  2. Read through the Scholarly Narratives.
    1. Look for common tasks that scholars describe.
    2. Look at the Narratives edited and prioritized by the Scholarly Narratives group.
    • If you want to describe a recipe for which there is no Narrative you should consider writing a narrative first. Try to give the context some concreteness. Ask colleagues to help describe what they want to do.
  3. Look at the existing Recipes to see if the task you have found exists already.
    1. Can you adapt an existing Recipe?
  4. Ask if it really is a Recipe or an Activity
    The difference between Recipes and Activities is one of scale. A Recipe should always have as its end a real academic task while an Activity might be step in a task that is not meaningful academically in itself. Thus an Activity might be creating a list of researchers which would be part of the Recipe creating a research group.
  5. Make a copy of our template to structure your Recipe.
    1. Try to follow the template. Obviously some parts may not be needed, but be sure you understand the parts.

What Bamboo can do with Recipes

  • Recipes can communicate to the scholars and others who use technology. They communicate what you can use Bamboo to do and how to use Bamboo.
  • Recipes assist in the negotiation of support and service.
  • Recipes can be used to prioritize what tasks will be supported. Ultimately Bamboo needs to imagine what tasks could be supported and then choose those they can support. Recipes are a user and task-focused way of doing that.
  • Recipes can be used to audit whether support is adequate to real academic tasks. The support of some tools needed, but not others is a "recipe" for not helping anyone.
  • Recipes can be used to audit what activities need to be supported and what tool types are needed to help scholars do academic work.
  • No labels