RDP RICs and Topics codes

We are using the RDP stories API to retrieve stories with the following call:
GET https://api.refinitiv.com/data/news/v1/stories/{storyId}
We then read the field "subject" and "assert" to find the subjects of the story, and have the following questions:
- Is it safe to make use of the news2000 codes with the prefix "N2:"? Are news2000 codes going to be deprecated? Should we use RCS codes instead? Is there mapping from all the news2000 codes to all the RCS codes?
- "assert.organisationDetails.hasInstrument._symbol" contains RICs. Shall we make use of it? What is the difference between "assert.organisationDetails.hasInstrument._symbol" and "assert.sameAs._qcode"?
Best Answer
-
Hello @pevangelidis and all,
Additional insight from our news product expert:
- Is it safe to make use of the news2000 codes with the prefix "N2:"? Are news2000 codes going to be deprecated? Should we use RCS codes instead? Is there mapping from all the news2000 codes to all the RCS codes?
While RCS and N2 codes are both currently supported, the RCS topic codes are deemed more strategic and have additional attached metadata such as confidence scores and provenance. Link to RDP news metadata with RCS to N2 code: https://my.refinitiv.com/content/dam/myrefinitiv/products/11528/en/Technical/630848.xlsx
- "assert.organisationDetails.hasInstrument._symbol" contains RICs. Shall we make use of it? What is the difference between "assert.organisationDetails.hasInstrument._symbol" and "assert.sameAs._qcode"?
For public and private company identification we would suggest leveraging the permId of the organization identified with prefix ‘P:’. Under the has instruments for public companies the primary news RIC code will be provided, but RICs can change and in actuality the RIC is a quote level identifier and there can be many RICs aligned to a organization. The sameAs code is typical for topic codes, where the RCS code
Same as example:
"_creator": "rftResRef:sys24",
"_how": "howextr:tool",
"_qcode": "M:2DZ",
"_why": "why:inferred",
"sameAs": [
{
"_qcode": "N2:PUBL"
}
],
"name": [
{
"$": "Public Company News"PermId example:
•{
• "_qcode": "P:4295904307",
• "name": [
• {
• "$": "International Business Machines Corp"
• }
• ],
• "type": [
• {
• "_qcode": "cptType:8"
• }
• ],
• "organisationDetails": [
• {
• "hasInstrument": [
• {
• "_symbol": "IBM.N",
• "_symbolsrc": "symSrc:TR",
• "_type": "symType:RIC"
• }
• ]
• }
• ]
• }
• ],0
Answers
-
Hello @pevangelidis,
The currently active news codes and the map to RCS codes can be reviewed at https://my.refinitiv.com/content/mytr/en/product/machine-readable-news.html->Machine Readable News - News codes
Please see former News 2000 codes in columns B and C mapped to the current codes in column A. I would suggest to use the current news codes.
On your second question, I would suggest to review RDP News User Guide look for section"assert". I do not see any description or reference for assert.organisationDetails. If you are looking to cover partially related RICs, I would go with assert-> _qcode, as described.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 24 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 714 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