Duplicate bonds in results when searching by issuer/entity orgid
Hi,
I'm finding I get duplicate bonds for an issuer/entity when using InstrumentSearch from the REST API. For example, if I search with orgid = 115689364
var resultingInstruments =
_searchContext.InstrumentSearch(
AllInstrumentSearchRequest.Create(
new DssCollection<InstrumentTypeGroup>() { InstrumentTypeGroup.GovCorp },
IdentifierType.OrgId,
"115689364",
IdentifierType.Ric));
I get back several bonds, but some appear to be duplicates on slightly different Ric's, for example:
ZATH14A7=J
ZATH14A7VT=J
I would like to choose only one of these, but I'm not sure how to differentiate them? If I do a composite and T&C lookup they seem to be on the the same exchange and other Composite and T&C fields seem to also have the same values.
Can someone please explain how I can eliminate one of them, or what Composite and T&C fields I should look at for this?
Thanks,
Lindsay
Best Answer
-
Hello @lcrawford,
I do not believe that what you see is duplicates, to my best understanding ( I am a developer, rather then a content expert) different RICs, even if they differ slightly, represent different instruments, so the search is not, in this case, returning duplicates.
However, to help you identify the correct instruments within the result, per your requirements, I would suggest, as a customer to directly open a content support case via Refinitiv Helpdesk Online -> Content -> DSS, and be connected with a Refinitiv content expert.
There may also be a more appropriate search type to use per your requirement from among the available searches, rather then InstrumentSearch, perhaps GovCorpSearch, and content experts will be able to help you to identify the optimal search.
0
Answers
-
Just forgot to mention that there is a pattern in that when there are duplicates of the bond the one will always have a Ric code ending in =J and the duplicate will end in VT=J. Another example:
ZATRA4A3=J
ZATRA4A3VT=J
0 -
Hi, yes, I've looked at GovCorpSearch but it does not take orgId's and therefore we can't use it to expand the entities into the bonds they've issued.
Thanks, I've now logged a support ticket at my.refinitiv.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 705 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 3K Elektron
- 1.5K EMA
- 259 ETA
- 569 WebSocket API
- 40 FX Venues
- 16 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 4 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 284 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.2K Refinitiv Data Platform
- 879 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 123 Open DACS
- 1.1K RFA
- 108 UPA
- 196 TREP Infrastructure
- 232 TRKD
- 919 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 103 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