Update LCS-EN-indicator.sps #204
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ValerioGiuffrida
requested changes
Oct 17, 2025
| *** Reminder: this is an example of four stress, three crisis and three emergency strategies. You need to replace with the strategies selected for your assessment | ||
|
|
||
| * this variable counts the strategies with valid (i.e. non missing) values - normally it should be equal to 10 for all respondents. | ||
| COMPUTE temp_nonmiss_number=NVALID(LcsEN_stress_DomAsset, LcsEN_stress_Utilities , LcsEN_stress_Saving , LcsEN_stress_BorrowCash , LcsEN_crisis_ProdAssets , + |
There was a problem hiding this comment.
Suggest to maintain the missing variable counts as part of the data quality procedure
Comment on lines
+46
to
+50
| *** Harmonize Data Quality Guidance measures | ||
| *** Check individual strategies. Check for missing values or non-standard values. Check for high usage of N/A. It is recommended to check this by enumerator. If this is the case, refer to the Data Quality Guidance | ||
|
|
||
| * COPING behaviour | ||
| FREQUENCIES LcsEN_stress_DomAsset LcsEN_stress_Utilities LcsEN_stress_Saving LcsEN_stress_BorrowCash LcsEN_crisis_ProdAssets LcsEN_crisis_Health | ||
| LcsEN_crisis_OutSchool LcsEN_em_ResAsset LcsEN_em_Begged LcsEN_em_IllegalAct. |
There was a problem hiding this comment.
Suggest to include in data quality step / statistical cleaning / logical cleaning
Comment on lines
+60
to
+97
| COMPUTE Crisis_coping_EN = 0. | ||
| IF (LcsEN_crisis_ProdAssets = 20 OR LcsEN_crisis_ProdAssets = 30 OR LcsEN_crisis_Health = 20 OR LcsEN_crisis_Health = 30 OR LcsEN_crisis_OutSchool = 20 OR LcsEN_crisis_OutSchool = 30) Crisis_coping_EN = 3. | ||
| EXECUTE. | ||
|
|
||
| DELETE VARIABLES temp_nonmiss_number. | ||
| COMPUTE Emergency_coping_EN = 0. | ||
| IF (LcsEN_em_ResAsset = 20 OR LcsEN_em_ResAsset = 30 OR LcsEN_em_Begged = 20 OR LcsEN_em_Begged = 30 OR LcsEN_em_IllegalAct = 20 OR LcsEN_em_IllegalAct = 30) Emergency_coping_EN = 4. | ||
| EXECUTE. | ||
|
|
||
| * tabulate results. | ||
| FREQUENCIES Max_coping_behaviourEN. | ||
| *** Add variable labels | ||
|
|
||
| VARIABLE LABELS Stress_coping_EN "Did the HH engage in stress coping strategies?". | ||
| VALUE LABELS Stress_coping_EN | ||
| 0 'No' | ||
| 2 'Yes'. | ||
|
|
||
| *----------------------------------------------------------------------------------------------------------------------------------------------------------------* | ||
| VARIABLE LABELS Crisis_coping_EN "Did the HH engage in crisis coping strategies?". | ||
| VALUE LABELS Crisis_coping_EN | ||
| 0 'No' | ||
| 3 'Yes'. | ||
|
|
||
| * ANALYSE THE REAONS WHY STRATEGIES ARE ADOPTED | ||
| VARIABLE LABELS Emergency_coping_EN "Did the HH engage in emergency coping strategies". | ||
| VALUE LABELS Emergency_coping_EN | ||
| 0 'No' | ||
| 4 'Yes'. | ||
| EXECUTE. | ||
|
|
||
| *----------------------------------------------------------------------------------------------------------------------------------------------------------------* | ||
| * The final question included in the LCS-EN module asks the main reasons why coping strategies were adopted (LhCSIEnAccess). | ||
| *Depending on the format you download the data sets and the import options you select the format of the variable could be different. | ||
| *In general, it is recommend downloading with the multiple response split into seperate columns (i.e. variables) with 1/0. | ||
| *The rest of the syntax assumes that the variable LhCSIEnAccess was exported in this way. | ||
| *** For CARI, we use the highest coping strategy applied by the HH. If no coping is used, recode to 1 | ||
|
|
||
| COMPUTE Max_coping_behaviourEN = 0. | ||
| COMPUTE Max_coping_behaviourEN = MAX(Stress_coping_EN, Crisis_coping_EN, Emergency_coping_EN). | ||
| RECODE Max_coping_behaviourEN (0=1). | ||
| VARIABLE LABELS Max_coping_behaviourEN "Which coping strategy was the highest applied by the household?". | ||
| VALUE LABELS Max_coping_behaviourEN | ||
| 1 'Household did not apply coping strategies' | ||
| 2 'Household applied stress coping strategies' | ||
| 3 'Household applied crisis coping strategies' | ||
| 4 'Household applied emergency coping strategies'. | ||
| EXECUTE. |
There was a problem hiding this comment.
As per the other LCS script, I don't find this approach very intuitive.
I believe it could be prone to misinterpretation of the computed variables (e.g.: Emergency_coping_EN assumes value 0 and 4)
Comment on lines
+144
to
+155
| *** Optional: Compute the same variable to be used directly for IPC analysis (referring to IPC phases) - can only be done with the LCS FS indicator, never LCS EN | ||
| IF (LhCSIEnAccess1=0 & NOT SYSMIS(Max_coping_behaviourFS)) Max_coping_behaviourFS=1. | ||
| COMPUTE Max_coping_behaviourFS_IPC = Max_coping_behaviourFS. | ||
| VARIABLE LABELS Max_coping_behaviourFS_IPC "Official IPC Classification for LCS". | ||
| VALUE LABELS Max_coping_behaviourFS_IPC | ||
| 1 "LCSI [none] - IPC Phase 1" | ||
| 2 "LCSI [stress] - IPC Phase 2" | ||
| 3 "LCSI [crisis] - IPC Phase 3" | ||
| 4 "LCSI [emergency] - IPC Phase 4-5". | ||
| EXECUTE. | ||
| VARIABLE LABELS Max_coping_behaviourFS "Summary of asset depletion (converted from EN to FS)". | ||
| *** Check distribution of final categories |
There was a problem hiding this comment.
Suggest to move to an IPC dedicated script
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.