The YAML configuration should be simplified #87
Description
Is your feature request related to a problem? Please describe.
The current configuration of the YAML file is overwhelming and impossible to cold start.
A 'simple' single class, with 8 attributes, requires keys for optional and un-used services. This 'simple' YAML file is over 600 lines.
The UI also complicates the initial setup with services like 'discovery', 'assessment', and 'agent', and 'summariation' that complicate setup, without strong linkage to documentation.
Describe the solution you'd like
The YAML file should NOT require optional steps, such as the ones listed above. There should be reasonable defaults, and there should be valid configuration without these optional services.
The UI should hide these options in the main configuyration of the classification and information extraction; They distract and confuse the experience of setup.
Describe alternatives you've considered
I've tried cold-start, it was hard.
I tried using existng configuration, and modifying through the UI, and this led to pipeline failures becuase of the optional services. They shouldn't get in the way.
Additional context
Add any other context or screenshots about the feature request here.