Navigation:
Documentation
Archive



Page Tree:

Child pages
  • Media Ecology Demonstrator Project Plan

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

Skip to end of metadata
Go to start of metadata

DRAFT

This demonstrator, initiated by Professor Mark Williams from Dartmouth, is affiliated with both the Tools & Content WG and the Education WG. The Media Ecology demonstrator seeks to explore how the community of experts gathered by the Bamboo effort might respond to a project which invokes a wide range of recurrent challenges in Arts & Humanities research. These challenges include intellectual property, citation, annotation, and longevity. Professor Williams described the challenge here. My sense is that in the limited time we have, we can approach the problem broadly or deeply but not both, and that this restriction applies to both the collections of content the site can interact with and the features offered. The initial direction we've chosen is to limit the number of content collections, and to be as broad as possible in assembling a range of tools and abilities for interacting with that content.

Narrative/Use Case:

Susan Wright is a student in Mark Williams' course, "This Just In: Understanding the 1950s Through News Broadcasts". For her mid-term paper, she chooses to focus on news reports which describe political unrest in South America in 1954. As part of the process of collecting materials for her paper, she visits the Media Ecology site and does some searches based on crowdsourced tags as well as official metadata. After she has collected a range of sources, she uses the tools available on the Media Ecology site to review each broadcast, marking the beginning and ending of interesting sections, and creating a clip of that subsection of video. She watches these clips repeatedly, using Media Ecology tools to add additional annotations at relevant points throughout the clip. She uses this collection of annotated materials as she develops the thesis of her paper, referring to them frequently. The final version of her paper includes links to her annotated clips, as well as to the original broadcasts.

Phase 1: Due Jan 31 -- "The Naive Beginning"

1) Survey the existing landscape and collect resources, advice, feedback, etc. [~khc@uchicago.edu:ONGOING]

We will want to make notes & share all information we collect. 

  • Professional/academic societies (Mark) -- in progress, will be ongoing
  • Broadcasters, archives (Mark) -- in progress, will be ongoing
  • Bamboo Community [~khc@uchicago.edu:DISCUSSION NEEDED] 
  • Existing work elsewhere -- models, tools, examples (Team)

2) A home -- we need a location for the process and products of our work.

We chose drupal as a platform to help us get started, in part because it was a platform we were familiar with, and in part because we knew it had a variety of features, plug-ins, etc. which we identified as desirable.

  1. Install a server (Done, 1/5/09)
  2. Distribute admin accounts to the work team (Michael)
  3. Establish a basic template for adding content into the site (Quinn)
  4. Configure built-in features to match project needs (Quinn)
  5. Add existing plug-ins to site (Quinn) 

Phase 2: Due Feb 7 -- "Sorting, Prioritizing"

 1) Sort through everything we've collected from the community

  • Who and what can help us? Collaborators, partners, existing tools?
  • What do we get for free from drupal? 
  • What already exists in a form that can be integrated with drupal?
  • What will need to be written from scratch?
  • What standards will help us, and can we comply with them using these tools?
  • What hurdles have emerged?

2) Establish a task list

Phase 3: Due March 15 -- "Build, Test, Build, Test"

Drupal 6, Quinn Dombroski

  • Allow any user with permissions (can include anonymous users) to add tags
    (Community Tags)
  • Create hierarchies of user-input tags, and automatically add parent terms
    (Taxonomy Multi)
  • Create custom vocabularies for individual groups in addition to site-wide
    vocabularies (OG Vocab)
  • Merge synonyms to avoid skewed results due to lexical choice (Synonym
    Collapsing)
  • Link to related material (Similar by Terms)
  • Faceted search to help users refine their queries and navigate through the material
    (Faceted search)
  • Display a hierarchical index of each vocabulary (Vocabulary Index)
  • Provide RSS feeds for individual terms
  • Display customized tag clouds on any page (Tagadelic)


     
     
  • No labels

4 Comments

  1. Unknown User (khc@uchicago.edu)

    Notes from 1/7 phone call -- Mark's suggestions

    How to collect?

    • presentation at W3
    • invite people to wiki
    • handout at W3
    • circulate e-mail 
    • What about all the un-networked people?

    If WGBH is an initial source, what about a Boston area -- Emerson? MIT?

    People w/journalism schools -- Northwestern? Penn State?

  2. Unknown User (khc@uchicago.edu)

    More Notes from 1/7 phone call:

    Anthony's review of usefulness of PBCore -- essentially an XML data dictionary. How can we make use of & tie in to this effort? Will boost interoperability in the future.

    Quinn: we can import XML taxonomies, so let's try that.

     Anthony: boosts usefulness for research -- can export a standards-compliant set of materials

  3. Unknown User (khc@uchicago.edu)

    Immediate Action Items from 1/7:

    - move to public IP

    - move to Drupal 6

    - set up logins for Mark & Anthony

    - re-survey web/video annotation tools (viddler? flash video variables?)

  4. Unknown User (markj)

    Drupal 6
    • Allow any user with permissions (can include anonymous users) to add tags
    (Community Tags)
    • Create hierarchies of user-input tags, and automatically add parent terms
    (Taxonomy Multi)
    • Create custom vocabularies for individual groups in addition to site-wide
    vocabularies (OG Vocab)
    • Merge synonyms to avoid skewed results due to lexical choice (Synonym
    Collapsing)
    • Link to related material (Similar by Terms)
    • Faceted search to help users refine their queries and navigate through the material
    (Faceted search)
    • Display a hierarchical index of each vocabulary (Vocabulary Index)
    • Provide RSS feeds for individual terms
    • Display customized tag clouds on any page (Tagadelic)