Make template input more consistent with each other and taxonomy naming scheme

[russellb]

The code dealing with differences between:

• taxonomy structure and naming scheme
• input structure and naming for different pipelines

is getting a lot more complicated than it seems necessary. #55 dealt with some short-term fixes. This issue is to track some cleanup work to make things more consistent and hopefully reduce the amount of data transformation necessary.

From #55

Longer term consideration:

None of this matches the source format for the dataset (taxonomy). Allowing people to specify a custom pipeline implies specifying their expected sample dataset format somehow.

Another idea instead ...

1. Always assume a consistent dataset format.
2. Add a new pipeline capability for dataset transformation -- rename fields if you want, squash the rows into groups of 3 seed questions/answers per row (for the knowledge case)

I think something like this is going to be necessary to allow more configurable custom pipelines, as we'll need a way for a custom pipeline to declare the dataset format it is expecting from a known starting point.

[github-actions]

This issue has been automatically marked as stale because it has not had activity within 90 days. It will be automatically closed if no further activity occurs within 30 days.

[github-actions]

This issue has been automatically closed due to inactivity. Please feel free to reopen if you feel it is still relevant!