Hi, looking for general insight into philosophy of OmekaS and external data. We are looking at OmekaS for managing external websites (exhibits essentially) and as an OAI-PMH repository but not using it as our main collection management tool.
After installation and getting a feel for it, and then doing google searches and reading the forums I get the sense that OmekaS is not designed to work with external data other than through the Data Repository, DSpace, Fedora (maybe others?) repository plugins. I found a Geometry datatype plugin that references Postgresql (GitHub - Daniel-KM/Omeka-S-module-DataTypeGeometry: Module for Omeka S that adds data types "geometry" and "geography" to store markers and area highlights on images and maps with wkt) but it looks like it is not actively developed? I see the plugins for data importing from CSV and Zotero.
It seems that I cannot reference an external database and its tables (example: postgresql/postgis used with a collection management system). Could this conceivably be done with in house development? Or does that somehow go against the model of OmekaS? Would having a different collection management tool require exporting from that tool and importing to OmekaS in order to use items from our collection?
Thanks for the insight.