Skip to content

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

@SteeveEbener

Description

@SteeveEbener

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions