Pipelines in 'Create Project' page are confusing

[tsteenbe]

Several of the ScanCode.io v35.3.0 built-in pipelines are confusing - to me and others they look to be doing roughly the same thing.

Talking about pipelines in below table - for a user new to ScanCode.io the words "analyze", "inspect", "resolve" and "scan" all basically mean the same. The static and dynamic resolving of dependencies seems "bolted on" to me.

Believe we should simplify the current built-in pipelines for a better user experience so the user is more likely to instantly pick the pipeline that's applicable to their use case. Ideally the UI would be 'smart' - meaning based on given inputs try to automatically select the pipeline that is most relevant

Pipeline	Description
inspect_packages	Inspect a codebase for packages and pre-resolved dependencies.
resolve_dependencies	Resolve dependencies from package manifests and lockfiles.
scan_codebase	Scan a codebase for application packages, licenses, and copyrights.
scan_single_package	Scan a single package archive (or package manifest file).

[mjherzog]

I agree that scan and inpect are close to synonyms, but not so sure about resolve.
We can certainly improve the naming conventions, but that would be a breaking change afaik.
Also it might be good for SCIO to suggest a pipeline or pipelines, but there are often multiple pipelines that can apply to the same input.