Downloading the constituents for the Russell 3000

Hi all, I hope you can help me with this. I am trying to download the constituents of the Russel3000 for a given date. The exact same query works for, say, stoxx600, but not for the russel 3000.
I have seen other topics on this but I haven't been able ot replicate the solutions e..g here:
The query that I use is:
ek.get_data("0#.RUT","TR.RIC")
and
ek.get_data("0#.RUT(2020-06-30)","TR.RIC")
both return no data and throw a code 413 error ('unable to resolve some identifiers)
Thanks for the help
Best Answer
-
Hi @Alex A. thanks for your question - first off 0#.RUT is the Russell2000 - not Russell3000 - so make sure you are looking for the right index.
In terms of your queries - the first one is working ok for me:
Your second query does return the same error as you are experiencing:
This maybe because we do not carry historical constituents for all indices - you would need to raise a content query to check that.
In this thread it was suggested that you can try a screener query - this does indeed return a list of stocks - but the number is 1999 not 2000:
df3, err = ek.get_data('SCREEN(U(IN(indices(4387873/*Russell 2000 */))/*UNV:Public*/))',['TR.CommonName']) df3
Another workaround from this thread suggests this approach to the historical constituent list - which also returns a list of stocks - though this numbers 2006 not 2000.
df4, err = ek.get_data('.RUT', ['TR.IndexConstituentRIC' , 'TR.IndexConstituentName'], {'SDate':'20200630'}) df4
Probably best to check with the helpdesk to see if you have the correct permissions for Russell 2000 as some indices are fee-liable and you may need to add separate access to those - perhaps this is why the first query is not returning anything for you. Please include this thread in your communications with them.
I hope this can help.
0
Answers
-
Thank you very much @jason.ramchandani. Indeed, I tried many different indices, for the Russell 2000 and Russell 3000 using the first method and the secon of those that I posted (which I had found while browsing the forum). I will try with the screener solution and in the meantime have asked the customer support whether we have access to those constituents. Thank you
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
- 684 Datastream
- 1.4K DSS
- 614 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
- 248 ETA
- 554 WebSocket API
- 37 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
- 641 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 89 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