Discussion: Abstraction/coupling of importers / and object insertion

Right now a custom importer extends a base importer ( and let me call that _a reader_ for now on for clarify ), and utilizes an _insert_ method within another base class for inserting content.

I think we need to reword the base importers ( files / csv / etc.. ) to be something like 'readers', and have another breed of classes for object handling like posts/users ( which already exists ), then custom importers ( probably the best name for these ) to couple a reader with an object, probably with a native method that reads a class variable which contains a mapping of attributes from reader input to an object output.
This will serve basic implementation pretty well, almost no logic to write. Comes to mind as L'express migration is that basic that it needs almost no additional logic but mapping existing fields to object attributes.

Start by reading the base importers for files and CSV, the base class containing insert, and the existing posts/users and custom importer classes. The issue needs an agreed reader/object architecture, naming, and attribute-mapping approach before implementation can be considered done.

Written by the indexing model from the issue text.