<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/30cd456e9bd54bd19db9d63376b4baea&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/30cd456e9bd54bd19db9d63376b4baea-734d79de57539da4.gif</thumbnail_url><duration>180.691</duration><title>Normalizing CSV Data for Client Workflows 📊</title><description>In this video, I walk you through the process of normalizing a CSV file that we receive from clients, particularly focusing on the inconsistency of the first name header, which can appear as &apos;fname&apos; or &apos;first name&apos;. I demonstrate how to extract the CSV into JSON format, normalize the header to our strict schema, and then convert it back to CSV for future use. The key action here is to ensure that we maintain data integrity while adapting to varying formats from clients. By the end of this workflow, we achieve a normalized CSV that aligns with our standards. Please review the steps and let me know if you have any questions or need further clarification.</description></oembed>