WFP-VAM / WFP-VAM/RAMResourcesScripts

[Analysis] Data Reliability Score

Open
#249 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scheme
Stars
35
Forks
31
Avg merge
1d 1h
Merged PRs (30d)
4

Description

Adding for reference

This implementation is not ready for production because:

  • it relies on computed indicators (not present in the script - the prerequisite would be to have a package that compute indicator for any household survey, which we do not have yet)
  • does not generalize checks (i.e. relies on specific livelihood coping strategies present in the dataset)
  • is it not efficient (i.e. checks 10000 variables to see if 9999 is present)
  • it cannot be called from an another piece of code (i.e. cannot be automated)
  • does not have validations and does not handle errors (i.e. the code will crash if the input data is not what it expects)

Originally posted by @AlexGherardelli in https://github.com/WFP-VAM/RAMResourcesScripts/issues/221#issuecomment-4388198331

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue provides no file, test, or entry point, and refers to an implementation discussed in issue #221. Start by reviewing that referenced implementation and the listed production limitations; the issue does not define a concrete change or completion criteria.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.