Avoid duplicate codes because of recodes

[GregorDeCillia]

The following json file is not handled correctly by sc_table()

{
  "database" : "str:database:deenenea",
  "measures" : [ "str:statfn:deenenea:F-DATA:F-EBIL:SUM" ],
  "recodes" : {
    "str:field:deenenea:F-DATA:C-VERWEND0-0" : {
      "map" : [ 
        [ 
          "str:value:deenenea:F-DATA:C-VERWEND0-0:C-VERWEND0-0:VERWEND0-1", 
          "str:value:deenenea:F-DATA:C-VERWEND0-0:C-VERWEND0-0:VERWEND0-2" 
        ], 
        [ "str:value:deenenea:F-DATA:C-VERWEND0-0:C-VERWEND0-0:VERWEND0-1" ]
      ]
    }
  },
  "dimensions" : [ [ "str:field:deenenea:F-DATA:C-VERWEND0-0" ] ]
}

It results in duplicate codes for the field C-VERWEND0-0 which causes all kind of issues with $tabulate() because if implicit assumptions.

sc_table('test.json')$field("C-VERWEND0-0")
#> # STATcubeR metadata: 3 x 7
#>   code       label                   parsed                 
#>   <chr>      <chr>                   <chr>                  
#> 1 VERWEND0-1 Space and water heating Space and water heating
#> 2 VERWEND0-1 Space and water heating Space and water heating
#> 3 SC_TOTAL   Total                   Total                  
#> # … with 4 more columns: 'label_de', 'label_en', 'visible', 'order'

The reason for that is that the map field in the json contains several URIs and only the first URI is used to generate the code column in $field(). It should be made sure that unique codes are generated in this case, possibly by concatinating the codes of the individual uris. A fixed version might create a field definition like this

sc_table('test.json')$field("C-VERWEND0-0")
#> # STATcubeR metadata: 3 x 7
#>   code                  label                   parsed                 
#>   <chr>                 <chr>                   <chr>                  
#> 1 VERWEND0-1;VERWEND0-2 Space and water heating Space and water heating
#> 2 VERWEND0-1            Space and water heating Space and water heating
#> 3 SC_TOTAL              Total                   Total                  
#> # … with 4 more columns: 'label_de', 'label_en', 'visible', 'order'

Time variables, should be converted to type category in this case, with a warning. Labels could also be concatenated. However, this would lead to very long labels which might not be ideal.

[GregorDeCillia]

Multiple codes and labels are now concatinated using a semicolon. In the above example, the first classification (useful energy category) of is now parsed as follows

• label: Space and water heating;Process heat <200 °C
• code: VERWEND0-1;VERWEND0-2

sc_table('test.json')$field("C-VERWEND0-0")
#> # STATcubeR metadata: 3 x 7
#>   code                  label                                        parsed                                      
#>   <chr>                 <chr>                                        <chr>                                       
#> 1 VERWEND0-1;VERWEND0-2 Space and water heating;Process heat <200 °C Space and water heating;Process heat <200 °C
#> 2 VERWEND0-1            Space and water heating                      Space and water heating                     
#> 3 SC_TOTAL              Total                                        Total                                       
#> # … with 4 more columns: 'label_de', 'label_en', 'visible', 'order'