The following interview was conducted by Sam Goven, a master’s student in Journalism at KU Leuven, with Andreas Ketele, BiblioTech Hackathon participant. Andreas is a master’s student in Digital Humanities and works as legal counsel for the Agency Opgroeien. Andreas’ team, Inked and Stamped, worked with the postcards collection. You can learn more about the team’s work by having a look at their project poster in the BiblioTech Zenodo community and by visiting their project website.

The BiblioTech Hackathon is a 10-day event organized by KU Leuven Libraries and the Faculty of Arts. Students, researchers, and staff members of KU Leuven worked in multidisciplinary teams with digitized collections from KU Leuven Libraries. The theme of the 2026 edition was travel, which was reflected in the selected datasets: historical postcards and historical travelogues. More information about the hackathon and its results can be found on the BiblioTech 2026 website.

To start off, could you tell us a bit about your academic background? Had you participated in a hackathon before, and what drew you to this one?

I have a degree in law and have been working for a few years now. At the same time, I’ve always been very interested in IT and programming, so I was really happy when I discovered that there is an advanced master’s program in Digital Humanities. The program is a collaboration between the Faculty of Engineering Science and the Faculty of Arts, and it is specifically designed for people with a humanities background who want to learn how to program and how to use computational methods to strengthen their own field. For me, that felt like a perfect match, and I really enjoy it.

During the program, we learned about the hackathon and were encouraged to participate. What interested me most was the chance to apply what we were learning and really put it into practice. The program does include practical components, of course, but there is still so much more to learn when you can actually work with a large and complex dataset like the one we received during the hackathon.

This was also my first hackathon. I had done some programming before, but I had never participated in a hackathon.

Your team won the prize for best enrichment. Could you briefly describe your project?

We worked with the postcard dataset. One of the first things we did was index the postcards based on their use of color. From that, we were able to derive several insights, for example, who was printing in color, when this happened, and how that evolved over time. In addition, we made the collection searchable by the places depicted on the postcards. Finally, we extracted a number of postage stamps, allowing users to explore those in more detail as well. This part of the project was still in progress: we had several additional features in the pipeline, but they were not fully completed yet, so we weren’t able to deliver everything we had initially envisioned.

The final outcome is a website where users can explore both the postcards and the postage stamps, combined with a poster presenting our research findings.

Did you have a clear idea of what a hackathon actually is? What were your expectations, and did you feel that, with your background in Digital Humanities, you had the skills needed to get started?

Yes and no, let’s put it that way. In general, I try not to have too many expectations and to step into things with an open mind. As for having the necessary skills, yes, to some extent. In the sense that I had already done a bit of programming.

But for me, having the necessary skills often sounds like you’re expected to know everything already and be able to build a complete project in five minutes. And what I really liked about this hackathon was that this wasn’t the case at all. It was very explicitly communicated that this was also a space to learn, and that’s exactly what we did. We learned a lot along the way, which made the whole experience even more enjoyable.

At the ‘Meet the Data, Meet the People’ event, you were introduced to the data for the first time. What was the brainstorming process like? Did you feel overwhelmed with ideas, or was it clear early on which direction you wanted to take?

It was mainly a lot of different ideas coming together at first. Michiel, our team leader, did a great job of getting the conversation going, and from there we continued brainstorming and gradually exploring the data in more depth. The dataset itself was enormous, around 200 gigabytes, which is not something you can fully grasp in just a few hours. So we took time to really dig into it after the event and see what was possible.

What I really enjoyed was that process of exploration. We reflected on our ideas and experimented a lot, and that’s exactly what a hackathon is about for me: discovering possibilities along the way. If you already know everything in advance and the only thing left is implementation, you might actually miss interesting directions.

As we explored the data together, we also discovered each other’s strengths, which is one of the nicest aspects of working in a group like this. Everyone in the team was genuinely motivated, and there was a strong sense of what can we create together. That kind of shared energy is really the magic of a hackathon.

Could you describe your role in the project? Was it in line with what you were expecting?

I mainly contributed by programming and working on the content. I supported others whenever I could and asked for help myself when I needed it. Overall, it was very much a team effort: we shared tasks and built on each other’s strengths.

How would you describe the entire process from start to finish? What was your own experience like?

It was a fantastic experience. I’m usually not someone who uses very strong words, but this really was fantastic. Programming on your own can be enjoyable too, you can build interesting things that way, but here we were working as a group of highly motivated people. We collaborated very well and benefited enormously from all the support we received along the way.

That support was really essential: the infrastructure, the help, the tips, and the exchange of ideas. It made a huge difference, because you learn so much and can really move forward. A concrete example of that support is my experience with an AI model. At one point, I was working on a specific task, and the first steps went well. But when I reached a stage involving dimensionality reduction, the process ran for five minutes and then crashed with an error saying it was trying to allocate 40 gigabytes of RAM. Having access to a supercomputer where you can offload that workload is incredibly valuable, and frankly, also really exciting.

What I also loved was, on the one hand, building something ourselves, and on the other hand, seeing the final presentations from the other teams. I was genuinely impressed by what the other teams had created.

As an outsider, I also had the feeling that there was a lot of support around the hackathon, and that the people from the organizing team put a great deal of passion into it. That really stood out to me, whenever I spoke with them, you could hear how genuinely enthusiastic they were.

That’s actually something I’d really like to add as well, because I’m very grateful for it. I’ve also told them this directly: for me, this has been the best experience of my entire KU Leuven education so far, and I’ve studied in Leuven for several years. Being encouraged to explore, and being in such a positive environment where you can really feel that everyone wants to move forward, was incredibly special. It felt almost magical.

You’ve mentioned several times that you learned a lot during the hackathon. Which specific skills or aspects do you think you’ll be able to apply in the future?

Well, I’m already working on projects using the tips and techniques I picked up during the hackathon. I also received additional advice from some of the participants during the final presentations that I want to look into. So I do already have a few ideas I’d like to explore in the future.

The only downside, and I say this partly as a joke, is that now I’ll have to do it on my own (laughs).

Were there any roadblocks during the process? Did you run into things that didn’t go as expected, and how did you deal with them?

Of course, everyone in the team ran into obstacles at some point. And how did we deal with that? Partly by doing our own research, partly through trial and error, and partly by asking for help. Looking back, we probably could have asked for help even more often. Once you realize that something really isn’t working after a while, it’s important to look for a different approach.

That’s also one of the things I really like about a hackathon: you’re allowed to hack, not in the sense of breaking into things, of course, but in the original sense of creatively finding ways to make things work.

Another challenge was combining the hackathon with my situation as a working student. It was made very clear in advance that participation was possible for working students as well, and that the duration of the hackathon was designed with that in mind. Still, it was quite intense, and I ended up putting in a lot of hours. That was definitely challenging, but then again, if everything went perfectly smoothly, it wouldn’t really be a hackathon. I learned a lot from that experience too, and I’m very grateful to all my teammates for the great collaboration.

As a final question, what advice would you give to future teams taking part in a hackathon?

First of all, I would say: enjoy the experience, and make sure you set aside enough time. That’s really important. We had the incredible luxury of being able to ask questions and get support. We did make use of that, but looking back, I think I could have done so even more, so I would definitely encourage future teams to take full advantage of that opportunity.

It’s also crucial to communicate well within your group, so that everyone is working towards the same goal and pulling in the same direction. That’s not always easy, but it really makes a difference.

And finally, don’t be afraid to experiment. A hackathon is exactly the right place to try things out and explore ideas!

As part of our blog series, “Stories from the Research Trenches,” we often invite researchers and colleagues to share their personal experiences. For this post, we are delighted to hand the floor to Bonnie Varlet from the KU Leuven Cultural Studies Research Group, who offers a closer look at how she integrates Zotero into her research workflow.

Written by Bonnie Varlet

New technology, like machine learning systems, are being deployed across a wide range of institutional backgrounds. Hospitals use it to flag diagnoses, and archives use it to catalog their collections. Modern machine learning has made great leaps in its capabilities. However, these tools do not exist in a vacuum.

My research looks at what governs the relation between institutions and the technology they use. For example, when a machine learning system is introduced into a new operational environment, it changes workflows, changes what skills are required, and creates new dependencies that did not previously exist. Validation processes that were designed for human-scale output volumes become inadequate when a system can produce ten times more at the same time. Accountability structures built around individual judgment become harder to maintain when outputs are generated algorithmically. At the same time, organizations also change technology. Institutional priorities shape which systems get acquired and how they are used, and informal workarounds created by staff can become de facto operating procedures. The system produced by this process is often meaningfully different from the system initially deployed.

These processes do not happen independently. They influence each other; it is iterative, and it compounds. There is currently no widely adopted methodology for tracking this relationship in a way that is observable in comparable and replicable terms. Most existing research either examines technology deployment in isolation or analyzes governance structures without tracing their operational consequences. This remains largely unmapped, which makes it difficult for organizations, regulators, and researchers to fully understand how technology and institutions interact in practice. My work aims to help develop a way of systematically observing these interactions as they take shape in real operational contexts.

Tackling a project like this, especially my first one done independently during my Fulbright, was also a lesson in how small logistical problems can get you off course. Over the course of the project, I collected tens of papers, books, website links, and other sources. At the start, when it was only a couple of papers, it was manageable, but as the project matured, it became increasingly difficult to stay organized. This became particularly challenging given the breadth of the topic, which required me to move between technical material, governance literature, and case-based examples.

At that point, I was lucky to have resources available through KU Leuven, such as the Artes Research team, where I was introduced to tools that could help manage my workflow. I decided to try Zotero, which was easy to set up and start using immediately. What changed right away was that I stopped getting lost in my sea of sources. All my papers, books, and links were kept in one place dedicated to my project, and I did not have to go back and look up publication details because the browser extension stored that information when I saved a new source.

As I explored Zotero further, I also shifted how I organized my work. Because it makes it easy to tag and sort sources, I grouped them in the manner in which I used them. Sources used for case studies were given a case study tag, while sources that provided foundational knowledge were grouped separately. Since my project is broken up into different parts, this made it easier to see where I was pulling information from and how it influenced my analysis. In a project that tries to trace relationships between governance decisions and technical systems, being able to clearly track how different types of sources contributed to different parts of the argument was particularly useful.

I also began annotating and brainstorming directly within the same program, instead of splitting my workflow across multiple tools. For example, I would highlight a quote in a source, save it, and add a note explaining how or why it was useful. This made it easier to trace my thought process and how I arrived at certain conclusions, both for myself and in the final project.

Looking back, I wish I had reached out for help managing my workflow sooner. Not only with this specific software, but also with the more general question of how to structure a research project of this scope. I spent a significant amount of time at the start recreating approaches to organizing my work, rather than focusing on the project itself.

I would not treat exploring research management tools as a last resort. No matter the field, the people around you have likely encountered similar challenges and found better ways to address them. Trying something new partway through a project should not feel like a disruption. In my case, it was what allowed the second half of the project to go substantially better than the first, and made it easier to carry out research that depends on systematically tracing complex relationships between institutions and technology. It also made it possible to more clearly trace how different sources, ideas, and cases connect—something that is central to my research itself, which focuses on understanding how relationships between institutions and technology take shape over time.

The following interview was conducted by Sam Goven, a master’s student in Journalism at KU Leuven, with Luisa Ripoll-Alberola, team leader of the BiblioTech Hackathon project Captacats. Luisa is a PhD candidate at Leipzig University working on the Horizon Europe funded MECANO project. Luisa’s team, Captacats, worked with the travelogues collection. You can learn more about the team’s work by having a look at their project poster in the BiblioTech Zenodo community and by visiting their project website.

The BiblioTech Hackathon is a 10-day event organized by KU Leuven Libraries and the Faculty of Arts. Students, researchers, and staff members of KU Leuven worked in multidisciplinary teams with digitized collections from KU Leuven Libraries. The theme of the 2026 edition was travel, which was reflected in the selected datasets: historical postcards and historical travelogues. More information about the hackathon and its results can be found on the BiblioTech 2026 website.

Congratulations again on your team winning the prize for most original project! To start, could you tell us a bit about your background, what first interested you in the hackathon, and whether you had participated in one before?

I’m currently a PhD student in Digital Humanities, working on the MECANO project. I had never participated in a hackathon before, but I knew that I wanted to take part in one at some point. There’s a very large Digital Humanities hackathon in Helsinki every year, with five or six different datasets, but participating there can be quite expensive.

While I was doing a research stay here in Leuven, I learned about the BiblioTech Hackathon. It really felt like the stars were aligning, because it was the perfect situation. As I mentioned, I was already thinking about joining a hackathon, and having the opportunity not only to participate but also to be a team leader was exactly what I was looking for. It allowed me to take part in a Digital Humanities activity in a more informal setting, which I really liked.

Could you describe your project and your output in a nutshell?

We created a prototype web visualization called ShipAdvisor, which is loosely inspired by modern platforms like TripAdvisor, but focused on historical Mediterranean travel routes. Using travelogues from the eighteenth and nineteenth centuries, the tool allows users to navigate different routes and see how travelers at the time rated places and journeys.

Through the visualization, users can explore which routes were most popular and how perceptions of safety and danger varied across regions. These perceptions were shaped not only by environmental factors such as weather, but also by historical phenomena like Mediterranean piracy. In terms of design and approach, we drew inspiration from digital humanities platforms such as ArcGIS StoryMaps and Itiner‑e.

You mentioned that you were the team leader in your group. What did that role involve, and was it in line with what you expected? Did you find it difficult to lead the team throughout the project?

I have to say it was actually super easy. I was very, very lucky with my team, they were all extremely motivated. Supporting them felt very natural and light. We had quite a lot of meetings during the process, but it never felt forced; everything just happened quite organically.

As a team leader, I didn’t want to take up too much space. I really wanted the group to feel horizontal and collaborative. However, in the first few days, when people were still a bit shy, I think it helped for the team leader to propose ideas, bring different ideas together, and guide things slightly in that sense. Beyond that, my role was more about offering support, often acting as a bridge between the participants and the experts. Before reaching out to the experts, I was there to help where I could.

