Computing has no significance whatsoever for research in the humanities other than in what is to be done with it, concretely and immediately. … innumerable directions may be taken. … which do we take? (McCarty 199)
Though in the above quote McCarty questions what the set of agendas for the field of humanities computing should be, he also argues individual scholars engaging with particular works are a “primary” driving force in the field (206). Given that, I feel free to ask myself what my agenda is, what direction I desire to take (see McCarty 200 on desire and planned action), as I examine the relationships between the symbols in Renaissance emblem books.
McCarty diagrams the stages of modelling from cultural artifact [emblem books] into computer science and back up to the artifact through humanities computing (197). It seems I have already begun the first two movements: problem specification, and systems analysis. With the first step I have already decided my “specific perspective”: I wish to look at the symbols related to and with the Judeo-Christian God. In a vague way, I already conceived emblem books as “a system of discrete components [the symbols] and relations [within and between emblems]” (McCarty 197). McCarty correctly states “sacrifices” and “compromises” are made during these steps (198). By picking one perspective, I limit what I am studying about the work. How I choose to study the system of symbols affects what sorts of results can be gained, at least from this project.
Yet, because of McCarty, I no longer think my “conceptual design” is “good enough” (see McCarty 198). Originally, I wanted to use the Iconclass hierarchy metadata (see McCarty 89-90 on metadata), to group symbols together in specific emblems and to see which groups persisted in many emblems. In general, projects using Iconclass tend to be very thorough regarding the “what.” For example, looking at this emblem “Invidia [Envy]” as catalogued by the Alciato at Glasgow project, one can see they have missed very little (if anything) with their Iconclass tagging. Reading McCarty’s description of his project looking at personification in the Metamorphosis, lead me to questions of context (54) and weighting (61). Contextually, I want to know what part of the emblem – motto, pictura, and/or subscription – the tags are pointing towards. Within the image itself, the element placement itself could have some contextual meaning: Is the main focal point of the image frequently in the centre? Perhaps I could experiment with image analysis/design software such as Pixcavator IA or PhiMatrix to generate data (taking the “off-the-shelf” route [McCarty 197]). Weighting wise: Should a connection between Iconclass tags be weighted more based on type of relation; in the example, should tags describing envy have a stronger link between them than with the “scenery”?
Like McCarty’s “blind man” I can use received knowledge, in the form of tools (Iconclass and software) and instruction (classes and reading), but my DH work is still self-moving and experimental (McCarty 51). I will learn by doing, and adjust direction based on interaction with the programs and data, making sure to remain explicit about and consistent in applying my choices (McCarty 25).
Adams, Alison et al. Alciato at Glasgow. University of Glasgow. Web. 9 Dec. 2015.
McCarty, Willard. Humanities Computing. Basingstoke, Hampshire: Palgrave Macmillan, 2014. Print.
 Oddly, my emblem example is a personification whose subscription comes from Ovid’s Metamorphosis. That was not planned.
 McCarty’s application of Heidegger to the process of modelling is quite apt here. For me, the Iconclass tool has gone from “ready-to-hand” as Heidegger defines a tool in use, to “present-at-hand” due to “a failure of the tool” to do what I want it to (McCarty 42), though admittedly not what it was designed for. I have to modify the tool. I expect this will happen more than once, as has been the case in my previous and current DH projects.