Import version
This flow configures what happens when a new version of a content is imported: what is kept, what is recomputed on the new version, and what the version number becomes.
It is not limited to the manual import: it applies to all version actions, including the end of a co-edition or the stop of a Teams share. Actions can be chained.
The actions follow one another in this order: a version configuration, an OCR, an AI categorization, an AI indexing, a form, then a set of metadata composers.
Available actions
Version settings: versioning rules applied. Mandatory.
OCR data extraction: document capture engine applied to the new version.
Categorization: AI categorization applied.
Indexing: AI indexing applied.
Form: input form.
Metadata uniqueness: uniqueness check applied.
Metadata composer: composer applied.
Transfer metadata: saves, or not, the metadata into the primary format.
- Save into the primary format / Do not save.
- The format is only changed if needed, and only if it handles metadata transfer.
- If the primary content is changed, a Transfer metadata audit is generated (advanced display: "Metadata saved into the format: DOCX/XLSX").