Ingrid Coll

Software Engineer

Currently at SailPoint as a Go-to-Market Application Engineer

Originally from Barcelona, I moved to the United States at 18 on a college scholarship.Now, I build serverless software in TypeScript, Node.js, and AWS. Based in Austin, Texas.

My featured work

A mix of personal projects and things I've built at work.

I built an app that saves my team 15 hours per week of manual work

Metadata Editing Tool for the City of Austin (2023)

The Austin Open Data Portal is a public-facing website you can find at data.austintexas.gov. It holds all kinds of assets from different departments at the City of Austin, like a dataset with all 911 calls received, a map of issued construction permits, or a chart that depicts the City's budget and spending.I was part of the team that managed the Austin Open Data Portal from June 2024 to February 2026, almost two years. During my time, I realized one of our biggest pain points was managing the 5,000+ assets we hosted in the portal...

Instant Personalized PDF Proposal

Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample text Sample textSample text Sample text Sample text Sample textSample text Sample text Sample text Sample text...

I built an app that saves my team 15 hours per week of manual work

I developed the Metadata Editing Tool for the City of Austin in 2023.

The Austin Open Data Portal is a public-facing website you can find at data.austintexas.gov. It hosts all kinds of assets from different departments at the City of Austin, like a dataset with all 911 calls received, a map of issued construction permits, or a chart that depicts the City's budget and spending.I was part of the team that managed the Austin Open Data Portal from June 2024 to February 2026, almost two years.

The problem

During my time, I realized one of our biggest pain points was managing the 5,000+ assets we hosted in the portal.Specifically, keeping each asset's metadata field (title, description, department, owner, etc.) accurate and up to date. These 25+ metadata fields are very important to maintain. Not only do they provide context about the data and keep visitors informed, but many third-party applications depend on the Austin Open Data Portal's assets.Imagine an app that tracks crime incidents around your neighborhood that uses a dataset hosted in the Austin Open Data Portal as its source. The app probably needs to know when the dataset was updated last and how often the data is updated, for example. That information is provided to the public via metadata fields, which you can see in the "About" page of an asset or by using the Open Data Portal APIs.

An asset's About page in the Austin's Open Data Portal (data.austintexas.gov)

The old process

Each of these metadata fields can be updated via the Open Data Portal by logging in as an Administrator and manually editing each field, one asset at a time. Each asset took us about 1 to 2 minutes to update manually and required over 20 mouse clicks. It added up quick when we needed to update, let's say, 100 assets. Now imagine 1,000. Or 5,000. That's when an alarm bell went off in my head: this is a great automation opportunity!

My solution

Over the course of 3 months, I built a fullstack app with Microsoft's Power Platform.

  • For the UI and client-side logic, I used Power Apps.

  • For the automation's backend logic, I used Power Automate.

  • For monitoring the backend logic and each workflow triggered by the app, I used SharePoint.

(arhitecture diagram)

Was it worth it?

Send me a message

Or you can connect with me on LinkedIn. Always open to talk about tech.