@junukitashepard found a limitation of this code:

The particular application was conversion of out:nd-nl-t-ya-c to 2 different quantities:

1. For "Gross Exports":
   • The nl (i.e. the exporting node/region) dimension should be mapped to the IAMC region dimension
   • The nd (the importing region) dimension should be collapsed into the labels for the IAMC variable dimension.
2. For "Gross Imports", it's the reverse:
   • The nd dimension should be mapped to the IAMC region dimension.
   • The nl dimension should be collapsed into the labels for the IAMC variable dimension.

The way the code currently sets the default existence and contents of the "rename" setting does not allow to do (2).

We identified a workaround, but to resolve on main:

• Add tests.
• Adjust the code.
  • In Add reporting of resource extraction to IAMC structure #451, similar (simplified) code was added for in the .report.util.IAMCConversion class. I think it has the same limitations. In fixing this issue, I'd prefer to drop the function in report/__init__.py, or slim it down to simply chain to the class.
• Improve documentation.