This page was last edited on June 22, 2022, at 22:11.
Comments or questions about this documentation? Contact us for support!
In the Column List:
Introduced: 8.5.014.09
In partitioned databases, this table is not partitioned.
This dimension table allows chat thread facts to be described based on where the chat session originated. This dimension table is populated only in cloud deployments with Advanced Chat. Depending on specific media, the media origin values are either the same as, or complementary to, the media types stored in the MEDIA_TYPE table. For instance, for Facebook public messaging, Facebook is the value recorded both as MEDIA_NAME in the MEDIA_TYPE table and as MEDIA_ORIGIN in the MEDIA_ORIGIN table. For Facebook private messaging, however, the value recorded as MEDIA_NAME in the MEDIA_TYPE table would be CHAT, while the value recorded as MEDIA_ORIGIN in the MEDIA_ORIGIN table would be Facebook.
Column | Data Type | P | M | F | DV |
---|---|---|---|---|---|
ID | int | X | X | ||
MEDIA_ORIGIN | nvarchar(64) | X | unknown | ||
CREATE_AUDIT_KEY | numeric(19) | X | X |
The primary key of this table. This ID is referenced from other tables as MEDIA_ORIGIN_KEY.
Based on KVP: csg_MediaOrigin
Identifies where the chat session originated (web chat, social media channels, SMS, and so on).
The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools—that is, applications that need to identify newly added data.
CODE | U | C | Description |
---|---|---|---|
I_MEDIA_ORIGIN | X | Ensures that the combinations of values that are stored in the dimension table are unique. |
Field | Sort | Comment |
---|---|---|
MEDIA_ORIGIN | Ascending |
No subject area information available.