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

Avoid multiple representations of the same data #39

Open
shankari opened this issue May 2, 2023 · 1 comment
Open

Avoid multiple representations of the same data #39

shankari opened this issue May 2, 2023 · 1 comment

Comments

@shankari
Copy link
Contributor

shankari commented May 2, 2023

This is a generalization of #31
Right now, the expectation in the codebase is that the config will contain the additional columns to be displayed.
But if the surveyinfo is MULTILABEL then (at least now), there are only a certain number of labels.
Requiring them to be specified in multiple places just increases the possibility of a misconfigured instance.

@AlirezaRa94 this is why I wanted the configs to be integrated and not to have a separate "admin dashboard" file.
Note also that the addition columns are not really a permission issue.

@shankari
Copy link
Contributor Author

shankari commented May 2, 2023

Enketo is trickier, but even if the surveyinfo is ENKETO, we already specify the important information to be pulled out and displayed in the label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant