{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/aacdf3b6a2cb4abe9e7063026f67d521\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/aacdf3b6a2cb4abe9e7063026f67d521-143396b1d2bddbc4.gif","duration":246.86,"title":"Mapping Source UID Through Evidence Schema","description":"This Loom explains a code change for propagating a source slot from Discourse nodes into both the evidence schema and evidence instances during a Rome to CrossHat conversion. It describes utilities like extractFieldFromTitle to extract fields from titles (including handling brackets and DiscourseNodeTitle) to derive source UIDs and page or node UIDs. The author notes that the conversion logic checks only for the presence of “source” in the format, not the evidence name, and propagates it into roles and local reference content. It also mentions extending sync to sync so all nodes are sent even if unmodified, supporting migrations shown in demos and tests."}