Overall, it was, as I said, very easy, and it never felt like an artificial hierarchy or like I was in a superior position. It really felt like teamwork.

At the ‘Meet the Data, Meet the People’ event, you were introduced to the data for the first time. How did the brainstorming process go?

At the beginning, we had four or five main ideas. Our approach was to take some time after the first day to reflect on them individually, and then meet again the following Monday to make a decision. During that meeting, we decided to go with the idea of ShipAdvisor, mainly because it allowed us to integrate many different elements.

For example, we could look at which routes were more affected by piracy, which was a particular interest for some of the team members, while others wanted to work with illustrations. The concept really allowed for different approaches to come together within the same interface.

At first, it can feel a bit overwhelming, you think, I need to produce something, but I’m not yet sure what that will be. But because everyone in the team was so motivated, we ended up arriving at a solid idea quite naturally.

What kind of audience did you have in mind when working on your project and the website? Who should be able to use it?

We mainly had the general public in mind. We didn’t want the website to require any specific background knowledge, whether technical or academic. The idea was that anyone could use it, people who are simply curious and want to explore the corpus in a different way.

Did you run into any problems during the hackathon, and how did you tackle them?

File coordination was probably the trickiest part. At the beginning, we planned to use all the infrastructure the library was offering, such as the computing cluster. In the end, though, we didn’t really use it. One reason was that the team had different levels of technical expertise, and for some people the computing cluster felt like too much to handle. As a result, everyone ended up working in their own way and sharing files through the Teams group instead.

That approach worked, but it wasn’t always ideal. At times it felt a bit overwhelming to navigate, because we had many documents and different versions circulating. Sometimes people were working in parallel, and you had to wait for the latest version from a teammate before you could continue your own work. Our file‑sharing setup certainly wasn’t the most structured solution, but in the end it worked for us.

You mentioned that this was the first hackathon you participated in. Do you feel you picked up any new skills along the way, and how might you use them in future research?

As a PhD student in Digital Humanities, I mainly work with text analysis. My thesis focuses on the reception of ancient authors in academic prose and academic discourse, so my work is very text‑based. Before this hackathon, I had never really worked with geographical data.

That made this project especially interesting for me, because in my own research I don’t often have the opportunity to work with spatial data. The hackathon gave me the chance to explore that a bit, experiment with different tools, and see how geographical data could be integrated into a digital humanities project.

What kind of advice would you give to someone who might be hesitant to participate in their first hackathon?

I think one of the biggest insecurities people often have is feeling that they don’t have enough technical skills to participate. What I would say is that the support provided by the library and the pool of experts was truly incredible, you were never really on your own. You were always supported, both by the experts and by your teammates.

People with less technical experience found other important roles within the team. That could be doing more close reading, contributing to the final analysis, or working on the design of the poster. I would definitely encourage anyone who feels insecure about their technical background to take part. First of all, you learn a lot. Second, as I’ve said, you’re never alone, you’re very well supported by both the experts and the team. And finally, even if you don’t feel fully comfortable at first, you will definitely find meaningful ways to contribute to the group.

And what kind of advice would you give to a future team leader of a hackathon team?

I would say: don’t stress too much. I remember feeling quite insecure at times about our final outcome, but in the end, whatever you produce is going to be fine. In reality, the hackathon is meant to be fun, and not a competition.

What really matters is not the end product, but the process: working together, learning new things, and enjoying the experience. That’s what makes it valuable.

The following interview was conducted by Sam Goven, a master’s student in Journalism at KU Leuven, with Dawn Zhuang, BiblioTech Hackathon participant. Dawn is currently the project manager and data coordinator for the research project RegInfra (Regionalizing Infrastructures in Chinese History). Dawn’s team, W@nder, worked with the travelogues collection. You can learn more about the team’s work by having a look at their project poster in the BiblioTech Zenodo community and by visiting their project website.

The BiblioTech Hackathon is a 10-day event organized by KU Leuven Libraries and the Faculty of Arts. Students, researchers, and staff members of KU Leuven worked in multidisciplinary teams with digitized collections from KU Leuven Libraries. The theme of the 2026 edition was travel, which was reflected in the selected datasets: historical postcards and historical travelogues. More information about the hackathon and its results can be found on the BiblioTech 2026 website.

To start off, could you tell us a bit about your academic background? Had you participated in a hackathon before, and what drew you to this one?

I’m currently working as a project manager and data specialist in the research group Regionalizing Infrastructures in Chinese History (RegInfra). My role combines digital methods with humanities research. I graduated from the Master in Digital Humanities three years ago, and that’s when I participated in the first edition of the BiblioTech Hackathon, in 2023.

That experience was a lot of fun, and I learned many new skills. It helped me see how the digital methods I learned during the program could be applied in a real project setting. On top of that, I made new friends throughout the hackathon, which is one of the main reasons I wanted to participate again this time.

On a more personal note, during the previous hackathon I worked with the postcard collection, and I noticed that the dataset was reused this year. I was curious to see how other groups would approach it. This time, I chose to work with the travelogue dataset, since it relates to the same overall theme. In a way, it felt like a continuation of an ongoing project.

Your team won the prize for best visualisation. Could you briefly describe your project?

We chose a small‑data approach and built an interactive map based on it. Starting from the travelogues dataset, we selected a small part of the larger corpus, specifically three volumes of The Book and the Land. We then visualized and mapped the routes described in those texts, as well as the stories that unfold along the way.

The result is an interactive map where users can click on nodes and routes to explore the journeys. Through this interface, they can see extracted illustrations along with their contextual information, which helps connect the visual material to the narratives in the travelogues.

As you mentioned, you had already participated in the first edition of the BiblioTech Hackathon. What were your expectations at the start of this one, and did you feel well equipped for the project?

Because techniques and AI have developed so much in recent years, I expected to learn even more this time, especially since the methodologies have evolved as well. I was also working with a different dataset, so overall I was really looking forward to trying out new approaches and learning new things with a different group of teammates.

At the same time, I did feel well equipped. During the first hackathon, I was still a student and everything felt very new to me. Now I already have some working experience with digital projects, and I can really see how my skill set has grown. I felt more confident this time and was happy to realize that I was able to take on more complex tasks.

At the ‘Meet the Data, Meet the People’ event, you were introduced to the data for the first time. What was the brainstorming process like? Did you feel overwhelmed with ideas, or was it clear early on which direction you wanted to take?

I’d say that during brainstorming you always get little sparks of ideas here and there. In our team, we had people from very different backgrounds, linguists, historians, and AI experts, and everyone just shared what they were thinking. At our first meeting, we didn’t go through the entire dataset yet, and some of the initial ideas turned out to be a bit too ambitious or not very practical in the end.

Still, I think the general direction was already quite clear early on. During the brainstorming phase, we decided fairly quickly that we wanted to work with an interactive map, and in the end that’s exactly what we managed to accomplish. After the weekend and one of the training sessions, we had an in‑person discussion where we exchanged our observations about the dataset and then pinned down a more practical pipeline and timeline to work with.

What’s interesting is that during the brainstorming itself, none of us really knew yet how we were going to do it. And somehow, through discussion and experimentation, it all came together. It’s a bit of a magical experience.

Could you describe your role in the project? Was it in line with what you were expecting?

I’d say it pretty much aligned with my expectations. I see myself as a digital humanities enthusiast, and through my experience I’ve become familiar with a range of tools and platforms that can help achieve different kinds of results. Within the team, I mainly took on a supportive role, contributing from the early exploration of the dataset to deciding which direction we should take.

I also have some experience with web design, so I ended up putting most of my effort into building the final webpage. Overall, I like working on different aspects of a project: trying out new techniques, moving between tasks, and supporting my teammates wherever needed.

Did you face any problems or roadblocks that you had to overcome during the project?

I think the most challenging part was moving from the initial idea to something concrete and practical. Before this project, none of us had experience linking data to a map and making it fully interactive. So while the concept was clear, the question was how we could actually realize it, what tools or platforms we could use, and how to build everything within the limited time we had.

We spent quite a bit of time and energy figuring out how to translate our idea into a realistic workflow and deciding what was feasible within the time constraints. I’d say that phase, moving from the blueprint to an actual work plan, was definitely the toughest part of the project.

Did you face any technical problems along the way, situations where things didn’t work as you had expected?

Initially, we wanted to retrieve the dataset directly from the ManGO platform. I tried running the code within the HPC environment, but I ran into a few issues. I then posted my question to the expert pool in MS Teams, and I received a lot of help.

The support was also very timely, I posted my question in the morning, and by the afternoon there was already a working solution. The expert team really provided solid support, which made a big difference in helping us move forward.

You already mentioned that during your first hackathon you picked up a lot of new skills. Did you have the same experience this time, and how might you use those skills in future projects?

Yes, definitely. I learned a lot from this project as well. For me, working with geo‑referencing and data conversion was completely new, and it’s actually quite relevant to my current work. I can definitely see myself using these skills in future research projects or for creating other visualizations.

Although our project didn’t ultimately rely on the HPC environment, I did participate in the training sessions and did some exploration on my own. I really appreciated the opportunity to work within that environment, especially because future projects I’m involved in will likely have some connection with the HPC. So for me, it was very good practice and a valuable learning experience.

What kind of advice would you give someone who is participating in their first hackathon?

I would say: think bold. There’s a lot of support available, and you’re surrounded by a great team of experts who are there to help you. If you allow yourself to think ambitiously and take a few risks, you’ll be surprised by how much you can accomplish by the end.

Lastly, how would you describe your overall experience?

For me, it was truly inspiring and very enjoyable. And something I didn’t mention earlier is that I really made good friends through the hackathon and learned a great deal from my teammates, as well as from the other groups. That’s a very precious takeaway for me.

The following interview was conducted by Sam Goven, a master’s student in Journalism at KU Leuven, with Roberta Pireddu, team leader of the BiblioTech Hackathon project PostScript. Roberta provides academic support for the Master in Digital Humanities at KU Leuven. Roberta’s team worked with the postcard collection. You can learn more about the team’s work by having a look at their project poster in the BiblioTech Zenodo community and by visiting their project website.

The BiblioTech Hackathon is a 10-day event organized by KU Leuven Libraries and the Faculty of Arts. Students, researchers, and staff members of KU Leuven worked in multidisciplinary teams with digitized collections from KU Leuven Libraries. The theme of the 2026 edition was travel, which was reflected in the selected datasets: historical postcards and historical travelogues. More information about the hackathon and its results can be found on the BiblioTech 2026 website.

Congratulations on winning both the first prize and the public’s favorite! Can you tell me a bit about what first drew you to the hackathon, and have you participated in one before?

I hadn’t participated in a hackathon before, but I had organized a small one myself. It was for a project on Artificial Intelligence and its application in the cultural heritage sector. I knew a lot about the organizational aspects, but not much about how to actually participate in a hackathon. What I mainly did then was observe the other groups: what they were doing and how they came up with their projects. So I was mostly involved from the sidelines.

As for why I participated: I’m currently praktijkassistant and teaching assistant for the Master in Digital Humanities, and digital humanities students are an important target group for the BiblioTech hackathon. Taking part myself allowed me to work on a project together with the students. I also already knew the postcard collection, as I had worked with it in the past, and I thought it would be nice to create something new using that material.

And your own background is in Digital Humanities as well?

Yes, that’s right. I studied Digital Humanities in Leuven, and before that I studied history, more specifically medieval history, so my background is very much in the humanities. I’ve mainly worked with heritage collections, like the ones that were used for this hackathon.

I already mentioned you won the first prize with your project. Could you describe it in a nutshell?

Our team worked with the postcard collection, which is a very large one, and visually very attractive. It’s rich in information, with a lot of detail in the metadata, but because of its size it can be quite difficult to really explore all of those details.

What we wanted to create was a kind of website or digital space where people could explore the collection more easily and from different perspectives. We chose three main perspectives. One of them, for example, is a map, where users can see the locations represented in the collection and then zoom in on the details. On the website, users can also explore specific elements, like all the trains in the collection, all the cars, parks, and so on.

In addition, we created a crowdsourcing section. We wanted to include user participation so that the collection could be enriched with additional information. For example, on the back of the postcards there are greetings, and we wanted to allow users to transcribe or translate those messages so they could be added to the metadata.

You were the team leader of your group. Was this role in line with what you had expected?

I expected that I would need to give structure to the team: define the focus of the project, set concrete steps, and remind everyone of deadlines. In the end, though, everything developed very organically and smoothly, and I was really happy with how it worked out.

At the ‘Meet the Data, Meet the People’ event, you were introduced to the data for the first time. How did the brainstorming process go?

At first, it wasn’t very clear what specific skills everyone could bring to the project, or how we should approach such a large collection. That led to a lot of questions: what do we actually want to do with this collection, and what do we want to highlight?

In the beginning, we had many different ideas. We thought about working with the colors of the postcards, or focusing on locations, and that’s when the idea of using a map came up. There were a lot of possibilities. At a certain point, though, we decided that we really needed to look more closely at the dataset, see what was actually there, and then make a decision. That happened a couple of days after the opening event. We had some time to reflect, explore the data, and then settle on a clear approach.

Was it difficult to decide in which direction you wanted to go?

A bit, yes. But in the end, the direction really emerged from what we actually found in the data. As I mentioned before, we initially wanted to work with color, but when we started thinking about the kind of results that would produce, we realized it wasn’t the direction that appealed to us the most. So at some point we had to make a clear decision: okay, let’s go in this direction and really commit to it.

That said, it was still a bit challenging, because along the way new ideas kept popping up. For example, we considered adding a gamification aspect to the crowdsourcing section, where participants could earn points based on how much they contributed. In the end, we had to leave that out because of time constraints. At some point we realized, there are only three days left, how can we realistically make this work? It’s important at that stage to be realistic and say, okay, this is something we can do, and this is something we can’t.

During your final presentation at the closing event, you mentioned the educational goal of the project and its collaborative aspect. What kind of audience did you have in mind? Who should be able to use the website you developed?

