This section provides an explanation of the identifier scheme concept. Identifier schemes are used to map metadata objects to other metadata during import, and to render metadata as part of exports. Please note that not all schemes works for all web-api calls, and not not all schemes can be used for both input and output (this is outlined in the sections explaining the various Web APIs).
The full set of identifier scheme object types available are listed below, using the name of the property to use in queries:
The general idScheme applies to all types of objects. It can be overridden by specific object types.
The default scheme for all parameters is UID (stable DHIS 2 identifiers). The supported identifier schemes are described in the table below.
|ID, UID||Match on DHIS2 stable Identifier, this is the default id scheme.|
|CODE||Match on DHIS2 Code, mainly used to exchange data with an external system.|
|NAME||Match on DHIS2 Name, please not that this uses what is available as object.name , and not the translated name. Also not that names are not always unique, and in that case they can not be used.|
|ATTRIBUTE:ID||Match on metadata attribute, this attribute needs to be assigned to the type you are matching on, and also that the unique property is set to true . The main usage of this is also to exchange data with external systems, it has some advantages over CODE since multiple attributes can be added, so it can be used to synchronize with more than one system.|
Note that identifier schemes is not an independent feature but needs to be used in combination with resources such as data value import and meta data import.
As an example, to specify CODE as the general id scheme and override with UID for organisation unit id scheme you can use these query parameters:
As another example, to specify an attribute for the organisation unit id scheme, code for the data element id scheme and use the default UID id scheme for all other objects you can use these parameters: