This relationship uses the same `org:organization` predicate that is also used for the local involvements relationship. When querying for local involvements data when an organization also has change events data, mu-cl-resources receives the change events data instead and runs into errors. This is likely a bug in the micro service itself. Renaming the predicate is a quick workaround so we have more time to find the real solution for the problem without a broken app.
If only the date is relevant we should not store it as a `datetime` since that would add timezone information which might cause the date to be displayed incorrectly in the frontend.
* Config changes to support the new "change event" data model
* Add mock data that matches the new change event model
This data can be inserted into the database by mounting the folder into the migrations service.
Co-authored-by: Boris De Vloed <boris.de.vloed@gmail.com>
Co-authored-by: Boris De Vloed <boris.de.vloed@gmail.com>
