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

Appropriate Data Levels #121

Open
redet-G opened this issue Nov 18, 2024 · 4 comments
Open

Appropriate Data Levels #121

redet-G opened this issue Nov 18, 2024 · 4 comments

Comments

@redet-G
Copy link
Collaborator

redet-G commented Nov 18, 2024

Evaluate the appropriateness of displaying PHCU and facility-level performance on the public dashboard. If it is unnecessary, restrict the display to national or regional data.

@redet-G
Copy link
Collaborator Author

redet-G commented Nov 19, 2024

Limit access to orgunit level via a custom attribute or via a data store

@redet-G
Copy link
Collaborator Author

redet-G commented Nov 26, 2024

let's create a data store object in the public-dashboard namespace and key of settings. This will serve any additional customizable information. The following object will specify the orgunit limit

{
    "orgUnitLimit":{
        "type": "BY_LEVEL",
        "value": "2"
    }
}

@redet-G
Copy link
Collaborator Author

redet-G commented Nov 26, 2024

For better scalability let's change the object to the following

{
    "orgUnitLimit":{
        "level": "Number|Max level from which orgunit level can be loaded",
        "groups": "[{`displayName`:`groupName`,`id`: id}] | array of organization groups allowed"
    }
}

@redet-G
Copy link
Collaborator Author

redet-G commented Nov 28, 2024

The namespace for public-dashboard and the key is settings

redet-G added a commit that referenced this issue Nov 28, 2024
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