MRN ID structures
Hi,
I'm currently developing an application to consume MRN (Elektron) via RFA API.
We are currently consuming and older NFD feed which the above will be replacing.
My question is related to the structure of the data in the new feed, specifically the ID.
In the same story this morning, we had the following ID's in the feeds above:
NFD: 20170420-073628004-nL8N1HS1AX-1-2
MRN: L8N1HS1AX_1704202aO8cjK3Mv0Q8P0a9EuJE/sMBuduop5jvxAX0o
Why are the ID's different in each feed?
Many thanks.
Best Answer
-
I believe you are comparing MRN's Item ID to NFD's Unique story index. These two IDs are not meant to be the same.
Comparing news across delivery methods is a bit complicate. The only ID that meant to be the same across all delivery methods is Primary News Access Code or PNAC.
However, PNAC itself is not unique. It is news access code, not news unique id. Each PNAC, when assigned to a news, is valid for that news for 24 hours only. After 24 hours, it can be reassigned to another news.
The PNAC is in "altId" field for MRN delivery. and in "PNAC" field for older delivery.
0
Answers
-
Please note that the old and new are not always 100% comparable since the newer feed carries enhanced / improved data.
Although you should be able re-create the id in MRN_STORY using the altId, versionCreated, takeSequence, and urgency, it can occasionally vary a bit: versionCreated may be off by 1 second, and takeSequence may be off by 1 or 2 for alerts
0 -
Hi @Umer-Nalla, I was looking to reconstruct the id =
20180124-201857000-nL2N1PJ1ZX-2-6
in MRN. I do have the following information i.e.
altid=nL8N1PK0S5,
VersionCreated = 2018-01-24 20:18:57.000
takeSequence = 2
But urgency = 3.
Please can you suggest me which value corresponds to '6' in this.
0
Categories
- All Categories
- 6 AHS
- 39 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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