 |
 |
Or ©
The codes are not wrong, but the names are wrong.
The descriptions (definitions) were, in my recollection, the original intended definition.
In my view Code 3 = Closed and Code 4 = Finalisation is a valid bug-fix.
I wasn’t aware of any knees jerking. Should I have been??
Strangely - I can’t see this addition of the ActivityStatus in the 2.01 changelog, nor the original proposals.
There is an indication that this code list might be modified in the color-coded table view for 2.01, but I can’t see where the text is derived from.
At GitHub, we can see that the all changes on this list were undertaken in 2013 & 14.
NB: I’m not trying to “blame” anyone here, but find it interesting in that we can’t pinpoint the exact source of the issue we’re discussing - this is also very important for standards!
Come on Bill. Changing the order of the codes clearly changes their meaning. And for newcomers to IATI, the idea that 4 comes before 3 will only add more confusion.
Do you have a source for this? Because I cannot find the current descriptions in any of the original consultation documents, whereas the codes and names have remained the same since 1.01. @stevieflow, the first time the descriptions appear is in the 2.01 upgrade process, right at the end in iteration 3, so it is not surprising that there was a mistake introduced here (below screenshot is from the linked Google Doc, clearly showing the descriptions did not exist before).
In which case, changing the English-language descriptions (introduced only at 2.01) would clearly also be a valid bug-fix, as it does not involve both re-ordering the codes in an illogical way (so that 4 comes before 3) and changing the English and French names.
So how do we move this forward as a bugfix? What sort of signoff do we need? What’s the protocol here?
Is there some documentation of process that you can refer us to, @bill_anderson?
Bringing this back up after the summer break.
I see this is now listed as part of a potential integer upgrade:
“[Fix Activity Status Mix Up 2] (agreement reached, but solution changes the meaning of the code and is therefore not backward compatible)”
I disagree with the statement that the solution changes the meaning of the code. Bill, you stated that clarifying the names was a bug-fix. Hence, correcting the descriptions cannot require an integer upgrade, it’s simply fixing a mistake.
Unfortunately the Discuss post listing the potential changes to the standard is not open for discussion, so I cannot put this comment there.
There’s now agreement on resolving this as a bugfix, by swapping the descriptions for codes 3 & 4. Please refer to the following post:
I understand this is now in the job queue but can someone help me understand when this change is going to take place? We have custom scripts written in our accounting system to assign the codes based on dates and system status. We will need to adjust the script when the definitions change.
Kind Regards,
Michelle
Michelle, if you are assigning proper codes to projects, you probably won’t have to change the script. The codes won’t change.
If you were assigning codes based on the definitions instead of the names, then your projects are miscoded & I’d recommend changing the script as soon as possible. No need to wait for the bug to be fixed since the codes are not changing.
We assigned codes based on our understanding of the definitions assigned to the codes. I’m still confused now as to what is going to change.
Can someone confirm if I have this correct?
Currently:
3 - completion - physical activity is complete or the final disbursement has been made
4 - post-completion - same as above BUT the activity remains open pending financial sing off or M&E.
Change will be:
3 - post-completion - physical activity is complete or the final disbursement has been made BUT the activity remains open pending financial sing off or M&E.
4 - completion - physical activity is complete or the final disbursement has been made
That sounds strange to me but I sure wasn’t around when all of this was initially discussed. If 3 (three) is really supposed to be something between implementation and completion then wouldn’t it be better to call it post-implementation rather than post-completion?
Happy to discuss this next week at TAG but we go to publish a new set of data the week after so I’d love to make sure we have our scripts right before that.
Sorry if I’m just making a mess of this but, well, consider me a great example on how newbies get lost in all this documentation.
Kind Regards,
Michelle
Hi Michelle
Ha, that’s where the confusion lies! You misunderstood the issue: the names and definitions are mismatched, not the codes and names.
The change will be:
3 - completion - physical activity is complete or the final disbursement has been made BUT the activity remains open pending financial sign-off or M&E
4 - post-completion - physical activity is complete or the final disbursement has been made
(Sorry, it’s IATI jargon: “completion” describes the state of the activities on the ground, from the point of view of stakeholders / beneficiaries. The project looks like it’s completed on the ground, even though stuff remains to be done on the admin side. “Post-completion” is the real end, nothing remains to tidy up. A project can go from Implementation straight to Post-Completion if everything ends at the same time.
Don’t shoot the messenger, I didn’t come up with these terms 
)
@YohannaLoucheur
Thanks for your patience.
Change will be:
3-Completion = physical activity is complete or the final disbursement has been made BUT the activity remains open pending financial sign off or M&E
4 - post-completion = physical activity is complete or the final disbursement has been made (and no more financial sign off or M&E - all is done, done,done)
I can get my head around that. No need to shoot anyone. On the contrary I may owe you a drink in Kathmandu.
Merci,
Michelle
Before @IATI-techteam implements this can we have final agreement on the wording. We have agreement on the logic (i.e. 3 comes before 4) but there are differing opinions on naming and the description for 4. Can I propose:
3 - Finalisation
Physical activity is complete or the final disbursement has been made, but the activity remains open pending financial sign off or M&E4 - Closed
Physical activity, financial sign-off and/or M&E are complete.
re: the description for 4 - I would assume physical activity and financial sign-off are necessary conditions, but M&E could go on for years after an activity has been closed, right?
Everything including M&E must be finished before the activity is closed. Yes, it can go on for a while (years even).
There’s a logic there: if M&E is not finished, then further expenses are likely (to pay the M&E work) so the activity remains in finalization status.
Dare I suggest that rather than calling it completion and post-completion the order be called
1- pipeline
2 - implementation
3 - post-implementation
4 - completion
Completion, in my head, is that everything is complete and yet that isn’t what we have. We have post-completion which really means the activity itself is physically done but there is paperwork/admin/finance/M&E to do.
Now I have no idea if this is a minor, major or bug or ??? but from a non-tech perspective this makes more sense in terms of descriptions and order of things.
Just a suggestion.
Michelle
I like ‘post-implementation’
We already had ‘finalization’ and ‘closed’ proposed to replace “completion” and “post-completion”. I would prefer that option to avoid entirely the use of "post’ - I’m concerned it could create confusion (given there was already a ‘post’-something).
Also, for the record I want to flag that Michelle’s latest response incorrectly describes 'post-completion". Post-completion is the final stage, when everything is done, NOT the penultimate stage when some admin/M&E remains to be done.
My post was not indicating what “completion” means but rather how it can be so easily confused as completion by normal (non-iati) definitions is that something is complete with nothing more to do. For IATI it only refers to the physical activity being complete but we all know there is “stuff” to do afterwards hence the use of 'post-completion".
The fact that this discussion string is as long as it is,to me, indicates that words and definitions are clear. As a native English speaker, I figure is I can’t figure it out then there are others who will struggle even further.
Whatever words are chosen I suggest we change them soon and expand the definitions well enough to ensure clarity.
Hi @Michelle_IOM,
Both the proposal I made here in April, and the one @bill_anderson made earlier this month remove the word “completion”, so should help avoid the confusion you’re talking about.
Just to restate my proposal (which is slightly different to Bill’s) the codelist would become:
Activity Status Codelist (updated)
| Code | Name (en) | Name (fr) | Description (en) |
|---|---|---|---|
| 1 | Pipeline/identification | Planification | The activity is being scoped or planned |
| 2 | Implementation | Actif | The activity is currently being implemented |
| 3 |
|
Finalisation | Physical activity is complete or the final disbursement has been made, but the activity remains open pending financial sign off or M&E. |
| 4 |
|
Fermé | Physical activity is complete or the final disbursement has been made |
| 5 | Cancelled | Annulé | The activity has been cancelled |
| 6 | Suspended | Suspendu | The activity has been temporarily suspended |
I’ve attempted to highlight the changes above, but just to state explicitly, there are two parts to this change:
A couple of supporting points to mention:
After @bill_anderson’s message prior to the TAG, I thought we’d resolved this issue. However, I see now that perhaps the details were still up in the air. I agree with @Michelle_IOM that it would be great to get this resolved soon.
