Data Quality Index - sub-section 1.2.2 Timeliness - Timelag (spend transactions)
Instructions for submitting your feedback
1. Read through the proposed methodology for this measure and / or download the PDF at the bottom of this page;
2. Share your feedback through the comment box below, consider the guiding questions in your comments and include the question number in your response;
3. And finally you can suggest track-changes or add comments directly on the specifics of the methodology of the Timeliness and Validation measures - go to this DQI Live-Editing-Page
Proposed Measures - 1.2.2 Timeliness - TIMELAG - SPEND TRANSACTIONS
Please find below the proposed methodology for this measure. Only active activities* will be assessed in the Timeliness measures.
*Active activities refer to activities which have an actual-start-date in the past and an actual-end-date in the future. If actual start and end dates are not present, the planned start and end dates will be used
DEFINITION: assess how recent a publisher's spend transaction data is at the point it is published
For instance, a publisher may refresh their data monthly, but the refreshed data is in fact three months old. Alternatively a publisher may refresh their data only once a year, but when they do it contains current data that is less than one month out of date.
OBJECTIVE / EXPLANATION
-
Data quality objective: When data is updated, it contains recent spend data.
-
Based on the methodology, this is measuring whether the data a publisher has published contains spend transactions (either disbursements or expenditures) that have occurred recently.
-
As such, this will motivate publishers to ensure that their updated data contains spend transactions with recent transaction dates.
-
Bigger picture, the goal is to motivate publishers to ensure that they when they update their data, that they are including data that is as recent as possible.
OUTPUT |
Categorisation of how many months in arrears the data is:
Note: visualisation to include the month the data was last updated in. |
METHODOLOGY Count the number of spend transactions that took place in the last 12 months. Collect the last update date. Calculate arrears assessment by comparing last update date to transaction dates:
Note: future transaction dates will be discounted from the measure as they contradict IATI rules. |
Please find below a visualisation for this proposed measure. Do note that this has been created to help participants picture what the DQI could look like. It is not final, nor part of the proposed methodology:
Guiding questions - please refer to the question number when you respond via the comment box below!
1. Do you have any suggestions for a more intuitive name for this measure instead of Timelag? Perhaps 'Recency'?
2. How many and which arrears categories should be used?
-
Would it be useful to capture arrears of more than 1 year, e.g., more than two years in arrears?
3. How many updates should be required to qualify for each category?
-
Do you agree with the number of updates needed per category? If not, how would you change them?
-
Should a publisher get credit for having data one month in arrears when they have achieved this in only 2 of the past 3 months or should 3 months be required?
4. Do you have any suggestions on how this measure could be visualised?
5. Should publishers get credit for publishing transactions with a transaction value of 0?
Webinar
For each discussion, the IATI Secretariat will organise a webinar to explain the proposed methodology, answer questions and further explain how to engage.
- Please find an overview of the most frequently asked questions of the Timeliness and Validation webinar here.
- Missed the DQI Webinar on Data Completeness held on March 30? Watch the recordings here or read the summaryhere!
Thanks very much for your comments, Yohanna, and again - a sincere apology for the delay in reponse here due to a technical error on my part. I am flagging for my colleagues Amy Silcock and Sarah McDuff your comments so that they can provide an appropriate response. Thank you!