Add POC for comparing datapack value vs datim

[flopez-bao]

• Add POC for comparing datapack value vs datim

Summary of Proposed Changes

• Add a tab to comparison download sheet comparing datim vs datapack value
• • join d$memo$datim$analytics and d$data$analytics to compare datim values vs datapack values

Related Issues

• DP-1118

Reviewer:

• Tests added/updated & passing.
• Clean linting.
• Related issue ticket in Jira/GitHub.
• Documentation added/updated.
• Code conforms to style guidelines.
• Well commented.
• Updates reflected in NEWS.md.
• Build check passes.

[flopez-bao]

hey @jason-p-pickering , set up the code in the latest commit to attempt the full join we had discussed last week and after playing with the columns noted that when pulling from just a datapack I ended up with differing values for mechanism code which got in the way of the join.

@jacksonsj mentioned a comparison would likely occur from a psnuxim tool, so I switched to loading a psnuxim tool OR both a datapack AND psnuxim tool. In both cases I unfortunately get a zero row comparison table:

If I turn off https://github.com/pepfar-datim/datapackr-app/blob/master/server.R#L956 then I am able to get a comparison (whether accurate yet is to be seen):

I tested with COP23 Indonesia and Botswana datapacks and psnuxim tools.

Is it expected behavior for the initial comparison_table object to be empty in the case of the upload of a psnuxim table?
And if so is it advisable to alter lines 956 to conditionally allow the workbook to be built for this use case?

[jason-p-pickering]

Please remove all commented code.

[flopez-bao]

removed commented code