Struct RuleBasedProperties

#[non_exhaustive]
pub struct RuleBasedProperties {
    pub rules: Vec<Rule>,
    pub attribute_matching_model: AttributeMatchingModel,
    pub match_purpose: Option<MatchPurpose>,
}

An object which defines the list of matching rules to run in a matching workflow. RuleBasedProperties contain a Rules field, which is a list of rule objects.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

rules: Vec<Rule>

A list of Rule objects, each of which have fields RuleName and MatchingKeys.

attribute_matching_model: AttributeMatchingModel

The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the attributeMatchingModel.

If you choose MANY_TO_MANY, the system can match attributes across the sub-types of an attribute type. For example, if the value of the Email field of Profile A and the value of BusinessEmail field of Profile B matches, the two profiles are matched on the Email attribute type.

If you choose ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for the Email attribute type, the system will only consider it a match if the value of the Email field of Profile A matches the value of the Email field of Profile B.

match_purpose: Option<MatchPurpose>

An indicator of whether to generate IDs and index the data or not.

If you choose IDENTIFIER_GENERATION, the process generates IDs and indexes the data.

If you choose INDEXING, the process indexes the data without generating IDs.

Implementations

impl RuleBasedProperties

pub fn rules(&self) -> &[Rule]

A list of Rule objects, each of which have fields RuleName and MatchingKeys.

pub fn attribute_matching_model(&self) -> &AttributeMatchingModel

The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the attributeMatchingModel.

If you choose MANY_TO_MANY, the system can match attributes across the sub-types of an attribute type. For example, if the value of the Email field of Profile A and the value of BusinessEmail field of Profile B matches, the two profiles are matched on the Email attribute type.

If you choose ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for the Email attribute type, the system will only consider it a match if the value of the Email field of Profile A matches the value of the Email field of Profile B.

pub fn match_purpose(&self) -> Option<&MatchPurpose>

An indicator of whether to generate IDs and index the data or not.

If you choose IDENTIFIER_GENERATION, the process generates IDs and indexes the data.

If you choose INDEXING, the process indexes the data without generating IDs.

impl RuleBasedProperties

pub fn builder() -> RuleBasedPropertiesBuilder

Creates a new builder-style object to manufacture RuleBasedProperties.

Trait Implementations

impl Clone for RuleBasedProperties

fn clone(&self) -> RuleBasedProperties

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for RuleBasedProperties

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for RuleBasedProperties

fn eq(&self, other: &RuleBasedProperties) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for RuleBasedProperties