Data access views, attributes, and lineage

SemQL supports data access views, attributes, and lineage navigation that enable the data certification process.

The tables below list the data access views, attributes, and lineage navigation transitions available in SemQL.

Data access views

The following table lists the available data access views. Each view is identified by an alias (e.g., SD for source data) that corresponds to the physical table storing this data, if one exists.

Alias Name Description

AE

Source Authoring Errors

Errors detected on source authoring data.

DU

Duplicates

Duplicates detected by the matching process.

GD

Golden Data

Consolidated and certified golden records.

GDWE

Golden Data with Errors

Golden data with errors.

GE

Post-Consolidation Errors

Errors detected after master data consolidation (i.e., post-consolidation errors).

GH

Golden History

Golden records' history.

GH4B

Golden Data As of Batch

Golden data history as of batch or golden data if not historized.

GI

Golden Integration

Latest consolidated (integrated) golden records before post-consolidation validation.

GX

Deleted Golden

Deleted golden records logs (and data for soft delete).

MD

Master Data

Enriched, validated, and cleansed master records.

MH

Master History

Master records' history.

MH4B

Master Data As of Batch

Master data history as of batch or master data if not historized.

MI

Master Integration

Latest integrated master records.

MX

Deleted Master

Deleted master records logs (and data for soft delete).

SA

Source Authoring

Source data authored by users.

SA4L

Source Authoring for Load

Source data authored by users for a given load.

SA4LK

Source Authoring Lookup

References lookup for source authoring data.

SAWE

Source Authoring with Errors

Source data authored by users with errors.

SD

Source Data

Source data successively loaded by publishers.

SD4L

Source Data for Load

Source data loaded by publishers for a given load.

SD4LK

Source Data Lookup

Reference lookup for source data loaded by publishers for a given load.

SDWE

Source Data with Errors

Source data with errors loaded by publishers.

SE

Source Errors

Errors detected on source data loaded by the publishers (i.e., pre-consolidation errors).

UG

Duplicates Management Consolidated Data

Data consolidated from user decisions taken in a duplicate manager.

UM

Duplicates Management User Decisions

Master records changed by a user in a duplicate manager.

Built-in attributes

The following table lists the attributes, with the views into which they are available.

Name Label Views Description

AuthoringType

Authoring Type

SA, SA4L, SAWE

For matched entities, type of authoring operation:

  • OVERRIDE for override.

  • DATA_ENTRY for data creation.

BatchDate

Batch Date

SA, SAWE, SD, SDWE

Date of execution of the batch.

BatchID

Batch ID

AE, GD, GDWE, GE, GH, GH4B, GI, GX, MD, MH, MH4B, MI, MX, SA, SA4L, SAWE, SD, SD4L, SDWE, SE, UM

Identifier of the batch into which the new data, data changes, overrides or duplicate decisions have been applied, or during which errors have been detected.

BatchSubmitter

Batch Submitter

SA, SAWE, SD, SDWE

User who submitted this batch.

ClassName

Class Name

AE, DU, GD, GDWE, GE, GH, GH4B, GI, GX, MD, MH, MH4B, MI, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE, SE, UG, UM

Unique name of class or entity to which this record belongs.

ConfidenceScore

Confidence Score

GD, GDWE, GH4B, GI, MD, MH, MH4B, MI, MX, UG, UM

Confidence score of the golden record. It is the average of the match scores in the match group.

ConfidenceScoreType

Confidence Score Type

GD, GDWE, GH4B, GI, MD, MH, MH4B, MI, MX, UG, UM

Algorithm used to compute a confidence score:

  • Direct Scoring (AVG_DIRECT_MATCH_SCORE): this method only takes into account the direct matches found with the rules. This group score is the average of these match scores. Pairs in the group that have not directly matched by any rule are considered as having a score of zero.

  • Transitive Match Score (AVG_TRANS_MATCH_SCORE): this method takes into account the direct matches found with the rules, plus indirect transitive matches, which are computed. The group score is also the average of the match scores in the group.

ConfirmationStatus

Confirmation Status

GD, GDWE, GH4B, GI, MD, MH, MH4B, MI, MX, UG, UM

