Open mhabimana opened 5 years ago
Thanks @mhabimana for reminding us this issue. The problem is not only for an operator seeing what others are doing but sometimes they may modify other station's data. I think the solution can be to create a user and assign one or two stations to him or her.
In Rwanda for example, Observers at outstations are entering data directly into the database at HQ but the problem here is that,they are not interested to see data from others stations apart their own entered data. The idea here is to restrict them to be able to see only their data and not the whole set entered by other users. This issue was raised by @Iyakaremyevedaste in Rwanda.
@smachua @Patowhiz @mhabimana how far with this issue? This issue needs more attention because now it is crucial. Our DB is being used by our staff at upcountry offices and data rescue team. You can imagine how key entry forms are busy! The moment you finish data entry for one station on a particular month, you find the station name has changed because another person is doing a key entry for that station! Assistance is much appreciated.
@Iyakaremyevedaste using Climsoft V4.1.5 and V4.1.6 you can avoid that problem. Data entry can be done at the local server at the stations then get exported to HQ where it will be imported into the same key entry form in the central server. These operations are achieved through the View button in any of the key entry form. It has been tried in Mozambique and @mhabimana can take you through that process.
In Rwanda for example, Observers at outstations are entering data directly into the database at HQ but the problem here is that,they are not interested to see data from others stations apart their own entered data. The idea here is to restrict them to be able to see only their data and not the whole set entered by other users. This issue was raised by @Iyakaremyevedaste in Rwanda.