When importing existing document collections through database tools like phpMyAdmin, no Create log entries are inserted in the Log table. A native import function shall be able to do this.
Desired Behavior
A tab in the module's Admin backend view shall show the option to import document collections via csv and other file types. While importing them, the module shall produce Create entries in the Log table.
I see this feature in a more general sense than just Loggable.
Here are a few considerations:
import options are generally and often interesting.
but they can be very versatile (different input formats, etc.) and must also cover extended requirements, like handling large amounts of data (chunk size, batch processing, etc.)
this is also a topic for which there are certainly already cool solutions in the Symfony ecosystem. So we don't have to reinvent the wheels here and generate import scripts for CSV, XML, etc. etc. for all kinds of entities.
if you are looking at generic import options, exports should also be rethought and adjusted in the same step.
How could that look like:
In ModuleStudio there could be a few check marks like "generateImportAbilities", "generateExportAbilities" or selections like "importFormats", "exportFormats" or something like that.
The generator creates a dependency in 'composer.json' to include the desired component.
It also creates adapter classes utilising this component.
It also generates a CLI command to start the import/export jobs from the console.
Summary
When importing existing document collections through database tools like phpMyAdmin, no Create log entries are inserted in the Log table. A native import function shall be able to do this.
Desired Behavior
A tab in the module's Admin backend view shall show the option to import document collections via csv and other file types. While importing them, the module shall produce Create entries in the Log table.