The outcome of the workshop can be found here: https://hedgedoc.research.software/XCp6ChiNQpOX78z7rPG-aQ?view#

After further discussion, we decided to go for the following approach:

User perspective:

• The preference is to have a single RSD which can also show/search/filter results from other RSDs.
• Remote software will also show up in the software overview page, mixed with the local software according to the sorting set by the user.
• Clicking on a remote software card will forward the user to remote RSD which is the 'home RSD' of the software
• We'll see if we can 'tag' the cards of the remote software somehow to indicate that they are from a different source.

What to harvest:

• An RSD must harvest the minimal data needed from other RSDs to show the software tiles and do search/sort/filter
• The RSDs to harvest from are configured by the admin. If nothing is set, the result will be a 'normal RSD' without remote software.
• Vice-versa, an RSD could have no local data but only show remotely harvested information. It would then be a pure aggregator.
• A brief delay (i.e., an hour or so) for the information to be harvested from a remote RSD is acceptable
• Local information should update immediately

Care must be taken not to introduce duplicates or cycles. For example:

• Cycle: The NLeSC RSD also shows the Helmholtz content and vice-versa. When the NLeSC RSD harvests the Helmholtz one, it should not receive it own software (or detect this and ignore it).

• Duplicates: The NLeSC RSD harvests the Helmholtz one and NFDI.software. The latter also harvests the Helmholtz one. We should take care that we don't receive duplicates of the Helmholtz Software.

Do we also want to support hierarchies? For example:

• The NLeSC RSD harvests NFDI.software, which has its own software + stuff harvested from Helmholtz. Helmholtz software then also shows up in the NLeSC RSD via the NFDI.software one.