Presentation
DZC Documents
Overview
The Presentation media type groups 10 active file types stored in DZC Documents.
DZC Folder
DZC DocumentsFile Type Count
10 active file typesFile Types
Presentation Available
Presentation — Live from Microsoft
Secure, read-only view focused directly on the Presentation folder.
Presentation-Specific Fields
These eight values are extracted from each individual Presentation file. They report detected format, presentable units, layout definitions, text, visual objects, packaged resources, interactions, and extraction status. Generic facts such as filename, path, size, timestamps, and SHA-256 remain governed by File Master Primary.
The format and version detected from the file itself, such as PDF 1.7, HTML5, a Power BI package version, an OOXML application version, a Tableau workbook version, or a vCard version.
The measured count of primary presentable units: PDF pages, PowerPoint slides, HTML or message surfaces, Power BI report pages, Tableau worksheets/dashboards/stories, Visio pages or stencil masters, shortcuts, or vCards.
The measured count of reusable layout and styling definitions detected in the package, including slide layouts, masters, themes, CSS style sources, Tableau layout rules, Power BI theme resources, and Visio masters or themes.
The number of text characters actually extracted from the presentable content, including visible HTML text, PDF text layers, slide text, message bodies, Tableau captions, Visio text, shortcut targets, and vCard content.
The detected count of presentable visual objects, including images, drawing objects, PowerPoint shapes, Power BI visual containers, Tableau zones or marks, PDF visual objects and annotations, Visio shapes, and contact photos.
The detected count of packaged or referenced rendering resources, including fonts, images, media, attachments, OOXML embeddings, Power BI models or static resources, Tableau extracts and assets, and Visio media or recordsets.
The detected count of hyperlinks, relationship actions, form actions, navigation controls, bookmarks, drillthrough or URL actions, shortcut targets, and contact communication endpoints.
The result of the file-level extraction: Parsed, Partial, Empty, Unsupported, or Failed. Unreadable and empty files are reported explicitly instead of receiving extension-based placeholder values.