getting TR.LastObservationDate in results for rd.discovery.search

i am searching for economic indicator via above search and want to get the same fields i would get in the workspace. for example the field TR.LastObservationDate, which seems impossible to get in the result data.

this is my attempt:

search = rd.discovery.search(
    view = rd.discovery.Views.INDICATOR_QUOTES,
    filter = "( SearchAllCategoryv2 eq 'Economic Indicators')",
    select = "DTSubjectName,SourceName ,RIC,RCSCountryOfIndicator ,StartDate,SearchAllCategoryv2 ,Unit ,SearchAllCategory,RCSCountryOfIndicatorLeaf,SourceName,StartDate,RCSIndicatorType,Unit,AdjustmentFactor,RealtimeRIC, TR.LastObservationDate")

some fields work, some dont:

i asked via the helpdesk but the sent me in here (which i dont understand, why cant they provide support via ticket?), so i'd appreciate your help.

thank you.

Find more posts tagged with

rdp search

#technology

refinitiv-data-libraries

Accepted answers

raksina.samasiri

Hi @andreas01 ,

The 'TR.LastObservationDate' is not available as a metadata for the search function, to see all available metadata, the code below can be used

import refinitiv.data as rd
from refinitiv.data.content import search
rd.open_session()

response = search.metadata.Definition(
    view = search.Views.INDICATOR_QUOTES
).get_data()

response.data.df

From this, I found the metadata named 'ObservationDate' and the data is returned as below, is this what you're looking for?

search = rd.discovery.search(
    view = rd.discovery.Views.INDICATOR_QUOTES,
    filter = "( SearchAllCategoryv2 eq 'Economic Indicators')",
    select = "DTSubjectName,SourceName ,RIC,RCSCountryOfIndicator ,StartDate,SearchAllCategoryv2 ,Unit ,SearchAllCategory,RCSCountryOfIndicatorLeaf,SourceName,StartDate,RCSIndicatorType,Unit,AdjustmentFactor,RealtimeRIC, ObservationDate")

For the detail regarding using search function, you could check these articles: Building Search into your Application Workflow and Build queries easily using Refinitiv's Search API with Python and Jupyter

Hope this helps and please let me know in case you have any further questions.

All comments

andreas01

i think i found it with a suggested post (funnily enough, i searched the hell out of it before posting and didnt come up with anything)

with that said, there seems to be a bug with the NextReleaseDate:

it shows the wrong date

why?

andreas01

doublechecked it with the workstation, it looks correct in there, just not via api

raksina.samasiri

Hi @andreas01 ,

The 'TR.LastObservationDate' is not available as a metadata for the search function, to see all available metadata, the code below can be used

import refinitiv.data as rd
from refinitiv.data.content import search
rd.open_session()

response = search.metadata.Definition(
    view = search.Views.INDICATOR_QUOTES
).get_data()

response.data.df

From this, I found the metadata named 'ObservationDate' and the data is returned as below, is this what you're looking for?

search = rd.discovery.search(
    view = rd.discovery.Views.INDICATOR_QUOTES,
    filter = "( SearchAllCategoryv2 eq 'Economic Indicators')",
    select = "DTSubjectName,SourceName ,RIC,RCSCountryOfIndicator ,StartDate,SearchAllCategoryv2 ,Unit ,SearchAllCategory,RCSCountryOfIndicatorLeaf,SourceName,StartDate,RCSIndicatorType,Unit,AdjustmentFactor,RealtimeRIC, ObservationDate")

Hope this helps and please let me know in case you have any further questions.

andreas01

Hi @raksina.samasiri , thank you for this. i found the Observation date but your code looks very valuable for any further enquiries.

have you seen the issue with the next release date? maybe you have an idea about this?

raksina.samasiri

Hi @andreas01 ,

You're welcome. Regarding the next release date issue, as this forum is dedicated to an API usage
question, the moderators on this forum do not have deep expertise in
every type of content available through Refinitiv products. Such expertise is
available through Refinitiv Helpdesk, which can be reached via MyRefinitiv. To be of help, ticket number 13181403 was raised on your
behalf and the support team is going to contact you directly to clarify this.

andreas01

thank you @raksina.samasiri , this is very much appreciated!

raksina.samasiri

You're welcome @andreas01 , I'm happy to help.

EXPLORE OUR SITES