webMethods, OneData, and Terracotta  10.2 | Managing Master Data with webMethods OneData | webMethods OneData Consolidation MDM Guide | Working with Consolidation Projects | Working with Cleansing Projects for Consolidation (Staging) Objects | Windowkeys
 
Windowkeys
OneData provides a Windowkey attribute, that is comprised of a combination of multiple fields in whole or in part. Windowkeys help the system narrow down the candidate matching records.
The process of generating Windowkeys is specific to the data quality server cleansing server. For example, for Trillium, Windowkeys are defined in Trillium; for webMethods Locate, OneData defines the following default Windowkeys. To define additional Windowkeys for Locate, first add the Windowkey as an outbound attribute in the cleansing project. and then, manually define the Windowkey in the OneData metadata tables using the steps mentioned in Defining Project-Object Mapping for a Locate Cleansing Project.
Attribute Name
Mandatory Inbound and Outbound Attributes
Windowkey Value and Use
Windowkey01
OUT_Address2,
OUT_PostalCode,
IN_Organization,
IN_Address
First four characters of Address
+
First four characters of PostalCode
Usage Notes: Define inbound attributes only in Windowkeys and use the outbound attributes as:
First four characters of OUT_Address2 (instead of Address)
+
First four characters of OUT_PostalCode (instead of PostalCode)
Windowkey02
IN_Organization,
OUT_Organization
First four characters of Organization
+
Subsequent consonants derived from IN_Organization.
Usage Notes: For example, if the IN_Organization value is “SoftwareAG”, thenWindowkey02 generated is Sftwrg.
Also, if the Organization name is not provided, Windowkey02 is not relevant, and therefore, not used.
Windowkey03
OUT_Address2,
OUT_Locality,
IN_Organization,
IN_Address
First four characters of Locality
+
First character of Address
+
Subsequent consonants dervied from OUT_Address2.
Usage Notes: Used if IN_Organization value is available and used in OUT_Address2 in order to generate the BusinessName. If no value is present for IN_Organization, use Windowkey06.
Windowkey04
OUT_Address2,
OUT_PostalCode,
IN_Organization,
IN_Address
First three characters of PostalCode
+
First character of Address
+
Subsequent consonants derived from OUT_Address2.
Usage Notes: Used if IN_Organization value is available and used in OUT_Address2 in order to generate the BusinessName. If no value is present for IN_Organization, use Windowkey07.
Windowkey05
OUT_Address1,
OUT_PostalCode,
IN_Address
Usage Notes: OUT_Address1 is used to generate the address in Locate.
Windowkey06
OUT_Address1,
OUT_Locality,
IN_Address
Usage Notes: OUT_Address1 is used to generate the address in Locate.
Windowkey07
OUT_Address1,
OUT_PostalCode,
IN_Address
Usage Notes: OUT_Address1 is used to generate the address in Locate.
Windowkey attributes are defined in the following metadata tables:
*OD_MD_DQSRV_MPNG. Stores the mapping name, which is displayed in the OneData user interface and the corresponding server. The Locate server is represented by the value 1000.
*OD_MD_DQSRV_MPNGPROP. Stores the attribute name that is passed to the data quality server, the attribute type, and the Windowkey definition. When you define custom Windowkeys, you must add the Windowkey attribute in the OD_MD_DQSRV_MPNGPROP table, with the prop_id value set to 36002. The following table lists the attribute types and the corresponding prop_id value.
Prop_id Value
Definition
36000
Attribute name.
36001
Inbound or outbound attribute.
*1- Inbound
*2 - Outbound
36002
Windowkey regex expression (only for Windowkey attributes).
Copyright © 2011-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release