Check https://madata.dev/ to use YAML files as the source of truth for entities.
We could also store the added regexes locally and have "async" logic to reconciliate, use the Mongo db as an intermediate...
=> We need to craft a big architecture schema to have the full picture here and reason about new schemas
Should we have a separate collection for entity matching rules?
Entities are also used by the surveyform, so altering them too often would trigger many rerenders for currently open surveys, while surveyform doesn't actually use the regexes.
Yet storing those alongside the entity makes it easier to find them back later on.
Updating regexes in the YAML easily?
Check https://madata.dev/ to use YAML files as the source of truth for entities.
We could also store the added regexes locally and have "async" logic to reconciliate, use the Mongo db as an intermediate...
=> We need to craft a big architecture schema to have the full picture here and reason about new schemas
Should we have a separate collection for entity matching rules?
Entities are also used by the surveyform, so altering them too often would trigger many rerenders for currently open surveys, while surveyform doesn't actually use the regexes.
Yet storing those alongside the entity makes it easier to find them back later on.