We definitely had researchers in mind. The idea was to help them shape their research by giving them access to all these additional details in the collection. Because the postcard collection is so broad, it’s not immediately obvious what kind of research questions you could explore with it, and we wanted to make that easier.

At the same time, we wanted to reach a wider audience, people who are curious about Belgium’s history, about tourist places, and what they looked like in the past. Some might be interested in comparing then and now, others in seeing how streets and cities have changed, or just browsing the collection and feeling a bit nostalgic.

One thing I found very appealing was how user‑friendly the website was, it really looked like something anyone could use.

Yes, absolutely. I think a lot of people would love the idea of being able to see how a place looked in the past and compare it to how it looks now, seeing how much it has changed, or sometimes how it no longer exists at all.

The end result was a success, but did you face any roadblocks during the hackathon?

There was one issue at the beginning related to the locations of the postcards. We wanted to create a map and link each image directly to a specific place, but the coordinates were missing in the collection. So we first had to retrieve that information, and that took some time. At one point, we even thought it wouldn’t be possible. In the end, though, one of the team members managed to clean the dataset and recover the exact coordinates for each location, which allowed us to move forward.

You mentioned that this was the first hackathon you participated in. Do you feel you picked up any new skills along the way, and how might you use them in future research?

The crowdsourcing concept was particularly interesting for me. It’s something I had already worked with in earlier projects where we involved the public. For example, we showed people images, often of places in cities, and asked them to share additional information about what they saw.

What was new for me in this project was the specific crowdsourcing tool that we embedded in the website. I think that’s something I’ll definitely use again in the future. It’s very user‑friendly and easy to integrate, and the fact that it automatically produces a file with all the participants’ responses is very useful.

What advice would you give to someone who might be hesitant to participate in a hackathon because of their background?

I really think everyone can participate, because there’s a place for everyone in a hackathon, even if you don’t have strong technical skills. Whatever your background or skills, there’s always a way to contribute and find your role within the group. That might be through creative ideas, working on the poster, or helping shape the concept of the project. There’s always something meaningful you can bring to the team.

Last question: what advice would you give a team leader?

I would say don’t be too strict at the beginning. It’s important to give everyone enough space to be creative and to let people explore ideas, so that everyone’s skills can really emerge. I think the brainstorming phase is especially important, because that’s when you start to understand what each team member can do and how everyone can contribute to the project.

Congratulations one more time! It’s amazing how much each team accomplished in such a short period of time. For me, it almost felt unreal, this looked like a year’s worth of work.

Yes, exactly. For me, this could have been a thesis, the kind of results you would expect from a master’s thesis. That’s really what made it so remarkable to me.

The following post was written by Sam Goven, a master’s student in Journalism at KU Leuven. It offers a participant’s perspective on the BiblioTech Hackathon, reflecting on the experience, the creative process, and collaborative spirit that shaped the event.

Libraries are often seen as places of preservation rather than experimentation, but the BiblioTech Hackathon turns KU Leuven Libraries into a digital playground. Drawing on rich library datasets, students, researchers, and staff from diverse backgrounds work in interdisciplinary teams to reimagine historical collections through digital tools and collaboration.

The second edition of the hackathon culminated on 26 March in the University Library in Leuven, where seven teams presented their final projects to a jury. Over the course of ten days, materials from the library collection were transformed into innovative digital outputs, ranging from interactive maps and searchable databases to experimental interfaces, which can be explored via the project websites. Team PostScript ultimately claimed both the jury prize and the audience award with an interactive digital archive of Belgian postcards.

By combining technical support, curated library collections, and an emphasis on experimentation rather than competition, the BiblioTech Hackathon demonstrates that digital humanities can be accessible, creative, and collaborative, even for those new to computational approaches.

What is a Hackathon?

During a hackathon, a blend of “hacking” and “marathon”, participants work together in teams on a project against a tight deadline. These projects often have a digital component and can be developed over one or several days, resulting in a website, database, or another form of digital output.

The first edition of the BiblioTech Hackathon took place in 2023, organized by KU Leuven Libraries and the Faculty of Arts. Participants could choose from seven datasets, including the Bible of Anjou and wartime posters. The focus was on exploring documentary heritage from a fresh perspective by transforming it into computational data. The hackathon proved to be a success and led to a second edition in 2026.

Meet the Data, Meet the People

The second edition kicked off on 12 March in Agora Learning Centre in Leuven. As the smell of pizza filled the space, the perfect brain food for sharp minds, the seven teams discovered both the datasets and each other for the first time. In total, 39 enthusiastic participants from a wide range of backgrounds took on the challenge. The hackathon attracted not only master’s students, but also PhD candidates, postdoctoral researchers, and KU Leuven staff. Participants represented a broad variety of disciplines and research fields, including Computer Science, Egyptology, Law, and Economics.

To make the most of this diversity, teams were formed in advance based on digital skills and areas of expertise, ensuring a balanced mix. Each team was supported by a designated team leader to keep the project on track, while technical experts were readily available throughout the hackathon to answer questions and provide assistance. To ensure everyone could get started smoothly, an additional training session on the technical infrastructure and tools was organized the next day.

Following an introduction to the datasets and the available support network, the teams dove into the material. This year’s hackathon offered two datasets: well over 35.000 historical postcards from Belgium and around 300 travel accounts written by European authors describing the destinations they visited. Once again, these historical sources provided ample opportunities for innovative perspectives. Four teams chose to work with the travelogues, while the remaining three focused on the postcards.

The brainstorming phase reflected the exploratory nature of the hackathon. Faced with rich datasets and a wide range of ideas and ambitions, teams took time to explore different directions before narrowing their focus. Working within a limited timeframe required careful consideration of what was both innovative and feasible. This process not only helped shape the projects but also allowed participants to recognize and build on each other’s strengths. Andreas Ketele, a member of the Inked and Stamped team, reflected afterwards: “What I really enjoyed was that process of exploration. We reflected on our ideas and experimented a lot, and that’s exactly what a hackathon is about: discovering possibilities along the way.” (full interview)

The Final Projects

On 26 March, participants, jury members, and guests gathered in the University Library for the final presentations accompanied by a poster exhibition, marking the culmination of the hackathon and an opportunity for teams to present their work. The evening opened with welcoming words from the organizing team, Demmy Verbeke (Head of KU Leuven Libraries Artes), and Geert Brône (Vice Dean for Research at the Faculty of Arts), who praised the creativity and commitment shown throughout the hackathon.

The presentations were opened by team CaptaCats with their project ShipAdvisor. Loosely inspired by the travel website TripAdvisor, the team developed a web platform that maps maritime routes in the Mediterranean during the 18th and 19th centuries, based on historical travel accounts.

Next, team DH.xml presented their analysis of the postcard dataset. They argued that historical postcards functioned as a form of social media avant la lettre, and used the collection to identify recurring visual trends and patterns.

All Reads Lead to Leuven focused on how 19th-century French travel writers wrote about African languages. Their project resulted in a website featuring Instagram-inspired posts that reveal the vocabulary and framing these authors used when describing linguistic encounters.

Using the postcard dataset, Inked and Stamped built a searchable digital database. Its intuitive interface allows users to explore the collection by location, date, and even the color of the postcards.

Team PostScript adopted a similar approach, but with a specific focus on postcards from Antwerp. In addition to a searchable database, they introduced interactive features such as maps that contrast contemporary photographs with historical images from the collection.

The penultimate presentation came from Team W@nder. Drawing on The Land and the Book, a 19th-century publication by W. M. Thompson, they visualized the author’s travels in the Levant. As with other projects, historical illustrations were juxtaposed with present-day photographs to highlight continuity and change.

The evening concluded with a presentation by Team Julie Verne. They developed an oracle-like search tool based on the travelogues dataset. Through their website, users can query the texts and receive the most relevant responses generated from the corpus.

After a brief deliberation by the jury and a public vote, the awards were announced. The jury consisted of experts in data and digital research: Julie Birkholz (Coordinator CLARIAH VL+), Geert Brône (Vice Dean for Research of the Faculty of Arts), Jo Rademakers, (Head of LIBIS), Fred Truyen (Head of CS Digital), and Katrien Verbert (Program director of the POC Digital Humanities). Team PostScript was awarded both the jury prize and the audience award. As in the 2023 edition, however, each team received recognition, including awards such as Best Research Potential and Best Visualization. The evening concluded with a reception, where teams presented their project posters over food and drinks. To share the creativity and impact of the hackathon with a wider audience, the posters are currently touring across KU Leuven.

A Community Built Through Collaboration

Not only were the results of the hackathon impressive, participants also praised the atmosphere and strong sense of community that developed throughout the event. In post-hackathon interviews, several participants reflected on the collaborative environment that emerged over the course of the ten days. Andreas Ketele described the experience as particularly rewarding: “I’m usually not someone who uses very strong words, but this really was fantastic. […] We were working as a group of highly motivated people. We collaborated very well and benefited enormously from all the support we received along the way.” (full interview)

The diversity of backgrounds and skill levels did not prove to be a challenge, but rather one of the hackathon’s greatest strengths. By bringing together participants with different perspectives, expertise, and levels of technical experience, the hackathon created space for learning from one another. As Roberta Pireddu, team leader of PostScript, explained: “I really think everyone can participate, because there’s a place for everyone in a hackathon, even if you don’t have strong technical skills. Whatever your background or skills, there’s always a way to contribute and find your role within the group.” (full interview)

For many participants, this emphasis on collaboration rather than competition was key. As advice for future participants, Luisa Ripoll Alberola, team leader of CaptaCats, encouraged newcomers not to focus too heavily on the final outcome: “What really matters is not the end product, but the process: working together, learning new things, and enjoying the experience. That’s what makes it valuable.” (full interview)

The second edition of the BiblioTech Hackathon proved once again how working with library data can foster meaningful collaboration across disciplines. By bringing together diverse participants, the hackathon strengthened connections within the academic community and opened up new ways of engaging with humanities collections.

More information about the hackathon, its datasets, and the final projects can be found on the BiblioTech 2026 website. We encourage you to have a look at the project posters and websites to explore the teams’ outputs and discover the creative ways in which KU Leuven’s library collections continue to inspire digital humanities research. We also invite you to explore interviews with participants, offering a personal insight into their experiences during the event.

As part of our blog series, “Stories from the Research Trenches,” we often invite researchers and colleagues to share their personal experiences. For this installment of the series, we are delighted to have our colleague Marleen Marynissen from KU Leuven Libraries Nexus Research Data Management team sharing about her recent Erasmus+ experience in Barcelona.

A Journey of Collaboration and Learning: My Erasmus+ Experience in Barcelona

In October 2024, I had the opportunity to participate in the Catalan University Libraries Erasmus Staff Week in Barcelona. This five-day event, held from October 7^th to 11^th, brought together library professionals from across Europe to collaborate, exchange experiences, foster collaboration, and explore the evolving role of university libraries in the field of open science.

The week kicked off with an international coffee break and an icebreaker activity, setting a friendly and collaborative tone for the days ahead. Hosted by the Consortium of University Services of Catalonia (CSUC), the event provided a platform for participants to introduce themselves and share their expectations. It was also very interesting and inspiring to see how CSUC facilitates shared services and infrastructures among Catalan universities and research centers, enhancing their efficiency. The first day concluded with a guided tour of Barcelona – allowing us to discover the city’s vibrant culture.

The next day we went to the Universitat Politècnica de Catalunya (UPC), where we explored the research support services offered by the libraries. We learned about the Library’s Research Café, user training programs, and cultural programming in collaboration with UPCArt. This day also featured the first round of participant presentations, including my own presentation titled: Empowering Open Science, promoting FAIR dataset publication through documentation and metadata enhancement.

On the third day, we visited the Universitat Pompeu Fabra (UPF), where we focused on teaching support services. We were introduced to La Factoria, a support service for digital production managed by the library and IT. The day also included engaging presentations and discussions.

At the Universitat Autònoma de Barcelona (UAB), we delved into open education and citizen science initiatives. One of the highlights was a collaborative task focused on creating an open educational resource, which allowed us to explore the opportunities and challenges of open education in practice. After visiting the UAB’s facilities and enjoying several participant presentations, we concluded the day with a social dinner.

On the final day we had a session to reflect on our shared experiences and key takeaways. The program concluded with a visit to the Catalan National Library.

The Catalan University Libraries Erasmus Staff Week in Barcelona was an unforgettable experience. Each location we visited enriched the program by showcasing its unique approach to library services and open science. The participant presentations offered fresh perspectives and it was really nice to meet and exchange ideas with colleagues from across Europe. Of course, the beautiful and dynamic city of Barcelona added an extra charm to the entire event. This week was a perfect blend of learning, networking, and cultural discovery, and I am grateful for the chance to be part of it.

As part of our blog series, “Stories from the Research Trenches,” we often invite researchers and colleagues to share their personal experiences. For this installment of the series, we are delighted to have our colleague André Davids from KU Leuven Library of Economics and Business share about his recent Erasmus+ stay at the University of Mannheim. André talks specifically about the opportunity to explore Optical Character Recognition (OCR) tools, a topic that Faculty of Arts researchers often seek advice about. Read about André’s experience learning about various OCR software options, his takeaways on how they do things at the University of Mannheim, and his impressions about the city itself.

Meanwhile, somewhere else: Erasmus+ in Mannheim

Hello, I am André, and in March 2023, as part of the Erasmus+ program, I spent five days at the University of Mannheim. Why did I choose Mannheim? In the context of my work at the Library of Economics and Business, where I am involved, among other things, with OCR (Optical Character Recognition), it quickly became clear after some online research that they are very actively engaged in that field there.

I was warmly received at the library by Stefan Weil, one of the most active current developers of the OCR software Tesseract. He told me a lot about the university and the city, but also introduced me to the world of Linux, Ubuntu, Debian. In addition, I was able to experiment with various OCR software (Tesseract, eScriptorium, Pero-OCR) and received more information about the OCR-D Project.

In Mannheim, they primarily work on the further development of open-source software. Additionally, they offer support to students and researchers in using this software. Once a month, they organize an open online OCR consultation hour in collaboration with the University of Heidelberg, where anyone can ask their OCR-related questions. The “clients” are mainly researchers, but also library staff from other universities.

