Image: Woman punch card operators working on Roberto Busa’s Index Thomisticus. Back left: Rosetta Rossi Bertolli; bottom right: Livia Canestraro. CC-BY-NC. Thanks to Melissa Terras, “For Ada Lovelace Day,” 2015.

I am surprised and thrilled that someone thought it worth nominating me for the Roberto Busa Prize, and overwhelmed to have been placed by ADHO in such illustrious company, fully aware that there is so much superb work in our community deserving of this recognition.

All knowledge is relational. It is fabulous to have recognition of scholarship that emerges from an intersectional perspective and is embedded in process: from making things that try to leverage technology in new ways, trying and failing, and yet continuing to try to make a difference to how we work and to enable us to create and share knowledge together, in better ways, in a changing world. For such work, collaboration is essential, which is to say it’s all about people.

My absolutely stellar colleagues here at LINCS gelled into a phenomenal team, even though we came together remotely, many of us for the first time, at the height of the pandemic, to build an infrastructure for linking scholarly knowledge across disciplines. The core LINCS team is at the heart of a growing network of scholars, students, and professionals who are, thanks to the combined efforts of these brilliant people, able to engage in serious exploration of the capacity of linked data to enhance cultural research and cultural experiences. The CWRC virtual research environment has involved 200+ wonderful people (and counting, since our credits need updating before we launch this spring as an instance of the LEAF software framework). And my belief in the magic of producing knowledge collaboratively in new digital ways grew out of formative experience as a new scholar in the Orlando Project, whose sterling participants include as active contributors ~150 students.

The point isn’t the numbers but the sense of expanding networks: there are overlaps between projects and roles, so the counting isn’t exact, indeed cannot ever be exact, because there will inevitably be inadvertent omissions, and because the strands of influence just keep linking out. I’m so grateful for all the rich relationships that infuse this work, amazed at what we’ve created and learned together, proud of those who’ve put it to work in other contexts and fields.

And there are so many other relationships, other people to whom credit is due. Mentors who bolster my confidence. Models whose thinking and practices inform and inspire mine. Co-authors and co-presenters who help me see things differently as we struggle to express ourselves together. Students and colleagues in courses and workshops whose reactions and questions spark such insight. Colleagues who carry on and remain dedicated despite the deplorable precarity of the conditions in which they work. Collaborators on projects led by others, in which I have learned so much, including Collective Biographies of Women, INKE, Lesbian and Gay Liberation in Canada, NovelTM, Staging Better Futures/Mise en scène de meilleurs avenirs, The People and the Text, Voyant,The People and the Text and the Women Writers Project. The creators and activists whose work reflects, reimagines, and reshapes the world we live in.

So many other projects that have worked with CWRC and LINCS, and the incredible array of digital humanities initiatives from around the world, working collectively to figure out how to make and share knowledge differently in this age of incunabula. Those in university administration—at the universities of Guelph, Alberta, and many partner universities—as well as funding organizations—CFI, CANARIE, DRAC, Mellon, SSHRC—who get that this work doesn’t fit the old moulds, who strive to remove barriers, and who develop new models. Colleagues who keep scholarly organizations like CSDH, ACH, ADHO, ACCUTE, ACQL, MLA, BWWA, VSAWC, and NAVSA ticking along so we have collegial spaces in which to connect. Colleagues on panels and boards who help me grasp the bigger picture and alternative views. Partners in GLAM and the knowledge ecosystem, like CRKN, CHIN, and Library and Archives Canada, who share the vision of what is possible if we work together.

Everyone in this particular web who is motivated by a sense of how the complexity and value of human cultures and histories—especially of women, BIPOC, colonized, 2SLGBTQI+, impoverished, and otherwise marginalized people—could register in digital space in different, more vibrant, nuanced, contextualized, respectful, and equitable ways.

When designing and building a web application, ensuring that it is responsive is paramount. A responsive application looks good and functions well on all screen sizes and devices. LINCS applications are being designed to be viewed in a wide range of ways: from tablets to laptops to whiteboard-sized interactive screens. It can be quite hard to achieve this level of responsiveness, but with the help of CSS tools, techniques, and frameworks, the task becomes a lot easier...

In my first meeting this summer as a data science research assistant, we each followed our personal introductions with declarations of our favourite ice cream flavours. Mine was and continues to be Häagen Dazs’ Strawberry Cheesecake ice cream, and I was pleasantly surprised to learn someone else on the team felt the same. However, the biggest surprise was learning that someone enjoyed microwaving their ice cream to change its texture. At that point is it still ice cream? Is it soup? Or a milkshake? What even counts as ice cream? ...

I’ve always found that context changes everything when learning something new, especially when it comes to understanding why that something matters. The first example I can think of is how, for all the general chemistry courses I’ve taken, the concepts never really clicked, nor did I see why I had to learn them. Four of these courses later, I wasn’t very excited to take biochemistry, but when I did, I couldn’t believe how much of a difference it made to have a real context: the human body, where chemical reactions happen for a reason. Suddenly, the abstract became pretty important—I could see how it all fit together, and in turn, my understanding of general chem probably increased threefold. Rest assured, this blog post is not going to be about chemistry. Rather, it’s about how the same phenomenon occurred this summer, when working on the Orlando Project changed the way I think about data...

LINCS is using ResearchSpace as a platform for exploring relationships in interlinked cultural datasets. With ResearchSpace, researchers can browse, search, and visualize data in the LINCS datastore. In summer 2022, I was part of a team that was developing new features for LINCS’s version of ResearchSpace.

Our team was a collaboration between contributors with a background in user experience (UX) and contributors with a background in software development. We worked in tandem: the UX group recommended features to improve the experience of using the web application. These recommendations were turned into tickets in GitLab. The tickets described what the desired end product would be, and it was up to the developers to determine how to achieve this goal. The development lead shared tickets out among the software developers, dividing them up based on what would be required to build the suggested features...

If you’ve ever listened in on a technical conversation between computer scientists, you might’ve heard them refer to something called an Application Programming Interface (API). What exactly is an API? Let’s break it down...

The UX team has been conducting user research on LINCS tools to get them ready to move from development to production. So far, we have completed card sorts, usability tests, surveys, and interviews. This research has provided us with a wealth of information. However, if we want to translate what we’ve learned into meaningful, productive changes to the tools’ designs, we must keep actionability at the centre of our research practice...

When I began my first co-op placement, I had no idea how software development worked in a professional environment. Previously, my experience had only been in the classroom, where  my classmates and I developed software for assignments. When I moved into a professional context, I was exposed to new ways of collaborating, among them stand-up meetings, or stand-ups...

As an English student, I was always told to keep my writing concise. Doing so was often easy because I could assume that the person reading my work would be an English scholar, so their expectations of my writing and the knowledge they brought to it would sit within a very specific range. In this way, I trained myself to default to an academic tone and level of complexity and to produce writing that was comparative and analytical.

This summer, however, as a member of the LINCS documentation team, I worked on an entirely different kind of writing: user guides and instruction manuals for the many software tools developed or employed by the project. To begin writing documentation, I first had to relearn how to write...

During my time at LINCS, the UX team has laid the groundwork for implementing an intuitive and effortless user flow for ResearchSpace. To accomplish this, we have conducted numerous user and usability tests, interviews, and card sorts.

Working on ResearchSpace was my first real experience in the world of UI/UX. It was also my first time working on a design team, and I was blown away by the talent of my peers...