Is there a universal framework in PHP that actively uses OOP for parsing, importing and exporting tables?

Question

PHP

For example, we have an exel table and, for example, we have "noname" cms
I can write a script that parses excel and, in accordance with what we see during parsing, execute various methods provided to us by "noname" cms. We get a footcloth, which is almost unsuitable for quickly applying it, for example, to another cms.
I'm wondering if there are solutions where smart people have thought and come up with such a thing that offers highly efficient organization of imports and exports, allows you to handle dependencies between tables, conversions, processing, etc. In short, work wonders. If you do not know about such solutions, then your opinion about this idea is interesting. What problems do you constantly face and what do you think such a framework should solve. Thank you!

Answer 1

We get a footcloth, which is almost unsuitable for quickly applying it, for example, to another cms.

It is impossible to write a solution that will be easily integrated into any CMS. Usually, some library is written to solve specific problems, and then supplemented with plugins that allow it to be integrated into various CMS. Moreover, each CMS has its own plugin.
The library itself should not depend on a specific CMS in any way, on the other hand, when writing a library, you can use anything you like. I would take PHPExcel , separate components from any popular framework (eg EventManager from ZF2). And I would write my own ORM, sharpened to work with Excel, based on the experience and architecture of Doctrine . If you need to work not only with Excel, then we additionally implement adapters for various data sources.
I haven't seen any ready-made solutions for such tasks.

Answer 2

The problem, in fact, is not that CMS are different.
The problem is that Yoksel is not data. These are just tables.
And in order to "work miracles", you still need to receive data as an input.
So the only way that leads at least somewhere is to discard crutches and exclude Yoksel from the technical process in principle.
Until this is done, footcloths and a headache are inevitable.

Answer 3

Haven't come across this.
What I would like:
1. To create a single integration / migration "bus" based on various types of data, you need to unify this data and simply create dependencies (data schemas) based on unified data.
2. Also, you need the ability to work with this data through ORM (this "bus"), i.e. the ability to operate with information objects and flows).
3. Also, there should be adjustable intervals for automatic collection of information from sources.
4. A system of events / triggers that can "pull" external APIs (GET / POST, etc.) on controlled events (for example, to signal one of the "bus" systems that its data has arrived - you can start parsing).
Manual Import/Export Excel:
https://dev.mysql.com/doc/mysql-for-excel/en/mysql...
https://sqlizer.io/
www.sqlmanager.net/ru/products/ mysql/manager

Answer 4

I would implement not a tool for cms, but a self-contained service. Under the hood, having all the necessary tools for working with Excel and other formats, you can not only markup, but also, for example, upload data on a specialized API to a CMS for a specific event / frequency, for example, once a day.