Confirmation status for duplicate management:

  • Confirmed (CONFIRMED): indicates that a master record is confirmed within a golden record or that a golden record consists entirely of confirmed master records.

  • Not-confirmed (NOT_CONFIRMED): indicates that a master record is not confirmed or that a golden record consists entirely of unconfirmed master records.

  • Historically confirmed (WAS_CONFIRMED, for master records): indicates that a master record has been confirmed into a golden record that has been merged into another golden record.

  • Partially confirmed (PARTIALLY_CONFIRMED for golden records only): indicates that a golden record partially consists of confirmed master records.

ConstraintName

Constraint Name

AE, GE, SE

For error records, name of the constraint causing the error.

ConstraintType

Constraint Type

AE, GE, SE

For error records, type of the constraint causing the error.

CreationDate

Created On

GD, GDWE, GH, GH4B, GI, GX, MD, MH, MH4B, MI, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE, UM

Creation date of a record.

Creator

Created By

GD, GDWE, GH, GH4B, GI, GX, MD, MH, MH4B, MI, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE, UM

User who created the record.

DeleteAuthor

Deleted By

GX, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE

User who deleted the record.

DeleteDate

Deleted On

GX, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE

Deletion date of a record.

DeleteOperation

Delete Operation

GX, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE

ID of a delete operation.

DeletePath

Delete Path

GX, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE

Cascade path through which the record was reached during a delete operation. Null for record directly selected for deletion.

DeleteType

Delete Type

GX, MX

Delete Type (SOFT_DELETE or HARD_DELETE for golden- and master-record deletion). The type of delete can be LEGLESS_DELETE for golden records deleted when they lose all their master records.

DupsCheckoutCause

Checkout Cause

UM

Cause that made the record part of the duplicate management transaction. Possible causes are:

  • User (USER): the record was checked out by the user.

  • Same Golden (SAME_GOLDEN): the record is part of the same matching group as another master record that has been checked out.

  • Same Suggestion (SAME_SUGG): the record is part of the same suggestion as another master record that has been checked out.

  • Same Exclusion Group (SAME_XGRP): the record is part of the same exclusion group as another master record that has been checked out.

  • Other (OTHER): Another reason.

DupsOperationID

Dups Operation ID

UM

Identifier of a duplicate management operation.

ErrorStatus

Error Status

GD, GDWE, GH4B, GI, SA, SAWE, SD, SDWE

Error status of a record. This value indicates whether or not a source or golden record has successfully passed validations. Possible values are:

  • VALID if the record has no error.

  • ERROR if the record has errors.

  • RECYCLED if the record has been recycled and is considered valid.

  • OBSOLETE_ERROR if the record had errors that have been fixed in a later version of the record.

  • a <NULL> value also indicates a record with no error.

ExclusionGroupID

Exclusion Group

MD, MH, MH4B, MI, MX, UM

Exclusion group ID. An exclusion group represents a group of records for which a user has made split decisions.

FromBatchID

From Batch ID

GH, GH4B, MH, MH4B

Batch in which the history record has been created.

GoldenType

Golden Type

GD, GDWE, GH4B

For fuzzy- and ID-matching entities, indicates the type of golden record—that is, whether the golden record was created and authored only in the MDM application (DE_BASED), or consolidated from master data and possibly overriden (MASTER_BASED).

HasOverride

Has Override

GD, GH4B

For fuzzy- and ID-matching entities, this flag (0 or 1) indicates whether the golden record has override values.

HasSuggestedMerge

Has Sugg. Merge

GD, GDWE, GH4B, GI, MD, MH, MH4B, MI, MX, UM

Flag (0 or 1) indicating that match-and-merge suggestions are available for this record.

IsConfirmed

Is Confirmed

GD, GDWE, GH4B, GI

Flag (0 or 1) indicated whether this golden record has been confirmed (fuzzy-matched entities only).

LoadID

Load ID

AE, SA, SA4L, SAWE, SD, SD4L, SDWE, SE, UM

Load identifier used as the unique transaction ID for external applications pushing data to the platform.

MastersCount

Masters Count

GD, GDWE, GH4B, GI, MD, MH, MH4B, MI, MX, UG, UM

Number of master records contributing to the golden record.

MatchGroupID

Match Group ID

MD, MH, MH4B, MI, MX

Identifier of the match group for the master record. This column is set when matching takes place.

MatchRule

Match Rule

DU

Rule involved in this record match.

MatchScore

Match Score

DU

Match score.

OriginalBatchID

Original Batch ID

SA, SA4L, SAWE, SD, SD4L, SDWE, UM

Identifier of the batch that included a record when it was originally edited out in a stepper or a duplicate manager.

OriginalConfidenceScore

Original Confidence Score

UM

Confidence score of the original golden record in a duplicate management operation.

OriginalConfidenceScoreType

Original Confidence Score Type

UM

Algorithm used to compute the original confidence score:

  • Direct Scoring (AVG_DIRECT_MATCH_SCORE): this method only takes into account the direct matches found with the rules. This group score is the average of these match scores. Pairs in the group that have not directly matched by any rule are considered as having a score of zero.

  • Transitive Match Score (AVG_TRANS_MATCH_SCORE): this method takes into account the direct matches found with the rules, plus indirect transitive matches, which are computed. The group score is also the average of the match scores in the group.

OriginalConfirmationStatus

Original Confirmation Status

UM

Original Confirmation Status in a duplicate management operation.

OriginalExclusionGroupID

Original Exclusion Group

UM

Original Exclusion Group in a duplicate management operation.

OriginalMastersCount

Original Masters Count

UM

Number of master records in the original golden in a duplicate management operation.

PublisherID

Publisher ID

AE, DU, GD, GE, GH, GH4B, GI, GX, MD, MH, MH4B, MI, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE, SE, UG, UM

For matching entities, code of the publisher that published the record.

PublisherID2

Publisher ID (2)

DU

Identifier of the matching publisher.

SourceID

Source ID

AE, DU, GD, GE, GH, GH4B, GI, GX, MD, MH, MH4B, MI, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE, SE, UG, UM

Identifier of the source record in the source publisher system (fuzzy-matched entities only).

SourceID2

Source ID (2)

DU

Identifier of a matching source.

SuggestedMergeConfidenceScore

Sugg. Merge Confidence Score

GD, GDWE, GH4B, GI, MD, MH, MH4B, MI, MX, UM

Confidence score for the suggested match group.

SuggestedMergeConfidenceScoreType

Sugg. Merge Confidence Score Type

GD, GDWE, GH4B, GI, MD, MH, MH4B, MI, MX, UM

Algorithm used to compute a confidence score for the suggested match group:

  • Direct Scoring (AVG_DIRECT_MATCH_SCORE): this method only takes into account the direct matches found with the rules. This group score is the average of these match scores. Pairs in the group that have not directly matched by any rule are considered as having a score of zero.

  • Transitive Match Score (AVG_TRANS_MATCH_SCORE): this method takes into account the direct matches found with the rules, plus indirect transitive matches, which are computed. The group score is also the average of the match scores in the group.

SuggestedMergeID

Sugg. Merge ID

GD, GDWE, GH4B, GI, MD, MH, MH4B, MI, MX, UG, UM

Identifier of the merge operation suggested by the automated matching.

SuggestedMergeMastersCount

Sugg. Merge Masters Count

GD, GDWE, GH4B, GI, MD, MH, MH4B, MI, MX, UM

Number of master records involved in the suggested merge operation.

ToBatchID

To Batch ID

GH, GH4B, MH, MH4B

Batch in which history records stopped being current or null if the records are still current.

UpdateDate

Updated On

GD, GDWE, GH, GH4B, GI, GX, MD, MH, MH4B, MI, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE, UM

Technical update date of a record

Updator

Updated By

GD, GDWE, GH, GH4B, GI, GX, MD, MH, MH4B, MI, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE, UM

User who updated the record

ViewType

View Type

AE, DU, GD, GDWE, GE, GH, GH4B, GI, GX, MD, MH, MH4B, MI, MX, SA, SA4L, SA4LK, SAWE, SD, SD4L, SD4LK, SDWE, SE, UG, UM

Returns the current view type for the record (e.g., GD, MD).

The following attributes are deprecated.

Name Label Views Description

BranchID

Branch ID

AE, GD, GDWE, GE, GI, MD, MH4B, MI, SD, SD4L, SD4LK, SDWE, SE

Identifier of the branch to which this record belongs. This attribute is deprecated and always returns 0.

FromEdition

From Edition

GD, GDWE, MD, MH4B

Identifier of the data edition in which this record was created or last updated. This attribute is deprecated and always returns 0.

OldMatchGroupID

Old Match Group ID

MI

Previous identifier of the match group for the master record. This attribute is deprecated and returns 0.

ToEdition

To Edition

GD, GDWE, MD, MH4B

Identifier of the data edition into which this record was deleted or closed. This attribute is deprecated and always returns null.

Built-in lineage navigation

Parent navigation

The following table lists the built-in lineage navigation to a parent record.

Pseudo-role Navigation Description Navigation path

CurrentGoldenRecord

Current Golden Record

Current golden record to which a history golden record is linked.

Basic entity:

  • GH to GD

Fuzzy-matched entity:

  • GH to GD

ID-matched entity:

  • GH to GD

CurrentMasterRecord

Current Master Record

Current master record to which a history master record is linked.

Fuzzy-matched entity:

  • MH to MD

ID-matched entity:

  • MH to MD

GoldenRecord

Golden Record

Golden record into which the master, source, or golden integration record consolidates.

Basic entity:

  • SA4L to GD

  • SAWE to GD

  • SA to GD

Fuzzy-matched entity:

  • GI to GD

  • MD to GD

  • MH4B to GH4B

  • SA4L to GD

  • SAWE to GD

  • SA to GD

ID-matched entity:

  • GI to GD

  • MD to GD

  • MH4B to GH4B

  • SA4L to GD

  • SAWE to GD

  • SA to GD

  • SD4L to GD

  • SDWE to GD

  • SD to GD

MasterRecord

Master Record

Master record corresponding to a source record.

Fuzzy-matched entity:

  • MI to MD

  • SD4LK to MD

  • SD4L to MD

  • SDWE to MD

  • SD to MD

ID-matched entity:

  • MI to MD

  • SD4L to MD

  • SDWE to MD

  • SD to MD

Record1

Master Record 1

Fuzzy-matched entity:

  • DU to MI

Record2

Master Record 2

Fuzzy-matched entity:

  • DU to MI

RecordWithError

Record with Error

Authoring record with error attached to a source authoring error.

Basic entity:

  • AE to SAWE

Fuzzy-matched entity:

  • AE to SAWE

ID-matched entity:

  • AE to SAWE

SourceAuthoringRecord

Source Authoring Record

Authoring record attached to a source authoring error.

Basic entity:

  • AE to SA

Fuzzy-matched entity:

  • AE to SA

ID-matched entity:

  • AE to SA

SourceRecord

Source Record

Source record attached to the current error record.

Fuzzy-matched entity:

  • SE to SD

ID-matched entity:

  • SE to SD

Child navigation

The following table lists the built-in lineage navigation to child records.

Pseudo-role Navigation Description Navigation path

Errors

Errors

Errors detected for a given source or golden record.

Basic entity:

  • SAWE to AE

  • SA to AE

Fuzzy-matched entity:

  • GDWE to GE

  • GD to GE

  • SAWE to AE

  • SA to AE

  • SDWE to SE

  • SD to SE

ID-matched entity:

  • GDWE to GE

  • GD to GE

  • SAWE to AE

  • SA to AE

  • SDWE to SE

  • SD to SE

GoldenHistoryRecords

Golden History Records

History golden records

Basic entity:

  • GD to GH

Fuzzy-matched entity:

  • GDWE to GH

  • GD to GH

ID-matched entity:

  • GDWE to GH

  • GD to GH

IntegrationMasterRecords

Integration Master Records

Integration master record attached to the integration golden record. Available in post-consolidation enrichers and validations.

Fuzzy-matched entity:

  • GI to MI

ID-matched entity:

  • GI to MI

MasterHistoryRecords

Master History Records

History master records

Fuzzy-matched entity:

  • MD to MH

ID-matched entity:

  • MD to MH

MasterRecords

Master Records

Master records consolidated in a golden record.

Fuzzy-matched entity:

  • GDWE to MD

  • GD to MD

  • GH4B to MH4B

ID-matched entity:

  • GDWE to MD

  • GD to MD

  • GH4B to MH4B

SourceAuthoringRecords

Source Authoring Records

Source data authored by users attached to a golden record.

Basic entity:

  • GD to SA

Fuzzy-matched entity:

  • GDWE to SA

  • GD to SA

ID-matched entity:

  • GDWE to SA

  • GD to SA

SourceRecords

Source Records

Source records attached to the current golden record (for ID-matching) or master record.

Basic entity:

  • GD to SA

Fuzzy-matched entity:

  • MD to SD

ID-matched entity:

  • GDWE to SD

  • GD to SD

  • MD to SD