Apps vs. web

On the bus to class today, the topic of web content for our students came up: what would students use in their courses, apps or websites?

My students, most of whom are non-traditional, older students who have recently returned to school and claim that they are not “comfortable” with technology, all carry phones and most carry the newest, shiniest, bells-and-whistles iPhones. They may not have computers, iPads, or printers, but they do have phones. They may not care about “pretty” sites, but access to phone apps do appeal to them. (See  this graphic at http://www.edudemic.com/apps-graphic/; it seems that most students, traditional or non-traditional, use apps, not websites.)

So I was excited about reviewing a phone app for my homework assignment, the phone app, Timeline Art Museum. Bad, sad and very irritating. It has the worst aspects of Corbis (you pay for high quality images, even if they are in the public domain), unclear functionality (until you click on the short biography, you don’t know that images by the artist are included in the app), and it focuses on those aspects of art that my students cling to like a lifeboat: biographical details and the canned analysis of the thumbprint description. The image is too small to encourage real analysis by the students, the descriptions encourage shallow understanding, and the argument of the app’s design, as Kimon Keramidas’s presentation pushed us to consider, is the wrong argument. And, as Lauren  Kilroy-Ewbank asked, if this isn’t for students, for whom is it designed?

I don’t know. Not for the audiences that I see at the Art Institute of Chicago; it is much too naive and uninformative. It certainly wouldn’t engage those who aren’t interested in art to become interested in art. And, as I said above, it ain’t for my students.

It does highlight the question of argument for a page and how visual elements contribute to the argument of the page. i want to talk more about this as I discuss the various tools to which we were introduced today. But tomorrow is another day.

The big takeaway, however, from today’s class for me: I need to dress up my WordPress site. It looks shabby, neglected, and woefully skeletal compared with my esteemed colleagues. Let me play some more.

 

 

 

Source: Apps vs. web

Platform Test Drives

Our afternoon was devoted to hands-on time with one- or more- of the presented platforms for our projects: Omeka, Drupal, or Scalar. I chose Drupal, but ended up spending much of the work time waiting for my site to generate. I got an email on my way home that the site was now available. So this evening, on my own, I gave it a try.

I chose Drupal because I liked the idea of doing something more like the hmtl websites that I had done in the past as opposed to my perception of Omeka, which seemed like more of a one-to-one presentation type tool. My institution has adopted Drupal for it’s content management system and I have attended one rudimentary training session. I found the session to be uninformative, despite Drupal being billed as akin to WordPress which I feel very comfortable with. I thought that starting on my own and using drupalgardens.com that I would find it easier to use. I did not. I was able to make one entry on something that I wanted to be a static page- simply text, and image, and an image caption. I knew there must be a way to format my image caption, but it was not readily evident to me. I also had a problem with word wrapping in my central column. I explored different control elements in the dashboard and felt pretty lost. I decided to try Omeka to get more momentum for my project and to keep from feeling discouraged at this early stage.

Omeka would be a good platform for a photo project that I have started. I am scanning photographs that I will then catalog at item level in MARC in my library catalog. I can then export those records as a CSV, crosswalk my MARC fields to Dublin Core, then use the Omeka CSV plugin to import them. I decided to experiment with a set of ten objects from our permanent collection, all collected in 1919, whose description data I happened to have in a spreadsheet already. I watched the screencast on using the CSV plugin and learned that I will need help setting up my FTP client to upload my spreadsheet. Moving on, I thought that maybe I could import the images that I will later attach to that data. I made the mistake of adding all of the images as one item, realizing that the best method is probably to upload the data, then upload and link the image files.

Scalar, which I saw demonstrated at the American Art History and Digital Scholarship symposium in the fall, was clearly not appropriate for my topic, at least at this stage. Perhaps as I continue to collect and analyze the collection data I’m interested in and a narrative is formed around my observations, Scalar could be a way to present the entirety of my project. But for now, I’m not dealing with a lot of content and I am not working on a narrative.

Source: Platform Test Drives

Omeka!

After a dizzying morning exploring the world of Omeka, Scalar and Drupal Gardens created sites, I was happy to spend the afternoon getting some hands-on time with Omeka. Truth be told, I have tried to use Omeka before, though it was such a disaster that I am not sure I should even mention it. In my desperate search for ways to create online exhibitions in my classes, I stumbled upon Omeka last spring (after an even more disastrous attempt at using Google SketchUp).

Source: Omeka!

“Use men to get the things you want!”

The above quote comes from Baby Face (1933), a “Pre-Code” Hollywood film starring Barbara Stanwyck that embraced Nietszche and exploitation as a primary means of Depression era survival. This did not go over so well with the newly empowered MPPDA, who upon enforcing their Production Code in 1934 required that any re-release of this film have the offending Nietszche material cut out and replaced by a new voice-over containing a moralizing lecture (and at least an implication that the book in the scene is a Bible, rather than the writing of Nietszche). No master and slave power dynamic and more a cautionary “there is a right way and a wrong way” for Lily Powers to get along in the world.

I think this is an appropriate choice for today’s workshop response, since we were tasked in the afternoon with “exploiting” one of three free content management systems–Drupal, Omeka, and Scalar–to see if one of them would suit our particular project. And because I tested Scalar using the above offending scene, creating a film and censorship project (still private, but also with all of one page and 2 media items in it, so not that interesting to the outside observer yet). I was attracted to Scalar because it was designed specifically to be used with multimedia projects using images, video, sound, etc, because a lot of those kinds of files could be linked in from outside sources (so not having to have a lot of server space built in for large media files), but also because, as I said to my other Scalar-testing colleagues at the table, it is rather like a “Choose Your Own Adventure” book, based on nodes and paths but not requiring a linear structure and including other visualization techniques to link data within the project.

Scalar was somewhat the reverse of my experience working with other CMS or blogging tools like WordPress, in that it required me to ingest or link to my media first and then build pages, comments, notes and annotations around that media second. Easy enough to re-orient myself to, and also not requiring me to have a grand plan or structure from the start. And the annotations and tags are truly wonderful. I could annotate my video clip, starting at the moment where the cobbler invokes the great philosopher and ending with Lily’s thoughtful “huh” (notice the clip above is just pulled in from Youtube and has no annotations). The annotation could include detailed text explaining why I made that particular choice (Here Be Voice-Over after The Code!) which would pop-up under the playback of the video when it came to the annotation starting point. Tags could be anything I want, and would be created as a page within my project, which meant that I could Tag any media object or other page, as well as add further explanatory information, links, bibliography or notes to the Tag itself–my first tag was “Pre-Code” and I can see how that could use some defining for audiences not familiar with the brief period from 1930-1934 when the MPPDA had a written censorship code but the studio members really didn’t make any attempt to enforce said self-produced code until further threats of Catholic boycotts forced them to finally capitulate and set up an office that would police the industry until 1968. I could add links to wikipedia, PDFs, and more. And, with more items tagged, and more tags, I could very easily look at my project as a network visualization (tags are links, lots of mentions in tags would mean sizeable nodes), showing how censorship could cross studios, films, actors, genres, gender, or any other grouping that would change the mostly linear and anecdotal story of film censorship in current scholarship. And I could see all of this potential after only an hour-and-a-half of work, which was even more exciting, especially if I am hoping to have students engage with this tool for a course assignment.

Source: “Use men to get the things you want!”

Platforms (and we’re not talking about the shoes)

There are a lot of different kinds of platforms in the world, but today the subject was web hosting platforms for art history research projects. As a group, we played with Drupal, Scalar and Omeka, but we also looked at a great variety of sites, thinking about their designs, their architecture, how well their design served their goals, how difficult or complex the sites were to construct and maintain.

I appreciated the chance to play with Omeka, especially to see what kind of a learning curve there would be to become truly effective in using the platform to accomplish what I would like to. As someone based in a museum, I know that my research will be hosted (eventually!) on the museum site and I won’t be personally responsible for constructing a website. I am looking forward to learning more and happy that I won’t have to rely completely on my limited skills to get my work out there.

For me the big takeaway today was the extended conversation in the morning about challenges faced by scholars at small schools with limited support for digital projects (or even research in some cases). It took a while but by the end of the morning, the group and our fabulous instructors, Sheila A. Brennan and Sharon M. Leon of the RRCHNM, and guest instructor Kimon Keramidas, Director of the Digital Media Lab, Bard Graduate Center, had come up with a range of strategies to address those challenges. Now we just have to lay the groundwork for those ideas to become reality.

Source: Platforms (and we’re not talking about the shoes)

Platforms and projects

This post is mostly speculative, since I didn’t try out most of the platforms presented today. And I’m only just starting to learn the one platform I tried, Omeka.

1. Omeka appeals to me as a pedagogical tool because it seems simple to understand and use, and offers a great format for student projects with the “Exhibit” plug-in. I am considering using it in a Fall seminar, where each student would create her own website on a research topic in lieu of a research paper. The students will still have to do research and formulate an argument, but in a different form from a term paper.

I am not sure how to use Omeka for my own research projects so far. My projects (the one on Brazilian modernism described in earlier posts, and two other research projects on architecture and urbanism) are not really about collections of discrete objects, but rather about sites and buildings that are inseparable from their urban locations and larger socio-spatial contexts. I can’t quite picture separating them as “items” and individual files with labels and metadata. Although I could use this format to tell a story about my projects, I don’t think this would take full advantage of their spatiality. But then again, there is a map plug-in in premium Omeka, so perhaps that would open up possibilities that I can’t envision yet. I’m thinking of the site on Visualizing NYC that Kimon showed us today–I think that was Omeka, and it had a very cool map. BUT: Kimon mentioned that they used a custom Java script for the map (which I don’t know how to do).

2. Prezi

Prezi seems great for organizing class materials for students. I didn’t try it out, but Kimon’s timeline was an amazing way of displaying information. I’d seen Prezi presentations before and I didn’t particularly like them, but today I changed my mind.

3. Drupal Gardens

I didn’t try it out, so I don’t have a sense of what it looks like or how it would work. It was described as very flexible, and based on a node structure–all of this seems appropriate for my projects, where I envision a map as the center of information and interactivity. As in: a page taken up mostly by a high-definition map with links to book passages and historical photographs placed on specific locations. From these links someone would open up new pages, which could be texts or images; and there could also be a reverse-lookup from the texts to the maps. It all sounds very abstract, I might try to sketch this out later.

4. Scalar

I must confess I don’t quite have an idea of Scalar compared to the other platforms (maybe I was in the restroom when it was explained in class?).

5. WordPress

I like the ease of use. It is appealing as a teaching tool for this reason. I also like it as a way of developing my thoughts and recording my work process, just as we are doing with the homework assignments. I wish it were a little more flexible in terms of its calendar/blog structure.

 

Source: Platforms and projects

Ugly Duckling

duckI was really really really looking forward to getting my project started today, especially with all the promises that Omeka was super-easy and awesome-intuitive.  Not true!  Maybe after having easy experiences setting up several sites on WordPress in the last years, I expected Omeka to be a souped-up version of what I already know, but more powerful, cooler, maybe even prettier.  Instead it felt clunky, and even by reading the step-by-step instructions, which helped me get a few things set up, I still just don’t have a clear sense of how everything fits together.  Also, it seems that the kinds of things I was counting on to make my project happen are not super-easy or available; or maybe that’s still just yet to be revealed. I ended the day with a sort of half-baked digital draft of something no one would want to look at, let alone use.

Overall, my experience this afternoon reflected those of my first time baking a pie, which was not that long ago.  I am pretty accomplished in the kitchen, but for some reason the skills for fruit pies elude me, and ultimately I think: why bother, when cake is better anyhow?  I’m not willing yet to throw out Omeka like I did with that sad blueberry pie, but I am willing to right now just claim the prize for Ugliest Ducklingest with hopes that this serious case of the uglies will resolve itself into something much more elegant, useful and beautiful in the (hopefully near) future.

image source: click here

 

Source: Ugly Duckling

Homework Day_3: The strengths and weaknesses of the platforms

In our hands on session today, I dove into Drupal Gardens (at least at first). I chose Drupal Gardens because it was touted as having the most flexibility in terms of site-design and capabilities (or at least that is what I took from the conversations around it), but that it might require a bit more elbow grease in getting the project/site off-the-ground.

This led me back to another set of issues that I have been contemplating, off-and-on, since my first thoughts about/on/around Mapping Paris: how much do I need to know about the technology going on in the background? If I need to reach out to others with different knowledge sets in the design/start-up phase of the project, how do I make them active contributors and not just service-providers to the project? Which led me to the place where I am now in this thinking: that I need to know at least a little bit about the inter-workings of the technology and software, so that I can (try to) 1) speak the language 2) understand other contributors 3) take software/tech into consideration while in the scope/planning phase of the project.

Drupal Gardens took too long to populate my website, so I decided to try my luck with the one-click installation of Drupal onto my webpage hosted by Reclaim Hosting. From what I understand, the differences between Drupal Gardens and Drupal, is that while the former is more flexible and open-ended than Omeka and SCALAR (the other CMS introduced today), it is more user-friendly and more regimented than plain-old Drupal, which is bare-bones AND (most important for me) needs some knowledge of HTML coding to really flesh out your site.

Which brought my previous musings on knowing the tech-side to the very-tangible present. I was able to make a node (a page, in Drupal-speak), but all it contained was some bare-bones text AND I was able to change the color schema and remove the logo (which I thought was distracting). Everything else will have to wait until I remind myself how to add emphasis to text via HTML tags, and (significantly) up-the-ante on my HTML skills. I have left my plodding work up for the moment, in an exercise of making myself vulnerable and allowing the unpolished, work-in-progress nature of the project to be visible, but it probably will be hidden soon, as I make slow progress towards a functional site. For now, check out clairekovacs.org/MappingParis/ to see my work, thus far.

Where am I going to start learning HTML? Good question, but here are some places I am going to start thinking about*:
Codecademy

The Programming Historian

Women’s Coding Collective

 

*My thanks to Lauren, Sharon and Stephanie for the programming suggestions!

Source: Homework Day_3: The strengths and weaknesses of the platforms