N2_UBMS equivalent FIDs in MRN_STORY
Hello Team,
We are using the following 4 FIDs to retrieve real-time news via "N2_UBMS" RIC.
1) STORY_ID
2) STORY_TYPE
3) AREA_ID
4) SF_NAME
Please advise the equivalent FIDs in RIC "MRN_STORY".
Thank you.
Regards,
Best Answer
-
Thank you both for your responses and the explanation.It is much clearer now.
0
Answers
-
Hi @NWM
These fields are either field for TR's back-end system or deprecate fields which are no longer part of MRN.
- STORY_ID is a unique ID.
MRN now use "id" field in MRN's JSON and GUID in the feed envelope as a unique ID. - STORY_TYPE is the type of the take as supplied by editorial.
The type is now determined by "messageType" field in MRN's JSON. - AREA_ID and SF_NAME are back-end fields that identify the source feed. They are no longer part of MRN.
0 - STORY_ID is a unique ID.
-
Apologies, please do not close this ticket now. One question regarding FID "STORY_TYPE". In the MRN/N2_UBMS FieldMapping document provided by Reuters, there is no mapping provided between "STORY_TYPE" and "messageType".
Also, in the article below
the equivalent of "messageType" is "DSPLY_NAME".
Please reconfirm the MRN equivalent of N2_UBMS FID "STORY_TYPE" and possible values.
Thank you.
0 -
Hi @NWM
STORY_TYPE is deprecated. It has no direct equivalent field.
The type is now determined by "messageType".
0 -
Thank you for the reply.
With reference to your earlier post,
[STORY_TYPE is the type of the take as supplied by editorial. The type is now determined by "messageType" field in MRN's JSON.]
However, looking at the value of "STORY_TYPE", it is always "S".
Whereas, the values of messageType and "FID#3 DSPLY_NAME" of N2_UBMS seem to be similar (1 character 0~8 depending on whether it is alert, first take,correction,etc..)
Agreed STORY_TYPE is deprecated however the value of "STORY_TYPE" is always "S" so it does not match the value of messageType.
So, please help to clarify in N2_UBMS what was the significancne of "STORY_TYPE" and the meaning of the value "S" ?
Thank you for your support.
Regards
0 -
Hi @NWM
STORY_TYPE was used to Indicate the permanence type of story where Z meant Permanent Item
anything else meant non-permanent. As my colleauge mentioned it has been deprecated.0 -
The value is set by the editorial team.
The value itself has no meaning from the client point of view.
But from the Elektron server point of view, "S" is normal news, while "Z" is permanent news.
So, what's permanent news?
In N2_UBMS, you have to get the news headline and PNAC from <N2_UBMS> RIC. Then use the PNAC to get the story body.
Normally, the PNAC story body is only available for 24 hours. But if the news is permanent, then it will be kept on the server indefinitely.
This is no longer the case in MRN, the client now receive both headline and body from MRN_STORY.
0
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 中文论坛