The data currently imported from the Galaxy tool metadata extractor come as a json file where many of the keys include whitespaces. Can we revise this to have no whitespaces in the keys? This is a very minor point, but sometimes whitespaces in JSON keys can cause problems (although there usually is a workaround).
Would it be possible to change these keys, e.g., Maybe replace whitespaces with underscores?
Another point is whether there is somewhere a documentation that describes the format of the CSV source file, detailing the meaning and source of each field?
Thoughts @arash77 @bebatut @paulzierep ?
The data currently imported from the Galaxy tool metadata extractor come as a json file where many of the keys include whitespaces. Can we revise this to have no whitespaces in the keys? This is a very minor point, but sometimes whitespaces in JSON keys can cause problems (although there usually is a workaround).
Would it be possible to change these keys, e.g., Maybe replace whitespaces with underscores?
Another point is whether there is somewhere a documentation that describes the format of the CSV source file, detailing the meaning and source of each field?
Thoughts @arash77 @bebatut @paulzierep ?