Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data inconsistency between project progress and groups' requireCount #1019

Open
ofr1tz opened this issue Mar 24, 2025 · 0 comments
Open

Data inconsistency between project progress and groups' requireCount #1019

ofr1tz opened this issue Mar 24, 2025 · 0 comments

Comments

@ofr1tz
Copy link
Collaborator

ofr1tz commented Mar 24, 2025

Some Validate projects (and, potentially also Street projects) that are near completion cannot be mapped on with MapSwipe web. This seems to be based on data inconsistencies within Firebase RTDB and between Firebase and Postgres. I checked for one project on the dev instance, and found the following:

  • All groups of that project had a requiredCount of 0 on Firebase. MapSwipe web queries Firebase for task groups with a requiredCount >0. Thus, to MapSwipe web, there are no tasks available for the user in this case.
  • At the same time, the project had a project progress of 92 on Firebase. With all groups having a zero requiredCount, I would expect progress to be 100.
  • In Postgres, there were two task groups of that project that had only 2 mapping sessions registered. With all groups having a zero requiredCount, I would expect that all task groups have at least 3 mapping sessions.

MapSwipe web will not allow users to map on task groups with a requiredCount of 0, as these groups are considered completed. As a consequence, MapSwipers will not be able to finish this project on the web version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant