Skip to main content Site map
HomeNews and blogs hub

MetaGreenData: Making Code More Sustainable, One Metadata File at a Time

Bookmark this page Bookmarked

MetaGreenData: Making Code More Sustainable, One Metadata File at a Time

Author(s)
Jyoti Bhogal Profile Picture

Jyoti Bhogal

SSI fellow

Posted on 22 July 2025

Estimated read time: 5 min
Sections in this article
Share on blog/article:
LinkedIn

MetaGreenData: Making Code More Sustainable, One Metadata File at a Time

Jyoti Bhogal in the backdrop of the ‘University of Stirling’ and the centrally located Airthrey Loch; The William Wallace Monument, also known as the National Wallace Monument, located on the Abbey Craig in Stirling, Scotland

Images (L to R): Jyoti Bhogal in the backdrop of the ‘University of Stirling’ and the centrally located Airthrey Loch; The William Wallace Monument, also known as the National Wallace Monument, located on the Abbey Craig in Stirling, Scotland

Ever thought about how much energy your code consumes? Or how to make your software more eco-friendly? Well, during the recent Collaborations Workshop 2025 Hack Day, my team decided to tackle this very challenge. Let me walk you through our journey.

The third day of the Collaborations Workshop 2025 was a dedicated Hack Day. The attendees were invited to pitch ideas for the Hack Day. Many wonderful ideas were pitched for the same. People started joining the team with the idea in which they were most interested to work upon. Ultimately, 10 teams were formed. The 10 teams collaborated for an intense hack day, leading to amazing ideas taking shape by the end of the day!

Earlier on the second day of the workshop I had attended a collaborative ideas discussion session on “MetaGreenData: standardised reporting of the environmental impact of compute” chaired by Kirsty Pringle and joined by Bryn Ubald, Caterina Doglioni, Connor Aird, Jyoti Bhogal, and Saranjeet Kaur Bhogal. This session motivated me to join the “Group: D - Delphinium” team for the Hack Day (Team members: Christina Bremer, Duncan Leggatt, Jyoti Bhogal, Loïc Lannelongue, Will Haese-Hill; Joining remotely: Michael Sparks). I enjoyed collaborating with my team during the Hack Day - we divided the tasks amongst each other. Throughout the day the judges visited the different teams asking questions, and at the end of the day, we were asked to provide a presentation of the work we did. In this blog post, I share the product my team created by the end of the Hack Day!
Group photo while working on the hack idea, (L to R) Caterina Doglioni, Will Haese-Hill, Duncan Leggatt, Loïc Lannelongue, Jyoti Bhogal, Christina Bremer

Image: Group photo while working on the hack idea, (L to R) Caterina Doglioni, Will Haese-Hill, Duncan Leggatt, Loïc Lannelongue, Jyoti Bhogal, Christina Bremer

Motivation

While many developers are keen on optimising their code for speed and efficiency, not many consider the environmental impact. That's where my team saw the opportunity. The idea was simple: create a tool that helps developers understand and reduce the carbon footprint of their software.

Brainstorming the Solution

The brainstorming session was filled with energy and ideas. The motive was to come up with a  solution that was:

  • User-friendly: Easy for developers to integrate into their workflow.
  • Informative: Provides clear insights into the environmental impact.
  • Actionable: Offers suggestions to reduce carbon emissions.

After much discussion, it was decided to have a metadata generator that captures essential information about software, making it easier to assess and improve its sustainability.

Building MetaGreenData

Enter MetaGreenData. This is a Django-based web application designed to help developers generate metadata files for their software projects. Here's how it was designed:

  1. Understanding the Standards: To begin with, existing metadata standards, like CodeMeta and the Citation File Format (CFF), were explored. These standards provide a structured way to describe software, making it easier to share and cite.
  2. Designing the Workflow: Then a simple form was created where users can input details about their software. This included information like the software's name, version, authors, and more.
  3. Generating the Metadata: The tool was designed to generate a metadata file in the chosen format (CodeMeta or CFF) based on the input. This file can then be added to the software's repository.
  4. Integrating Carbon Footprint Estimation: Next, the Green Algorithms calculator was integrated to estimate the carbon footprint based on the software's computational requirements. 

Visualising the Process

To make things clearer, here's a simple flowchart of how MetaGreenData works:


 

The Outcome

MetaGreenData is now available on GitHub! 🎉
The idea was developed on a GitHub repository called MetaGreenData. We plan to develop it further and make it user-friendly.

Last but definitely not the least this project won the first prize at the Collaborations Workshop 2025 Hack Day. Here’s my team’s picture from the day!

Christina Bremer, Will Haese-Hill, Duncan Leggatt, Loïc Lannelongue, Jyoti Bhogal, Joining remotely: Michael Sparks

Image credit: Software Sustainability Institute; (L to R) Christina Bremer, Will Haese-Hill, Duncan Leggatt, Loïc Lannelongue, Jyoti Bhogal, Joining remotely: Michael Sparks

And here’s my certificate:

Certificate of Achievement: First place at the Hack Day

Certificate of Achievement: First place at the Hack Day, Collaborations Workshop 2025, organised by the Software Sustainability Institute

References and Inspirations

The project was inspired and informed by several resources:

MetaGreenData is just the beginning. The vision is of a future where sustainability is a core consideration in software development. By making it easier to assess and reduce the environmental impact of code, the hope is to inspire developers to make greener choices.
 

Back to Top Button Back to top