IBM Content Navigator, Version 2.0.3

Property mapping

When you run a cross-repository search, you can search for content in different repository types. Use the rules to map the properties into logical combinations to return the most specific search results.

You must follow these rules when mapping properties between repositories:

You can map only one property for each repository.
All mapped properties must have compatible data types.
All mapped properties must have the same cardinality. For example, a single value string property cannot be mapped to a multi-value string property.
Only one property with a fixed value is allowed in a mapping. To use another fixed value property, you must create another map.
A child component property can be mapped only to itself.
All mapped properties must have at least one operator in common.

Intersection of operators

All mapped properties must have at least one operator in common so that you can select a valid operator to apply in the search criteria. For example, if you want to map an integer property to a string property, only the operators that are valid for both properties are available when you define search criteria.

Integer operators: Equals, Not Equal, Less Than, Less Than or Equal, Greater Than, Greater Than or Equal, Include Any, Exclude All, Is Empty, Is Not Empty, Between, Not Between.
String operators: Equals, Not Equal, Less Than, Less Than or Equal, Greater Than, Greater Than or Equal, Include Any, Exclude All, Is Empty, Is Not Empty, Starts With, Ends With, Like, Not Like.

The operators that are available when you define search criteria for an integer property and a string property include the following operators: Equals, Not Equal, Less Than, Less Than or Equal, Greater Than, Greater Than or Equal, Include Any, Exclude All, Is Empty, Is Not Empty.

The operators that are not available include the following operators: Between, Not Between, Starts With, Ends With, Like, Not Like.

Restriction: When the supported operators are different for each repository, you can use only the operators that are supported by all repositories that are included in your property mapping. If an operator is not supported in one of the repositories that is included in your property mapping, you cannot use that operator when you define search criteria. Also, if you configured IBM® Content Navigator to restrict the list of operators, the restricted list is applicable to your property mapping.

Search criteria entry data validation

When you have a simple mapping with one property, property constraints are validated before you run the search. For example, if an integer property is defined with a minimum value of 10 and a maximum value of 100, the search runs if you enter a value 10 - 100. If you enter a value of 9, or 101, or any other value that is out of range, the search does not run. You must correct the value that you entered before you can run the search.

When you have a mapping that combines two or more properties, the property constraints are not validated.

Properties that are unique to IBM Content Manager OnDemand have the following impact on validation:

Required: If you combine a required property with other properties, a value is required for the search. If you do not enter a value, the search does not run.
Fixed value: The defined fixed value is the only valid value for the search criteria. Because you cannot enter any other value, the fixed value is provided as read-only in the search criteria.