🎩 What? Why?

There are some problems while serializing taxonomies. Usually, a resource can have multiple taxonomies and the current export method is not well structured. CSV exports are messy too if there are more than one taxonomy.

This PR should fix exports and imports when taxonomies involved

• Export taxonomies in structured way in JSON
• Correctly applies exports for CSV files when multiple taxonomies
• Imports taxonomies in resources (results, proposals)

Notes on taxonomy serialization:

Categories where a one-to-one relation with resources. Taxonomies are one-to-many. As the CSV exporter is not well equiped to deal with arrays, I've decided to transform them to an object with keys => values in this manner:

taxonomies: {
  ids: [123,234],
  123: {
    en: "Taxonomy name"
  },
  234: {
    en: "Another taxonomy name"
  }
}

As is shown, there one key ids containing an array with all the taxonomy IDs for the resource. This comes in handy on imports, as this is the only column used to find the related taxonomies. The rest of the keys are just the ids of the taxonomies pointing to the name of the taxonomy.

📌 Related Issues

Link your PR to an issue

• Related to Remove legacy categorization systems #13821
• Fixes #?

Testing

Describe the best way to test or validate your PR.

📷 Screenshots

JSON Export:

CSV Export:

♥️ Thank you!