Research API, combine "Views" selectors.

vitali

Hello everyone! I'm currently progressing on a project focused on companies that have been delisted. For this project, I'm utilizing the Refinitiv Search API. I've successfully managed to extract data on US companies that were delisted, including the reasons for their delisting, which are currently limited to two categories: Acquisition and Merger.

 response = rd.discovery.search(
        view = "Organisations",
        filter = "OrganisationStatus xeq 'Delisted' and RCSCountryHeadquartersLeaf eq 'Uni       ted States'",
        select ="DocumentTitle,CommonName, DelistedDate, OrganisationStatus,DTCharacteristics, FormOfTransactionCode, ReasonDelisted",
        top = 1000
)

Given these constraints, I've decided to make the best of the available data.

My current objective is to delve deeper into the specifics of Acquisition and Merger deals to enable the calculation of Delisting Returns for these companies. To achieve this, I've been exploring the DealsMergersAndAcquisitions View, which offers a plethora of fields that could potentially aid in my analysis. However, I've encountered a significant hurdle: the API does not support the simultaneous use of two Views.

What I aim to do is integrate certain selectors from the DealsMergersAndAcquisitions View into the Organisation View or combine data from two views for the same companies into one. This integration would allow me to maintain a comprehensive list of delisted companies, complete with reasons for delisting and detailed information about the corresponding deals. Does anyone know how to accomplish this integration effectively?

Would appreciate any help! Thank you in advance!

nick.zincone

Hi @vitali

The Search service does not support the ability to specify a list of views as you discovered. However, there is the option of using 'SEARCH_ALL' which should cover every View. What this may do is introduce hits/results that you are not interested in, i,e. more data than you need. However, because Search does provide filtering, you can filter out hits based on relevant criteria. For example, within the Search article, you can review some of the Common Properties as a way to filter unwanted data. Properties such as: 'SearchAllCategoryv3', 'RCSAssetCategory', 'RCSTRBC2012' can potentially help. There is not a specific property that filters out Views but I believe some of the above are pretty close to aligning with the View organization. Because Search is so rich and granular, this does require more investigation. What really aids in this activity is utilizing the browser capabilities as presented in the "Building queries easily using Refinitiv's Search API.." article. Using that, you have a nice way of looking at all properties and their values as well as the domain of values available within navigator properties. This does provide a nice way of understand how data is categorized and thus much easier for you to build intelligent filters.

Hope this helps