Also interesting to mention: The library has a room, the ExpLAB, which is dedicated to brainstorming, Design Thinking, etc. This room is fully equipped for brainstorming sessions, but also has Eye-Tracking Stations, Virtual Reality glasses, etc., which can be used by both students and staff.

This Erasmus+ experience not only enriched my knowledge about OCR but also about the city and university. Although Mannheim is a well-known city, I didn’t know much about it myself. Due to its architecture, it was chosen by the Allies in 1940 as a place to experiment with air raids and complete city destruction. As a result, there wasn’t much left of the city after World War II, and it had to be rebuilt. After long debates, the Baroque Palace (Barockschloss) was also rebuilt. Luckily so, because in 1967, the University of Mannheim could establish itself there. This building, with its width of 450 meters, is the second-largest baroque palace in Europe, after Versailles (but – and this is important – it has one more window than Versailles).

Navigating the city was quite a challenge since the city center has no street names but has been divided into squares since the 17th century. The most striking street is the one in front of the university, the “Kurpfälzer Meile der Innovationen” (Palatinate Mile of Innovation), which has 42 bronze plaques on the ground honoring famous innovators such as Carl Benz (automobile), Karl von Drais (precursor to the bicycle), Werner von Siemens, and others. Maybe an idea for KU Leuven?

What stuck with me most in terms of their work culture is the Teams channel called “Mittagessen” (lunch). This is where colleagues arrange lunch plans. This is also how I met a colleague who, as a student, did Erasmus at KU Leuven. I still don’t fully understand their working hours. Apparently, they work 40 hours a week, but I was always the first one there and one of the last to leave… Maybe they calculate time differently there. Everywhere is different, but a lot is still familiar. I look back very positively on my trip to another library and can highly recommend it to everyone.

Also interesting to see is the university library’s introductory video:

The following is an interview between Alisa Grishin, Artes Research intern 2022-2023, and Lode Moens, BiblioTech Hackathon participant. The hackathon took place in March 2023. It was a 10-day event and included a pre-hackathon orientation moment called “Meet the Data, Meet the People.” Lode’s group, called StudentsBlock, worked on the Magister Dixit dataset, which features a collection of handwritten lecture notes of the old University of Louvain (1425-1797). You can learn more about the team’s work by having a look at their project poster in the BiblioTech Zenodo community. To read more about the hackathon and the results, you can visit the BiblioTech website.

Members of the StudentsBlock team pose for a photo at the reception of the closing event.

What first interested you in the hackathon? Have you done one before? What is your background?

I’d never done a hackathon before, since this was the first one directly associated with the Faculty of Arts [I decided to participate]. I was interested in it because my friend was going to apply, and she asked if I was interested. I’m not a huge ICT nerd but wanted to improve my skills, so it sounded like a good opportunity. So I looked at the datasets, and it sounded interesting. [I know] Professor Fantoli; I do some student work for her and thought why not. I have no experience programming, but I’m always eager to learn new stuff. I study Greek and Latin and a bit of Theology as part of my master’s.

What was your primary concern when beginning the project? The project? The process?

My first concern was whether we were going to find a subject. We had a lot of ideas but not a lot of it was super straightforward. So it took a while to establish a clear idea. Even then, it was a bit chaotic, but it was nice to see people taking the lead and our team leader did a good job at coordinating everything.

What kind of audience did you have in mind?

Our project was to optimize an existing database of student notes. Our first target audience was researchers – students, professors, PhD students, etc. of the Classics, history, philosophy, theology, law, basically anything that the notes represent, as well as anyone doing research on the Old University of Leuven for a Bachelor’s or Master’s thesis. Secondly, just people interested in the Old University and the courses. Yannick and Linde [team members] were also both familiar with notes from the University and are trying to reconstruct the old student and professor notes. So that was the less abstract audience. Very topical and applicable. The jury asked us what we would you do if we couldn’t read Latin, but transcribing all this material would take some time.

How did you establish your methodology and approach to the data set? Were you inspired by any other platforms or projects?

We had a PhD student on our team who comes from the Faculty of Economics and is now working in DH. She absolutely loves data and was able to figure out what we should do. We had three people working on the XML file. They cleaned the data and structured it. We had a specific goal in mind; we wanted to structure the data according to students, dates, etc., but we had some unorganized data. We also had two people working on the presentation. One was writing the HTML for the Toledo page [KU Leuven’s educational platform], and I myself took care of communication. So, the project was quite structured and everyone knew what they had to do. People used their backgrounds to work together. We had someone doing DH, Greek, and our team leader, Daria, is from LECTIO. So we knew what was possible to accomplish. We had a lot of meetings – two each day – so communication was efficient.

When did you reach out to the experts?

We reached out to ask if we could use the CSS profile of Toledo, as well as the Python script. So not in the very beginning, but during the first step.

What was the brainstorming process like at the “Meet the Data, Meet the People” event before the hackathon officially kicked off? Was there a clear vision from the beginning?

There was not a clear vision. Daria’s first idea was to work on doodles – so what students wrote in the margins of their notes. But the manuscripts we had were neat and more polished than expected. So if they talked about how to construct a globe, there would be technical drawings but no funny doodles. We were going to reconstruct the lecture cycles, but that was a bit too narrow. But it was great to meet the people before the stress of the actual hackathon. Once the hackathon started, it was chaotic. So having [established] personal connections first, then the technical skills, was a nice approach. One or two people also came [to the “Meet the Data, Meet the People” event] and had to withdraw – so it was good for them to get that first taste, and we didn’t immediately start working with them.

Were there any issues you ran into when cleaning up the data or creating the database?

There were some problems with the cleaning process because of the dates; not all manuscripts had dates in the metadata. So then we had to try to figure out what should be included in our data but we weren’t sure how to structure it. We had some conflicting ideas on how to target this. There were some Python problems which had to be recoded too. I also reached out to an old professor of Daria’s to take a second look at the Latin and help correct it.

How was the idea for the Toledo-inspired website first conceptualized and then implemented?

At the opening event we were throwing ideas out and someone said “oh we could visualize it as a Toledo page.” The idea stuck, but there was a practical problem: to be able to make it a decent page, we needed one student and three courses for the tiles [on the homepage of the platform]. That was something we managed to do with our dataset. It was kind of all or nothing. Once we saw it was possible, the writing started: the CSS profile, the underlying HTML. One person had a clear idea of what it could look like. Then it was a matter of filling it with content descriptions, side notes, history. We actually had someone who did a Master’s in History and so we were able to use some of his thesis topic and really had some fun with it. We had a structured dataset so we wanted to present it in a fun way. Toledo was a natural decision since it was familiar to so many students. All in all, it was a result of hard work.

How would you describe your experience?

It was very nice to work with people from so many backgrounds; math, history, philosophy, Dutch; you came into contact with people you wouldn’t normally meet. There were challenges in ways of working, ideas, etc., but in the end we worked well. We also all had a drink after so we all got along well [laughs] and we’re all pretty friendly now. It was interesting to be a part of the hackathon without a strong ICT background. It was really interesting to see what can be possible, especially when watching the other teams’ presentations. Our own dataset didn’t lean towards visualization like some of the other teams, but we still were able to learn a lot about the university, which brought the data to life.

How could you use these skills for future research?

I do textual research, so I look at lots of manuscripts. At this point, a model can’t really be trained for OCR because there are too few manuscripts and handwriting, regional differences, etc. make it difficult to analyze in that way. Medieval Latin is also not easily analyzed because the syntax is different and sometimes one manuscript has more authority than another. Sometimes it can also be wrong. The difficulty now is to interpret the Latin and there is difficulty in interpreting the data. As a classicist, the language should always be the main objective. DH can be a tool or asset, but it is not the main objective. I’ve been testing out different DH approaches, and, while I still like to work with it manually, there are always chances that my research will be become more digital.

What kind of tips would you give to a team doing their first hackathon? Any tips for someone from your background?

Try to apply your strengths – know your strengths and weaknesses. Try to look at the possibilities and what would be interesting to you on the subject of DH. I’m hoping to learn Python but also Old Norse and Arabic. It can be very stimulating to think about how to solve problems in a new way, and it might even be a bridge to build an interest in DH. And, don’t panic… there will be times when there is a lot of chaos but just look at what you have and where you want to go and just keep moving.

The following is an interview between Alisa Grishin, Artes Research intern 2022-2023, and Ivania Donoso Guzmán, BiblioTech Hackathon participant. The hackathon took place in March 2023. It was a 10-day event and included a pre-hackathon orientation moment called “Meet the Data, Meet the People.” Ivania’s group, called the Poststars, worked on the historical postcards dataset, featuring over 35,000 old Belgian postcards. You can learn more about the Poststars’ project by having a look at their project poster in the BiblioTech Zenodo community. To read more about the hackathon and the results, you can visit the BiblioTech website.

Ivania presents her team’s project during the closing event of the BiblioTech Hackathon.

What first interested you in the hackathon? Have you done one before? What is your background?

I had done one before, but it was the more traditional type where you work all day and all night. I didn’t like it [laughs]. So when I saw this opportunity to work with data, and it was over the course of a few days, it really interested me. I wasn’t sure whether or not to participate since I didn’t know who I would work with and what their experience was, but I had a friend who wanted to participate so we signed up. In the end he couldn’t make it, but I thought it was a good experience! Even though I was the one with more experience in programming, it didn’t feel like it was a bad thing. I really liked that there were people from different backgrounds. For the dataset, I actually love to collect postcards so this dataset interested me. I had also worked with digital humanities before because I participated in a project which tried to explain a political process that was happening in my country. I had worked with historians, sociologists, journalists, and poltical scientists and that experience was very interesting to me. So I wasn’t afraid to work with people from another background; it was actually an exciting opportunity to me.

I’m an engineer. I got my degree in Chile and France. I’m officially an IT engineer, but I’m not very interested in the industrial and high-level side. I was always more interested in computer science, user interfaces, AI, user relationships, etc., so that’s what my master’s focused on. I’ve worked for two years in computer science, and now I’m doing my PhD. I’m working ith Prof. Katrien Verbert in user and AI relationships, specifically explainable AI. 

What was your primary concern when beginning the project?

My main concern was that there were limitations in the time frame. I think that as far as technical competence goes I didn’t know what to expect, but realized the other members’ skills were an asset. Additonally, there were lots of people supporting us throughout the process.

What kind of audience did you have in mind?

At first, we wanted to really understand the connection between the postcards and the places where the photos were taken. We wanted to look beyond the postcard itself. This would have been really interesting, but it didn’t work out. We ended up creating a search engine where you could write a sentence—for example, “children playing outside in the park”—and it would return postcards that matched. It was a really interesting approach for a search engine because usually search engines look at metadata, but with our project, the search engine analyzed the image itself. When we developed the project, we had in mind someone who would be interested in exploring the postcard set as a dataset for future research projects.

How did you establish your methodology and approach to the data set? Were you inspired by any other platforms or projects?

Our brainstorming process involved thinking about how we could contextualize the postcards: time period, location, etc. We also were interested in exploring the destinations the postcards were sent to. So we could collect and organize information about where the postcard was from and where it went. We also thought about the usage of the postcard: postcards used to be a way to communicate with people. It was cheaper than a telegram and would arrive before you returned home. But exploring these ideas wasn’t possible because the metadata didn’t contain that information, and it was really hard to find this information. We decided to work on the search engine. For this, we were inspired by current AI models and their usages. CLIP, a model created by open AI had good examples on how it worked, and it matched some of our ideas, so we decided to use it.

How did you create the search engine for the website?

Our team leader, Prof. Tim Van de Cruys, suggested we use the CLIP model. It brings images and texts into the same plane. So we first created a mathematical representation for the dataset, and then it would convert the search entry to a mathematical representation. From there, it would produce results. There were some cases when it didn’t match. For some sentences there weren’t any matches. But I think that for this dataset, which is very image-based, it was quite useful.

How did you use your professional/academic experiences to help with the hackathon?

I used some approaches I had learned from my experience as a software engineer and data scientist. We used Github to share and collaborate. Specifically the project tracking tools helped us stay up-to-date with what everyone was doing. I had experience putting systems in production (putting them online), so I was able to join what everyone had done into one system and make it available.

Did you apply any of the topics you are studying for your PhD to the project?

Not really [laughs]. But now I proposed three masters topics that would work with these datasets. I see so much potential for enriching the data. One idea is a date analyzer for the postcards. For this, we could try to use an AI model to predict the time frame of the postcard. In some cases, we have dates, but they’re not complete. Sometimes there is an x in the date, or it’s incomplete. So, we want to train a model that can predict the dates. The model could also predict aspects of the postcard, including color, image, shape, quality, and then the researcher can confirm manually if it is right. The other project ideas were more about how to transcribe what was written on the postcards. Understanding what is written on the postcards can be hard since they are handwritten and messy. Creating an interface to help researchers to add more information to the postcards would allow them to be analyzed better by researchers. [These projects] would relate to my PhD because they provide explanations of predictions made by an AI model. People have to make decisions, but the AI decisions have consequences for research.

Was there any main motivator/goal that encouraged the team when things didn’t go as expected?

Everyone had this level of compromise where we wanted to do something cool. Nobody was like “we have to work every day all day.” But there was also this idea that we will do what we can. It was very propositional, and we were able to adjust and move on quickly. 

What were some of the roadblocks you faced?

There were some things we wanted to focus on, like the text on the postcards, that we couldn’t. There was also no information in the metadata about the stamps. So the metadata—or the lack of it—presented a problem. 

What kind of tips would you give to a team doing their first hackathon?

Enjoy it! It’s an opportunity to learn, so don’t stress about it. Make sure to think about how to fix things if it doesn’t work; don’t feel defeated. Move forward. In a hackathon, if it doesn’t work, then you need to keep moving on so that you have a project. It’s better to try and to not give up immediately. Try two or three times, and if it doesn’t work, then move forward. The proposal of the hackathon was just to do something new since nobody has been working very closely with all of these datasets. So anything you do is contributing – anything you do is better than nothing.

