Is your feature request related to a problem? Please describe.
As we reach out to more groups to share their data with us and to share their verification status with us; we expect many of these groups will share the same resources. This will create a massive duplication problem at our end. True verification status of the resource won't be available and our JSONs will become very large.
Describe the solution you'd like
Take the record with latest updated status as true source
If state, district etc. are different between sources, send them an email about the discrepancy so that they can fix the issue.
Use other details from true source record (future problem to be solved)
Describe alternatives you've considered
We can choose to ignore verification status updates from most sources and only use their help in lead generation
We can choose to 'whitelist' certain sources for verification status updates
We can choose to update 'final' data only when there is a change in status between one sync and another for a source
Additional context
We expected some duplication to exist but with our current aspirations to scale both API / data usage from central data and decentralised verification mechanism this duplication is all set to become a huge issue.
Is your feature request related to a problem? Please describe. As we reach out to more groups to share their data with us and to share their verification status with us; we expect many of these groups will share the same resources. This will create a massive duplication problem at our end. True verification status of the resource won't be available and our JSONs will become very large.
Describe the solution you'd like
Describe alternatives you've considered
Additional context We expected some duplication to exist but with our current aspirations to scale both API / data usage from central data and decentralised verification mechanism this duplication is all set to become a huge issue.