Data collection with Enketo not working

[kauedesousa]

I was trying to demonstrate the data collection using Enketo and it is not working. I put the username and password and it does not go thru. The login UI load and returns to the same point when it started asking for the username and passport. This needs to be solved urgently.

[kauedesousa]

Here an example

ScreenRecording_06-12-2025.17-07-49_1.mov

[BrandonMrBot]

@kauedesousa

I have performed tests and Enketo is working correctly.

What is happening with the explanation and the example you shared with me is due to a known limitation of this functionality, which was discussed at the time of designing the solution. Let me explain:

Currently, only a single Enketo link is generated for data collection, and this link is associated with the project owner. This means that only field agents registered under the project owner will be able to log into the form through that link.

How can this limitation be solved?

• Create a generic field agent:

  The project owner can create a generic user (with a user name and password defined by him/her) and share it with all the people who will use the form.

• Register each field agent individually:

  The project owner can register each field agent in his library and then assign them to the project. This allows a more detailed and secure access control.

About the example you shared:

I don't have much context, but it seems to be about a shared project. In these cases, if you try to log in with a field agent that does not belong to the project owner, Enketo will not allow access to the form, generating the behavior you mentioned in your example.

How can we solve the limitation:

As I mentioned, currently only one Enketo link is generated linked to the project owner. To solve this in a more flexible way, an Enketo link should be generated for each user with whom the project is shared, and each group of field agents should use the corresponding link.

Example:

If a project is shared with 10 different users, 10 Enketo links should be created, one for each user. Each user's field agents would be able to access correctly using the appropriate link.

Final note:

This solution was not initially implemented due to possible confusion between the number of links generated and the number of field agents, which could make project management difficult if not handled carefully.

[kauedesousa]

Ah ok I remember. Maybe we can put this information on ClimMob saying that there is a maximum of field agents that can be registered using Enketo. The main issue that I was trying to address is to use the current features to allow for farmer-led data submission, but I think this will not be possible to be done using the current features we have. I will create another issue to address this need and we add it as part of new features for a next version. What do you think?

[kauedesousa]

The username needs to be registered by the project owner. If the field agent account comes from another user other than the project owner this will produce this issue. Let's just put it documented somewhere and close the issue.