Related components

[fossygirl]

Given that components are often released in sets, we should allow users to discover sets of components that have definitions and add these to the components list.

This one is a little abstract as we don't have a concrete way of defining "related". One relationship is Source. Another is "other package format". The scenario that inspired this issue was a set of packages that all go together (e.g., foo-sdk, foo-cli, ...). Unfortunately without some additional context that may be hard to automate.

[fossygirl]

@jeffmcaffer I believe this issue is superseded by the suggestions work we're doing. Can you confirm and we can close this?

[jeffmcaffer]

This is different. Suggestions is suggesting how the user can curate a given definition. This is aimed at helping the user find related components to curate. So say you are looking at Foo 1.0 and find the license is missing. It should be really easy for you to also then add all other versions of Foo (or 1.* or just ones also missing licenses or, ...) to your curation list. At that point you can use the Suggestions facility to correct the license (whatever) and do one or more PRs with the curations.

[storrisi]

This needs to be discussed. Probably with the mongo store in place, now we can provide this kind of relationship and find all the related components of a specific one.
We should understand how this would impact both the UI and the service side of things.

[dabutvin]

see clearlydefined/service#402 for the service side of this task.

I think a nice place to prompt the user to add related components to their definition list is right after a contribution is sent.

Another place may be inside the definition list when there is only 1 component added?

Any other ideas?

[storrisi]

@dabutvin maybe could be like a "suggestion" for components?

Currently, if a field has a suggestion, an icon appears near to the field and the user is able to see the details and eventually pick a selection.
Maybe the same thing could happen for a definition, with a custom icon that identifies that the component has some relations, and after clicking it we could show a list of all the relationships, so the user could select which ones add to the list.

Thoughts?