Recently, we deployed the Targets feature in the CHT app. However, the data is currently displayed in the Gregorian calendar instead of Nepali calendar (Bikram Sambat). Since the Nepali calendar (Bikram Sambat) is officially used in Nepal, our users have requested that data in the Targets feature be displayed in the Nepali calendar.
I would like to request the forum leads for the necessary support.
Thank you!
cc @nitin @jkuester
1 Like
@Bhishan_KC thanks for raising this! Please have a read through this issue I logged:
opened 06:12PM - 19 Feb 26 UTC
Type: Feature
**Is your feature request related to a problem? Please describe.**
Requested [on… the forum](https://forum.communityhealthtoolkit.org/t/cht-targets-feature-display-data-in-nepali-calendar-bikram-sambat/5515).
Currently [CHT Targets](https://docs.communityhealthtoolkit.org/building/targets/) and UHC counts are collected and stored per user _per Gregorian calendar month_. It is possible to customize the _day of the month_ that target collection begins/ends by setting the [`uhc.visit_count.month_start_date` value](https://docs.communityhealthtoolkit.org/building/forms/configuring/uhc-mode/#settings) in the settings. This allows for adjusting target collection to be based on the `nth` day of the month instead of the `1st`, but this value is bound to the day of the Gregorian calendar month.
In regions that use the Bikram Sambat calendar, reporting cycles may be tied to BS months and not Gregorian months. In this case we would want the Target/UHC counts to reset at the beginning of the BS month (or in a fixed interval of days from the beginning of the BS month).
**Describe the solution you'd like**
We should add configuration that would allow aligning the Target/UHC counts to reset at the beginning of the BS month instead of the Gregorian calendar month.
@bhishankc a key question here that maybe you can help with is: `Is it possible for a BS month to ever start and end within the same Gregorian calendar month?`
If the answer is "no" (it is not possible), then I think the code changes necessary to support this feature should be localized to just the date logic we use for calculating when the intervals should start/stop. The updates may not be "simple", but they will be limited in scope.
If the answer is "yes", then things get more spicy. Currently target documents are stored for each user with an identifier that includes the `YYYY-MM` value for the Gregorian month. If two BS months can _start_ in the same Gregorian month, then we may have a collision for our target identifiers. Any resolution here would seem to involve challenges with compatibility when enabling/disabling this configuration. (Maybe that is fine 🤷).
Let me know if I missed something or misrepresented anything.
2 Likes
