Consistent field types in metadata formats

[mihai-sysbio]

We've stumbled upon an issue of handling the 'version' field of different types, and wondering if that could be made consistent; see related issue below:

to convert numeric versions to strings when generating the JSON files, and we'll have clean data from the backend

I'm thinking even further upstream, in the content repo. What do you think?

@mihai-sysbio I agree! Fixing it in the content repo would be the cleanest solution. We could ensure the data matches exactly with our Tool Metadata Schema, and then we can remove the redundant type handling in the frontend/backend.

Originally posted by @itisAliRH in research-software-ecosystem/RSEc-Atlas#6 (comment)

[arash77]

I had created this research-software-ecosystem/utils#39, hopefully it could fix this issue.