How to Harmonize CoDex and RSEc

[paulzierep]

We currently have similar efforts, especially on the frontend side between CoDex and RSEc, that could be harmonized to make things faster and simpler. Since for all of us this is rather a side project, which nevertheless is becoming increasingly useful and therefore in demand, anything to make work more efficient should be considered !

We now have a frontend view for the RSEc (https://itisalirh.github.io/RSEc/). It does not include all metadata now, but has all tools and all metadata that comes from CoDex. And in my opinion it looks amazing - thanks to @itisAliRH - a true frontend dev.
Dev repo: https://github.com/itisAliRH/RSEc
This is in many ways comparable to what was build based on the Elixir Toolkit #237
The big advantage is that it can include metadata from all tools in the RSEc, that includes the CoDex, but also many more - so probably better suited to accommodate broader communities, such as ELIXIR.
It also allows using tag based search, so we could just add tags in the CoDex and get a filtered view for communities.
In short, I opt for following this approach and focusing on the improvement of the CoDex base code.
@supernord you did a great job with the Elixir Toolkit, so I do not want to just replace the work ... wdyt ?
For ideas of improvement and changes to https://github.com/itisAliRH/RSEc, I think you can just add an issue to the reop.

Currently, the RSEc also includes a workflow related to tools (only the urls), I will add name and version as well, this will improve the view.

I would also opt to create a similar view for workflows and trainings, I am not sure though if / how that can /should be integrated with the RESc, any ideas ? We should discuss that, but I wont make it to next weeks meeting.

Any other ideas for harmonization, please add them here, I will follow this up in september !

[supernord]

Thanks for sharing @paulzierep
Do you have a link to the dev repository?
The link on the page goes straight to the RSEc organisation GitHub.

[paulzierep]

https://itisalirh.github.io/RSEc/

[paulzierep]

One point of strategic discussion is where to add workflow / training metadata to related tools. We could do that in the CoDex. But this would bloat the tools.json, or during codex import in the RSEc: https://github.com/research-software-ecosystem/utils/blob/main/galaxytool-import/galaxytool-import.py

[supernord]

@paulzierep

My two cents is that the RSEc Atlas looks great. Thanks @itisAliRH

It also looks better than the current version of the CoDex interactive tables, and appears to be moving in the direction we intended for the CoDex website anyway.

Additional thoughts and questions:

• Do we still want to keep a website for the CoDex effort? Or is the idea to replace the website with the RSEc Atlas as it captures so much more of the overall ecosystem?
• Who are the key users of the atlas?
• Does this change the connection to Galaxy Labs at all?

Maybe we could discuss this in the next RSEc technical call?