DATIM

DATIM4U Resources

Ping Huang -

Datastore Change References

Purpose  

As the approval and dedupe apps require updates based on Dataset and DSD/TA UIDs, the datastore settings based on DATIM Global are published so that systems such as DATIM4U can independently update their app settings accordingly. 

Note, these values are published according to PEPFAR's quarterly reporting calendar.  This means that in order to operationalize the datasets outside of the normal reporting period (such as during a cleaning period), you will need to amend the appropriate values in the datastore according to your required usage.  This will likely only require extending the Approval and Dedup dates.

Datastore References

This document includes the following datastore references:

  • Approvals period settings

    The Approvals period settings in the datastore are used by the Data Approval app in order to display the appropriate periods.

    Instructions for updating:
    • Go to Datastore Manager app
    • Click approvals from the left navigation panel
    • Click periodSettings
    • Change the setting values based on the approvals period settings published on this page
    • To use the code to update the period settings: select the Code from the dropdown list where Tree is displayed (next to the Save icon), replace the content with the approvals period settings code published on this page.
  • Dedupe period settings

    The Dedupe period settings are used by the deduplication app in order to calculate and display the relevant period.

    Instructions for updating:
    • Go to Datastore Manager app
    • Click dedupe from the left navigation panel
    • Click periodSettings
    • Change the setting values based on the dedupe period settings published on this page
    • To use the code to update the period settings: select the Code from the dropdown list where Tree is displayed (next to the Save icon), replace the content with the dedupe period settings code published on this page.
  • Dedupe crosswalks

    The Dedupe crosswalks are used by the Deduplication Crosswalk section in the deduplication app in order to calculate and display the relevant period.

    Instructions for updating:
    • Download dedupe crosswalk code in json format
    • Go to Datastore Manager app
    • Click dedupe from the left navigation panel
    • Click crosswalks
    • Select the Code from the dropdown list where Tree is displayed (next to the Save icon), replace the content with the crosswalks code downloaded.
 
Note: The Periods used to denote the quarters in the datastore are based on the calendar year, not to be confused with the PEPFAR Fiscal Year. This is in adherence with DHIS2 (DATIM) standards.

Back to the top.

Approvals period settings

Year Type Period Name Start End
2017 MER Results 2016Q4 Oct - Dec 2016 Aug 20 2017 16:00:00 GMT-0500 Dec 01 2017 15:00:00 GMT-0500
2017Q1 Jan - Mar 2017 Aug 20 2017 16:00:00 GMT-0500 Dec 01 2017 15:00:00 GMT-0500
2017Q2 Apr - Jun 2017 Sep 1 2017 13:00:00 GMT-0500 Sept 01 2017 17:00:00 GMT-0500
2017Q3 Jul - Sep 2017 Sep 29 2017 13:00:00 GMT-0500 Dec 22 2017 17:00:00 GMT-0500
2017Q4 Oct - Dec 2017 Jan 05 2018 16:00:00 GMT-0500 Feb 15 2018 17:00:00 GMT-0500
2018 MER Targets 2018Oct Oct 2018 - Sep 2019 Jan 12 2018 21:00:00 UTC Dec 31 2018 21:00:00 UTC
2017 MER Targets 2017Oct October 2017 - September 2018 Jan 31 2017 21:00:00 GMT+0200 Dec 22 2017 15:00:00 GMT-0500
2016 MER Targets 2016Oct October 2016 - September 2017 Jan 31 2017 21:00:00 GMT+0200 Jun 29 2017 21:00:00 GMT+0200

Approval period settings in JSON format:

