Workflow engine parsers
Workflow engines like fhi-vibes, Phonopy have underlying codes (vasp, fhi-aims etc.) to calculate desired properties. Typically, all the settings for these codes are not saved by the engines themselves but only a reference to these calculations are provided. In the case of Phonopy, a special normalization layer is added to fetch the information from the reference calculations belonging to the same upload. I personally do not favor this strategy as it will become cumbersome as we integrate more and more workflow engines. We, @himanel1 @mscheidg @ladinesa should think about a more general approach to this problem.