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

Need to differentiate between master and non-master geographic object types and hierarchies #951

Open
SteeveEbener opened this issue Dec 10, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@SteeveEbener
Copy link

User stories

Some organizations might have to create geo-object types that are not under their curation mandate for an operational purpose (e.g. the Ministry of Health creating a "Village" geo-object type as the line Ministry having the curation mandate over it has not yet created it).

The same applies to hierarchies (e.g. the need for a ministry to use a version of the administrative unit hierarchy that does not contain one particular level (e.g. Communes).

Problems this relates to

Proper CGR content documentation to avoid content misuse (e.g. someone using the operational list of village from the MOH as the official one)

Proposed solution

  1. Include the possibility to specify if a geo-object type is master or not in the geo-object type metadata (dropdown, not check box)
  2. Include the possibility to specify if a hierarchy is master or not in the hierarchy metadata (dropdown, not check box)
  3. Display the information (Master, Non-master) next to the geo-object type or hierarchy name in the module. Example
    image

Considered alternatives

  1. None

Additional context

None

@SteeveEbener SteeveEbener added the enhancement New feature or request label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant