COAR launched a photo exhibit with artist Eliza Gregory. Titled “FUSE: Portraits of Refugee Households in Metropolitan Phoenix,” the exhibit sought to raise awareness in the community regarding Phoenicians’ newest neighbors. From the summary of the exhibit:
"> COAR launched a photo exhibit with artist Eliza Gregory. Titled “FUSE: Portraits of Refugee Households in Metropolitan Phoenix,” the exhibit sought to raise awareness in the community regarding Phoenicians’ newest neighbors. From the summary of the exhibit: "> COAR launched a photo exhibit with artist Eliza Gregory. Titled “FUSE: Portraits of Refugee Households in Metropolitan Phoenix,” the exhibit sought to raise awareness in the community regarding Phoenicians’ newest neighbors. From the summary of the exhibit: " />Product. Data. Science.
02 February 2009
In April 2008, COAR launched a photo exhibit with artist Eliza Gregory. Titled “FUSE: Portraits of Refugee Households in Metropolitan Phoenix,” the exhibit sought to raise awareness in the community regarding Phoenicians’ newest neighbors. From the summary of the exhibit:
FUSE is a portrait exhibit of the complex worlds of resettled refugees in the Phoenix metro area. It fosters critical thinking on who refugees are and how, through sharing experiences, the Phoenix metro community can seek common ground. The photographs validate the struggles and triumphs of these families, portraying them in a way that cultivates a deeper sense of belonging in the community.
In order to support this effort, I helped put together an integrated system, allowing audience members to engage on a more direct level with the portraits.
Using podcasts of interview clips with the refugee subjects of the photos allowed us replicate on a very tight budget what would be quite expenisive with a proprietary museum guide system. With Podlinez, audience members could also call a phone number printed next to the portrait in order to hear the podcast.
Finally, audience members were also able to give feedback on the exhibit via SMS, which was compiled into a Twitter feed for the exhibit (I’ll describe this last piece later, in Part 2).
So, here is the basic outline of the system:
I’m not going to go through the nitty gritty details of installing Drupal modules, but here is the list of modules we used for this system:
Drupal’s framework is incredibly flexible, allowing you to do amazing things with just a little bit of elbow grease. This was all done under Drupal 5, so I am not going to go into too much detail with the configuration because the details are probably out of date even though the concepts are still valid with the new CCK and views modules.
Drupal is built around nodes (units of content). For our purposes, we wanted a “portrait” to be our content type. Each content type will have a photo, a number (the title), and a caption. Some of the content will have an mp3 audioportrait as well.
So, we first create a new custom node type and called it portrait. Then, we add the following CCK fields: photo (an image field), photo_caption (a text field), and audioportrait (an audio field).
Next, we can go to pathauto settings and set the URL pattern for each portrait to be **fuse/portraits/[title] **
Now, to control the visual presentation of the content we can do a few things. First, we can use Imagecache to setup automatically resized versions of the uploaded photo. Then, we can go to the view option for the content type and change the presentation of each of the fields. For example, we can get rid of the labels for each field, set the image field display mode to the resized image_cache version, and set the display for the audioportrait to the Media Field Display. That last one will let the users play back the audio portrait right in the browser.
Next, we use the views module to setup each of the views for the different modes of presentation. This is the key to the whole deal because it lets us build the actual feeds for the podcast and for Podlinez.
Podlinez is a free service that lets you call a podcast from a phone. You simply submit the URL of the podcast feed and they kick back a phone number. They preface the podcast with a “brought to you by Podlinez” kind of ad. They cull the list of numbers periodically, though, so if no one calls your podcast for more than two weeks, you might lose your number. It was brought to my attention by Casey Muller.
Since you have a list of feeds (one for each file) from the view you setup in Drupal, simply go to the Podlinez homepage and drop that URL into their phone number generator.
Word of caution:* Be sure to test your phone numbers before “going live” and printing panels with phone numbers on them. Sometimes the numbers that they give you don’t work. This can be particularly problematic if you are trying to throw this together at the last minute, hours before opening, like I was. I tried adding the feed again and it would tell me “We already have a phone number for that feed” and give me the non-working phone number. The tech people at Podlinez were quite helpful in taking down such numbers, but you should give yourself a few days before opening to get the kinks worked out.
*
In hindsight there were a few things that I would pay closer attention to if I were to do this again:
I’ll post soon on Part 2 of this series, which will cover adding the “interactive” layer to the system: using 4INFO, Twitter, Yahoo Pipes, and a few other tools to let audiences respond to the exhibit in real time.