-
Notifications
You must be signed in to change notification settings - Fork 27
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
Information mapping, gap analysis & schema revision #9
Comments
Hi @ypriverol, can we use this thread to start the conversation you mooted at the recent ETP meeting, re use-cases of the data? My interest is in the modelling of biotoolsSchema to ensure that can in future support whatever integrations / applications we want. |
Redirecting post of issue: @piotrgithub1 @joncison @hmenager @matuskalas @bgruening Hey all, I am thinking about bio.tools data (model / schema) better supporting external projects and collaborators like Bioconda, Debian, Bioconductor and ELIXIR partner projects like OpenEBench, TeSS etc. Technically we already have some support for this in our model by having Links of different types or Downloads with different types. While this is kinda ok, we could probably have more, in terms of annotations that are available. It could be nice to have something a bit more custom with some additional properties coming from the other projects and all of this can be displayed nicely on the bio.tools tool cards, perhaps with logos to the other projects. What do you think? Please tag other people who would want to participate in the discussion. |
Adding myself to discussion @osallou |
sorry for taking an age to get back to this @hansioan. In broad terms, I think we should aim to extend the model where sensible, but not aim for one unifying schema for everything necessarily (which would likely be clunky and monolithic). We can always have a modular schema architecture (extensions around a core). So ... simple changes could be to pull out Software package and Container file from Download and covert to elements (same as for Links, Download and Documentation):
Better to do this systematically rather than piecemeal though, which means the mapping / gap analysis mention in the thread title. cc @osallou |
Mapping of tool information from different projects (to be integrated) with gap analysis for anticipated information requirements, followed by revision of biotoolsSchema to support integration of new data where possible and desirable.
The text was updated successfully, but these errors were encountered: