Local Units Updates/Changes

[udaynwa]

Tasks

• Form Updates
• Reverse Geo-Coding
• XLSX Import Template
• Disclaimer Messages Updates
• Create fields

Related comment/ticket

• Local Unit Edit Functionality - Remaining Issues and Improvements #1824

[arunissun]

@udaynwa cc @tovari
I this comment I am highlighting the issues that are present as per the current tasks:

• Health local unit template does not allow multi select options : There are some fields which have option of selecting more than one option from the front end, but not in the excel template. For example General Medical services, specialized medical beyond primary level and blood services

• Review and delete button still visible on the local units which are externally managed : Review and delete button visible for validators for units which are externally managed

• Provide a marker on the map when an address is searched : Users can't identify the exact building when they search for an address. It would be good to Add a prominent marker on the searched location.

[udaynwa]

@arunissun , thanks for taking time to review the updates and adding your findings.

1. We will implement the multi-select options for the fields that require them.
2. We will remove the Review and Delete buttons from the externally managed Local Units.
3. The map currently zooms in based on the centroid of the searched location. Adding a marker at the centroid may not accurately represent the exact position of the Local Unit. Therefore, it would be more effective for users to manually pinpoint the correct location by clicking on the map after searching for the address.

cc @tovari @frozenhelium

[arunissun]

A few more things to be looked at : @udaynwa cc @tovari

• Delete button is still visible for non validators eg for user Aalavi for Spain who can only add and edit a local unit. Although the delete button is visible no validators cannot delete the local unit. But, Delete or Review Button should not appear on the local unit form for users who only have permissions of Local Unit Addition and Editing

• Add a hint to notify the user that LU that has closed is not to be deleted but to be edited and change status attribute from Open to Closed

• Location changes are not displayed on the map for validators: Old and new locations should be visible on a map. Map should zoom by default to old and new location bounding box. Zooming, panning should also work

• Set initial map zoom level when opening LU form: Need a closer zoom level to the location like on the screenshot instead of the country level zoom. the Zoom level does take the user to the location but may be we can increase a little bit more so that the location becomes identifiable easily.

• Focal Point details must be removed: The details of the focal points are still visible, they should not be visiblle.

• At the moment, only users with admin rights can do edits or create new LUs. Generic users without admin permission should be able to do edits and add new ones as well. Need to add this permission to all NS users. This is crucial because NS users are the ones who are going to primarily enrich the LU information

[udaynwa]

@arunissun , thank you for adding your comments.

1. We will hide the Delete and Review buttons for the Country admins and Region admins. This will be pushed along with hiding the buttons for the externally managed local units (from your pervious comment). We will update you once it is deployed to the Alpha instance.
2. We currently do not have any status attribute in the form to update from Open to Closed. If this is required, we can plan to add this in the future.
3. We can plan to show the old and new maps in the review pop-up in the future scope of work.
4. We will set the zoom level to as shown in the screenshot. We will update you once it is implemented and deployed to the Alpha instance.
5. We will hide the Focal Points details from the List view. However, these fields exist in the form and import template (with some of the fields being required), as per the list with the order of items that need to be changed.
6. Currently, the Country admins and Region admins can add and edit the Local Units. They cannot validate, review, or manage which Local Types are externally managed. In order to grant these permissions to the users, the super user (or the user with admin panel access) can go to the admin panel and grant the {country name} admin or {region name} admin permission to those users. If any modification is required, happy to discuss this one over a call, @arunissun

cc @tovari

[tovari]

@udaynwa, thanks. Regarding 6., we need to provide the permission of submitting edits by default to any NS and IFRC users (not only admins of the NS).
@davidmuchatiza, @arunissun

[udaynwa]

Understood, @tovari . Can we discuss the implementation during the next Developer call?

[tovari]

@davidmuchatiza, @udaynwa, I analyzed the user accounts and came to the conclusion that we should provide editing permissions to NS and IFRC users to the countries they set on the account page. This Country info is intended to provide information about the users duty station. It is a required field, available for each user. So, users, with api_profile.org_type "NTLS", "DLGN", "SCRT" should have ability to edit LUs in the api_profile.country_id

[udaynwa]

@davidmuchatiza, @udaynwa, I analyzed the user accounts and came to the conclusion that we should provide editing permissions to NS and IFRC users to the countries they set on the account page. This Country info is intended to provide information about the users duty station. It is a required field, available for each user. So, users, with api_profile.org_type "NTLS", "DLGN", "SCRT" should have ability to edit LUs in the api_profile.country_id

@tovari , this has been implemented and is ready for your review in Alpha-7 instance.

[tovari]

• the LU editing form cannot be colsed, the X doesn't work, it is not active
• 'Done' button doesn't work either when editing a LU

[udaynwa]

• the LU editing form cannot be colsed, the X doesn't work, it is not active
• 'Done' button doesn't work either when editing a LU

@tovari , it is working fine now. We could not replicate it. I believe the issues could be caused by the cache. If the issue persists for you, could you provide the steps to replicate?