<?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/70541ae7760941be84b748ca0f6f0b0b&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/70541ae7760941be84b748ca0f6f0b0b-c0fed948b539ecc2.jpg</thumbnail_url><duration>265.366</duration><title>Understanding FileVine Projects and Databases</title><description>Hey, Derek with VineSkills here. In this Loom I walk through how projects and databases work in FileVine, especially how it connects to boards and dashboards in Domo or Periscope. I explain that a project is one to one in a project report, while collection sections are a multiple to one ratio for a project ID, so we use collection section reports to drill down rather than total policy limits. I also point out that data quality can be imperfect, so dashboards are only as good as the data entered. No action was specifically requested from you.</description></oembed>