Do you have any final comments?

I really enjoyed the hackathon. Some of my data visualization students were in my group, which was fun. I loved the technical support. We didn’t have to worry as much about the data because it was well documented. We didn’t have to worry about getting access to it or how to handle such big datasets because that infrastructure was already place. That made it very fast to experiment. I thought it was great!

The following is an interview between Alisa Grishin, Artes Research intern 2022-2023, and Daria Kondakova, BiblioTech Hackathon group leader. Daria is the Research Manager at LECTIO, the KU Leuven Institute for the Study of the Transmission of Texts, Ideas and Images in Antiquity, the Middle Ages, and the Renaissance. The hackathon took place in March 2023. It was a 10-day event and included a pre-hackathon orientation moment called “Meet the Data, Meet the People.” Daria’s group, called StudentsBlock, worked on the Magister Dixit dataset, which features a collection of handwritten lecture notes from the Old University of Leuven (1425-1797). You can learn more about the team’s work by having a look at their project poster in the BiblioTech Zenodo community. To read more about the hackathon and the results, you can visit the BiblioTech website.

Some members of the StudentsBlock team pose together during the reception of the closing event.

What first interested you in the hackathon? Have you done one before? What is your background?

I’m a Classicist, and I’m currently working with Digital Humanities. I’ve never done a hackathon before but was always interested in how they work, so this seemed like an interesting opportunity. The Magister Dixit dataset was specifically why I chose to do it because there is a project on it at LECTIO. It was a nice way to get to know the dataset better, especially since Magister Dixit has a long project history, and I’ve only been with LECTIO for one year. 

I had an interest in digital humanities before; I did programming whenever I could, then found DH in 2014/2015. I wouldn’t call myself a digital humanist, though, since I only use DH methods and my background is very traditional. My background is in Classics. My PhD is in Classics, and I mostly do things in Greek and Latin, specifically -300 BCE to 200 CE. I don’t really work on Early Modern stuff. So, in a way, the only link between the Magister Dixit collection and my research is the fact that it’s in Latin. But for the project this helped because I also knew about the history, layout, color fonts, and how to pull the data. There were things I would have liked to explore more. So this project was more connected to my technical interests. I’m very open minded when it comes to DH and don’t worry about the relevance of something and whether or not I will work on it again – it’s just fun.

Can you expand on a topic you wish you could have explored more? Do you mean the doodles in the margins of the notes?

Yeah, there weren’t many doodles and the student notes weren’t like what you expect now. It was more of a syllabus rather than actual notes. It wasn’t spontaneous production in the same way that your class notes are today. It was more formal. There were illustrations, but we also didn’t really know what to do with those. The data extraction approach presented us with a less shiny option, but it was more practical and usable. The design of the team’s project website was great, but the data was just a simple table.

What was your primary concern when beginning the project? Interface? Usability?

I’m accustomed to working with texts, so when beginning to work with Magister Dixit I wasn’t expecting it to be so metadata-heavy and was thinking we would work directly with the student notes. Once I realized we couldn’t approach the dataset in the way I was expecting, I was a bit concerned about how we could adapt our approach. I wasn’t that much concerned about the technical aspect as it seemed that after the first meeting we would be able to work together. My main concern was just finding out what to do with the metadata.

Before beginning the project, were there any other platforms or projects which you were planning to use as inspiration?

Not really. We decided we would do the metadata analysis and we had the help of Jarrik Van Der Biest, an expert on the dataset, who is working on the student notes for his PhD. A few other people also knew about student life and the content of the course, which helped us frame our question. So we started with reconstructing the lecture cycles. Ultimately, we did this by creating a Toledo-like website, mirroring the e-learning environment [Toledo] that current KU Leuven students use.

How did you apply your knowledge from working at Lectio to the hackathon? Were there any tools or methodologies that were translated to this dataset?

My job is to support and implement DH in the projects. As such, I have to have a good overview of what is out there and bring people and tools together. This is something that worked well, but I also learned a lot from the team members, too. Even as a team leader, I learned a lot; I didn’t want this to be a classroom exercise. We had someone who worked with Open Refine, which I had not used before, and it worked really well since Python can be hard to understand sometimes. My role was less about suggesting or incorporating tools and more about bringing people together. There was an intrinsic connection with what I do at LECTIO just by listening to the team members and seeing how all the tools worked together. In the last few days, I also joined in with the data analysis and with the help of two other team members, I was able to brush the dust off my coding skills. The main connection to LECTIO, I think, was the subject matter and just seeing, on a smaller scale, the challenges and advantages of having a variety of people with different backgrounds working on a single project.

Do you think participating in a hackathon as a student would have benefitted you in your career?

Definitely. I would have loved to be able to do that. I did a group project when I was doing a DH class during my master’s. There wasn’t enough commitment and things just didn’t work; we didn’t learn from each other. But with a hackathon, if you stick around, you learn a lot from your team and other teams. The final presentation, for example, I took a lot away from. There we had the opportunity to figure out what else we could have done and what would have worked. As a student, it’s great to have a result. There’s an output. You’re not doing it just for the sake of doing it, and you have the support of others as you’re working on it. So it would have been great to be able to do this as a student.

What kind of practical knowledge do you think can be gained from a hackathon like this? 

Open Refine was a great tool that I learned about. I also learned a lot about MARC 21 XML tagging scheme from the Library of Congress since we had to go through the tags. I also got a better understanding of the material of the Magister Dixit collection without even going through the actual content. I knew metadata is a treasure trove of information but I only knew that in theory. So then seeing it up front was more practical. Project management was also a skill I worked on. Other projects I’ve done were more extended and involved a lot of reflection and checking things. Having 10 days was a challenge, especially when combining with my job at LECTIO, as I had to check in and stay continuously involved. 

Was there any main motivator/goal that encouraged the team when things didn’t go as expected?

I don’t know. There was a moment in the middle when it felt like everything was falling apart. Meeting online was very hard, and it was difficult to get everyone together anyway. I used Gathertown to have virtual drop-in rooms, which I think helped. We did feel like a team and wanted to work together, and during the rush we were all working on the same thing. Checking with Jarrik towards the end was very helpful as he was very encouraging and remarked on the project’s practicality and usefulness for researchers. Getting that feedback motivated us to improve the platform, and it felt good to know that we have a practical product. We were also kind of competitive and wanted to win [laughs].

What kind of tips would you give to a team doing their first hackathon?

Be open and ask questions. That was something that worked well for us. Sometimes people ask questions a bit too late. Reaching out to the expert pool earlier also would have been great. Because everyone has questions, and we need to address them to move forward. Be proactive. It is better to have five ideas and only one works than to not have any at all. Try to find something you would like to do. Even just observing something you don’t feel equipped to do, follow along and see what you can learn from your teammates. Use your strengths. Have fun! You shouldn’t approach a hackathon like an exam (but you do still have to be committed).

For team leaders, I learned a lot about how to organize groups. I would remind myself to notice when things don’t work. I had an idea in my head and then when it stopped working, I got stuck and had to become flexible quickly. And I thought I was flexible, but I realized I really wasn’t [laughs]. 

Any further comments?

I really enjoyed it. I didn’t realize it could be so fun! I really liked the sense of relevance for the library and seeing the datasets be used. I really appreciate the team of organizers and hope we do it again. I would love to be a team leader again, or maybe a team member. I would love to see the Magister Dixit collection used again, and we’re hoping to organize a way to discuss the other approaches and to further develop the database our team built. I think a lot of the projects have a lot of potential.

The term “preprint” is actually used for two related, but still slightly different, things. The term can refer to an author’s original manuscript (of an article, a book chapter, or a complete book) as it is submitted for publication (hence also known as “the submitted version” of the text). This submitted version typically remains private, whereas later versions of the text (revised after peer review and/or copy-edited by the publisher) are made available, either behind a paywall or in Open Access. However, the term preprint can also refer to the first public version of a text, which is being disseminated before formal peer review took place and which afterwards might or might not be developed into a more traditional publication. This second meaning of preprint is thus basically identical to what is known as “working papers” in disciplines like economics, law, and political sciences. To put it succinctly: the first meaning of the term preprint refers to a manuscript of an article, a chapter, or a book before publication; the second meaning – typically only used for articles – is considered to be the first public version of a text and therefore oftentimes treated as a publication in its own right. Both meanings of the term have in common that they refer to a text which was not submitted to formal peer review (yet).

Lately, the second meaning of the term preprint has become more dominant, not in the least because the habit of disseminating articles before they have been peer-reviewed is becoming more widespread.

Preprints can be distributed through designated preprint servers, i.e. online repositories where researchers share articles before they have undergone formal peer review. Preprint servers are often connected with a specific discipline, such as medRxiv (health sciences) or bioRxiv (biology), or region, such as AfricArXiv, and typically guarantee some basic form of quality control such as a plagiarism check before the text is accepted for publication as a preprint. However, preprints can also be shared using general repositories which are discipline-agnostic (like Zenodo) and/or platforms which accept all kinds of research outputs (such as the CORE repository of Humanities Commons), and which do not perform such basic quality checks. Preprints typically get a permanent identifier (such as a DOI) and are indexed by services such as Google Scholar, Open Science Framework (OSF) Preprints, or Web of Science’s Preprint Citation Index.

As said, the practice of disseminating preprints is on the rise. In some disciplines, such as astronomy and mathematics, up to 35% of articles start out as preprints, which are seen as an important instrument for Open Scholarship (as preprints can always be shared openly), as a way of speeding up research (since dissemination of research results is no longer slowed down by pre-publication peer review) and as a way to establish priority of discoveries. Preprints also make other innovations in scholarly communication possible (such as open peer review or the publish-review-curate approach – topics which deserve a blog post of their own) and put into question the exorbitant prices of journal subscriptions or article processing charges. Recent research by Brierley et al. and Davidson et al. in the context of the COVID-19 pandemic even brought to light that differences between preprint and final versions of articles published in biomedical journals are limited, which gives cause to reconsider the time and money spent to develop a preprint into a journal article.

Recommended reading:

J. Bosman et al. (2022), New Developments in Preprinting and Preprint Review, DOI: 10.5281/zenodo.7040997

K. Hettne et al. (2021), A Practical Guide to Preprints: Accelerating Scholarly Communication, DOI: 10.5281/zenodo.5600535

L. Mesotten – J. Berckmans (2022), To preprint or not to preprint? KU Leuven researchers share their thoughts on the (dis)advantages of preprint publishing, https://www.kuleuven.be/open-science/what-is-open-science/scholarly-publishing-and-open-access/schol-pub/interview-preprints

The following is an interview between Alisa Grishin, Artes Research intern 2022-2023, and Annelore Knoors, BiblioTech Hackathon participant and student in the Advanced Master in Digital Humanities. The hackathon took place in March 2023. It was a 10-day event and included a pre-hackathon orientation moment called “Meet the Data, Meet the People.” Annelore’s group, the ChaoTech Warriors, worked on the wartime posters dataset featuring proclamations issued by the German General Government in Belgium during World War I. You can learn more about the ChaoTech Warrior’s project by having a look at their project poster in the BiblioTech Zenodo community. To read more about the hackathon and the results, you can visit the BiblioTech website.

Members of the Chaotic Warriors team pose for a playful team photo.

What first interested you in the hackathon? Have you done one before? What is your background?

I hadn’t done one before, but since the DH Master only lasts one year I wanted to take the opportunity to learn more, especially since there are so many different types of analysis and approaches. Also, the interdisciplinarity of the hackathon was an interesting opportunity. I think my team had a historian, informatics, PhD student, and two linguistics students. Then I have a linguistics and literature background and now do DH.

Why did you choose the DH Master?

I was curious to know about the recent developments within my field, and other fields since DH allows you to move beyond your initial field. This happened for me as I did the linguistics program. There are some classes that are for all of the Faculty of Arts which have to do with data and those really got my attention.

What were your expectations of the hackathon before beginning? Did you feel like you would be well-equipped for the project?

I didn’t think I would have enough skills to contribute to the team. Especially since the hackathon started in March, so I only had one semester of classes. But through the Introduction to DH course, I got a great basic knowledge. With technical things and analysis you always need to look at things precisely, so I knew what I had to look for. We did have to do a lot since we lost a few members, but the remaining members were able to do a lot, even without much previous knowledge. 

Any concerns?

Not really. I hadn’t considered that so many people would drop out, but we managed well enough, and I think we had a great result even with the limited team members.

What was the group brainstorming process like for this project?

First, we noticed that people in the team had different approaches to the theme in relation to their profiles. So we really used our imaginations and were able to think non-traditonally. In the end we found a combination of ideas.

How did you establish your methodology and approach to the dataset? Were you inspired by any other platforms or projects?

I did the topic modeling, which I had already done for the Introduction to DH class when we did different titles of journals. I did topic models on the titles and institutions’ names. So that was nice because I could go in and only had to change a few things. We also made a timeline, which I had experience doing for an art history course, so I knew the platform was accessible and good for less technical users to use. 

What was your role in the project and how was it different/in line with what you were expecting?

On a conceptual level, I thought I would be a beginner DH’er and people would have to teach me things. But I was more of the expert DH person. I could really teach the other team members like the informatics students with no background in humanities, and the others who didn’t know a lot about the digital side. So it was nice to be able to share what I had been learning for the past six or seven months. They told me they really liked learning that way.

What was the most challenging part of the hackathon?

I don’t think there was anything that was that big of a hurdle, honestly. I think the most difficult thing was the OCR that we wanted to correct; the layout wasn’t right. The timing of the presentation also meant that we had to tone down our ideas. Maybe if we had a bigger group we could have tackled a bigger project, but we were limited.

Was there any main motivator/goal that encouraged the team when things didn’t go as expected?

We basically got a lot of confidence in knowing that we can just go for it. 

What kind of advice would you give to a team doing their first hackathon?

I think in the starting phase, don’t be afraid to sign up. Even if you don’t have any experience in the field, it’s a great opportunity to learn about data and meet people from other programs. You also have a team leader and the experts to help. It’s a great time to learn, and you get a lot of help.

