Description:
Currently, the location of observations is movable in Territory view (Md), and then this change is visible in Mm and in the Observation view (Md). Issues with data accuracy and validation.
Until we have another solution, for example different behaviours for different data (monitoring data vs territory data), we should fix this and not allowing the location of the observations to be moved, coz the integration and validity of data can be jeopardized.
Solution:
- Allow it to move
- However not save the new path in the backend
- When reloading, the path is kept as is
@gmaclennan can you elaborate on this solution from a tech perspective
Description:
Currently, the location of observations is movable in Territory view (Md), and then this change is visible in Mm and in the Observation view (Md). Issues with data accuracy and validation.
Until we have another solution, for example different behaviours for different data (monitoring data vs territory data), we should fix this and not allowing the location of the observations to be moved, coz the integration and validity of data can be jeopardized.
Solution:
@gmaclennan can you elaborate on this solution from a tech perspective