Bioschemas lesson metadata integrated to lesson.html

[samumantha]

• adds sphinx-bioschemas extension to sphinx workflow
• adds bioshemas.yml with lesson metadata from CITATION.cff (script exists but not added; could become another action later to only maintain one metadata file) and lesson itself
• combine license and reuse info into reuse.md under "about" instead of link to webpage; this reusing page also links to raw citation.cff and Bioschemas.yml file.

I have tested the general workflow and build locally. Slight uncertainty if it's in the right place in sphinx.yml. Please check :)

This is the test lesson for this implementation. If it looks good we can implement for other lessons too.

[rkdarst]

I think it looks good to me! This is how I would do it. It seems like such a simple but useful idea.

[bast]

I am reviewing bioschemas.yml and reusing.md.

[bast]

In reusing.md, I would move "How to cite this lesson" and "Structured metadata" above "Website template" and "Instruction material".

Reason: Many people have seen CC-BY legal text and they might stop reading further and miss the part where we recommend how to cite and how to use the metadata.

[bast]

bioschemas.yml looks to me consistent with CITATION.cff. I haven't verified that bioschemas.yml validates its schema.

[samumantha]

In reusing.md, I would move "How to cite this lesson" and "Structured metadata" above "Website template" and "Instruction material".

Reason: Many people have seen CC-BY legal text and they might stop reading further and miss the part where we recommend how to cite and how to use the metadata.

Good point! Agree, I'll update tomorrow ⚒️

[samumantha]

• Removed keywords without content from bioschemas
• Validated that the Bioschemas itself is ok with: https://validator.schema.org/?hl=en-US
• Updated reusing according to comments

Done.

[samumantha]

The metadata does not change that often. I think metadata update could be up to maintainers instead of making it a separate action?
What do you think?

[bast]

The metadata does not change that often. I think metadata update could be up to maintainers instead of making it a separate action? What do you think?

sounds good