Also, if you’re considering doing the DH Master’s, it’s a great opportunity to get to know the people in the DH community. The community is really strong. You get to know a lot of people, talk to them at the reception, etc. It’s great to get to know the people and the subject matter. 

What kind of advice would you give to someone from the DH Master’s?

I would tell them that they will learn a lot from the expereince, and that they shouldn’t underestimate themselves. 

---

The following is an interview between Alisa Grishin, Artes Research intern 2022-2023, and Tom Gheldof, BiblioTech Hackathon group leader. The hackathon took place in March 2023. It was a 10-day event and included a pre-hackathon orientation moment called “Meet the Data, Meet the People.” Tom’s group, called the ChaoTech Warriors, worked on the wartime posters dataset, featuring proclamations issued by the German General Government in Belgium during World War I. You can learn more about the ChaoTech Warrior’s project by having a look at their project poster in the BiblioTech Zenodo community. To read more about the hackathon and the results, you can visit the BiblioTech website.

The ChaoTech Warriors team show their warrior stances during the closing event of the hackathon. On the right, Tom animatedly delivers the presentation of his team’s project at the closing event.

What first interested you in the hackathon? Have you done one before? What is your background?

I am an ancient historian by training and have a degree in journalism and cultural studies, after which I followed a training in what is now called digital humanities. When I started working as a researcher, I realized I could use my programming and digital skills more than my scientific skills. So when a position opened up with DARIAH (a European consortium for Digital Research Infrastructure for the Arts and Humanities), they were looking for someone with a balanced profile. I’ve always liked to balance digital tools and methods, even 10 years ago, so it’s a personal and professional interest. Now I am the day-to-day coordinator for CLARIAH-VL – the collaboration of DARIAH and CLARIN in Flanders. I’m mainly involved in helping researchers working in digital humanities where possible by using my main interests: historical databases and linked open data.

I can’t remember how I first got included in the hackathon [laughs]. The organizers had already planned that I would be participating, but through more casual meetings, the question came up whether I would be interested to take part as an expert or as a team leader. I had already participated in a hackathon at a conference before, but it was a lot more condensed. I enjoyed that hackathon in a way that I hadn’t expected. Mainly there were a lot of researchers, and it was the first time I worked in a small group with [people from] such different backgrounds. We worked with our own materials, which made it more ambitious, yet a lot more straightforward. With two days, you get right into it and have to keep to a timeline, making it a great experience.

What was your primary concern when beginning the project? Interface? Usability? What kind of audience did you have in mind?

My primary concern was whether everyone would show up [laughs]. I also had to prepare myself beforehand, because even though I am used to being a coordinator, I didn’t know what the background or level of enthusiasm of the group would be like. Also, the wartime posters corpus was beyond my familiarity and comfort zone as a researcher, so I wanted to familiarize myself. I began by exploring the corpus on the digital platform and had a look at the metadata.  I looked at it as if I were a contestant to see what it would be like, then I decided to let the team give their ideas first.

How did you establish your methodology and approach to the data set? Were you inspired by any other platforms or projects?

The first thing I noticed was the quality of the digitization was not 100%. While most of the automatic translations were okay to read, we encountered problems with the metadata. I reflected on my past experiences with some other digitization projects, services, and tools that might have the potential to improve the translations. I asked my group members which ones they were familiar with and how they would approach such a challenging corpus. In their answers, it became clear that the members brought valuable backgrounds to the table, particularly from fields like linguistics, Natural Language Processing (NLP), and philosophy. The first gathering during the “Meet the Data, Meet the People” event was very exploratory. During that meeting, we just brainstormed about potential tools and methods.

How did the workflow and work distribution change once some group members could no longer participate?

I should disclaim that our group was struck with a bit of misfortune. Two of the eight group members cancelled their participation, and they were the ones who knew the most about the ManGO platform and the High Performance Computing infrastructure (HPC). Additionally, one of the more technically skilled members—who followed the explanation of the platform—also cancelled further on. So out of the 8, only 4 participated over the full 10 days. But even with a small group, we were motivated. I took encouragement from their motivation and expertise. I tried to encourage them to go beyond their comfort zones to explore the other tools that they might not have considered at first. This was very positive, but also a lot more work for each of us. In the end, we overcame the challenges, but we did have to downsize our ambitions because of the workflow. All in all, I think the members were pleased with the outcomes and with being able to build up their skills by using tools they hadn’t used before.

In the poster it says there were advantages and disadvantages to having a small corpus. What were those?

Our corpus was composed of 171 posters, but we were able to familiarize ourselves with it very quickly. We noted that it was mostly multilingual, and asked ourselves if we could do anything with that. And regarding the metadata: can we scrape it for a multilingual use? One of the disadvantages was that we couldn’t use some of the more ambitious tools. So, for example, exploring the use of the HPC infrastructure wouldn’t be of much help because of the feasibility, and our laptops weren’t able to do those computing tasks.

Was there any main motivator/goal that encouraged the team when things didn’t go as expected?

I must give credit to my team members for pursuing their personal interests. A lot of the members entered the hackathon not knowing if they wanted to do a research position or do the Advanced Masters of Digital Humanities. For them, it was great to experience if they would want to pursue this further. Speaking for my group as whole, the more you delve into the research corpus, the more you can see what can come out of it. Despite not having a lot of experience in the subject area, I was impressed by the language, content, formation, and layout of the posters as we explored a wide variety of research questions.

What kind of tips would you give to a team leader participating in their first hackathon?

I would again give the group as much responsibility as possible. You don’t need to worry, as a team leader, if they have the skills or digital competence, they will delve into it out of their own interest. By giving them responsibility, they might start exploring tools which they would have easily given to someone else. Don’t underestimate the creativity of the team members. At our brainstorming session, we ended with a variety of approaches after talking for only one hour. Out of their creativity came the most interesting research questions. I also benefited from how the main organizers said to not be afraid to reach out to the experts. We waited too long to do that. We had a great pool of experts from the library, Faculty of Arts, ICT department, PhD researchers, etc., and I was surprised to learn how wide their support reached. I think we might have benefitted more if we had reached out to them at the beginning. I will admit, I did want the team members to have full responsibility first so that they wouldn’t immediately reach out to the experts, but it’s a double-edged sword. Still, an expert could have made up for a missing team member. And according to feedback from my team, they really enjoyed the collective motivation to continue and the learning of new tools and methods that they applied.

Final Remarks

Thank you to the organizers for the flawless organization. It was a great balance of personal and online meetings, and, as a DH event, it worked really well. I really enjoyed the final event and was pleased with the quality of the posters, including our own. So for myself, it was a very pleasant experience, and I would not hesitate to be a candidate again as a team leader or even as a team member, just to see how fun that can be.

The following is an interview between Alisa Grishin, Artes Research intern 2022-2023, and Sandra Elpers, BiblioTech Hackathon participant and Bachelor student in Theology. The hackathon took place in March 2023. It was a 10-day event and included a pre-hackathon orientation moment called “Meet the Data, Meet the People.” Sandra‘s group, the Illuminators, worked on the Bible of Anjou dataset. The Bible of Anjou is one of the most important and valuable pieces in the collection of KU Leuven’s Maurits Sabbe Library, the library of the Faculty of Theology and Religious Studies. The Bible of Anjou dates to 1340 and is a unique and beautiful illuminated manuscript created at the Royal Court of Naples. To learn more about the manuscript and The Illuminators’ hackathon project, have a look at their project poster in the BiblioTech Zenodo community. To read more about the hackathon and the results, you can visit the BiblioTech website.

 

Sandra presents the Illuminators’ final project during the closing event of the hackathon. On the right, the Illuminators pose for a team photo.

 

What first interested you in the hackathon? Have you done one before? Can you tell us more about your background?

This was my first hackathon and what interested me were the datasets. I also liked the fact that participating in the hackathon was available to all students. Since I’m only a bachelor’s student, it was a nice way to get launched into the program; originally I started studying French and Latin, but then I switched over to theology. For the hackathon, I was interested in an academic sense, but I also thought it was a good opportunity to learn new skills.

What was your primary concern when beginning the project?

Maybe my lack of technical skills. I found myself in a group with people with a lot of skills already and didn’t really know where were we going with it. But this worry was resolved quickly by just trusting the others in my team. We lifted each other up.

What most excited you about working with this dataset?

The beauty of the object. As an illuminated manuscript, it is aesthetically very beautiful.

Were you familiar with the Bible of Anjou before the hackathon?

I was not familiar with the Bible of Anjou itself. I was familiar with the Bible and Bible translations, but for this specific piece, I had only heard of the name and knew it is a big deal in the Maurits Sabbe Library.

What was the brainstorming process like for this project?

We had a lot of ideas come up originally; stuff based on the images and the text, but the text and the potential of OCR was more uncertain. With the images, though, we knew that with the animals we could make a sort of “medieval zoo.” Looking at the illustrations of musical instruments and categorizing the illustrations were some of the other immediate ideas.

What was your primary audience for this project?

I don’t think we really had an audience in mind when developing the project… it was more general. We just wanted to make the images work.

Were you inspired by any other platforms or projects?

We weren’t really inspired by anything specifically. One of the main aspects of our project involved creating GIFs of the illustrations in the manuscript. For this, we just came up with the idea and then researched how to do it. Researching the options told us it would be possible, and we just wanted to do it.

How were you able to apply knowledge from your studies to the project?

I was mostly learning as I went. But for the poster presentation, we did look into the historical context for the Bible of Anjou, and I saw some stuff that I already knew from my studies. So there was a bit of overlap. One interesting takeaway: I went to the library and had a great talk about the book and its content and the different locations it had been stored in. This helped us to be able to also contextualize its history.

Was your role in the project different or in line with what you were expecting?

My expectations were different. I tried to not have too many since it was my first hackathon. The experience turned out to be mostly in line with what I thought it could be. Since my technical skills were limited, I figured I’d have to learn some new things, and since I’m strong with presentations, it wasn’t too surprising that I ended up presenting our project during the closing event.

What kind of advice would you give to a team doing their first hackathon?

Try to be flexible and available. It was nice having 10 days and not having to meet every day, but it was necessary to sometimes see everyone. The Microsoft Teams environment was also very important to attend the meetings online. The organization within the chat on Teams was good, so there was a good stream of communication.

What kind of advice would you give to someone in your field, specifically?

I would tell them that they definitely have something to offer to the team. If not the technical skills, then it’s at least a way to provide more perspective. We all had different ideas and brought new ideas and perspectives.

 

 

 

The following is an interview between Alisa Grishin, Artes Research intern 2022-2023, and Heike Pauli, BiblioTech Hackathon participant and MA student in linguistics. The hackathon took place in March 2023. It was a 10-day event and included a pre-hackathon orientation moment called “Meet the Data, Meet the People.” Heike’s group, the Digital Peripatetics, worked on the Lovaniensia dataset. Lovaniensia comprises the old academic collection, featuring the work published by members of the Old University of Leuven and output linked to the university spanning the period between 1425 and 1797. You can learn more about the team’s project by having a look at their project poster in the BiblioTech Zenodo community. To read more about the hackathon and the results, you can visit the BiblioTech website.

Heike delivers her team’s project presentation at the closing event of the hackathon. On the right, three members of the Digital Peripatetics team pose for a team picture.

What first interested you in the hackathon? Have you done one before? What is your background?

I had not done one before. My initial interest was because it was an opportunity to combine my passion for Latin, Greek, and AI. You don’t see that overlap often. So before the hackathon, I hadn’t seen a place where I could combine my overlapping interests in AI and the classics. This was a unique opportunity for that. Then a few of my professors mentioned it, and I continued hearing about it–probably like three times–and took it as a sign [laughs].

What was your primary concern when beginning the project?

I would say, for me, the OCR. But that was a surprising concern. We had to skip it entirely due to the quality and the number of errors. Apart from that we didn’t have a lot of troubles. And once we established that the OCR would be a challenge, we all just worked together. It was a missed opportunity because there was a lot we could have done and a lot available, but since we decided to look at the metadata and not the OCR it was a bit restricting. I would have liked to look at the text more. There is still a lot of room to explore this data.

What was your primary audience for this project?

Our target audience was mostly people interested in the Old University. Our group leader was a prime example of the type of person we were catering to. We tried to look at the university itself: what was being created, who was there. So, the target audience was basically the people who were in the group [laughs]. It was almost like we were creating a resource for ourselves.

How did you establish your methodology and approach to the dataset? Were you inspired by any other platforms or projects?

Indeed, I think some people were inspired by past projects. We just had to start with the metadata. We did the usual stuff like making a word cloud and other things you would typically do for Natural Language Processing (NLP); it was pretty exploratory. During the introduction at the “Meet the Data, Meet the People” event, the explanation of metadata was also really helpful. And it just started with the basic approach, and then, from there, we knew where to go. We used the tools we already had. I was at first disappointed that we couldn’t make a crazy new tool or code, but it’s challenging to do that in 10 days.

What was the brainstorming process like for this project?

We had a lot of ideas at first. At “Meet the Data, Meet the People” everyone was writing all over the brainstorming paper. Then we had to tone it down to make it coherent and achievable. We picked three or four tasks, which was only the tip of the iceberg. We had to think about what was manageable, so the different analyses were the best approach.

What was your role in the project and how was it different/in line with what you were expecting?

I was expecting that I’d need to program a lot, but I’m not an expert or anything. So it wasn’t necessary; we found that a lot of tools exist which could help with that. I focused more on the language. It was nice because we all had a place where we could best apply our skills. Some people were really great at social network analysis and worked on that, and my job was to work on, or maybe get mad at, the OCR [laughs]. Sometimes it was really accurate and helpful and then other times there were errors. At the end, I found my place in the language analysis side. So in looking at my background, the Natural Language Processing was an obvious approach. And I also loved presenting the project at the closing event. We divided the tasks according to what people wanted to do. At first it was hard to organize it that way, but it helped make it coherent and a singular project.

How did you use your academic experience to help with the hackathon? 

