pub struct Metadata {
pub title: Option<String>,
pub author: Option<String>,
pub subject: Option<String>,
pub keywords: Vec<String>,
pub creator: Option<String>,
pub producer: Option<String>,
pub created_at: Option<String>,
pub modified_at: Option<String>,
pub custom: BTreeMap<String, String>,
}Expand description
Scene-level metadata. Carried through to exports when the target
format supports it (PDF document info dict, MP4 meta box, etc).
producer and creator are intentionally distinct, mirroring
PDF’s /Info dictionary:
creator— the tool that authored the source content (e.g. the NLE, drawing app, or word processor the user worked in).producer— the tool that wrote the output file (this crate / oxideav exporter).
Fields§
§title: Option<String>§subject: Option<String>§keywords: Vec<String>§creator: Option<String>Authoring application — the tool used to create the source
content. Distinct from producer; PDF’s
/Info dictionary has separate /Creator and /Producer
keys for the same reason.
producer: Option<String>Producing tool name — the writer that emitted the output file.
created_at: Option<String>ISO-8601 string; not parsed here so exporters can pass it through unchanged.
modified_at: Option<String>ISO-8601 modification timestamp. Mirrors created_at; PDF
/Info has both /CreationDate and /ModDate, mp4 mvhd
has both creation_time and modification_time, etc.
custom: BTreeMap<String, String>Extensible per-format extras. Lets callers carry metadata
the standard fields don’t cover: PDF /Info custom keys,
Matroska ContentTrack tags, RDF properties, mp4 udta
items not covered by the standard fields, ID3 frames, and
so on. Keys are case-sensitive; uniqueness is the caller’s
responsibility (the map enforces it).