Women Architects and World Fairs

Category: Digital Art History (Page 1 of 2)

Time got away from me in more ways than one this week

So I may have gone a little overboard this week.

Inspired by exploring Mina Loy: Navigating the Avant-Garde (https://mina-loy.com/) and given the assignment to make a timeline using TimelineJS (original recipe or reimaged), I decided to fill a gap in my own scholarship. I was impressed by how Mina Loy: Navigating the Avant-Garde went beyond a timeline to incorporate multiple projects from visualizations to games to capture different aspects of Mina Loy’s life and artistic work. While I was only making a timeline, I also wanted it to fill a gap in my own scholarship while painting a complex picture of the topic.

A missing area in video game scholarship that has proved to be a major problem for my study of artist book and fake game guide Vermis I: Lost Dungeons and Forbidden Woods has been the lack of a even somewhat cohesive history of the game guide format. While there are good sources of information on that history, they are all partial focusing on only a few aspects of the topic like publisher history or magazines. I decided what was needed was a fuller timeline with overarching game guide history in the form of news and events, specific notable game guides and publisher history, console launch dates to add context to what games would have been written about at a given period, and release dates for games mentioned. I also decided from my research that a game guide history would have to cast a wide net, including not just standard printed game strategy guides but other areas where guides have been published like magazines, zines, video, and websites.

Did I do too much? Absolutely. The timeline is a mess of dates on top of each other with very little that is readable.

Do I regret it? Not really. My timeline ended up being a great example of digital humanities as process instead of product. I learned an immense amount creating the timeline about how game guides changed over time. I also picked up on interesting trends in other areas like the consoles and games release windows getting shorter as more saw global or near global releases over time while past releases were more piecemeal and slower. In the course of my research, I found game guides and information that did not even make it into the timeline that is relevant to my thesis on Vermis I.

It was also a learning experience for using the new TimelineJS reimagined (https://knightlab.northwestern.edu/2026/08/13/timelinejs-reimagined/index.html). Overall, I found being able to see my slides as I added and edited to be much more intuitive than creating a spreadsheet in envisioning how my timeline would flow. This may have also contributed to my slide bloat (from my assigned 20 slides to the final 28 slides) since the process was creating each slide individually rather than thinking of them as a whole. Grouping was easy and essential though I wish there was an option to mass change the name of groups. The date range functionally was also lacking with no way to show that a slide was ongoing into the present. Perhaps this is for the best when a timeline is not stamped with a date of creation, but it made it frustrating to see items that should show as a range showing as single point because they had no end date. These may be issues that I could have fixed had I experimented more deeply, but on the surface, there did not appear to be a way to address these pain points. The uploads also began to chug as I neared editing slide 70 which is understandable as I was also feeling overloaded at that point. Still, these are all minor issues in what was otherwise a dangerously easy process.

Despite the information density, I do believe the timeline still has some great information. I do recommend full screen for reader’s eyes and sanity though.

Narrative, deception, privacy, and purpose in situated data visualization

Where do we draw the line in data visualization between what is storytelling and what is deception? According to data visualization author and expert Nathan Yau, the answer is to question the context of the creation of the chart. Who made it? What is it trying to say? Does the data actually support that narrative or does the visual have to be skewed to make it suggest the desired narrative?1 Ultimately the suggestions for assessing the honesty of a data visualization boils down to maintaining the “essence of the data” in the visualization.2 How to determine what that essence is requires different tactics depending on if you are making the visualization or trying to judge the honesty of a visualization as a viewer.

Nathan Yau suggests a few aspects to consider when creating or assessing a visualization: context, acknowledging all visualizations have a narrative or purpose, and remembering that people are the ones who create visualizations.3 Scholars Catherine D’Ignazio and Lauren Klein also address these points in “Chapter 3: On Rational, Scientific, Objective Viewpoints from Mythical, Imaginary, Impossible Standpoints” in their book Data Feminism. By charting how data visualization has historically focused on an objectiveness goal that is fundamentally impossible, they show how the humanity of creators shows in all aspects of data handling. This is regardless of if a visualization is deliberately trying to persuade or not. Every person brings themselves to the collection and interpretation of data including the viewer.4 Because we are human, when we model data we should also consider emotion as a valid data point or component of communication.5 D’Ignazio and Klein state that this isn’t a binary choice between an attempt at objectivity and “a retreat into complete relativism and a world in which alternative facts reign and everyone gets a gold medal for having an opinion.”6 They suggest instead a number of theories that all return to noticing that people make choices with data to communicate.

D’Ignazio and Klien put the human context primarily on the creator, and suggest situating as a method of adding human context. They position themselves in the introduction to Data Feminism by noting “the gender, race/ethnicity, class, ability, education, and other subject positions” they hold..7 While this is not their only suggestion, I am addressing it because it has great potential to do harm to the very people at the margins that feminist approaches try to center. Situating oneself along demographic lines and encouraging that in others ignores that these types of disclosures might be felt as an invasion of privacy or create real danger. It reminds me of well meaning fans of a television show that forced an actor to publicly disclose his sexuality to keep his job (I am not naming the show or actor deliberately). While perhaps well intended, the result was still that they forced a young person to not only label a sexuality they were still exploring but to do so in a public statement. Not only is that harmful to the very community it is trying to protect but being situated in a specific identity does not always mean you are the best person to speak on that identity. I have seen an aspect of my own identity presented by several writers both those that hold the identity and those that don’t. Of my three favorites, one shares the identity, one does not, and one is an unknown.

No approach is without issues, but I much prefer Yau’s which puts faith in creators wanting to be honest8 while also putting judging that honesty on the viewer.9 Yau couples this approach with the idea that context is valuable but can be both explicit or implicit.10 I think this approach also shows in Yau’s about page. Yau situates himself according to who he is as a person not a demographic list and appears to balance details that help the reader understand where his opinions come from without disclosing more than he wants to as an introvert. I believe this balance is a deliberate choice since his about page ends with “My work is based on these experiences.”11 which makes it clear that Yau is aware of both the need to situate himself for the reader and how to do so in a way that is contextually relevant and within the bounds of his own choices.

Another aspect of data visualization that came to mind during these readings was how the approach to honest situated data visualization changes when the purpose is for internal research instead of external display. To experiment with that aspect, I ported a small dataset from my Information Science masters paper12 into Palladio. The data used was a simplified version of my analysis of the age of video game related materials in nine academic art libraries. All three were organized by library. My original spreadsheet also included the titles of the earliest and most recent materials and details about their content. Since the spreadsheet was not created to be parsed by a service like Palladio, I decided to remove those data points for this exercise.

Two timeline bar charts and one timespan line graph. The two bar charts show the earliest and latest year of a work in a library's collection. The timespan shows the range from earliest to latest. It is difficult to distinguish detailed information from the overly simplistic visuals.
Three visualizations from Palladio based on a sliver of my Information Science masters thesis.

I’m mixed on the result. When viewed as potential ways to display my data, I feel I made a smart choice when I decided to avoid visualizations in my paper, a choice that is as editorial as the choices made when making a data visualization. I felt that including data visualizations would risk privileging the numbers when the nuances of conducting the study added invaluable context to the numbers. My spreadsheets were in the paper as support for my conclusions, not as a way to communicate anything about the landscape of video games in art libraries on their own. As an analytical tool with this dataset, I think there is a major risk of accidental self-deception. There was no way I could find to change the parameters of either the timespan or the timelines. Because the latest year x axis is divided into months and the earliest year axis is in year increments, it appears like the earliest materials and the most recent materials cover an equal range of time. In truth, the span between the latest dates is only 3 years. Meanwhile, the earliest dates range over decades (another shortcoming of the earliest chart is it’s lack of division between years making it impossible to discern exactly what the earliest date for each library is).

The timespan filter was more promising. It showed a comparatively massive timespan of materials at the University of North Carolina Sloane Art Library. When I wrote my paper, I also noted this and it lead me to more closely examine that earliest item. By taking a closer look at the types of materials that were the earliest in each collection, I discovered that there was much more variety in earliest material than in latest. While a tool like Palladio was unnecessary for this discovery, I imagine that with a much larger dataset, the timespan view would be a good tool for catching this sort of information that might other wise be overlooked.


  1. Nathan Yau, “Defense Against Dishonest Charts,” FlowingData, February 13, 2025, https://flowingdata.com/projects/dishonest-charts/.↩︎

  2. Nathan Yau, Data Points: Visualization That Means Something (John Wiley & Sons, Inc, 2013), 98.↩︎

  3. Yau, “Defense Against Dishonest Charts”; Yau, Data Points.↩︎

  4. Catherine D’Ignazio and Lauren F. Klein, “Chapter 3: On Rational, Scientific, Objective Viewpoints from Mythical, Imaginary, Impossible Standpoints,” in Data Feminism, Strong Ideas, ed. David Weinberger (MIT Press, 2020), 8, https://mitpress.mit.edu/9780262044004/data-feminism/.↩︎

  5. D’Ignazio and Klein, “Chapter 3: On Rational, Scientific, Objective Viewpoints from Mythical, Imaginary, Impossible Standpoints,” 16.↩︎

  6. Yau, Data Points, 15.↩︎

  7. D’Ignazio and Klein, “Chapter 3: On Rational, Scientific, Objective Viewpoints from Mythical, Imaginary, Impossible Standpoints,” 16.↩︎

  8. Yau, Data Points.↩︎

  9. Yau, “Defense Against Dishonest Charts.”↩︎

  10. Yau, Data Points, 112–16.↩︎

  11. Nathan Yau, “About,” FlowingData, June 13, 2007, https://flowingdata.com/about/.↩︎

  12. Mert (Meredith) Overcash, “”I’VE EXPERIMENTS TO RUN, THERE IS RESEARCH TO BE DONE”: VIDEO GAME ART WITHIN ACADEMIC ART LIBRARY COLLECTIONS” (The University of North Carolina at Chapel Hill University Libraries, 2026), https://doi.org/10.17615/MRFG-SD27.↩︎

The overlooked creative practices of metadata tracking, annotation sharing, and boundary setting

Matthew J. Westerby opens his article “Annotating Upstream: Digital Scholars, Art History, and the Interoperable Image” with the story of how downstream uses of the British Library’s IIIF images and manifests lost their own access when the Library was the subject of a cyberattack. This domino effect showed a “change in the relationship between institutions and users of online collections in which separate layers exist to serve images and also to present the digital surrogate of a real-world object like a book.”1 Similar complex layers of delivery and downstream/upstream usage have been on the minds of video game scholars for a long time. There is always a layering between the game’s software and the hardware or the display, as well as between the game as code and the physical object that carries that code, such as a cartridge. Especially with online-all-the-time consoles, a game can be pulled or updated or changed at any time without user consent or warning. These delivery layers are perhaps more apparent to the average gamer than the average user of an IIIF image art surrogate because they have demonstrably affected how games are released and experienced. It is now common (though not acceptable) practice for a game to release in a broken state with day-one patches to download. Patching post-launch was a near impossibility before internet-connected gaming, so the uneven quality of games at release has been felt by all video gamers.

This is not the only place where Westerby’s suggestions and insights for art history run parallel to emerging practice in game studies. Annotating video games is one way game studies is looking to share knowledge weither via annotating games themselves, annotating screen captures of video games, or through examining existing annotation practices like wikis and let’s plays that are a part of the larger life of “networked hyperlinked videogames”.2 For the practice part of this post, I used Panopto to experiment with annotating a brief screen capture of me playing The Blood of Dawnwalker.3

Annotated video incoming, technical issues, check back by Tues 10/5

One of the reasons wikis are such a robust source of information for video games is that they are such complex artworks that one person could never annotate a full game by themselves. It also adds to the robustness of scholarship when sharing is part of the process, not just the outcome. The Zelda object-focused digital humanities project4 that I mentioned in my post about Collection Builder was one project that used this style of sharing. My portion was about multiplicity and repetition of objects in the Zelda series, focusing on small keys, but I was doing it alongside Sydney Bauer whose object was a single American painting, Hannah Iovanna who was examining the still life paintings of a single artist, and Addie Magyar who worked with me on the Zelda portion and also acted as coordinator (Magyar was actually who noticed that small keys are the only constant in all the games). Being able to do those separate case studies with the same methodology while in communication during the process made the projects much richer and more enjoyable. Our discussions and brainstorming sessions brought up the question that I swear one day I will write about: why is there always a wheel of cheese with one little slice out in every video game? I sometimes wish I had picked the history of the wheel of cheese with one little slice out as my art history thesis: a study of why it is the most filling and delightful of foods across time and medium.

Annotating interoperable images is a mode of scholarly communication that is fundamentally different from the traditional sharing of only finished writing in journals and academic press books but no less a creative or scholarly act.5 When there’s a wider variety of acceptable ways to communicate information, writing a book or a journal article becomes a choice, not an obligation. The quality of all scholarly communication increases as forms increase because the output mode is not just one default option regardless of the needs of the argument or the data. This also allows for more modes of scholarship that cannot be studied or communicated as well via paper alone, like GIS mapping projects from my previous post. I was unfamiliar with the idea of thick data or data pollution6 as terms when I wrote the mapping post, but they are great terms for the concept I was exploring at the end of that post: messy data that balances the line between being so messy it’s no longer a useful tool but isn’t so clean that it carries unquestioned authority with data pollution also covering the source of data like AI or how data is used.

Westerby’s choice to end the article with how you can’t control other people’s usage of your images or metadata if you share them, and how the fear of misuse should be a known risk but not a reason to abandon openness was nuanced and powerful.7 There will always be people who take good things and warp them. Making decisions based around absolute prevention of misuse is an impossibility and an unnecessary burden. It is better to work from being risk-aware, with practices like the usage tags that Westerby suggests.8 It reminded me specifically of the Wretched & Alone SRD,9 a system written by Matt Sanders for making solo journaling games in the style of Chris Bisette’s game The Wretched.10 The Limitations section of the SRD includes “Finally, nazis, homophobes, transphobes, and other bigots are expressly forbidden from making new content using the Wretched and Alone system. If you have to ask whether this includes you, it does.”11 Are parasites going to ignore the usage terms? Likely. Still, by making clear the usage and specifically taking a stance on who is forbidden to use the material, bigots cannot hide behind not knowing or accidental infringement. It makes the deliberate nature of the theft apparent.


  1. Matthew J. Westerby, “Annotating Upstream: Digital Scholars, Art History, and the Interoperable Image,” Open Library of Humanities 10, no. 2 (2024), https://doi.org/10.16995/olh.17217.↩︎

  2. Austin Anderson, “Dark Souls as Networked Hyperlinked Videogame,” Electronic Book Review, ahead of print, September 28, 2025, https://doi.org/10.64773/1f7a-df6c.↩︎

  3. “The Blood of Dawnwalker – A Dark Fantasy Narrative Sandbox RPG,” The Blood of Dawnwalker – A Dark Fantasy Narrative Sandbox RPG, accessed October 5, 2026, https://dawnwalkergame.com/us/en/home.↩︎

  4. “Scaling Stories,” Scaling Stories, accessed October 5, 2026, https://sydbauer.wixsite.com/scaling-stories/interactive-feature.↩︎

  5. Westerby, “Annotating Upstream.”↩︎

  6. Westerby, “Annotating Upstream.”↩︎

  7. Westerby, “Annotating Upstream.”↩︎

  8. Westerby, “Annotating Upstream.”↩︎

  9. Matt Sanders, “Wretched & Alone System Reference Document V1.1,” SRD, with Chris Bissette, Sealed Library, 2020, https://sealedlibrary.itch.io/wretched-alone-srd.↩︎

  10. “The Wretched by Chris Bissette,” Itch.io, accessed October 5, 2026, https://loottheroom.itch.io/wretched.↩︎

  11. Sanders, “Wretched & Alone System Reference Document V1.1.”↩︎

The dangers of cartography: I made a map and now I have to plan a trip to get a Braxxie lantern

Behold the Cryptid Art map!

The inspiration for my Cryptid Art map was growing up hearing tales of the Mothman and the Braxton County Monster (also called the Flatwoods Monster or Braxxie to her friends). The Mothman has risen in fame in the last decade, and yet most people I talk to who know the Mothman is from Point Pleasant, West Virginia, only know that as a general factoid or from the video game Fallout 76. Most have no idea the Mothman has any connection to the 1967 Silver Bridge collapse, which is a shame.

It may seem strange to connect a massive infrastructural disaster that ended in the deaths of 46 people and the creation of the National Bridge Inspection Standards to the celebration of a cryptid. But the lore of both is deeply intertwined. The Mothman was seen perched on the Silver Bridge the day before it collapsed, and so has taken on the status of an omen or, more charitably, the idea that he was “trying to warn us.” The tragedy was also caused by systemic infrastructure failure, a reason not to trust what the government tells you, a common theme in West Virginia stories. The danger of trusting the faceless people in power is echoed in the phrase that I heard most during the Mothman Festival hayrides and have a pin repeating: “Don’t fear the Mothman. Fear the Men in Black.” The Mothman behaved like an animal, and so could hurt someone, but never with malice. The Men in Black who came after from the government were the ones who threatened people. Admittedly, it’s a paranoid viewpoint. But given West Virginia’s history, from the Mine Wars to vote buying, and most recently the opioid crisis, I don’t think it’s a misplaced view.

I used Google My Maps1 for the Cryptid Art map, but I also explored Knight Lab’s StoryMapJS.2 I chose My Maps because it focuses it’s display on place, while StoryMapJS prioritizes content. Many of the artworks and related sites have very little information available, so a small description and image work well. For pins with more information available, it is nice to be able to focus on the most unusual or helpful source, like using the Braxxie lantern documentary for the Exxon station where they are sold. StoryMapJS is better for focusing on the object first and the location second, particularly in how it pulls up a large secondary window for the embedded material for each pin. When I was thinking of projects that might work with it, I was thinking of comparatively looking at falconry gloves within different archives and museum collections: where they were found, where they were made, where they were used, and where the material was sourced. This is also reflected in how StoryMapJS uses fixed icons that are tied to the type of material embedded and also the ability to control the order that pins are navigated through.

I think there is some baked-in skepticism of the accuracy and completeness of maps that maybe isn’t there for museum exhibitions, and that skepticism is valuable to engage with. Because we’ve probably all had a GPS app try to take us down a closed road or otherwise lead us astray, it’s all the more illuminating to notice how much maps can be used to both enforce and question authority. Béatrice Joyeux-Prunel in her chapter for The Routledge Companion to Digital Humanities and Art History, uses the example of how nationalists (including the Nazis) use “artistic geovisualization” to claim spaces, heritages, and artworks as their own and to justify their crimes.3 Joyeux-Prunel continues by explaining how art history is returning to cartography via digital mapping because it allows new questions to emerge “that had been buried for a long time, either because they could be embarrassing (such as the place of origin of a style, too often understood as a ‘center of influence’), or the geopolitics of art, or because they could not be given satisfactory answers[.]”4

An excellent example of case studies that ask all three of those types of questions and investigate them with “Historical Geographic Information Systems (GIS) methods” is Paul B. Jaskot and Anne Kelly Knowles’ “An Approach to Institutional History and the Built Environment in Nazi Germany.”5 In my opinion, the case studies have the added benefit of dejustifying Nazi crimes by picking them apart and not allowing them to hide in historical assumption. Mapping the SS camp system and the architecture of the SS camp at Auschwitz-Birkenau, Knowles and Jaskot used different sources of information and visualization approaches. What they had in common was how GIS was able to shed new insight even in a field as highly studied as the SS camps and raise new questions because it was able to connect information to a spatial context.6

Building my own map, I was surprised by how difficult many of the decisions I needed to make were and how they immediately made me realize I was creating from a position of authority whether I wanted that or not. One of my earliest decisions was whether to pin the Silver Bridge Wall mural. The Mothman and Silver Bridge stories are connected, but they are not the same. Still, the Mothman stripped of the Silver Bridge is stripped of an important part of its history in Point Pleasant. So I included the mural, with a simple description focused on the purpose of the map: “The Mothman was seen on top of the Silver Bridge the day before it collapsed, leading some to believe he is an omen of doom or was trying to warn the town of the approaching tragedy.”

I plan to continue to work on my Cryptid Art map with the mission that there should be art of cryptids in their hometowns (as long as those communities want it). So in the future I plan to add cryptid origin points even where there isn’t art yet. I may also add local artists who make cryptid art. Lately, instead of worrying whether something fits a set of rules or parameters, I’ve been asking whether it’s kinder to include it than to leave it off. Being messier but kinder in action is perhaps how we keep tools with an inherent authority, like cartography, from having so much power to warp or control. The future of transparency in digital tools may be to strip back the veneer of clean data and UIs without losing the purpose of the tool, embracing messiness and a degree of friction so that questions naturally arise about where the information comes from and who decided its presentation.


  1. “My Maps,” accessed October 5, 2026, https://www.google.com/maps/about/mymaps/.↩︎

  2. “StoryMapJS,” StoryMapJS, accessed October 5, 2026, https://storymap.knightlab.com.↩︎

  3. Béatrice Joyeux-Prunel, “Digital Humanities for a Spatial, Global, and Social History of Art,” in The Routledge Companion to Digital Humanities and Art History, ed. Kathryn Brown, Routledge Art History and Visual Studies Companions (Taylor & Francis Ltd, 2022), 88–89.↩︎

  4. Joyeux-Prunel, “Digital Humanities for a Spatial, Global, and Social History of Art,” 89.↩︎

  5. “An Approach to Institutional History and the Built Environment in Nazi Germany,” accessed October 5, 2026, https://www.getty.edu/news/dah_jaskot_knowles/.↩︎

  6. “An Approach to Institutional History and the Built Environment in Nazi Germany.”↩︎

Linking humans and data

Working on the Artist Book Critical Index (ABCI), I’ve already gotten to work with data I really enjoy: linked data, the semantic web, distributed knowledge graphs. I enjoy ontology and vocabulary creation and being part of building semantic frameworks that other organizations can then pick up and use.

Angela Dressen’s “Cultural Heritage Data for Research – An Introduction” covers semantic web work in the art history space with clear appreciation and understanding, but in the Linked Art section, it also presents the idea that with proper tools, you then don’t need data scientists in the museum space.1 The idea that if the structure’s in place and it’s easy enough to use, museums don’t need data professionals in permanent positions is part of why digital humanities projects fall short or become obsolete. When data projects are approached as short-term, quick-burst projects, they die out quickly. Not because the data isn’t good anymore or the tools are bad, but because there is no one cranking the engine to improve the data and move the project forward. If there’s one thing I’ve learned working on the ABCI, it’s that there has to be human energy for all aspects of the project, including the data handling and project maintenance.

The ABCI started as a Zotero library made by the Sloane Art Library’s now-retired manager, Josh Hockensmith, who is a book artist. He was making an index of reference works connected to artists’ books: where they were cited and on what page an image could be found. Graduate students were then assigned to the project and started expanding beyond UNC’s own collection by adding WorldCat links. It is a really unique, robust data set that could only come from human beings.

One of the key points Broman and Woo make in “Data Organization in Spreadsheets” is that the raw data should live in a different place than where it is analyzed and manipulated.2 This was one of the untidiest aspects of the original Zotero ABCI library. The workflow for photographing artist books was living in the same Zotero, and it was difficult to untangle verified entries from unverified ones, even when they were marked with workflow tags.

We also had to deal with missing data, the equivalent of what Broman and Woo talk about with leaving cells empty.3 The early ABCI entries had full metadata. But as the point became simply tracking citations between books and linking to the catalog entry at UNC or WorldCat.org, entries started having just author and title, with no standardization in capitalization, author name order, or which creators should be listed. And because the citation information had to live in Zotero’s notes field, which is a free-for-all of text, we had to figure out some constraints, along with using Claude Code, to pull the citation data out and attach it to the items it belonged to.

One of my favorite parts of the process has been creating ontologies and vocabularies. It’s modeling how the data should look in triple format, in our case Turtle, with an example, because often when you start doing an example is when you start saying, “Oh no, that data would be great to have, but we don’t have that,” or, “What do we call a construction method?” Luckily, I was able to piggyback off the work of the Book Arts Research Database4 and Opening Artists’ Books5 for reference.

Sometimes a tool becomes unexpectedly good at another job, in this case, metadata checking. One unexpected side effect of the ABCI has been pointing out where our catalog metadata was misentered or left out. More than once, the Sloane Art Librarian, Alice Whiteside, has asked me to use the tool to pull books with a particular construction method, only to find that a book is missing or mislabeled. If you are working with incorrect data to start with, you’re going to end up with incorrect data.

As for data I would like to work with in the near future, I’ve been fascinated lately by maps of crafters and craft spaces. Especially having read more of Brendan Keogh’s recent work about viewing video game developers as craftspeople, I’d like to make a network map of video game creators and the companies or specific games they’ve connected to. Art history already acknowledges that who an artist is taught by and where they have worked has a large influence on their oeuvre. This type of lineage study is not something I’ve encountered yet in game studies.

My first step for a network map of game artists/craftspeople would be to model one simple connection. I generally do not start in a spreadsheet but think with pen and paper about how the graph might flow and then start throwing it into Turtle triples. I would start with a relatively well-established indie or smaller-team game from a company where English is a primary language. From there, I would pick one creator in an art leadership role, like an art director or character designer, and work through their CV. Once I know what information I’m looking for, I’d break out the spreadsheet to gather everything about one person, translate it over, see how it works, and troubleshoot. Then I’d look to other sources of linked data I could link out to, like Wikidata. From there, whether or how to proceed to a larger scale would really depend on what the data revealed in the small model.


  1. Dressen, A., (2025) “Cultural Heritage Data for Research – An Introduction”, Open Library of Humanities 11(1). doi: https://doi.org/10.16995/olh.18710↩︎

  2. Broman, Karl W., and Kara H. Woo. 2018. “Data Organization in Spreadsheets.” The American Statistician 72 (1): 2–10. doi:10.1080/00031305.2017.1375989.↩︎

  3. Broman, Karl W., and Kara H. Woo. 2018. “Data Organization in Spreadsheets.” The American Statistician 72 (1): 2–10. doi:10.1080/00031305.2017.1375989.↩︎

  4. https://researchbookart.uicb.uiowa.edu/↩︎

  5. https://oab.lib.utah.edu/↩︎

What are we building towards?

For a recent class assignment to make a Collection Builder exhibit, I created an exhibition of the first 10 boss fights from the mainline Legend of Zelda video games, specifically the final blow in each boss fight (https://beeyop.github.io/zelda-death-blow/). What weapon has to be used? Who’s involved in the fight? What part of the timeline, via the Hyrule Historia, does it come from? This was an expansion of a previous project where I looked at repeat objects in the Legend of Zelda series (https://sydbauer.wixsite.com/scaling-stories/zelda ).

I immediately ran into some issues. I couldn’t get the YouTube links to show properly if I wanted to start them at a specific time. I also struggled for a while trying to figure out why a thumbnail wasn’t showing, only to discover that it was an errant capitalization. Frustrations aside, Collection Builder did a really nice job of creating a professional-looking digital exhibition space. For that, I think it fulfills a valuable niche.

I only had one major criticism of the Collection Builder exhibits we examined in class: all the websites felt the same. By the second collection I looked at, that sameness made me gloss over and lose interest in the content. The visual layout was pretty much identical, even with different themes and some custom CSS. I think this is indicative of a larger issue. I believe many cultural institutions view tasks like metadata curation as mechanical, logical chores. In reality, it is a fusion of artistic skills and data skills. If the visuals and experience don’t feel curated to the data, then it is a cute toy, not scholarship or a tool. Some of the exhibits we examined did have a cohesive feel and told a clear story, but I don’t know that they did more than a well-annotated photo gallery.

I think Collection Builder is a gift for smaller museums, organizations, and student projects as a tool for displaying work when you’ve got one, maybe two people working and there isn’t room to expand. In some environments, finding someone with the education and experience in both curatorial work and digital tools would be very hard. Hiring online is an option, but then you run into control issues and management duties. In a single-person or very small team space, hiring out isn’t saving any time or workload the way I think Collection Builder does. I think the well-written and well-organized guide does most of the work of making it a better alternative for that use case. Anytime I wanted to know how to do something with my collection, the guide had an easy-to-understand, easy-to-find, simple process. I have some background in using GitHub and VS Code, but I heard from other people in the class that they also appreciated how well thought out the guide is.

What concerns me is that every time I see a tool like Collection Builder that makes what seems to be a mechanical task, like cataloging, display, or access, easier, I see organizations pushing people to do more with less instead of hiring someone to do these things or paying people appropriately for an increased scope of their job. Budget issues often become the scapegoat, but that is no excuse. Most individuals’ budgets are equally, if not more, stressed than those of any organization they work for. That’s not Collection Builder’s fault by any means, but it is something to note, especially as we decide when to use what tools and what projects to pursue.

In Paige Morgan’s blog post “How to Get Your Digital Humanities Project Off the Ground,”1 Morgan heavily cautions against making a digital humanities project part of your dissertation. The current status of digital humanities projects in academia is reflected in Morgan’s own experience creating projects while working on a separate dissertation. Morgan notes there were times when the dissertation had to take precedence and the projects suffered. That shouldn’t have to be the case, but from what I have experienced and witnessed, not much has changed between when Morgan wrote the blog post in 2014 and today.

While the cautioning is absolutely valid, and a realistic way of looking at the field and the way academia treats digital humanities projects, I think this advice exacerbates the problem. It’s going to take some people who are willing to push back and say, “No, this is a valid form of scholarship,” to really upend the idea that the only valid way to present mastery over information or share scholarship is the often recursive ouroboros of academic paper and book publishing.

With the rapid pace at which people are expected to graduate, to write, to do, we’ve lost a lot of the time to reflect and a lot of the purpose of academic scholarship. Academia must slow the speed and return to a contemplative pace or start accommodating other modes of scholarship as equally valuable and equally valid (preferably both).


  1. Paige Morgan, How to Get a Digital Humanities Project Off the Ground, June 5, 2014, https://www.paigemorgan.net/how-to-get-a-digital-humanities-project-off-the-ground/.↩︎

Charting Japonisme

As an undergraduate, I had an idea for my senior independent study thesis that I couldn’t quite figure out how to realize. I wanted to create a digital collection of Japonist paintings from 19th century Europe. More specifically, I wanted to chart out just how quickly Japanese imagery (stylization, recreations, motifs, etc.) and goods (kimono, fans, ceramics, etc.) appeared in European paintings. I had lots of visual data – which is to say, I had knowledge of many works of art that would have fit into my project – and I had a pretty solid research question: just how many works of art fall into the category of Japonsime? The only issue is I had no idea how to even approach such a topic as the scope and methodology just felt too ambitious. Now that I am a masters student, I see how I could use data analysis and digital art history to make my project into reality. So, after six years of rumination, here is my proposal for how I could achieve my academic dream of realizing my project which I shall affectionately title Charting Japonisme.

La parisienne japonaise by Alfred Stevens, 1872.

Literature Review

In 2018 Van Gogh and Japan, Treaty of Kanagawa,

The Courtesan (after Eisen) by Vincent van Gogh, 1887.

Research Questions

Timeline of when it became popular, how prevalent it was, what areas it was most prevalent in. Connect that data to art dealers and track trade movement of real objects.

La collectionneuse au kimono vert by Frans Verhas, 1881.

Methodology

Scope of project to just paintings and just Europe (maybe even just France). One approach to keep this project feasible as a student would be to focus on a specific few artists. I am most notably interested in Vincent van Gogh and Claude Monet. I could use their catalogues raisonnés and chart exactly when they began incorporating Japanese objects and iconography into their paintings.

La Japonaise by Claude Monet, 1876.

Future of this project?

I miss doing this work!!!!!

Relevance Searching for Images Using Different Platforms

Google has been around since 1998, but I recently found out that Google Images has only been around since 2001. Even further, reverse image searching was only added as a function to Google Images in 2011. The internet seems so built around images, but search functionality is entirely built on text infrastructure. Finding relevant images with a Google search is a game of careful search engine optimization and it is a game that the user has to master. Finding relevant images from a search inquiry is a skill that we have come accustomed to, but are there other ways we can find images? Consider a museum as an analogy to consider alternative image search options. We may go to the MoMA looking to see Starry Night and Starry Night only. We can go to the help desk and inquire, “where is Starry Night?” and we would get an exact answer to find our image. This is akin to a traditional text-based image search inquiry. Consider instead someone who is interested in seeing late 19th century French landscapes and interiors. Upon inquiry, they will be delighted to know that someone at the MoMA has already curated an entire gallery of works that are relevant to their needs. Their inquiry is more broad, so with a traditional image search inquiry might produce a wide variety of results ranging in relevance. Importantly, in a traditional search, the user has to vet these images for relevance. In the museum example, the curator of the museum has already done the vetting. The museum has eliminated the possibility of finding irrelevant works. Intentionally curated image collections change how we are able to find relevant images.

For this blog post, I will explore how search image results vary depending on which platform the inquiry is made. The search platforms I will use are Google, the built in search function on the Museum of Modern Art website, and ChatGPT. I then will assess the results for their relevance to the inquiry, their ease of use, and any other noteworthy observations. For consistency of results, I will use the same search inquiry for all platforms: “late 19th century French landscapes and interiors.”


The Museum of Modern Art

Screencapture of Museum of Modern Art Map https://www.moma.org/visit/guide/map?location=501. Accessed September 13, 2026.
Screencapture from Gallery 501 https://www.moma.org/calendar/galleries/5695. Accessed September 13, 2026.

The Museum of Modern Art, like many museums with an online presence, have digitized the pieces from their on-display collection.


Google


ChatGPT

Take a seat. Please.

This week I explored the digital art history tool imgs.ai and got some interesting results. imgs.ai provides “a Web-based interface, and machine-learning-based backend that allows the end user to both descriptively and visually search arbitrary image dataset.”1 More simply put, it allows a human to guide an application using computer vision to find images in selected museum databases that are the most similar to an uploaded image, text prompt, or both. The idea being that the user will then continue to engage with more images by selecting from the suggested images that are “positive” or “negative,” furthering the search with this new information.2

The ability to mark negative results is where I hit my first issue: it wasn’t an option for me. This is likely because I was using the site without a login (getting one takes days for approval). While I understand the necessity of gatekeeping databases in the age of AI scraping and how intentionally using AI is fundamentally different from random bots shutting down your site, the irony of the website being protected being built on AI scraping images was palpable. How many of the models imgs.ai uses were built using the same tactics the required login was keeping out? Even if copyright was the driving force instead of defense against bots, how many artworks outside of these museum collections had their copyright violated to train the models to “see”? I am not anti-AI, but I think they are questions worth asking. A team that calls out “Transparency” as one of five “essential criteria”3 should say more about the black box components at work beyond naming the databases or models used.4 Minimally, it should give an explanation of why options are locked behind sign-up instead of forcing the user to guess.

I also wouldn’t be as harsh in my critique if imgs.ai as a tool had provided me an experience that felt more like what the article outlined. To show where imgs.ai gave me interesting results and where it fell short, let me walk you through my experimental searches.

I started with the image from Vermis I: Lost Dungeons and Forbidden Woods I digitized in my last post.5

A pixelated image of a skeleton kneeling and being hugged by a kneeling armored person.
[Scanned image from Vermis I]. plastiboo, Vermis I: Lost Dungeons and Forbidden Woods, 11th printing, 2026. Used here for educational and commentary purposes; no copyright infringement intended. All rights remain with the original owner.

I knew this wouldn’t necessarily be an easy image with its dithered graphics, but I thought it was fair to work with an image I am actively using in my art history study. While imgs.ai can only show results from the databases it has access to, unlike some other digital art history projects, it does not limit itself to a specific time period or type of art. So I didn’t expect it to return other video game related results necessarily, but I did expect it to be able to get an accurate read on the image’s general contents since testing it with an AI alt text tool had produced flawed but not totally off-base results.

imgs.ai has four feature extractors to choose from for each search, each with a different focus: “stylistic similarity,” pose, “raw color data,” and CLIP which allows combining an image with a text prompt.6

Results were mostly okay if not super useful until I switched to the pose extractor.

Well that’s a choice. There weren’t only but a variety of objects that had no relation to the pose regardless of the database used. The chairs would take on an added strangeness with my next search though.

I decided to try another image. One I took directly from the Smithsonian collection.

a pixelated title screen for a video game
Ed Fries. Halo 2600. 2010. Video game for Atari VCS, color, sound. Smithsonian American Art Museum. © 2010, Ed Fries. Reproduced for critical commentary on imgs.ai, the tool through which this image was retrieved; not licensed by the artist or SAAM.

The results were better but still not great. I only got results that were clearly connected to the search image but still novel enough to be useful when I added “videogame” to my CLIP search.

Screenshot of imgs.ai search results for "videogame" and Halo 2600 image in the MoMA collection, showing a grid of abstract and pixel-art thumbnails.
Screenshot of imgs.ai search results for the positive query “videogame” (image: Atari 2600 Video Chess box/screen) within the MoMA collection subset, showing 50 of 72,365 results. Author’s screenshot, 9 Sept. 2026.

All was well until I tried the pose feature extractor again.

an elaborate armchair, one of a pair
Pair of Armchairs. Late 17th–early 18th century. Carved and gilded walnut, with crimson and gold silk cannelé fabric (not original), Italian. The Metropolitan Museum of Art. Public domain.
an armchair with an unidentifiable beast depicted on the back cushion
Manufacture Royale, Aubusson (tapestry weaver). Armchair (part of a set of nine). Mid-18th century. Carved and painted walnut; Aubusson tapestry upholstery, French. The Metropolitan Museum of Art. Public domain.

Oh no.

Ohhhh nooooooooo.

I wracked my brain for the cause of this seating-based poltergeist haunting my results. Was it a similarity of a curve in the chair to the curve in the image? Then why were some of the EXACT SAME CHAIRS in the results from both starting images? Other more obvious connection images were not shared between results.

Away from the chairs, most results made sense as to why they were selected. They just didn’t provide anything useful beyond confirmation that yes, it has that color or a frame or someone in armor. Some images I found really intriguing, and they made me think of my image in a different way. It was most successful again when CLIP added texted to the search, in this case, “Skeleton.”

That was when I realized something important. While the point of imgs.ai is not to have an autonomous AI match images, but rather to include the human user in the research loop actively,7 I was doing the heavy lifting for the AI instead of with it. I was taking an image that seemed random to me and taking on the task of finding the connections and assigning meaning. In some ways, this is great. The human should be the one doing those tasks. But I was also struck that I could have done the same cognitive work and gotten the same benefit if the AI had served me completely random images from the collection and told me they were related to my image.

Two more images gave me additional insight into a major issue. Olivia Butler’s typewriter which appeared for both images…

a blue typewriter sits in a black open case
Olivetti Studio 46 Typewriter Used by Octavia Butler. Between 1974 and 1979. Plastic, metal. Anacostia Community Museum, Smithsonian Institution. CC0, public domain.

…and the immense amount of beads that showed up search Atari 2600.

a blue and gold bead on a black background
Bead, quintuple. 1550–1196 BCE. Glass, Egypt. Freer Gallery of Art, National Museum of Asian Art, Smithsonian Institution. CC0, public domain.

The computer wasn’t “seeing” the artworks as objects but as the images themselves. So not only was the background included but it was given as much consideration as the art. The tool appears to search hierarchically level parts, not the whole.

Perhaps if I had access to the GRAD-CAM to show me where the AI was seeing similarity,8 I would have had a richer experience, but either I could not find that feature or it was behind the login gate. Ultimately, the need driving the creation of the tool seems valid. But until OpenAI understands (not just consumes) Emma Stanford’s “A Field Guide to Digital Surrogates”,10 imgs.ai will be like building a chair with a staple gun: some chance of surprise success, maybe worth the experience, but you can’t make an Eames with it.


  1. Fabian Offert and Peter Bell, “IMGS.AI.: A Multimodal Search Engine for Digital Art History,” International Journal for Digital Art History, no. 9 (2023): 5.30, https://doi.org/10.11588/dahj.2023.9.91295.↩︎

  2. Offert and Bell, “IMGS.AI.” 5.30.↩︎

  3. Offert and Bell, “IMGS.AI.” 5.32.↩︎

  4. Offert and Bell, “IMGS.AI.”↩︎

  5. Plastiboo, Vermis I : Lost Dungeons and Forbidden Woods : Official Guide, ed. Michele Nitri, with Marco Cirillo Pedri, Vermis 1 (2023; 11th printing, Hollow Press, 2026), Paperback (Regular Edition).↩︎

  6. Offert and Bell, “IMGS.AI.”↩︎

  7. Offert and Bell, “IMGS.AI.” 5.32.↩︎

  8. Offert and Bell, “IMGS.AI.” 5.35.↩︎

  9. Offert and Bell, “IMGS.AI.” 5.36.↩︎

  10. Emma Stanford, “A Field Guide to Digital Surrogates,” in The Routledge Companion to Digital Humanities and Art History, 1st ed., ed. Kathryn Brown (Routledge, 2020), https://doi.org/10.4324/9780429505188-19.↩︎

« Older posts

© 2026 Beyond the Women's Building

Theme by Anders Noren — Up ↑