The easiest part was the Latin. We were the most academically prepared for this. For me, it also helped to see that I could do some useful stuff with my interest in computational linguistics; I already knew a bit of Python, so it was nice to apply my DH skills and see that they are useful.

Was there any main motivator/goal that encouraged the team when things didn’t go as expected?

It helped that we all had a background and were interested in the dataset ourselves, so that was our main encouragement. It was within our field and we all had a common love for the material.

What kind of advice would you give to a team doing their first hackathon?

Just do it! Don’t overthink it. Even though there was a prize, the main interest was to get knowledge and to explore the data. We didn’t worry too much, honestly. Sometimes there can be frustrations or things won’t work, but those aren’t necessarily failures and you can explore new approaches.

What kind of advice would you give to someone in your field, specifically?

You can bring a new perspective even if you don’t know about technology. You can help those with a technological background if you’re open to it. There’s a stereotype for people in the Classics that we don’t know about computers and only care about books [laughs], but you don’t have to become a professional programmer during or after the hackathon. The knowledge you gain could be helpful for research, your career, anything. It’s not just for people who know how to program. It’s an option for everyone. Blur the lines.

Final comments:

I found it very useful to have a chance to explore all the fields I’m interested in. I would consider participating again. The 10 days was also a good timeframe in the grand scheme of things.

The following is an interview between Alisa Grishin, Artes Research intern 2022-2023, and André Davids, BiblioTech Hackathon participant and employee at KU Leuven Libraries Economics and Business. The hackathon took place in March 2023. It was a 10-day event and included a pre-hackathon orientation moment called “Meet the Data, Meet the People.” André’s group, the Demographic Dynamo, worked on the historical census dataset. You can learn more about the team’s project by having a look at their project poster in the BiblioTech Zenodo community. To read more about the hackathon and the results, you can visit the BiblioTech website.

André Davids and Stijn Carpentier, two members of the Demographic Dynamo team, receiving their prize from Demmy Verbeke, jury member.

What first interested you in the hackathon? Have you done one before? What is your background?

It was my first hackathon. I saw an advertisement about it and thought it looked interesting, but I didn’t subscribe because I didn’t have a technical background. I was convinced by Nele Gabriëls who enthusiastically encouraged me to join. As I provided one of the datasets, industrial countings from the 19th century in Belgium, I was already familiar with some of the data. At the time this dataset was created, Belgium had a top class statistician, Adolphe Quetelet, and the Belgian statistics were the first that were open to the public and for research. The Belgians were the first to make this type of data available for research. It became a model for many other countries. This is also why it’s interesting to other countries to see the Belgian countings. So I’ve been converting these over to Excel files and universities often contact me regarding this dataset. I wanted to see the potential up close of using a dataset like this for researchers from Belgium and abroad.

I started working at KU Leuven Libraries in January 2000. It was mostly by coincidence. I graduated with a degree in Information and Library Science and then came to Leuven to fully learn Dutch. By coincidence, I found a job at KU Leuven; it was actually my first job interview. My first task was to be at the information desk, and then I switched to cataloging and then acquisition. Now I do digitization. So, I’ve been here for 23 years, but my job is always changing; there was never a day when I didn’t want to come to work.

What was your primary concern when beginning the project?

My primary concern before seeing who was in my group was that our group wouldn’t have enough technical skills to do something nice. My group was made up of mostly researchers, and I saw very quickly that I was a bit ad hoc and that they knew a lot. We started on our project quite late. At the beginning, we weren’t sure what to do with the data and had to make a selection. I was already very familiar with the data, so I helped them select the tables. 5 days after we received our datasets, we had a meeting and decided what to do with it. At the beginning, I was a bit stressed because time was passing and we didn’t have a concrete goal. After that meeting though, we found direction. So even though we were starting late, the technical members were very efficient.

How did you establish your methodology and approach to the data set? Were you inspired by any other platforms or projects?

Nope. The teammate who came up with the idea we went with had a dynamic map of Belgium, so she said we could adapt that. Then we looked at the data to see what could be used for the map. We saw that we had tables that showed internal Belgian migration. By putting this on a map, you could watch how people moved from one place, such as Brussels, to another. It was actually quite impressive to me.

What was the brainstorming process like for this project?

At the “Meet the Data, Meet the People” event, we actually spent most of the time coming up with a name [laughs]. We didn’t have a lot of ideas at the first meeting. And it took a few days to find that direction. But since I knew the data, I was able to share my knowledge with the team.

Were there any obstacles the team had to overcome?

Well, some of the members were absent because they were attending conferences. The people who were the strongest technically were not able to be at the closing event where we presented the project. I could speak mostly to the data, but luckily Stijn volunteered to present since he already does that pretty often. I told him he should be a salesman [laughs]. We were worried that there would be more technical questions. Neither of us could really speak to the code, but luckily the questions didn’t go there.

What was your role in the project and how was it different/in line with what you were expecting?

I don’t know what I expected. I had no idea what the outcome would be. I was pleasantly surprised that we had a dynamic product. But given the time frame, I wasn’t expecting to do something like that. Still, it was nice to see how quickly people with a technical background can do something.

What advice would you give to someone who is hesitant to participate in a hackathon due to their background?

I was initially afraid since I don’t have a lot of technical skills. But now I would say that everyone has something that they can bring. In my case, I knew the data and was willing to put a lot of time into the project. But if someone mentioned to me that they didn’t want to participate because of their technical skills, I would just say “[it] doesn’t matter. Other people will have the technical skills.” Just the fact that someone is willing to participate means that they will have ideas to bring and can contribute in their own way.

Did you apply any skills from your career to the project? Did you take away any knowledge you can now use for your job?

I didn’t really get new technical skills since I didn’t really have any preliminary technical knowledge. When we started working on the industrial counting project, though, we were focused on the numbers, not the categories. Eventually, as a researcher, I decided to start working on the categories. So I started using color codes for the tables and when doing this project, my teammate said that this actually helped him a lot with the code. So now, in the context of my work, I make sure to use the same colors since it will help the people working on the data in the future.

Also, last week, two researchers came to me and were asking for new volumes. I showed them our dynamic map because even though they need the volumes, showing our map shows them the possibilities of the industrial data.

What are some benefits of a hackathon for someone with a career in the GLAM sector?

It was a nice experience. Because we won the hackathon it was nice to have that, as well. It was nice to see that the data we had been working on could produce a winning project. But even if we hadn’t won, I would have come away with a good feeling. Even though I’m quite competitive [laughs], in this case, I was just happy to have something to show. The census data is usable for a ton of different fields and faculties and there was already interest in the data. So there’s still a lot of potential in the development of that. And it’s nice to see that people are interested in the data and what we generated even before this project.

What kind of tips, as the winning team, would you give to a team doing their first hackathon?

I feel that, in this case, winning was not our main objective. If we had more time, we could have done a lot. Just have an enjoyable experience and don’t think too much about winning. I’m not even sure if we would have had a better project if we had wanted to win in the first place. I don’t think we would have because of the pressure. But even if I could restart and pick a team, I would still work with this team and this dataset.

The following is an interview between Alisa Grishin, Artes Research intern 2022-2023, and Fien Messens, BiblioTech Hackathon participant. The hackathon took place in March 2023. It was a 10-day event and included a pre-hackathon orientation moment called “Meet the Data, Meet the People.” Fien’s group, “God Save the Tweets!,” worked on the contemporary news media dataset featuring tweets including the hashtags #queueforthequeen, #abolishthemonarchy, and #queenelizabeth during a short span of time around the death of Queen Elizabeth II in September 2022. You can learn more about the team’s work by having a look at their project poster in the BiblioTech Zenodo community. You can also find data related to the technical aspects of the project in the God Save the Tweets! GitHub repository. To read more about the hackathon, view the full photo album, and discover the teams’ results, you can visit the BiblioTech website.

 

 

What first interested you in the hackathon? Have you done one before? What is your background?

When I first learned about the hackathon, I was immediately drawn to the opportunity of  tackling a challenging problem within a limited time frame and collaborating with a team of individuals with specific expertise from a variety of backgrounds. I have a background in art history and digital humanities, especially with born digital collections in the GLAM scene. I can archive and preserve a tweet in a stable way, but have little knowledge on how to analyze the output. So this hackathon provided me with a learning platform where I could go about learning about this through trial and error.

What was your primary concern when beginning the project? Interface? Usability?

We analyzed the tweets from the first 10 days of the passing of Queen Elizabeth II. Our primary concern at the outset was the sheer volume of the data. We were confronted with a vast corpus comprising multiple languages, but we swiftly narrowed it down to English only. Despite this refinement, we still faced the challenge of dealing with a substantial dataset of 300,000 posts. Our main objective became comprehending and effectively managing this extensive stream of tweets by employing suitable methodologies.

What kind of audience did you have in mind?

That’s a tricky question.

The project posed a complex challenge as we used text analysis, sentiment analysis and data mining techniques. In addition, we also created a tweet generator, utilizing our existing corpus to craft newly generated tweets. The primary objective of our tweet generator was to cater to users who sought to share opinions and partake in engaging discussions on Twitter, fostering a sense of community and/or collaboration. Our target audience encompassed not only researchers but also a wider public audience, aiming to provide a platform for diverse individuals to express themselves and facilitate meaningful (or not so meaningful) interactions. In general, we were aiming for a broad public, not just researchers.

How did you establish your methodology and approach to the data set? Were you inspired by any other platforms or projects?

The methodology revolved around text analysis, also known as text mining. To ensure relevance, we filtered the English language tweets using specific keywords and then employed sentiment analysis techniques to analyze the data.  In addition to drawing inspiration from other sentiment analysis projects, we benefited from the expertise of one team member who had previously explored sentiment analysis methodologies during a digital humanities course.

When it came to the tweet generator, we found inspiration in various existing tweet bots. We especially liked the @TorfsBot tweet bot, from the old rector of KU Leuven, which had publicly available source code that proved immensely helpful. While we drew insights from existing bots, we primarily relied on our own experiences and creatively adapted concepts from other tweet bots to shape our unique implementation.

Why did you choose to do the most active users as opposed to a larger pool? Was it just to downsize the data size or was there another reason?

We focused on the most active users because it helped us get a grasp on the users and those who were actively participating in online discussions. We observed an occurrence of overfishing in specific hashtags, where certain users exploited the hashtags to promote unrelated content. So, by looking at the top 10 or so active users, it allowed us to better understand the overall sentiments surrounding the Queen’s passing. This approach aided us in filtering out the excessive use of certain hashtags and reducing their impact. It allowed us to focus on the overall sentiment analysis without being influenced by the promotion of unrelated tweets or ideas that were going viral at the time.

How did you classify words/users on a -1.00 to 1.00 scale?

We utilized a sentiment analysis algorithm that employed a numerical scale ranging from -1.00 to 1.00. A score closer to -1.00 indicated a negative sentiment, while a score closer to 1.00 indicated a positive sentiment. The algorithm took into consideration various linguistic and contextual factors, such as keywords, to determine the polarity of sentiments expressed in the text. It is important to highlight that one of our team members had expertise in sentiment analysis, which significantly enriched our project.

Given the size of our team, we were able to allocate tasks efficiently. I primarily focused on developing the website, while other team members handled tasks such as presentation creation, analysis, and more. This division of responsibilities within the team proved to be highly beneficial, ensuring a smooth workflow and allowing each member to contribute their expertise to the project.

Was there any main motivator/goal that encouraged the team when things didn’t go as expected?

Digital humanities is all about embracing the adventure of trial and error, and boy, did we dive headfirst into it! Our incredible team leader, Leen Sevens, was our ultimate cheerleader, always keeping our spirits high with her GIFs and emojis. But it didn’t stop there – the organizing team of the hackathon also rocked our chat with their infectious motivation. Knowing that we had this amazing support system, cheering us on and having our backs throughout the process, made the journey all the more exciting and rewarding. It’s safe to say we had a real dream team!

What were some of the roadblocks you faced?

Our initial plan was to generate tweets for the tweet generator in the backend, but it proved to be more complex than anticipated. Not only would it have required purchasing additional storage, but it simply didn’t work out as intended. Thankfully, we had a solid plan B in place. We resorted to manually creating the tweets for our generator and seamlessly integrating them into the HTML and Java Script system.

Timing also presented its own challenges. With numerous tasks and responsibilities on our plate, the 10-day timeframe seemed like a whirlwind. However, there was a silver lining to this intense rush. It brought the entire team together, all of us uniting our efforts to meet the deadline. In a way, it fostered a sense of community among us, reinforcing our shared commitment to achieving our common goal.

What kind of tips would you give to a team doing their first hackathon?

I’ve already written some down [laughs].

1. Plan, divide, and conquer. Let folks explore what tickles their brain and make it a learning experience for everyone.
2. Communication is key. Regularly touch base, share ideas, and foster an environment of open dialogue.
3. Embrace the beautiful chaos of errors, because that’s where the magic happens!
4. Have fun and enjoy the process. It’s a great opportunity to learn from each other and work towards one shared goal.

In March of 2023, Artes Research Intern Alisa Grishin interviewed Professor Fred Truyen of the Faculty of Arts. As a professor in the Digital Humanities and Cultural Studies programs, Prof. Truyen has also been involved in numerous projects related to digitization, archives, databases, and other manifestations of DH. In this interview, he was asked about best practices for organizations, industry structures and barriers, as well as some general reflections on the development of the humanities.

---

Based on your background in ICT, how do you think there could be a better relationship between more traditionalist approaches to the humanities with newer developments, such as Open AI? Why do you think certain barriers still exist?

