Conversion of our content to a database

[haesleinhuepf]

We should take the content in our yml files and convert it to a relational (SQL?) database. Therefore, we need to identify mandatory and optional meta data + we need to design the structure carefully. We should also explore how similar databases handle their content, because we want to be compatible with them:

• https://biii.eu
• https://bio.tools/

[bgruening]

I guess https://tess.elixir-europe.org is the service you should look at as well. What functionality are you missing on TeSS?

[SeverusYixin]

let me check it later :)

[bgruening]

Sounds good. Just make sure it's not too late and you are redoing work that was already done :)

[SeverusYixin]

redoing work

Hi @bgruening, may I ask, does 'redoing work' mean we have our own database?

[bgruening]

Mh, not sure I understand your question, sorry.

But TeSS is a platform for discovering online information and content, including training materials, events and interactive tutorials. So my naive assumption is that they have a database, a webfrontend and a sophisticated search system that overlaps a bit with this project. So it might be worthwhile to look at this.

TeSS is also scraping content from other websites. So you could also annotate your training here with bioschemas and TeSS will automatically find our trainings and integrate it into their DB/website.

[SeverusYixin]

ahhh, that's my problem. My question was in relation to your comment "you are redoing work that has already been done :)", which part of the work is this referring to? At first I misunderstood you to mean that we already have our own database。