Think about switching from duplicating columns to list columns

Working with duplicated columns like "modification parameters" for multiple modifications is not great.
When loading with pandas for example you will receive renamed columns like "modification parameters.1" and then need to do a prefix matching to apply validation rules.

Having a list column would also make the transition to parquet or json or anything more structured easier.

No files, tests, or entry points are named. Start by examining how duplicated modification-parameter columns are represented and loaded with pandas, then evaluate the proposed list-column direction alongside parquet and JSON; done requires an agreed schema change and migration scope.

Written by the indexing model from the issue text.