Parse creator and license information from CWL documents.

[jmchilton]

galaxyproject#10408 adds the ability to view this data in the GUI and annotate it in tools and workflows.

The Galaxy hook on the tool side is parse_license and parse_creator inside of lib/galaxy/tool_util/parser/cwl.py.

The workflow hook is lib/galaxy/tool_util/cwl/parser.py:WorkflowProxy.to_dict. This method produces a vanilla Galaxy workflow description for a CWL workflow - if that is populated with license and creator metadata as it would appear in a .ga file - the GUI should display the info.

[mr-c]

Here's an example of the recommended way to encode metadata about CWL documents themselves (as opposed to metadata about the tool(s) they are describing)

https://github.com/common-workflow-language/user_guide/blob/1f49ff5fa7d01081378afdbf3eb0d388f744ca6d/_includes/cwl/17-metadata/metadata_example2.cwl#L26

so if a CWL document has $namespaces: { s: https://schema.org/ } (or equivalent) then the CWL s:license: https://spdx.org/licenses/Apache-2.0 maps to Galaxy's license: https://spdx.org/licenses/Apache-2.0 or license: Apache-2.0. Note the CWL document might spell out "http://schema.org/license": "https://spdx.org/licenses/Apache-2.0" or use a different prefix other than s as a shorthand for https://schema.org/. I don't know if this fork of Galaxy has access to the post-schema-salad processing document tree, if so, then you won't need to parse $namespaces, everything will be expanded to the full URL.

Rendered lesson is at https://www.commonwl.org/user_guide/17-metadata/index.html

Does this fork already bring over any listed tool citations about the tool being described? If not, then look at https://www.commonwl.org/user_guide/20-software-requirements/index.html to learn about the optional SoftwareRequirement including optional version and identifier fields.