%iKnow.Matching.MatchingProfilepersistent class %iKnow.Matching.MatchingProfile
This class represents the parameters controlling the match score calculation resulting from
the iKnow Smart Matching process driven from the
A Matching Profile can be linked to a domain, or just exist "namespace-wide", when
The total score of a CRC-level match is multiplied by this number.
This multiplier is applied to the aggregate match score for a CRC, path or sentence if the matched entities appear in a different order than in the dictionary term.
The domain ID this Matching Profile is associated with. When 0, this profile can be used across the namespace.
Use this parameter to add an additional requirement on the number of concepts from the Dictionary Term that should be matched for an aggregate match to be considered. A value of 1 (100%) implies all concepts should be matched. A value of at least 0.51 for example means both concepts in a CRC should match. A value of 0 (default) does not impose additional restrictions.
This is the lower threshold for match scores. Matches having a total score less than
MinimalMatchScorewill not be stored or returned.
A name for this profile. This name should be unique within the domain (case-insensitive) and cannot contain colons. For backwards compatibility, empty names are permitted, but these profiles cannot be retrieved with
Use this parameter to modify the score of matched entities which are part of a negation. Typically, this value will be either 1, ignoring the fact an entity is part of a negation, or 0, which will make the algorithm skip these entities. Other positive numeric values are also accepted and just modify the entity-level score for the affected entities, causing them to be considered partial matches.
The entity-level score of path-relevant entities will be multiplied by this modifier.
The total score of a path-level match is multiplied by this number.
The ID of this profile. This will be a negative number for namespace-wide profiles (which have
When calculating an aggregate match score for a CRC, path or sentence, the "length" of the matched section is compared to the total "length" of the CRC, path or sentence. This "length" is calculated taking a value of 1 for each concept and a value of
RelationshipLengthMultiplierfor each relationship. Therefore, setting this property to a lower value will decrease the weight of relationship entities in calculating this ratio.
The entity-level score of relationship entities will be multiplied by this modifier.
The entity-level score of scattered entity matches will be multiplied by this modifier. For example when matching the entity "blue big car" against the term "big blue car", The initial score of 1 (as all words in the entity are matched) will be multiplied with
The total score of a sentence-level match is multiplied by this number.
Copies all non-ReadOnly property values of the supplied Matching Profile object to the current object. This excludes
ProfileId, DomainIdand Name.
Utility method to instantiate a Matching Profile. If passed a negative integer for pProfileId, it will look for a namespace-wide Matching Profile (which means
DomainIdis 0), otherwise it will take look in the domain specified through pDomainId. If pProfileId is empty, the default profile for this domain will be returned.
This is the recommended way of instantiating a %iKnow.Matching.MatchingProfile object.
Looks up a Matching Profile by name in the domain identified by pDomainId (or in the set of cross-domain profiles if pDomainId = 0). pName should be a nonempty string and can be prepended with the domain ID to look into (overriding the value of pDomainId), separated by a colon. This allows configuration settings to refer to a particular Matching Profile with a single string. Matching Profiles without a name cannot be looked up through this method and should be looked up by ID using