What we need is organized data import. Right now, for each experiment (or series of experiments), there is a separate import script. Ideally, this needs to be split into data preparation and data import stages. During data preparation stage, some kind of structured output will be created. Right now it seems to me that separating data in accordance with experiment - subject - block - trial - stimuli logic seems to be valid. Maybe we don't need separate files for each node type, but on the other hand, if we do it all the same, why not? In addition to the files themselves, there should be a translation between csv columns and DB properties.
During data import pre-prepared files should be imported in DB. This should work for every possible import as long as it is correctly prepared.
What we need is organized data import. Right now, for each experiment (or series of experiments), there is a separate import script. Ideally, this needs to be split into data preparation and data import stages. During data preparation stage, some kind of structured output will be created. Right now it seems to me that separating data in accordance with experiment - subject - block - trial - stimuli logic seems to be valid. Maybe we don't need separate files for each node type, but on the other hand, if we do it all the same, why not? In addition to the files themselves, there should be a translation between csv columns and DB properties.
During data import pre-prepared files should be imported in DB. This should work for every possible import as long as it is correctly prepared.