rubyforgood / rubyforgood/skillrx
Discrepancies between SkillRx and Azure
@dcollie2 is already working on this.
Since Aug 23, 2026.
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Reported by stakeholder:
While prepping new devices for rollout in Africa, I notice a few anomalies in content management including multiple entries for some topics and missing files:
Example:
For provider: emDoc > May 2026
Topic: Journal Feed Weekly Wrap Up May 2 (is displayed 3 times)
I checked the csv files and found these corresponding Topic IDs:
Topic.csv: 21480, 21485, 21481
File.csv: there is no 21481
The topic should only be listed once and have one corresponding file associated with it.For provider: emDoc > May 2026
Shift Pearls Sepsis Sources (is displayed 2 times)
I dug deeper and found this:
in CMES, related Topic IDs are: 21482, 21483
However, only one file exists in Azure for this topic. In Azure folder, it shows:
21482_emdoc_2026_5_shift_pearls_sepsis_sources.pdf (this file is not in Azure)
21483_emdoc_2026_5_shift_pearls_sepsis_sources.pdf (this is present in Azure)
in SkilRx, this Topic shows as: [skillrx_internal_upload]_shift_pearls_sepsis_sources.pdf 199 KBFor provider: Other Foam > May 2026
Case of the Month May 2026: Pituitary Adenoma > 21476_other-foam_2026_5_case_of_the_month_may_2026.pdf (shows 404)
In Azure: this file not present
In SkillRx, this shows as: [skillrx_internal_upload]_case_of_the_month_may_2026.pdf 0 BytesFor provider: Other Foam > May 2026
ID4U Episode 26 Vaccine Hesitancy Part 1 (no file listed for this topic)
In Azure: 21477_other-foam_2026_5_id4u_episode_26_vaccine_hesitancy_part_1.mp3
In SkillRx: [skillrx_internal_upload]_id4u_episode_26_vaccine_hesitancy_part_1.mp3 16.5 MBMight it be that the error is caused because the person loading content may have a) tried to enter the files multiple times, b) tried to delete and reload the file?
Can you please look into this? Am cc-ing Jess on this so that if the problem is triggered by user error, then we can inform the folks loading the content accordingly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.