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


Page Tree:

Child pages
  • W4 Action Plan - 3.3 Recipes (Workflows)

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

Skip to end of metadata
Go to start of metadata

What should be the qualities of a project in this area?

  • We need to interact with many of the other groups, like narratives, services, etc.
  • A narrative could have multiple recipes. We see two different types of narratives: those that just describe a problem and those that may describe a problem and a process to a solution.
  • Recipes need to be able to relate to the different audiences (scholars and technical). So recipes would education both sides; scholars would learn new tools; IT people would learn how tools are applied.
  • We need to define what a successful recipe would be: One, success would be to take a narrative, create a recipe for it, then find other narratives that could use some of these recipes. Two, would be showing the reusability of recipes/tools outside of their original context.
  • We need to select some low hanging fruit to demonstrate in year 1.

What could be done in one-two year?

  • We need a selection process for choosing the narratives. For instance, we could select narratives that were using a specific set of tools that we have identified that we want to use (such as zotero, seasr, monk, tapor, etc).
  • We need to identify narratives and their recipes. These recipes need to be generalized and services need to be data driven, so that they can be applicable in other situations.
  • We may need to solicit narrative that use desired tools.
  • We need to use a visualization tool (like IBM's Many Eyes) to display patterns in the narratives and recipes. For example:
  • We need to develop the recipes for the selected narratives.
  • We need feedback loops for the scholars about the recipes and we need comments to discuss problems and features, etc.

What could be done after two years?

  • We need to identify gaps in the recipes.
  • We will need to document the scholarly success of using the recipes. Scholarly publications may mean this is after 2 years.

What may be the dependencies or necessary relationships?

  • We need narratives to move forward.
  • Recipes will direct services that need developed.
  • We need exchange in 3-5 years for connecting scholars and developers for the gaps and future narratives.

Notes scribbled down during the discussion

3.3 Recipes
Neil Fraistat, Tim Cole, Katie Hayne, Debjani Ganguly, Howard Morphy, James Chandler, Robert Gibbs, Steve Bennett, Loretta Auvil

Work with existing narratives.
Describe an example recipe
Map of languages in austrailia; maybe 5 recipes for this; map to google maps
Process analysis - need to know the audience; confuses the audience with our description of recipes; so who are the recipes being written for;
version to emphasize the technologies; version available to the scholar; show it in action
as our prototype choose a low hanging fruit; tools;
develop narrative and recipes
all scholars may not want to perform all the steps
we have a project, let to this... we also have this... can we change the first to use the 2nd data set
need data driven
promote some scholarly narratives the first year...
discussion of diff narratives: some describe a problem; some that describe what was done to solve a problem;
some narratives are in search for a recipe; some have a recipe;
generalizable set of narratives that has developed some software (happy conclusion)
get recipes that are applicable to more...
what is the action plan of what we can do in a year or 2?
what selection process do we want to use for narratives...
Action : identify a selection process for the narratives (might need to use specifically identified tools)
each recipe uses some of these tools
recipe might need to change for authentication across univ
will fit into the exchange
identify a method
choose topic and choose narratives that use these
genres of narratives
short term and long term
data stores; jstor; australia
show reusability of tools outside of their original context
survey narratives
success would be developed recipes for a collection of narratives to make second order narratives;
new scholar can save time by using results of another scholars narrative
another order of generalability - kinds of analysis that could be done...
identifying gaps - tools may be built much later, but the identification can be done...
education from both sides; scholars learn new tools; IT people learn how tools are used
documentation on areas of problems...
recursion model; used in these recipes,
many eyes - comment/ feedback

  • No labels

1 Comment

  1. Unknown User (

    May want to look at "My Experiment". Uses the 'workflow' word but may contain some inspiration: