How can we get the news story if I know MRN_SRC and GUID on RFA api ?
Best Answer
-
Hi @rleung
I assume you have referred to the tutorial mentioned in moragodkrit's reply above and ran the example.
You will notice that when you subscribe to MRN_STORY, each new story is delivered in realtime on the MRN_STORY RIC and is access by decompressing the FRAGMENT buffer(s) and extracting the JSON payload.
The idea is that you discard any news story that you are NOT interested in, whilst extracting and keeping any news story that you are interested in - as it is delivered to you in real time.
If you are asking 'How do I request an individual story at some later point in time after the story has already been delivered as an update on the MRN_STORY stream?', the answer AFAIK is that is not possible from the realtime feed using our realtime APIs.
It may be possible to do the above using a non-realtime service - please contact your Thomson Reuters account manager to discuss further.
0
Answers
-
It seems like you want to get the News Story Body from MRN data, is this correct?
Basically, for MRN_Story , you have to decode the fragments data to get the news story body and we provide decoded fragment data in JSON format.
The following tutorial may help you understand how to decode MRN Story
MRN Data Models and Elektron Implementation Guide
Below is the sample JSON data from the decoded fragment.
{"altId":"nBERbMJC64","audiences":["NP:BER"],"body":"PUTRAJAYA, Jan 11 (Bernama) -- I am deeply saddened to hear the sudden demise of\r\nDatuk Patinggi Tan Sri (Dr) Haji Adenan Bin Haji Satem, Chief Minister of\r\nSarawak. I’ve had the pleasure of knowing and working with Tan Sri Adenan during\r\nhis period as cabinet minister and Chief Minister. We have had many discussions\r\non improving the healthcare service at Sarawak. He will be greatly missed by all\r\nof us. We have lost a great and pragmatic leader who always displayed moderation\r\nin his leadership. My thought and prayers to his family. \r\n\r\nDATUK SERI DR. S. SUBRAMANIAM\r\nMinister of Health, Malaysia\r\n\r\nSOURCE : Ministry of Health\r\n\r\nFOR MORE INFORMATION, PLEASE CONTACT: \r\nName : Nor Suzaman B. Abdul Rahman\r\nTel : 03-8883 3470 / 013-399 7025\r\nEmail : n.suzaman@moh.gov.my\r\n\r\n--BERNAMA\r\n\r\n","firstCreated":"2017-01-11T10:26:01.775Z","headline":"PRESS STATEMENT MINISTER OF HEALTH MALAYSIA","id":"BERbMJC64_1701112rnZsduUNQrFtbV6YUmSIoDUJ2cfyhErU/uszR","instancesOf":[],"language":"en","mimeType":"text/plain","provider":"NS:BER","pubStatus":"stat:usable","subjects":["G:1","G:2EK","G:8S","G:CI","G:K","G:S","N2:ASEAN","N2:ASIA","N2:ASXPAC","N2:EMRG","N2:MY","N2:SEASIA"],"takeSequence":1,"urgency":3,"versionCreated":"2017-01-11T10:26:01.775Z"}
0 -
Totally agree with Moragodkrit,
Like to add a little on the content.
To subscribe to a story directly, the first segment is identified by PNAC (Primary News Identifier Code), and will contain the pointer at the next segment, if more then one. PNAC is used to subscribe to a news story just as RIC.
PNAC is contained in STORY_ID fid of legacy news headlines (N2_UBMS)
Or is contained in ALTID of MRN feed (MRN_STORY)
It will look similar to "nDJMK00E7C"
PNAC may be reused after 24 hours, so if you are searching within an archive of news, is only fully valid in conjunction with date and time of the story.
0 -
Dear zoya.farberov, moragodkrit,
As listed in the MRN Elektron Data Model, "A single MRN data item publication is uniquely identified by the combination of RIC, MRN_SRC and GUID." If I know the RIC, MRN_SRC and GUID, How can we re-request the whole news story from MRN news feed?
For example,
RIC= MRN_STORY, MRN_SRC= HK1_PRD_A, GUID= FWN1F602C_17011622n7nUzkkfLZyZ19eSWJpiFYfSU+HU9ymfkEci
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 中文论坛