Support arrays in input data by transforming the data

[sveinugu]

From https://github.com/orgs/fairtracks/teams/fairtracks-developers/discussions/39:

I have an idea now of how we could implement array search in TrackFind. One could extract all arrays as separate object types internally when crawling, and then reinsert them as arrays in the search results, or for validation, keeping the standard and the implementation separate. Also one could make this invisible to normal users (but probably not for curators). This would be an extension for after the deadline, if we are able to keep the standard without nested arrays for now.

We could have a similar solution for the id->object maps that can be found in some jsons (e.g. IHEC), which is also not directly supported by TrackFind (it does not support searching for attributes labels [the specific ids in this case], only leaf values). Automatic transformation into object types when crawling (might even be possible to auto detect such structures), and transformation back in search results and validation.