avniproject / avniproject/jnpct
[JNPCT] Removing duplicate child locations and migrating data if present
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Currently there exists only one block for "Dharampur" which is active (not voided) - However there is another block for the same location named Dharmpur which is voided but child locations for it are active.
Because of this, these child locations are available to be added in catchment plus also visible in the drop-downs in Data entry app. The child locations under the parent "Dharmpur" should be removed after making sure that there is no data recorded against those child locations. If data is there then that data should be migrated to correct location hierarchy and afterwards the child locations under "Dharmpur" parent should be removed.
Attaching screenshots for reference:



Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the active Dharampur and voided Dharmpur location records, including their child locations and any associated data. Determine whether records require migration to the correct hierarchy before cleanup. Done means the duplicate child locations are removed without data loss and no longer appear in catchment or Data entry app dropdowns.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100