Metadata created for our courses (from the YAML headers and elsewhere) are compiled into a JSON file. The problem is primarily that the metadata included there is unstructured and difficult to make sense of. There is also unnecessary information there, but that is less problematic. It is also likely that the metadata that is included doesn't follow the convention set out by Bioschemas.org.
It is important that our training materials are interoperable with other training materials (e.g. from the Carpentries) so this should be resolved to harmonise our metadata with commonly used metadata standards.
Further information
This is visible through the inspector tab on the browser's developer tools. The relevant section is: Githubissues.
Githubissues is a development platform for aggregating issues.
About
Metadata created for our courses (from the YAML headers and elsewhere) are compiled into a JSON file. The problem is primarily that the metadata included there is unstructured and difficult to make sense of. There is also unnecessary information there, but that is less problematic. It is also likely that the metadata that is included doesn't follow the convention set out by Bioschemas.org.
It is important that our training materials are interoperable with other training materials (e.g. from the Carpentries) so this should be resolved to harmonise our metadata with commonly used metadata standards.
Further information
This is visible through the inspector tab on the browser's developer tools. The relevant section is: Githubissues.