My usual work flow of logging simulation result is exporting to a .csv file, which captures the scalar value. Then, I can create visualizations in third-party tools such as matlab or python. What I lack is the metadata (such as corner, temperature, modelFile, global variable, local variable, .etc.) info logged together with the data.
Usually, I manually fill in the corner and temperature sweep and which test it is.
If I want to increase the chance of being able to reproduce the same simulation result later or knowing the variable value, I save the global variable to .csv, I save the local variable to .csv, then save the corner to .csv. If spending enough effort, these info can be combined to calculate which is overwriting which. (Actually, I found a relevant post to show how to do this)
At the same time, the datasheet exported by maestro contains all the info I need: 
If I were to do it manually, this would be more or less the final outcome. This disadvantage is
1. The format of the default report does not fit all my need
2. The .html or .xml file (with multiple sub-files) does not work so well in terms of being embedded as part of the report. (Again, if I look at the individual .xml files, the info are there, just not straight-forward to reverse-engineer)
Therefore, I wonder what is currently (2023) a smart way/ (the smartest way) to retrieve metadata info, so that I can combine them into the report, together with the simulation data.