Thank you for the reply, Jason.
Is it advised to first acquire the material_id with .summary.search, and then using the .elasticity.get_data_by_id to finally get the tensor through .elasticity.elastic_tensor? (I used this post for inspiration: Best practices for heavy API usage?)
I ask because I struggled to get .elasticity.search to understand my chemsys and material_id field commands, etc.
Using the longer route I managed to get the full elastic tensor, as I wished.
Warm regards,
Erik