Import content
This flow configures the course of a content that enters Any through import: what the user enters, what an OCR or AI engine extracts from the file, what the content inherits from its room, then the controls and the filing. Actions can be chained, and several forms can follow one another.
Order of the actions
The actions follow one another in this order: one or several inheritances, one or several forms, an OCR, an AI categorization, an AI indexing, a metadata uniqueness, a relation creation, a set of inheritances from another source (only after the form, the uniqueness and the relation), a set of metadata composers, a propagation (relation only), the application of a lifecycle, then the components.
This order is not entirely fixed. The forms, the OCR, the AI categorization and the AI indexing can be placed anywhere, as long as they come before the uniqueness: the uniqueness check must see the final metadata to be reliable.
In a relation creation, metadata can be propagated from the content to the targeted content, provided the relation is carried by the created content: that is, that it goes from the parent to the child.
Available actions
Metadata inheritance: inheritance applied to the content.
Form: input form.
OCR data extraction: document capture engine applied to the content.
Categorization: AI categorization applied.
Indexing: AI indexing applied.
Metadata uniqueness: uniqueness check applied.
Relation: relation created with another content.
Metadata composer: composer applied.
Metadata propagation: propagation applied.
Lifecycle: lifecycle applied to the content.
Components: automatic attachment of the content to the packages waiting for it.
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").