- Collaborative Digital Heritage Studio

CoDHerS News

Preserving Stories: CoDHerS Summer Research Assistants Reflect on their Experiences
Our Summer Worklearn assistants share what it was really like working with global indigenous archives and digital heritage preservation, the skills they picked up, the challenges they faced, and what the experience meant to them.

September 5, 2025

Briefly Introduce Yourself

Kamila Maral

I’m a fourth-year Political Science and Law student, finishing the last two years of my dual degree with Sciences Po at UBC. I’m from Kazakhstan, and as a true nomad at heart, I love exploring new places and learning about different cultures, languages, and traditions. My team refers to me as the “Kamfire of the lab” for the positive energy and enthusiasm I bring, even during the most stressful moments.

Berfin Ustabaş

I’m Berfin, an undergrad in Global Resource Systems at UBC and a Research Assistant/Designer at the Collaborative Digital Heritage Studio (CoDHerS). I design systems and interactive solutions for community-driven projects, with a focus on Indigenous cultural heritage. I grew up in Istanbul, Turkey and I’m Hemshin (Turkish Armenian) and I care deeply about health equity, women’s rights, and ethical storytelling. My team sees me as the “Vision Weaver” behind our projects.

Aibibi Akshulakova

I am a third-year student, double majoring in Honours Political Science and Economics. I am from Astana, Kazakhstan, and very passionate in cultural preservation, public policy, dance, and graphic design. My team calls me “A.I.bibi” because of my expertise in archives and cultural protocols.

Sai Manas Pandrangi

I am a 2nd year undergraduate student majoring in Computer Science at the University of British Columbia. I work as a Software Engineer at the Collaborative Digital Heritage Studio. Moreover, I am a pianist with over 12 years of experience. I enjoy spending time outdoors in nature and have been going hiking in North Van lately. My team appreciates how I serve as a bridge between code and culture.

What motivated you to join CoDHerS, and what insights have you gained about the global Indigenous landscape, archives, or digital heritage?

Kamila Maral

Berfin Ustabaş

I joined because CoDHerS sits exactly where I live: between community care, design, and technology. Our work treats archives as living relationships, not neutral storage. I’ve learned how protocol, consent, and data sovereignty shape every decision; that language revitalization and metadata aren’t “back-office” tasks but cultural lifelines; and that elders’ knowledge and community governance must lead the tech, not the other way around.

Aibibi Akshulakova

I was motivated to join the CoDHerS Lab because of my strong interest in cultural heritage and the ethical dimensions of digital preservation. Coming from Kazakhstan, I was especially drawn to how Indigenous and marginalized communities engage with their histories and knowledge systems in ways that challenge Western archival norms. Through my work, I have gained insights into the global Indigenous landscape, particularly the importance of culturally sensitive metadata, relational approaches to information organization, and the role of community-driven decision-making in shaping archives.

Sai Manas Pandrangi

I was motivated to join the CoDHerS lab because of its domain of focus- the intersection between software and cultural heritage. One of CoDHerS’ goals is language revitalization, which I deeply resonate with, being a polyglot myself, speaking English, German, Hindi, & Telugu. Since joining CoDHerS, I have developed a deeper appreciation for Indigenous cultures and languages, along with a newfound respect for Indigenous elders.

What have you taken away from working on collaborative research projects this summer?

Kamila Maral

I have learned that working collaboratively in a team is really valuable, and that it’s important to be able to share your vision, ideas, and perspectives with others. I also found it fascinating how much more productive and effective it is to work together compared to working independently. Another thing I’ve learned is that when working on interdisciplinary research projects, collaboration is essential to avoid mistakes and problems in the future.

Berfin Ustabaş

Co-design beats “build then ask.” Listening first, documenting clearly, and iterating openly create better tools and stronger trust. Interdisciplinary teams move slower at the start, but the outcomes are cleaner, kinder, and more sustainable.

Aibibi Akshulakova

Working on collaborative projects this summer taught me how interdisciplinary and team-based work really is. I learned the value of clear communication when merging technical, cultural, and ethical perspectives. I also saw firsthand how knowledge co-creation, rather than top-down research, leads to richer and more inclusive results. One of my main takeaways is that collaboration is not about dividing tasks – it’s about learning to listen deeply and adapt methodologies so that everyone’s contributions are valued and centered.

Sai Manas Pandrangi

Over the summer at CoDHerS, I experienced firsthand how great things can happen when people come together as a team. I also had the opportunity to practice the essential skill of listening and translating problems, perspectives, and decisions into technology solutions.

What challenges did you encounter, and how did you and your team address them?

Kamila Maral

One of the main challenges I encountered was understanding the technical aspects of the projects, especially how different software works. At first, this felt overwhelming, but thanks to my team’s patience and willingness to explain things, I gradually became more confident. By the end of the summer, I was able to understand everything much more clearly, and what once felt complicated started to make sense.

Berfin Ustabaş

Translating community needs into technical schemas and access rules was hard, especially balancing openness with cultural protocols. We addressed it through plain-language documentation and metadata tiering and clear governance (roles, review cycles, and consent pathways).

Aibibi Akshulakova

One of the biggest challenges I faced was having to quickly learn completely new skills – whether it was video documenting and editing, or gaining the technical knowledge needed for web development and digital platforms. At times, the learning curve felt steep, but our team approached it by breaking tasks down, sharing knowledge, and supporting one another’s growth. We relied on tutorials, peer feedback, and lots of trial and error, which turned what initially seemed like a challenge into an opportunity to expand my skill set and adaptability.

Sai Manas Pandrangi

The main challenge I faced was conveying technical problems, perspectives, and decisions in a way that non-technical audiences could understand. I quickly realized that this is a skill developed over time, and I am committed to improving it.

If you could describe your experience at CoDHerS in three words, what would they be?

Kamila Maral

Collaboration, Adaptability, Supportive

Berfin Ustabaş

Care, Craft, Co-design

Aibibi Akshulakova

Community, Growth, Courage.

Sai Manas Pandrangi

Technology, Creativity, & Leadership

What is one thing you want the broader public to know about the CoDHerS lab, and how do you think it differs from other multimedia labs?

Kamila Maral

I want the broader public to know that the CoDHerS Lab is not only about innovation and technical projects, it is also a family and a community that makes students feel at home, even when they are far from home. It creates something deeper, bringing people together through a shared passion for preserving cultures.

Berfin Ustabaş

CoDHerS is relationship-centered. We don’t just digitize; we build community stewardship; multilingual, multi-script, protocol-aware systems where communities retain voice and control. Students lead real products, and accountability to partners matters as much as aesthetics.

Aibibi Akshulakova

One thing I want the broader public to know is that CoDHerS is not just a multimedia lab – it’s a space where digital tools are used to question power, uplift communities, and preserve cultural heritage in ways that are both ethical and innovative. Unlike many labs that prioritize technical innovation above all else, CoDHerS blends new tools with community-centered approaches and creative expression.

Sai Manas Pandrangi

One remarkable aspect of CoDHerS is the family-like love and respect shared among its team members and executive members. This supportive environment sets CoDHerS apart from other multimedia labs and workplaces in general.

What skills from this summer will you carry forward into your academic or professional journey?

Kamila Maral

I have developed both soft and hard skills during my time at CoDHerS. In particular, I have strengthened my management and multitasking abilities, which I believe are highly valuable and will help me effectively balance work throughout my academic and professional journey.

Berfin Ustabaş

Product management for cultural tech (road-mapping, PDLC), metadata and taxonomy design, and UI/UX prototyping, plus the discipline to slow down for context.

Aibibi Akshulakova

This summer gave me the chance to grow in so many different directions. On the technical side, I learned how to handle video and audio equipment, edit high-resolution footage, and navigate the basics of web development. I also built organizational skills through planning and running events, and I deepened my ability to conduct meaningful, critical research in archives and digital heritage. Beyond these practical skills, I learned how to adapt quickly, balance creative and technical tasks, and work collaboratively across different disciplines. Altogether, these experiences have strengthened both my academic foundation and my professional toolkit, and I know they’ll carry forward into whatever research, leadership, or career opportunities I pursue next.

Sai Manas Pandrangi

Effective communication in a team-setting is a skill I developed at CoDHerS over the summer that I will carry forward into my professional journey.

If you could describe yourself as a piece of equipment or a software tool, what would it be and why?

Kamila Maral

I would describe myself as Figma because, like the software, I am both creative and complex. I might seem hard to understand at first, but once people get to know me, I’m much easier to connect with and work with.

Berfin Ustabaş

Figma, because I prototype fast, invite collaboration early, and layer complexity without losing clarity.

Aibibi Akshulakova

If I could describe myself as a piece of equipment, I would be a camera. A camera captures details that might otherwise be overlooked, preserves moments for the future, and frames stories in ways that bring out new meaning. In the same way, I try to observe carefully, highlight what is important, and document experiences so they can be shared with others.

Sai Manas Pandrangi

I think the only fair answer is VS Code.