Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The value stored and expected by Convergence for MDM to identify the publisher of a record is the Publisher Code, and not its Name. The code, unlike then name is always in UPPERCASE.Best practice:

  • Codes in UPPERCASE
  • Names in MixedCase

There are several reasons for a preferred publisher to be ignored in a consolidation:

  • The Data loaded in the SD_ table do not use the Publisher Code in the B_PUBID column. This publisher code is case-sensitive. The data integration job must be loaded in UPPERCASEuse the case-sensitive Publisher Code. In most circumstances this should be ALL CAPS.
    If the value in B_PUBID does not match an existing publisher code, then this publisher is considered at the last position in the preferred publisher consolidation. Other publishers' values will always be taken into account for consolidation.
  • When the PublisherID built-in attribute is used in a Custom Ranking consolidation, the literal values specified in the SemQL expression should be equal to the Publisher Code. These values are also in UPPERCASEcase sensitive.
    If the SemQL clause does not contain a literal that exactly matches the publisher codes, the clause will never not work as expected.

...


Filter by label (Content by label)
showLabelsfalse
max5
spacesSKB
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("publisher","preferred","consolidation") and type = "page" and space = "SKB"
labels consolidation preferred publisher

Page Properties
hiddentrue


Related issues
Jira Legacy
serverId33195043-5496-3fe4-8861-13723e5774ba
keySUPPORT-2509