Add logic to add tags from other communities

[paulzierep]

Based on the work of https://github.com/research-software-ecosystem/micoreca
we are currently thinking about, how the filtering of tools for a specific community can be forwarded to the RSEc content, so that it can be used in the Atlas.
There is filtering based on tags in the Atlas, which is currently only working for the collectionID element coming from bio.tools.

    "collectionID": [
        "de.NBI",
        "denbi-gcbn"
    ],

What would be a good way to add tags in bulk to the tools without having to go through bio.tools ?
We could add a tags.json for each tool, that can be added automatically or manually.
We could also update the *.biotools.json files in the content repository, but will that also update bio.tools upstream yet.
Any other ideas ?

[hmenager]

Good point. This would mandate a discussion with bio.tools (poke @veitveit @anitamnd). I can think of a "spectrum" of solutions to address this:

• from adding tags directly to bio.tools files.
• to having separated dedicated deployments of RSEc atlas that filter entries on dedicated filters (which could be lists of entries, or something a bit more dynamic).
  Danger with "arbitrary tags in bio.tools" is who decides which are relevant (or not)?

[veitveit]

In principle, adding tags in a consistent way is very welcome. We could even generate collections on bio.tools from changes in the ecosystem.

Having a system with certain safety measures, and having actual people behind such an approach should be preferred. And then why not going through bio.tools?

My suggestions would be:

1. Use bio.tools when feasible
2. Create pull requests to the RSEc when adding them programmatically, as we then also have a layer of revision.

Does this make sense?