Extract common search index functionalities
... for search index application (https://gitlab.com/oersi/disresi) that can be reused in different usage scenarios (oersi, resodate, course catalog, ...)
notes:
-
resourceId may be an internal id that is no URI (from OOAPI - course catalog)-> differentiate between id and url/link- note: we decided to always need a landing page for resources in the search index. Therefore, we can always assume there is an URI for the resource (field configurable per instance)
- schema (even base fields) have to be configurable
Edited by Mirjan Hoffmann