Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review remaining element-level data completeness alerts for correctness #1597

Open
8 tasks
emmajclegg opened this issue Oct 28, 2024 · 2 comments
Open
8 tasks
Labels
Intuitive data entry ODS Issue initiated by ODS

Comments

@emmajclegg
Copy link
Collaborator

emmajclegg commented Oct 28, 2024

Following implementation of #1553, can we review data-completeness logic for remaining elements where I suspect it is incorrect.

Requirement:

  • Elements should be marked "completed" on the Activity Data or Organisation Data pages if all their mandatory sub-elements have been populated.
  • If an element has no mandatory sub-elements (e.g. location), then it should be marked completed if any of the optional sub-elements have been completed.

Activity elements affected:

  • recipient-country and recipient-region covered in #1595
  • contact-info
  • planned-disbursement

Organisation elements affected:

  • total-budget
  • recipient-region-budget
  • recipient-country-budget
  • total-expenditure
  • document-link

Please ask if any of the mandatory vs. optional logic is not clear for these elements.

This test activity should have all elements completed with their mandatory sub-elements - i.e. it shows which data completeness alerts are too strict currently

@PG-Momik
Copy link
Collaborator

PG-Momik commented Nov 5, 2024

@emmajclegg
Following our discussion, I've reviewed the module for completeness calculation. For us to implement new completion rules that reflect the recent changes of #1553 , the actual changes in the back-end would be 1 liner. However we'd need to update some of the existing unit tests and also perform some degree of manual testing.

cc: @BibhaT

@emmajclegg
Copy link
Collaborator Author

For us to implement new completion rules that reflect the recent changes of #1553 , the actual changes in the back-end would be 1 liner. However we'd need to update some of the existing unit tests and also perform some degree of manual testing.

Ok thanks @PG-Momik. This sounds sensible to do in that case.

In terms of new work to pick up when you can this month, I've ordered the "proposed user story/task" Github list in rough order of priority, so this issue doesn't need to be done straight away. #1596, for example, is at the top as it's causing users to publish data with errors, so that issue would be higher impact to work on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Intuitive data entry ODS Issue initiated by ODS
Projects
None yet
Development

No branches or pull requests

2 participants