Versions Compared

Version Old Version 2 New Version Current
Changes made by

Armin Franke

Armin Franke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The SharePoint request to tia Connect contains meta properties that are stored in the tia Content Server CMIS as CMIS properties. Attributes can hav

When no metadata - mapping or type - mapping applies to an attribute meta property name, it is stored in the CMIS type that is set by customType parameter, and the attribute name is prefixed by the string in customPrefix parameter.With the setting metadata-mappings an incoming property can be mapped to a different property on the cmis-side. The mapping also applies when fetching the properties, the cmis-side property is mapped to the original value. The definition of the cmis-side must specify the full cmis-id of the target property.
Examplesthe CMIS property name is prefixed by the customPrefix parameter and stored as property of CMIS type specified by customType parameter. Only when the meta property name starts with cmis:, the prefix is not applied building the CMIS property name.

The metadata mapping allows direct mapping of a meta property name to a CMIS property name, and overrides the building process. However, for the metadata mapping, the CMIS property mapped must be known to the tia Content Server.

Example:

Code Block
metadata-mappings:
  customvalueabstract: 'cmis:description'
  othervaluecontent: 'sapbo:basedocument:Document'

The first mapping maps the incoming value customvalue to the cmis property cmis:description, which is a default property. The second mapping maps the incoming value othervalue to the cmis property sapbo:basedocument:Document. The latter will fail, because the cmis property is a non-standard property. To be used, the type mapping parameter must be added.

After the CMIS properties are mapped, the type mappings allow map CMIS types: When there is a type mapping for a CMIS property to be added, then the CMIS type is also added.

Example:

Code Block
type-mappings:
  "[sapbo:basedocument:Document]": 'sapbo:basedocument'
Info

Use always “[ … ]” (double-quotes with square brackets) on the left-hand-side of an association in YAML file. One the right-hand-side ' (single quotes) are sufficient.

Background is, that : is a separation character and may otherwise split the CMIS type name leading to unexpected results.

This setting defines, that whenever the property Assuming both example mappings are active for the same instance, then if the meta property content is present in the request, it will be mapped to sapbo:basedocument:Document is filled, the CMIS property because of the meta mapping. Then because of the type mapping the CMIS type sapbo:basedocument must is also be added. In combination with the above metadata-mappings, this means whenever the property othervalue is filled in an incoming metadata request, either on create or on patch, the type will be added.

Metadata mappings

Parent

Parameter

Description

Required

Supported values

Default

tia.instances.<name>.sharepoint

customType

CMIS custom type for sharepoint metadatanot mapped meta data

no

<string>

tia:archiveProperties

tia.instances.<name>.sharepoint

customPrefix

Prefix for extension of the sharepoint metadatafor not mapped meta data

no

<string>

tia:archiveProperty:

tia.instances.<name>.sharepoint

metadataIgnoreFields

List of meta fields from Sharepoint property names that should be ignored.

Info

Specify this parameter to append to the list in default column. The listed values cannot be unset.

no

<List of Strings>

[
SharedWithUsers,
SharedWithUsers@odata.type,
SharedWithUsers#Claims,
SharedWithUsers#Claims@odata.type
]

tia.instances.<name>.sharepoint

metadata-mappings

Mapping of custom meta property name to CMIS property name.

no

<Map of configurations>

-

tia.instances.<name>.sharepoint

type-mappings

Mapping of custom meta property name to CMIS property name.

no

<Map of configurations>

-

...