Period: 2017 Results; 2016, 2017, 2018 Targets

  {
  "MER Results": {
    "2016Q4": {
      "end": "Dec 01 2017 15:00:00 GMT-0500",
      "name": "Oct - Dec 2016",
      "start": "Aug 20 2017 16:00:00 GMT-0500"
    },
    "2017Q1": {
      "end": "Dec 01 2017 15:00:00 GMT-0500",
      "name": "Jan - Mar 2017",
      "start": "Aug 20 2017 16:00:00 GMT-0500"
    },
    "2017Q2": {
      "end": "Sept 01 2017 17:00:00 GMT-0500",
      "name": "Apr - Jun 2017",
      "start": "Sep 1 2017 13:00:00 GMT-0500"
    },
    "2017Q3": {
      "end": "Dec 22 2017 17:00:00 GMT-0500",
      "name": "Jul - Sep 2017",
      "start": "Sep 29 2017 13:00:00 GMT-0500"
    },
"2017Q4": { "end": "Feb 15 2018 17:00:00 GMT-0500", "name": "Oct - Dec 2017", "start": "Jan 05 2018 16:00:00 GMT-0500" } }, "MER Targets": { "2016Oct": { "end": "Jun 29 2017 21:00:00 GMT+0200", "name": "October 2016 - September 2017", "start": "Jan 31 2017 21:00:00 GMT+0200" }, "2017Oct": { "name": "October 2017 - September 2018", "start": "Jan 31 2017 21:00:00 GMT+0200",
"end": "Dec 22 2017 15:00:00 GMT-0500", },
"2018Oct": {
"start": "Jan 12 2018 21:00:00 UTC",
"end": "Dec 31 2018 21:00:00 UTC",
"name": "Oct 2018 - Sep 2019"
} } }

Back to the top.

Dedupe period settings 

Note: The Start and End values use Epoch time, aka Unix time.  You may want to use a converter such as https://www.epochconverter.com to assist when altering these values. 

Year Type Period Start End Datasets
2017 Results 2017Q1 1506715200 1491080400
  • kkXf2zXqTM0
  • K7FMzevlBAp
  • MqNLEXmzIzr
  • UZ2PLqSe5Ri
  • LWE9GdlygD5
  • CGoi5wjLHDy
2017Q3 1506715200 1513980000
  • O3VMNi8EZSV
  • Ir58H3zBKEC
  • uTvHPA1zqzi
  • asptuHohmHt
  • kuV7OezWYUj
  • jTRF4LdklYA
2017Q4 1515189600 1518735600
  • WbszaIdCi92
  • tz1bQ3ZwUKJ
  • IZ71Y2mEBJF
  • uN01TT331OP
  • BxIx51zpAjh
  • mByGopCrDvL
2017 Targets 2017Oct 1485554400 1513972800
  • YWZrOj5KS1c
  • BuRoS9i851o
  • ePndtmDbOJj
  • AitXBHsC7RA
2018 Targets 2018Oct 1515189600 1518735600
  • l796jk9SW7q
  • BWBS39fydnX
  • eyI0UOWJnDk
  • X8sn5HE5inC

Dedupe period settings in JSON format:

Period: 2017 Results; 2017, 2018 Targets

  
{  
  "TARGETS": {
    "2018Oct": {
      "start": 1515189600,
      "end": 1518735600,
      "datasets": [
        "l796jk9SW7q",
        "BWBS39fydnX",
        "eyI0UOWJnDk",
        "X8sn5HE5inC"
      ]
    },
    "2017Oct": {
      "start": 1485554400,
      "end": 1513972800,
      "datasets": [
        "YWZrOj5KS1c",
        "BuRoS9i851o",
        "ePndtmDbOJj",
        "AitXBHsC7RA"
      ]
    }
  },
  "RESULTS": {
    "2017Q4": {
      "start": 1515189600,
      "end": 1518735600,
      "datasets": [
        "WbszaIdCi92",
        "tz1bQ3ZwUKJ",
        "IZ71Y2mEBJF",
        "uN01TT331OP",
        "BxIx51zpAjh",
        "mByGopCrDvL"
      ]
    },
    "2017Q3": {
      "start": 1506715200,
      "end": 1513972800,
      "datasets": [
        "O3VMNi8EZSV",
        "Ir58H3zBKEC",
        "uTvHPA1zqzi",
        "asptuHohmHt",
        "kuV7OezWYUj",
        "jTRF4LdklYA"
      ]
    },
    "2017Q1": {
      "start": 1506715200,
      "end": 1491080400,
      "datasets": [
        "kkXf2zXqTM0",
        "K7FMzevlBAp",
        "MqNLEXmzIzr",
        "UZ2PLqSe5Ri",
        "LWE9GdlygD5",
        "CGoi5wjLHDy"
      ]
    }
  }
}

Dedupe crosswalks

Click the link to download the crosswalk reference in HTML or JSON format.

Reference HTML JSON
MER crosswalks HTML JSON

Back to the top.

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk