How is Origin Context tracked with Events?
in TR Internal
When clicking on an item in my WestlawNext favorites, I see Favorites in the Origin Context in Crazy Train. Likewise when I click on a Frequently Used Item, I see FrequentlyUsed in the Origin Context column.
Looking at the URLs before I click on the links, I see an originationContext query string parameter that contains the above values.
How does this value get into Crazy Train? Does the harvester take it off of the URL directly, or does it end up as part of an event some where?
Looking at the URLs before I click on the links, I see an originationContext query string parameter that contains the above values.
How does this value get into Crazy Train? Does the harvester take it off of the URL directly, or does it end up as part of an event some where?
Tagged:
0
Best Answer
-
The simple answer is that if you see it in its own field in Crazy Train, it was populated in the Page Event as the OCID parameter, and it was populated by the Page Event's creator from that value in the URL. But, to elaborate: The OCID parameter in the Page Event is, however, no longer required (at least, it is no longer required to be populated), so it may or may not be populated, even when the OriginationContext is in the URL. Origination Context is a component used to calculate Access Method which is reported to Online Charges for billing purposes. The Cobalt Events/Billing application used to calculate the access method, so the Origination Context (OCID) was required. Later, the calculation of access method was moved to UDS (I believe to support retrieving pricing information for Warn screen). Since Access method (accessMethod) is now supplied to the Cobalt Events/Billing application, it no longer uses the OCID parameter.1
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