As discussed today with @bgruening and @wm75, there might be some demand for a tool that parses parameter values from the metadata of datasets. I was about to create such a tool specifically for images:
https://github.com/BMCV/galaxy-image-analysis/pull/226/changes#diff-bfb2c10cf195c34a55ca9ead4f640efb91c9888715903f58648bc58c01fa092b
…but it was pointed out that having a more general tool will probably be more sustainable.
While I absolutely agree that having a general tool is much better, I have a bit doubts regarding usability of such a tool. For example, in the image-specific version linked above, we can simply hard-wire all the known metadata fields to corresponding outputs. However, in a general tool, I think this isn't possible, so the user would have to select what metadata fields they need to be parsed.
The issue is that—I think—it is not really user-friendly to require users to provide tokens like width or height in a free text field, tokens that are not really documented somewhere, tokens that users would need to look up in the Galaxy sources. Can this be done in a user-friendly manner somehow?
As discussed today with @bgruening and @wm75, there might be some demand for a tool that parses parameter values from the metadata of datasets. I was about to create such a tool specifically for images:
https://github.com/BMCV/galaxy-image-analysis/pull/226/changes#diff-bfb2c10cf195c34a55ca9ead4f640efb91c9888715903f58648bc58c01fa092b
…but it was pointed out that having a more general tool will probably be more sustainable.
While I absolutely agree that having a general tool is much better, I have a bit doubts regarding usability of such a tool. For example, in the image-specific version linked above, we can simply hard-wire all the known metadata fields to corresponding outputs. However, in a general tool, I think this isn't possible, so the user would have to select what metadata fields they need to be parsed.
The issue is that—I think—it is not really user-friendly to require users to provide tokens like
widthorheightin a free text field, tokens that are not really documented somewhere, tokens that users would need to look up in the Galaxy sources. Can this be done in a user-friendly manner somehow?