DHIS2 Metadata Assessment
DHIS2 Implementation Team
2021-11-10
Target server: https://play.dhis2.org/2.36.4/
Metadata issues
Users
- Total users: 130
- Total disabled users: 0
- Total users logged in within 7 days: 3
- Total users logged in within 30 days: 3
- Total users logged in within 90 days: 5
- Total users logged in within a year: 8
- Users who have never logged in: 106
- Percentage of users who are disabled: 0 %
- Number of users who have superuser: 75
- Percentage of users who have superuser: 58 %
Distribution of last user logins
Distribution of users within the hierarchy
Guidance section
This section of the report contains guidance information which provide more context and expiation of each of the checks.
Categories
Categories without category options
Level: Warning
Issue count: 6 (21%)
Recommendation
Any categories without category options should either be removed from the system if they are not in use. Otherwise, appropriate category options should be added to the category.
Category options with no categories
Level: Warning
Issue count: 12 (13%)
Recommendation
Category options which are not part of any category should be removed or alternatively should be added to an appropriate category.
Additional default category option combos based on category option.
Level: Critical
Issue count: 0 (0%)
Recommendation
All references to the additional default category option combination should be replaced with the desired default category option combination.
Category option combinations with incorrect cardnality.
Level: Severe
Issue count: 0 (0%)
Recommendation
Category option combinations which have an incorrect cardinality will be ignored by the DHIS2 analytics system and should be removed.
Category options with more than one membership for a category.
Level: Severe
Issue count: 2 (1%)
Recommendation
Bibendum pellentesque nibh nisl vitae rutrum quis vestibulum feugiat porta et netus parturient mauris. Nec nascetur libero lacinia id vel mauris pulvinar at augue pharetra. Elementum urna eget mauris magnis proin. Risus sed sapien ante himenaeos. Hac vitae vestibulum vestibulum nulla vestibulum ut non consectetur vel lectus ultricies euismod. Suscipit sed sed orci.
Charts
Charts that have not been opened in the last 12 months
Level: Warning
Issue count: 140 (100%)
Recommendation
Vestibulum quisque vel in dolor in proin, ipsum et urna mauris. Sit lorem dis et hac non feugiat. Mi pulvinar, curae nisi ipsum libero aliquet. Id id. Sed tortor vestibulum tincidunt facilisi elementum mauris euismod, tincidunt.
Dashboards
Total number of dashboards
Level: Info
Issue count: 27 (100%)
Recommendation
DHIS2 should contain useful dashboards for users.
Dashboards that have been viewed 1 time or less in the past three years
Level: Warning
Issue count: 6 (22%)
Recommendation
Vestibulum quisque vel in dolor in proin, ipsum et urna mauris. Sit lorem dis et hac non feugiat. Mi pulvinar, curae nisi ipsum libero aliquet. Id id. Sed tortor vestibulum tincidunt facilisi elementum mauris euismod, tincidunt.
Dashboards that have not been opened in the last 12 months
Level: Warning
Issue count: 19 (70%)
Recommendation
Dashboards that should be reviewed routinely and are not point to a broader data use issue that will not be addressed by technical means. Such dashboards may need to be kept while a process for reviewing them more frequently becomes more well defined.
Dashboards with no content
Level: Info
Issue count: 0 (0%)
Recommendation
Dashboards without content that have not been modified in the last 14 days can be removed.
Data elements
Aggregate data elements not used in any favourites (directly or through indicators)
Level: Warning
Issue count: 447 (71%)
Recommendation
Data elements that are not routinely being reviewed in analysis, either directly or indirectly through indicators, should be reviewed to determine if they still need to be collected. If these are meant to be used in routine review, then associated outputs should be created using them. If these data elements are not going to be used for any type of information review, consideration should be made to either archive them or delete them.
Aggregate data elements assigned to 1 or less orgunit
Level: Warning
Issue count: 25 (4%)
Recommendation
If the dataset is active, then review the organisation unit assignments. If the dataset is not active, then it should be removed from the system.
Data elements not in any data element groups.
Level: Warning
Issue count: 149 (14%)
Recommendation
Data elements that are not in a data element group should be added to a relevant data element group. If the data elements are not needed, they should be deleted.
Aggregate data elements that have not been changed in last 100 days and do not have any data values
Level: Warning
Issue count: 206 (32%)
Recommendation
Data elements which are no longer being reported on should be removed from datasets.
Aggregate data elements with no data values in the last 3 periods (based on data set period type).
Level: Warning
Issue count: 239 (37%)
Recommendation
NA
Aggregate data elements with NO data values
Level: Warning
Issue count: 209 (33%)
Recommendation
Consider removing data elements with no data values.
Datasets
Total number of data sets
Level: Info
Issue count: 33 (100%)
Recommendation
DHIS2 should contain datasets which are useful for data entry.
Data sets that have not been changed in last 100 days and are assigned to 1 or less orgunits
Level: Warning
Issue count: 1 (3%)
Recommendation
Datasets which are not active should be removed from the system to decrease system clutter and metadata size.
Data sets with no data values in the last 3 periods (based on data set period type).
Level: Warning
Issue count: 6 (18%)
Recommendation
- If a data set is not being updated with new data or no new data values are being entered within the last 3 periods (relative to the period type assigned to the dataset ex. monthly will be the last 3 months, quarterly the last 3 quarters) against the dataset but there are data values from previous periods the data set should be archived (ie. assign it a prefix)
- If a data set has no new or previous data values within the last 3 periods (relative to the period type assigned to the dataset) and will not be used to collect data, the data set should be removed.
Dataset sections with non-sequential sort order
Level: Warning
Issue count: 18 (78%)
Recommendation
Diam eu vehicula a accumsan velit arcu aenean lacus dui torquent. Vel curabitur at, cubilia mauris cum ut parturient velit sit. Eu et ligula sed luctus. Non ante eget suscipit turpis nibh vivamus blandit diam. Lectus molestie netus laoreet vitae non nostra ligula.
General
Object names which have leading spaces
Level: Warning
Issue count: 2 (-)
Recommendation
These objects may be able to be corrected through the user interface of DHIS2. Alternatively, they can be corrected directly in the database using SQL. You can use the following SQL as a pattern to help you create the exact query which you need: - UPDATE chart as a SET name = b.name_new from ( SELECT chartid,REGEXP_REPLACE(name,‘^+’,’‘) as - name_new from chart where name ~’^+’) b where a.chartid = b.chartid;
Object names which have trailing spaces
Level: Warning
Issue count: 38 (-)
Recommendation
These objects may be able to be corrected through the user interface of DHIS2. Alternatively, they can be corrected directly in the database using SQL. You can use the following SQL as a pattern to help you create the exact query which you need: - UPDATE chart as a SET name = b.name_new from ( SELECT chartid,REGEXP_REPLACE(name,‘+\(','') as - name_new from chart where name ~ '\s+\)’) b where a.chartid = b.chartid;
Object names which have multiple spaces
Level: Warning
Issue count: 13 (-)
Recommendation
These objects may be able to be corrected through the user interface of DHIS2. Alternatively, they can be corrected directly in the database using SQL. You can use the following SQL as a pattern to help you create the exact query which you need: - UPDATE categorycombo as a SET name = b.name_new from ( SELECT categorycomboid,REGEXP_REPLACE(name,‘’,’ ‘) as - name_new from categorycombo where name ~’’) b where a.categorycomboid = b.categorycomboid;
Indicators
Total count of indicators
Level: Info
Issue count: 81 (100%)
Recommendation
DHIS2 should contain useful indicators for users.
Indicators not in any groups
Level: Warning
Issue count: 20 (24%)
Recommendation
Indicators that are not in a indicator group should be added to a relevant indicator group. If the indicators are not needed, they should be deleted.
Indicators not used in favourites OR data sets
Level: Warning
Issue count: 5 (6%)
Recommendation
Indicators that are not routinely being reviewed in analysis, either in an output or data set, should be reviewed to determine if they still need to be calculated. If these are meant to be used for routine review, then associated outputs should be created using them. If these indicators are not going to be used for any type of information review, consideration should be made to either archive them or delete them.
Indicators not used in favourites
Level: Warning
Issue count: 17 (20%)
Recommendation
Indicators that are not routinely being reviewed in analysis, either in an output or data set, should be reviewed to determine if they still need to be calculated. If these are meant to be used for routine review, then associated outputs should be created using them. If these indicators are not going to be used for any type of information review, consideration should be made to either archive them or delete them.
Option sets
Unused option sets
Level: Warning
Issue count: 66 (38%)
Recommendation
Consider deleting unused option sets, or alternatively, ensure that they have been properly assigned.
Option sets with incorrect sort order
Level: Severe
Issue count: 41 (24%)
Recommendation
If it is possible to open the option set in the maintenance app, you can resort the option set, which should correct the problem. Another possible solution is to directly update the sort_order property of in the optionset table in the database, ensuring that a valid sequence is present for all options in the option set.
Empty option sets
Level: Warning
Issue count: 0 (0%)
Recommendation
Options should either be added to the option set, or the option set should be deleted.
Organisation units
Orgunits that are not in all compulsory orgunit group sets
Level: Severe
Issue count: 269 (20%)
Recommendation
Add all organization units to exactly one group within a compulsory organization unit group.
Organisation units which have an opening date later than the closed date.
Level: Severe
Issue count: 0 (0%)
Recommendation
Alter either the opening or closing date of all affected organisation units so that the closing date is after the opening date.
Organisation units should not have trailing spaces
Level: Warning
Issue count: 1 (0%)
Recommendation
If the number of affected organisation units is small, the easiest remedy is to correct them directly from the user interface. Another possible option would be to replace all of the multiple spaces using SQL.
Point coordinates which are not contained by their parent
Level: Warning
Issue count: 123 (20%)
Recommendation
Often boundary files are simplified when they are uploaded into DHIS2. This process may result in facilities which are located close to the border of a given district to fall outside of the district when the boundary is simplified. This is considered to be more of a cosmetic problem for most DHIS2 installations, but could become an issue if any geospatial analysis is attempted using the boundaries and point coordinates. In cases where the facility falls outside of its parent’s boundary you should confirm that the coordinates are correct. If the location is close to the boundary, you may want to reconsider how the boundary files have been simplified. Otherwise, if the location of the facility is completely incorrect, it should be rectified.
Organisation units close to Null Island
Level: Severe
Issue count: 0 (0%)
Recommendation
Update the coordinates of the affected organisation unit to the correct location.
Organisation units should not have multiple spaces in their names
Level: Warning
Issue count: 2 (0%)
Recommendation
If the number of affected organisation units is small, the easiest remedy is to correct them directly from the user interface. Another possible option would be to replace all of the multiple spaces using SQL.
Organisation units with invalid geometry
Level: Critical
Issue count: 1 (0%)
Recommendation
Update the geometry of the affected organisation units to a valid geometry. It may be possible to use the PostGIS function ST_MakeValid to automatically fix the problem. However, in other cases the geometry may need to be edited in a GIS tool, and then updated again in DHIS2.
Organisation hierarchy should have a single root
Level: Critical
Issue count: 0 (0%)
Recommendation
Vel nec fringilla diam conubia conubia et ipsum nec. Condimentum per elementum et urna diam mauris et. Massa at enim eu a justo ut a dui in. Magna cubilia, enim dui justo netus maximus lobortis ut enim donec feugiat. Tristique eu laoreet non eros eleifend mi, metus morbi natoque volutpat sociosqu. At fermentum ut quis, pulvinar ac duis. Laoreet tempor natoque sociis porta nunc turpis ante sed.
Validation rules
Validation rule missing value stratgies which are NULL
Level: Severe
Issue count: 0 (0%)
Recommendation
Using the results of the the details SQL view, identify the affected validation rules and which side of the rule the missing value strategy has not been specified. Using the mainteance app, make the appropriate corrections and save the rule.