Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

automate inclusion in TeSS #19

Open
ac812 opened this issue Mar 29, 2023 · 2 comments
Open

automate inclusion in TeSS #19

ac812 opened this issue Mar 29, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@ac812
Copy link
Collaborator

ac812 commented Mar 29, 2023

Talk to the TeSS team to see if given that the training lesson has a Bioschema in it, is there a way to automate the inclusion in TeSS?
Message from Patricia: Currently Glittr is in discussion with the TeSS Team to see if the training materials in Glitter can be automatically added to TeSS.

@ac812 ac812 added the enhancement New feature or request label Mar 29, 2023
@GeertvanGeest
Copy link
Collaborator

That's correct regarding the glittr remark. If there will be direct bioschemas support from the side of glittr, the bioschema record will be based on what it can find at the github/lab api (i.e. what's written in a.o. the 'description' and 'title' in the gh repository) + the topics that are assigned by glittr -> we would basically reformat https://glittr.org/api/repositories. It will not parse any schema records in the repo/website itself. However, glittr could be used to point to repositories/websites that then can be parsed by TeSS ..

@GeertvanGeest
Copy link
Collaborator

If we standardize the use of bioschemas in the templates, there is no 'easy' way (I think?) for TeSS to scrape them all, including new ones. We can automate collecting bioschemas markup from this GitHub organization and emit them at elixir-europe-training.github.io.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants