{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/f8dfcb85f25941b095d018e5376cfa70\" frameborder=\"0\" width=\"1110\" height=\"832\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":832,"width":1110,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":832,"thumbnail_width":1110,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/f8dfcb85f25941b095d018e5376cfa70-1336fc254a515cd9.gif","duration":230.367,"title":"Coca-Cola AEM Assets Migration Discovery Call","description":"This Loom discusses Coca-Cola’s asset migration from Sitecore to Adobe Experience Manager, with a focus on how AEM Assets will function alongside Binder as the system of record. Rosemary from Genpact clarifies that AEM Assets will serve as both the authoring DAM and delivery mechanism, where creative teams manage master assets before publishing. Laksh discusses needing file counts and media details, including binaries over 100MB, video quantities, and unused content from the last two years, plus whether image renditions are actually used in HTML. An email recap to Loxia at lab0.ai is requested to confirm the file counts; the team also asks how many of the 14 image renditions per image are required and which can be regenerated."}