I think with Open AI we have come to a pivotal moment. There has been a long tradition of linguistics research, engineering research, and mathematical context to come to this point. We are starting to realize that we will be operating in a more intelligent environment and it’s not our kind of intelligence – our digital environment is a more responsive, anthropocentric environment and it allows us to build up our world and our world views in our own image. I think it’s a pivotal moment and forces us to rethink many of the approaches that we do daily which will be much more mediated and information-based. But for me, it’s always a rediscovery of fundamental humanistic skills. You know that I studied philosophy, and I remember that at a certain moment, there was this idea that ‘oh philosophy is just talk and now with social sciences we will do all these things empirically and that is true, you can do a lot in social sciences and they have made a quantum leap in progress and insights which also transpires in the kind of new innovations that in these disciplines have emerged. We statistically can see that these are very innovative domains. But in my view, the fundamental paradoxes of humanity, which have been captured in the basic philosophy context, have never been superseded by any kind of science whatsoever. So they have never been solved. And perhaps we shouldn’t have the ambition to solve. The great things of the past have taught us to appreciate the limited position of humanity in the world. Our essentially very limited understanding of what we are doing here, why, and where it comes from – even if there is substantial progress in personology, neuroscience, that doesn’t solve the core paradoxes. That’s why I think that critical thinking in the humanities will always stay with us. We will always have recourse to expressions like art, music, to partly cope with this failing and understanding that it is just part of our destiny. There will never be total clarity.

And from a more practical perspective, what do you think the potential role of hackathons, such as BiblioTech, could have in improving the relationship between more scientific disciplines and the humanities?

I think a hackathon is a fantastic example of interdisciplinarity. You have an element of serendipity, you bring people together at random, mix profiles, you have an open theme, you try and see what can come out of it. By trying to make something very practical, not only are you exchanging ideas, but you’re finding things that work. And in that sense, it’s always interesting when there are interdisciplinary themes. That is the charm of something like digital humanities. You work with people with very different backgrounds to find solutions that you want to explore and implement. I also think that libraries are an excellent place to do so. I have an extremely warm heart for libraries, museums, and archives. The library was meant as a place to safeguard and consolidate knowledge. You want to safeguard intellectual production, primarily books, and make this accessible. This absolutely honorable mission is still behind libraries today. They were very early to understand that this would transcend the book, would include every new meaning of knowledge expression, and that they had to go digital, and go into multimedial formats. And so many libraries were always at the forefront of organizing these kinds of hackathons and their mission is also closely related to things like what Wikipedia is trying to do. It’s a natural environment. So many people might think that the heritage sector is a kind of mummified sector of people doing the same thing all over again *laughs*. It’s absolutely the contrary. I’ve never experienced such a dynamic environment with people constantly rethinking their roles, even when these roles have very formal missions like archives, which are partly very legal missions. They have certain duties that they just can’t set aside. They have an extreme ambition to rethink the way in which it evolves. To come up with new ideas about what they should archive, how, who should decide what is an archive, what condition can be granted, all kinds of questions. They get a new environment for technology but it’s still the same question.

You also started going into my third question: “how do you see the intersection between Cultural Heritage (CH) and Digital Humanities (DH) in your line of work?” Archives and heritage can be seen as quite traditional approaches to managing our history. Can you elaborate on the importance of incorporating DH in these sectors?

Yeah, there’s a clear interest of CH in the DH profiles. They evidently need people with sufficient humanities background to actually understand to the full mission, the collections, the preservation that’s used, etc. You cannot just train that overnight. Most of these professionals in the sectors have a quite solid background in the humanities. The same goes for implementing digital solutions. You cannot just invent an engineer in one year *laughs*. So we need to bridge very, very distant disciplines that require deep training and the DH profile is an interface profile. In my sector, the heritage sector, we see this rather in more junior positions and we hope that they will be the next generation middle management. There is a very high demand and that is situated more at the junior-master level that heritage institutions are now taking on board. And they come from a variety of domain expertise, but with sufficient understanding and vision of digital technologies and digital reasoning. We see a trickle-down effect. If you see the digital humanities, you see techniques have been doubled up with computational linguistics, then corpus linguistics, then broader language strategies. Now we are taking hold of history because also historians work on texts. And so there is a whole battery of tools that you can just take on board from linguistics and you can apply to historical research. Technologies have also been doubled up with social science; I think of everything that has to do with social network analysis and all the tools there. We see from certain disciplines, a trickle-down of technologies to broader humanities fields. To me, don’t be afraid, it will never change the core of the humanities. That has a perennial value and will be part of society in 100 years. It’s not so that we are going to end up with statisticians and engineers and robots, *laughs*. It’ll be a very important part, but not the only part *laughs*.

And in a broader sense, what do you wish the public and the academic world and beyond knew about DH?

Well, I think they should know that humanities easily translates into the concepts and problems that it is part of critical thinking about the challenges that we face today. So you need this humanities background and the humanities disciplines have the capacity to adapt to the requirements of today’s science. Python is a part of scientific language and just like English, has become a lingua franca for scientific research. They are part of the way of scientific work and scientific thinking and so a digital humanities student has sufficient background to express themselves in that language and to assess and to discuss with developers how this can be implemented without being a software engineer, because that’s not the intention. When I started with ICT at the university, many of my colleagues who were responsible for ICT in the humanities faculties came from the humanities and were partly self-learners. So I hope that in many sectors people understand that digital humanities students have this capacity to bridge expertise and to make a coherent analysis of the different aspects involved, but still with a problem-oriented perspective behind it.

What do you think makes the humanities so adaptable? Is it the fact that it’s so abstract and focused on critical reasoning and perhaps isn’t as confined to theories?

I think it has to do with that. It’s like learning a second language and to learn a second language it’s always beneficial if you master your own language. Then you have a head start when you want to learn another language, and it’s the same here. We do want students with a solid humanities background and so they need to have proper training and that’s why we are not offering it [the Master of Digital Humanities] as an initial master at this moment. We had an excellent doctoral defense half a year ago from a student from architectural engineering who does these excavations in Turkey with a very interdisciplinary team of biologists, sociologists, anthropologists, archaeologists, and historians. So it’s a very interesting binary. And she focused on this, on the negotiations between these different teams. How can they experience the excavation side as a common object of study? How? How does it work? Because they use different time scales, they use different terminologies. They have thoroughly different basic concepts, often using similar words. But meaning quite different things. For me, that is digital humanities. Trying to understand how small differences in concepts can lead up to difficulties in implementations. This can force revisions of procedures; it’s a kind of humanities engineering. It’s not true engineering, but it’s humanities engineering. This is really at the core of what a digital humanist should be doing; helping in this translation of data into information and how it emerges.

And then going off of that, what would you say to a student coming from a traditional humanities background who’s interested in DH, but maybe a little hesitant because they don’t have the exact training?

Be confident. Be confident in your own skills with your training in the humanities, you are well prepared to take this step. So be confident and be bold. It’s our philosophy that we want to empower students. Because the frustration could be that you have this rich historical literacy or art background and you are faced with the challenges of today and the dominating role of technology. You are forced into a consumer role and that can be very frustrating. You feel powerless because you don’t speak the language of technology exactly. And to this we say yes, you can learn this language, you learned languages before. You can make this step and you can become a proactive user. You can work in teams that change technologies. To give an example, in heritage, there is the challenge to adopt the contents that we digitize and put them out in the open. Many of these archives are written in languages that are not adapted to today’s times. And if you think about the colonization context, you understand the depth of the problem. Many of these descriptions are racist and we shouldn’t be shy about addressing this. Now the challenge is how can we meet the demand of Open Access? How can we give the same collections to these people in a non-hurtful, contributive way? Well, manually, we can’t do this. It’s all technology, it’s all databases, it’s information systems, it’s artificial intelligence. But who is leading the teams? Historians, anthropologists, sociologists and lawyers. These [entities] are leading the way in developing the ontological approaches. What kind of software do we need? How can we give co-governance? How can we enable communities to actually participate in the development of the technologies that they will be using?

How can museums and other cultural organizations better incorporate DH into their work and mission? Have you noticed a significant increase in cultural institutions using DH methods? Do you have any predictions or any ideas on the direction of that? 

The sector actually is embracing this. It’s the role of the European Commission to stimulate innovation in these domains. What we lack a bit in Europe is “platformization.” The big platforms are of course not in Europe and that’s a sore point that needs to be addressed still. But the sector is embracing the development of databases, imaging techniques to scan the objects, digital tools for crowdsourcing for engaging audiences, 3D technology, and augmented reality applications. So the sector is embracing that and mid-size to large heritage institutions all have a very decent digital part of their working and they often still lack an embracing digital strategy. That is what we are working with now. 

AI is also in many of the current projects that are being funded today. I’m currently involved in a project called AI4Europeana. So the name says it all, yeah, but there were AI projects in the past already. And the reason is simple. The reality of AI is very, very neutral. And so in research projects, we are also thinking about how we can diminish a bit of “black box” over AI. How can we give people more confidence in trusting what the algorithm is doing? I see that when you look at AI programs in the heritage sector. It is often related to rebuilding trust relationships and using digital environments for that by looking at how we can reestablish transparency.

So that’s our role from the humanities: to challenge the bias, too. I’m now involved in a project which is called DE-BIAS for exactly that reason, as we are trying to see in the heritage sector where the bias is in the data that we accumulate and that we are now publishing through digital means.

Are there then some challenges in DH in terms of sustainability and preservation of digital materials? How do you prolong the benefits of these approaches?

The heritage institutions that are now safeguarding and preserving will gradually contain more and more digital artifacts. So there is already a movement underway to think about how we can acquire digital assets and how we can safeguard digital production. 

The core rules of a library, a museum, and an archive in relation to digital artifacts will include the preservation of digital artifacts. Preserving old versions of software; preserving cd-roms, you name it. And it’s increasingly challenging. We already saw this with, let’s say, the recorders of the 80s; these are now objects that are for preservation in an audio-visual archive. These are quite challenging things and a lot of technological thinking is needed to address proper preservation methodologies for that. You have analog film tape but you also have videotape, and videotape is also already the next step in the preservation problem. And then we go to the true digital formats and that is a whole history on its own, too. And so historians of the future will, instead of treating manuscripts, early books, early prints, etc., they will be treating tapes. And I’m not even sure that you can open some older files in the current version of Windows. So these are all challenges that lie ahead. And there are conferences about that and digital preservation and so there are a lot of disciplines emerging in that sector. But yeah, I guess the work is just never done. It’s just a matter of adapting to whatever is next in line for preservation. 

Shifting gears a little bit to briefly focus on cultural policy, are there any improvements that can be made to European cultural policies as to encourage DH? Or has Europe, at the policy level, been relatively receptive to digital approaches due to an interest in innovation?

Yeah, certainly reference to Europe, it also has to do with the specific mandate that the European Commission has and the balance that it needs to keep with the Member States, which is always a very fraught relationship. And so it was always the idea that culture is something that we export, is something that attracts people to us, is something that we have a long history in, and so we should be at the vanguard of what happens in culture. And this connects to the idea of innovation because innovation is truly at the heart of the Commission’s mission. They have always thought that there is a nice mix between innovation and culture and this means that, for example, when you look at heritage at the European level, it’s often a discussion in close connection with the creative industries. So how is Europe’s heritage part of the new creative industries and how can we valorize this? So on cultural policy, I think that it has been colored a bit by technology, by innovation at the European level.

For example, the rediscovery of craftsmanship that you see throughout Europe. You see this integrated in digital approaches. There are many quite interesting projects which are trying to marry look, quality, craftsmanship, the rediscovery of natural, agricultural processes, and seeing how digital technologies can be helpful in that context. For example, there are many YouTube channels on how to do crafts, so that there is a natural way of self-organizing knowledge transfer on very local things. The digital space mediates between the diaspora and the local. And that’s also empowerment because communities can protect their tradition and their sociality. 

Are there common internal concerns when approaching a DH project? Any legal, structural, and sustainability concerns?

From the viewpoint of the Commissioner, but not from DH. I think that their main concern is the human resource, the competency. Do we have the right profiles? Do they have interdisciplinary skills? If you need a conservator or engineer or a graphic designer, well, that’s a variety of roles that you need to integrate. That’s something totally different than when you have your classic preservation work or classic digitization work. That’s very focused. But the DH project goes broader. And then the real scare is, can we pull it off? Can we really bring the right people together and can we pay for the resources? That’s why I would think that we need a mindset shift. In the beginning, when organisations went to digital projects, they were side projects: we need a new cataloging system; we need a website; we need a kind of community forum; we need a social media manager. It was all fragmented, small-scale things that you think you would do and now we see that the digital permeates every aspect of your business. And that is a scary thing, because you realize that you need very, very different competencies than before.

What predictions did you have about DH which have not yet been realized, any technology that never took off, methods that didn’t become mainstream etcetera?

Ohh. That’s a difficult one. I think we waited very long for the breakthrough that we now see with generative AI. I think it was a much longer route and credit to my colleagues who held on! I don’t think we had misconceptions about what would happen. I think we always took into account that adoption would be slow, but again, in the 21st century, this is pivotal. And in academia for humanities, it was the monography in literature that was important: the article that you wrote by yourself as a single author. That took very long to go away. But today it has dramatically changed. The same if you look at PhD proposals. We waited for the whole last quarter of the 20th century for PhDs that would become more interdisciplinary. Now, in most disciplines, it’s just a given. 

I’m not sure that there are a lot of promises that didn’t come through. In linguistics, language technology took longer than expected. It then went through more probabilistic statistical analysis and that brought about the Googles of this world. But now we see that again.

So nothing really surprises you too much about the direction that technology is taking?

Well, what we couldn’t imagine is the power of imaging technologies and its response from the world. And now we are even talking about microdrones in your body. So these are technologies that were underestimated. And it’s used everywhere now, also in archaeology and on heritage sites. So that’s a type of technology that’s very rapidly taken hold that we’d underestimated.

And then what do you think the future of DH looks like? 

Well, there is always this debate about whether Digital Humanities will just become humanities or whether the humanities will become digital humanities. I think it’s a silly question. For example, photography came from scientific research in optics and chemistry. Chemistry advances made photography possible. So it came from science and it’s a technology that we all adopted and that we don’t even question. We don’t see it even as technology. The core of the humanities is linked to the process of human existence; it will exist forever. It’s not something that was part of modernity. We now speak about digital humanists, but the “digital” is such a broad term. Think about quantum computing, etc. That could bring us a totally new way of approaching technology. Will we still call it digital then? Or will we talk about quantum humanists? I don’t know, but I don’t care. It will be humanist.