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

[discussion] What filters are available for map/list views from Reveal #65

Open
cafootitt opened this issue Mar 8, 2021 · 3 comments
Open
Assignees
Labels

Comments

@cafootitt
Copy link

cafootitt commented Mar 8, 2021

It was mentioned Reveal supports structure type filter, task status filter, as two examples named.

Use case from EUSM:

  • I'm going on a mission to visit all water points in Tana, so I'd like to filter the list of SPs to only see type = water point
  • There are too many service points in Tana showing on the map, and I'd like to focus just on those with product check tasks assigned to them, i.e. NOT the service points with only Record GPS and/or Service Point Check tasks

In the latter scenario - this could be a configuration on the server side, so that tasks are not generated at all unless the SP also has a Product Check task assigned.

Relatedly, a location filter might be helpful for SPs without a GPS and therefore, not shown on the map view. Right now, the user has to search by service point name on the list view, so it would be useful if there was some sort of location filter, so e.g. the user can filter down to a particular location level and just see the SPs for that location level.

@Rkareko
Copy link
Contributor

Rkareko commented Mar 9, 2021

Reveal supports Task status filter, Task type filter and an Intervention unit filter (i.e which entity a task is generated against e.g structure, family or operational area).

I'd like to filter the list of SPs to only see type = water point if the location object has a field that contains the type then a filter for this can be added

Concerning the location filter I'd need to have a chat with @bennsimon to get a clear picture of how the current implementation works

@bennsimon
Copy link
Member

@cafootitt I've had a talk with @Rkareko and to add the new filters specific to eusm will involve some modifications of the tasking library. L.O.E 3 days. @cafootitt Could you create an issue for the filters we should add?

@cafootitt
Copy link
Author

cafootitt commented Mar 10, 2021

Filter options:

  1. Task business status filter - has problem (only for product check task type), not visited, visited (this is against the task, but the task has a for parameter that specifies the ID of the service point)
  • This is already supported in Reveal
  • No use case identified for this in EUSM (yet)
  1. Task status filter - completed, ready
  • Not currently supported in Reveal, but it would be "straightforward, but will take some time" to extend the task business status filter to support this
  • No use case identified for this in EUSM (yet)
  1. Task type filter
  • Reveal: i.e family registration, distribution - currently supported
  • EUSM: service_point_check, product_check, looks_good, record_gps
  • This is supported in Reveal, so we'd have to add the filter functionality to EUSM, but should be supported
    Use case required for EUSM: view only service points with at least one product check task where task status = ready
  1. Intervention unit filter
  • Supported in Reveal, but not needed for EUSM (as far as we know)
  • Example for EUSM would be to filter service points by whether the task is for a product or the service point itself
  1. Structure/service point property filter
  • Not supported in Reveal
  • Use case in EUSM: show only service points where type = water point

LOE to add filters 3 and 5 for EUSM is 3 days, assuming we use the same filter UI from Reveal:

Screenshot_20210310-140302_Reveal

@cafootitt cafootitt assigned rowo and mberg and unassigned Rkareko Mar 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants