<?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/2c96a0bfe098410694af7002bb1ec3d8&quot; frameborder=&quot;0&quot; width=&quot;1668&quot; height=&quot;1251&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1251</height><width>1668</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1251</thumbnail_height><thumbnail_width>1668</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/2c96a0bfe098410694af7002bb1ec3d8-18311ee6f0850d8d.jpg</thumbnail_url><duration>430.571</duration><title>Filevine to Domo via Amazon S3</title><description>In this video I walk through how data flows from Filevine into Domo and Periscope using an Amazon S3 bucket, since that is the preferred method. First I create Filevine reports, set them on a daily schedule, and push raw copies into S3 as backup and an audit trail. Then Domo reaches into the bucket, pulls the datasets, and runs a simple ETL to clean and transform them into optimized final datasets for faster reporting. Finally I build cards and dashboards that update on that same schedule, not in real time, so there is usually a small delay. No action was specifically requested from viewers.</description></oembed>