<?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/bfd4e591ed53413cb290dac349645f15&quot; frameborder=&quot;0&quot; width=&quot;2552&quot; height=&quot;1914&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1914</height><width>2552</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1914</thumbnail_height><thumbnail_width>2552</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/bfd4e591ed53413cb290dac349645f15-aecaf0dd0a3083df.gif</thumbnail_url><duration>159.323</duration><title>Ingest Data from Google Drive to OSO</title><description>This Loom demonstrates setting up a first data integration using Google Drive in Oso. The creator adds and imports a Google Drive spreadsheet named testuserdata, taking all tabs, and watches the ingestion run for about a minute. After it completes, they preview the ingested dummy data with fields like GitHub repositories, an internal project name, launch date, and status, and then run a SQL query to confirm the data loads cleanly. They note that ingestion adds two artifact columns that are often filtered out or cleaned via a staging model.</description></oembed>