Blog Archives

If a picture is worth a thousand words, then…

I found the examination of image analysis helpful going into our discussion of what elements to keep for the image collection. I feel like two area examined were already something we have considered – namely “Levels of Analysis” and “Vocabulary” control. The other area of examination “The focus on relationships, processes” struck me as pertinent and unnoticed until I read this article. Quite simply it states that many instances of images derive their “aboutness” meaning not simply from the objects or subjects pictured, but from the relationship the two objects have between one another. In the example given in the article the picture considered is a stork carrying a baby elephant. Separate they have meaning, but the meaning they carry together and then the meaning is only understood culturally. Ins electing which elements to keep and those to dispose of it seem pertinent then that we consider all the information users would need to have for the correct contextual understanding of the image.

DC Type element: A Change of Heart

When we received our elements I at first considered I had made a folly in choosing Type. Since this collection is all images, what use would my element be? “It says Images in the title”, I thought to myself. In reading the DCMI definition of Type closely though I was struck by the advice, “…best practice to ensure interoperability is to include at least one general type term from the DCMIType vocabulary in addition to the domain specific type term(s)…” It occurred to me I was thinking only locally in my dismissive thoughts on Type and neglecting to consider that these images would be of interest to other institutions which may desire to utilize them within the parameters of their institutions policies. I believe now that utilizing DCMI Type vocabulary – in addition to any local descriptions of Type we may deem relevant and useful – will ensure that the collection can be integrated with outside systems efficiently and effectively. Further I think the Type terms “Image” and “Event” are both applicable to efficient utilization of the image collection. Before using the “Event” term though, further explication of proper usage would be necessary.