Property mapping is different from the standard metadata extraction mechanism and should be carefully configured to ensure that different properties are set up. Properties stored in the Alfresco repository are injected into Office documents when these files are read through AOS, and equally properties are extracted from Office files written through AOS and then updated in the Alfresco repository.
- Single value properties only can be mapped in Office documents. Multi-value properties are ignored.
- Accepted data type properties are text, mltext, int, long, float, double, date, datetime and boolean. Other data type properties are ignored.
- The following constraints are supported: MINMAX for numeric data types, LENGTH for text, or LIST for text. Properties that have other constraints are ignored; for example, REGEX for text.
- Property mapping is only available for OOXML files (.docx, .xlsx, .pptx) and OLE files (.doc, .xls, .ppt). OLE files do not support read-only properties and are ignored. Protected properties are available in OOXML files only.
It is possible to define a list of types for new documents. Whenever a user creates a new document with the Save As dialog, Microsoft Office displays this list to choose from. If the type contains mandatory properties, Office enforces values for these properties before the file can be saved. Files created outside of Office (for example, in Windows Explorer) are created with a type of cm:content.
Alfresco provides basic configuration of four patterns, includedTypesPatterns, excludedTypesPatterns, includedAspectsPatterns and excludedAspectsPatterns in the aosBaseDataModelMappingConfiguration abstract bean.
Rename or copy the
This sample configuration file activates metadata mapping for the basic cm:content type and all its sub-types, except for some system types. All type properties and all applied aspects (except for some system aspects) are mapped into the documents.
In custom-aos-metadata-mapping-context.xml, check your file type
based on the includedTypesPatterns and
Both properties contain a list of regular expressions that are applied to the fully qualified QName. A file is valid for property mapping if its type is accepted by one of the regular expressions in the includedTypesPatterns list and does not exist in the excludedTypesPatterns list. For more information on regular expressions, see Class pattern.
In custom-aos-metadata-mapping-context.xml, check the file aspects
based on the includedAspectsPatterns and
If a file is valid for property mapping, aspects applied to this file are filtered further depending on the two properties, includedAspectsPatterns and excludedAspectsPatterns. Property mapping occurs only if the file type is included in the includedTypesPatterns list (even if there are aspects that are included in the includedAspectsPatterns property).
In custom-aos-metadata-mapping-context.xml, check the
These properties define the list of types that are available to users for document creation in the Save As dialog. If the includedInstantiableTypesPatterns is empty or not set, new documents are always created with the default type. If no system type matches the types configured in includedInstantiableTypesPatterns, the base type cm:content is used by default. If exactly one type matches the configuration, this type is automatically used for all documents created with the Save As dialog in Microsoft Office.