How to correct for duplicated bond identifiers in Refinitiv workspace or through RDP API

I am using Refinitiv python API to clean the data for a project for which I have a dataset with a massive number of international bonds with CUSIPs and ISINs as identifiers. I have to keep a record of unique bonds and merge them with another dataset. My problem is specifically two groups of bonds :
1) bonds with only one unique issue, but multiple sets of identifiers are assigned to them. For example, take the bond with the PermID 46643978220. As in the following picture, both CUSIPs of 03965UAC4 and 03965UAD2 are assigned to this unique bond (each for a different set of investors). Therefore, in my dataset with CUSIPs and ISINs, I see these two identifiers as two distinct bonds, which is problematic if I add their face values to get the issuer's debt.
PS: Please note that in this case, I solved the problem by finding the PermID of the two CUSIPs, which are identical. I would be happy to know if there is a better way to solve it.
2) Some bond issues are distinct (in their target market and identifiers) but coupled in their issuing. For example, from the same issuer above, the two issues whose ISINs are US03965TAA16 and USP04568AA23 are duplicates of each other, as shown in the following picture. Crucially, since for such bonds, one of them is a portion of the other, the amount outstanding and amount issued must not be added up; otherwise, double counting happens in the issuer's debt. Furthermore, investors' ownership has to be aggregated for the bonds; otherwise, one would erroneously think she observes only half of the actual bondholders while she observes all. How should I link together such duplicated assets?
PS: I can not solve this problem with PermIDs as in case 1 since such bonds have distinct PermIDs.
Bests, Alireza
Best Answer
-
Hi @alireza.aghaee ,
Thank you for your question. This forum is dedicated to software developers using Refinitiv APIs. The moderators on this forum do not have deep expertise in every bit of content available through Refinitiv products, which is required to answer content questions such as this one.
The best resource for content questions is the support team, which can be reached by submitting queries through MyRefinitv. The support team will either have the required content expertise ready available or can reach out to relevant content experts to get the answer for you.
Best regards,
Haykaz
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
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