Is your feature request related to a problem? Please describe.
As a developer, I have an existing Postgres database that I wanted to use AGE with. However, I do not want to migrate my existing schema to the AGE schema and alter all my processes to support the new data layout.
Describe the solution you'd like
I would like AGE to be able to handle alternative schema other than the one AGE currently supports and the a tool to map my existing schema to vertex and edge system that AGE supports. This tool will need to be able to read my existing schema, provide a best guess of the graph that the user wants to create and allow the user to make alterations to the graph that will be created.
Describe alternatives you've considered
A complete data migration of my database and alter all processes that use my database.
Additional context
I think the backend for this tool would be cool if it was written in a rust. I think it has a lot of advantages that AGE could take advantages of when building the conversion tool.
We could take advantage of the thread safety features to improve the performance of the tool, without losing the advantages that C provides.
The frontend and the way the user is able to map their schema, is a web application.