[FEATURE] Save or predefine column mappings

[BastianBalthasarBux]

Add a possibility to predefine or save some column mappings.
For recurring imports with lots of columns, this would add some more comfort for the user.
Predefinition could then be overridden on presentation like it is already.

[calien666]

Hello @BastianBalthasarBux,
Your'e right, this is a quite good feature. How do you think, an implementation can look like?

IMHO it would be a good idea creating an import template on the fly while importing a spreadsheet. Additionally, a predefined set could be placed as TSconfig as per table import?

Please let me know, which one could be useful.

[foppelfb]

My inital idea would either be a Typoscript structure or some kind of record-type.. If it would be the record, I would think a json-structure in a text field with a renderType would be ideal? The question for both versions would be: can an editor create the mapping without seeing the data.
On the other hand the same record could be created in the import-mask itself when a mapping for the current xls has been made, before importing. Like 'save this mapping as a preset'

What would the next expectation be? That someone selects presets on the preview-screen? or that someone would select a preset on the upload-screen and it would be applied automatically, skipping the preview screen? or both?

[calien666]

AFAIK TypoScript in backend should be avoided, we should use PageTs, which is for backend setup. But yes, something like this was in my mind, too.

[sbuerk]

I would say - create a table / tables for it to save these presets, and let it be choosable.

* tx_xlsimport_preset
  - uid
  - pid
  - title
  - description
  - tablename
  
* tx_xlsimport_presetmapping

  - uid
  - pid
  - preset_id (-> tx_xlsimport_preset.uid )
  - csv_column_position (or name)
  - table_column_name

Than, if a preset is selected for an import it could be validated if all columns are in there or not or similar adjustable options.

I would stay away from PageTS config (and TypoScript is out if discussion). Using tables for it allows to be simply editable / maintanable in the backend with TYPO3 core ways (list module and form engine).

Another way could be, to use yaml files for it - and provide a way to register them in some way. This would make this "deployable", but not having backend edit options for it.

[BastianBalthasarBux]

Hello @BastianBalthasarBux, Your'e right, this is a quite good feature. How do you think, an implementation can look like?

IMHO it would be a good idea creating an import template on the fly while importing a spreadsheet. Additionally, a predefined set could be placed as TSconfig as per table import?

Please let me know, which one could be useful.

Hi, sorry, I was on T3BOARD24 and had no time to answer here. For me, a predefined TSConfig would be great!

[BastianBalthasarBux]

I would say - create a table / tables for it to save these presets, and let it be choosable.

* tx_xlsimport_preset
  - uid
  - pid
  - title
  - description
  - tablename
  
* tx_xlsimport_presetmapping

  - uid
  - pid
  - preset_id (-> tx_xlsimport_preset.uid )
  - csv_column_position (or name)
  - table_column_name

Than, if a preset is selected for an import it could be validated if all columns are in there or not or similar adjustable options.

I would stay away from PageTS config (and TypoScript is out if discussion). Using tables for it allows to be simply editable / maintanable in the backend with TYPO3 core ways (list module and form engine).

Another way could be, to use yaml files for it - and provide a way to register them in some way. This would make this "deployable", but not having backend edit options for it.

A TSConfig is also deployable, you just need to add it to your sitepackage. I don't get it, what YAML makes here any better. If it needs to be editable in the backend, you could add it inline to page tsconfig. You'll lose deployability, but this you lose with your table approach as well.

[Although there are ways to deploy databases as well, which resolves in either case ...]