To address some data quality concerns - some dirty data that was already in the system, some that has been added by people testing - I'm going to be turning off write access for a while. The system will remain readable.
I'm considering implementing a protocol that allows changes to be posted but not immediately available - e.g. a log of "changes" that can either be reviewed manually or otherwise quality assured before being integrated into the main data. This isn't clear in my head just yet, but if anyone has any thoughts on this I'd appreciate if we can share ideas.
My goal is to have more people involved in the decision making - at least in the long term, as there are many problems to solve on the way to building out a distributed system.
Apologies for not responding to questions and issues in a timely manner. I'll try to be more on the ball from here on in.
Hi folks
To address some data quality concerns - some dirty data that was already in the system, some that has been added by people testing - I'm going to be turning off write access for a while. The system will remain readable.
I'm considering implementing a protocol that allows changes to be posted but not immediately available - e.g. a log of "changes" that can either be reviewed manually or otherwise quality assured before being integrated into the main data. This isn't clear in my head just yet, but if anyone has any thoughts on this I'd appreciate if we can share ideas.
My goal is to have more people involved in the decision making - at least in the long term, as there are many problems to solve on the way to building out a distributed system.
Apologies for not responding to questions and issues in a timely manner. I'll try to be more on the ball from here on in.
-Tom