You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Include the possibility to specify if a geo-object type is master or not in the geo-object type metadata (dropdown, not check box)
Include the possibility to specify if a hierarchy is master or not in the hierarchy metadata (dropdown, not check box)
Display the information (Master, Non-master) next to the geo-object type or hierarchy name in the module. Example
Considered alternatives
None
Additional context
None
The text was updated successfully, but these errors were encountered:
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
Considered alternatives
Additional context
None
The text was updated successfully, but these errors were encountered: