Nashville Sites – Page 2 – Mary Ellen Pethel

Project Progress 3/23-3/30

I met with Jessica Reeves of the Metro Historical Commission (MHC) this week. We looked at other municipalities (and one university) that had created “walking tour” type projects based on historical markers. We also discussed how to attach signage to the existing markers that will connect the potential audience to the project via the physical location and physical marker. Jessica and I have also designed a logo, approved by Tim Walker, and are working to have it professionally designed. I am currently using a rough draft of the logo on my current project on Omeka: http://www.drpethel.com/exhibit/

Here are three projects with similarities to the proposed goals and working strategy of Nashville Sites. For some the web presence is great, for others pretty bad. There is an even wider range when considering metadata, scholarship, and sponsors. If anything, these reveal that such projects are desirable but the planning, execution, design/layout (to be mobile and desktop friendly), navigation, and overall usability remain key. Also key is reaching the intended audience.

1) Fort Wayne, Indiana—http://archfw.org/heritagetrail/centraldowntown/

It is managed through a local heritage non-profit. They use WordPress and include audio clips. No meta data.

Article about the project—http://beqrioustracker.com/history-markers-come-alive-with-qr-codes/

2) St. Augustine, Florida— http://staugustineexplorers.com/

This was funded by a state grant and administered by the Planning Department of the city. It had two components: markers and QR codes going up on buildings; and the website that hosts the digital content. The markers are beautiful, the site is…not. No meta data, very hard to navigate.

Article about the project with photos— http://staugustine.com/news/local-news/2016-09-05/added-touch-city-st-augustine-places-historical-marker-qr-code-some

3) University of Illinois, Urbana-Champaign— http://publicaffairs.illinois.edu/markerstour/

Funded and managed by the Public Affairs division of the University. The QR codes are attached to the posts in some way (I’m waiting on an email back from Joel Steinfeldt, the social media/site manager who put up the QR codes, to see how they are attached). Site has audio/video clips, no meta data.

Article about the project— https://news.illinois.edu/blog/view/6367/209634
__________________________________________________________________________

As encouraged by Dr. Leon, I need to develop five items to answer an inquiry question for each exhibit. I also need to figure out how to created “nested pages” within the exhibit builder to develop content. I also need to carve out some designated “work days” for this project so that I can consider what kinds of strategic framing I plan to use for content to attract users and to entice them to explore the full depth of the exhibits. I have a manuscript due on April 3 for a traditional writing project for a local nonprofit organization here in Nashville. I have been working on it since August, and despite my best efforts, I am a bit double booked until I can put the writing project to bed. The good news is that the light is bright at the end of the tunnel. At that time, I will be able to devote much more time to Nashville Sites. Thank goodness for flex modules!

Project Progress 3/16-3/22

I had two very productive meetings this week related to my Nashville Sites project. The first was with Tim Walker and Jessica Reeves who both work for the Metro Historical Commission (MHC) in Nashville. The MHC is the local government agency here in Nashville who is partnering and sponsoring the project. We were joined in the meeting by Nicholas Lorenson who is one of the lead administrators for Code Nashville. We discussed the project goals, looked at several examples, and discussed strategy, audience, site layout, function, and deadlines. As part of our discussions we explored several options. One option is to move away from Omeka and to use WordPress instead. I was concerned (as were Tim and Jessica) about the ability to use Dublin Core so that the project can maintain its scholarship and metadata components. Nicholas discovered that there is a Dublin Core plug-in for WordPress. I am not sure of the final outcome, and this week Mr. Lorenson is going to “look under the hood” at the project as it exists currently in Omeka and make recommendations about next steps. One reason to move from Omeka to WordPress is that it is much easier to find and receive technical support from Code Nashville (or other tech subcontractors). Omeka is far less common outside of the public history or digital humanities world. It might also be easier to maintain if long term control falls to the MHC. We agreed to meet again in the next two weeks.

The second meeting was with the marketing committee for the Metro Historical Commission Foundation (MHCF). The MHCF is a 501(c)(3) that raises money and awareness for MHC projects that need funding/support beyond the appropriated MHC budget, which is based on taxpayer dollars. I presented my project to the committee, it was approved and I was encouraged to write up a short grant proposal for funding. I was also asked to present the project at the next MHCF meeting on 4/14.

So while it was a productive week, I don’t yet have much to show for it and the project site itself is largely as it was last week. This week I hope to shore up some of the inconsistencies of my Dublin Core records and further develop the exhibit. I have decided one thing for sure: I plan to stick with Omeka for my class project. While I think this project will eventually migrate to WordPress, I will continue to work within the Berlin default theme. It will not look as good, but the content is what matters for this course, and that is my top priority in the short term.