Checklist: Microdata Catalog submission
Get printable version here. For more detailed instructions on Sections 1 and 2 of this checklist, see Data Cleaning and De-identification. For more information on Microdata Catalogs, see Microdata Catalog. Note that this checklist is best displayed in Chrome, Firefox, Safari or any other modern browser.
Project name: _______________________________________ | |||
---|---|---|---|
Country: ___________________________________________ | |||
District: ____________________________________________ | |||
Year, Month and/or Day: _____________________________ | |||
1. Data Cleaning | |||
Initials | #No | Checklist Item | |
[ __ ] | 1.1 | Does the ID variable uniquely identify observations? | |
[ __ ] | 1.2 | Are all variables labelled? | |
[ __ ] | 1.3 | Do all factor variables have value labels? | |
[ __ ] | 1.4 | Are all missing values correctly coded and labelled? | |
[ __ ] | 1.5 | Do variable names match the accompanying questionnaire? | |
[ __ ] | 1.6 | Is the ID the first variable listed? | |
[ __ ] | 1.7 | Does the other variables’ order match the accompanying questionnaire? | |
2. De-identification | |||
Initials | #No | Checklist Item | |
[ __ ] | 2.1 | Make sure all personally-identifying information (PII) is removed! If you wish to deposit all variables in the survey for completeness, create de-identified versions of variables containing PII as described below and attach a list of all PII variables that should not be released to you submission | |
[ __ ] | 2.1.1 | DROP names of survey respondent, household members, enumerator, and associated contact information | |
[ __ ] | 2.1.2 | ENCRYPT categorical variables by simply dropping the labels for encoded variables (if string, encode first). This applies to names of schools, village and possibly names of other administrative units (will differ by country and by project) | |
[ __ ] | 2.1.3 | MASK values of GPS coordinates if GPS information is related to the research question. Otherwise, remove GPS variables | |
[ __ ] | 2.2 | If results haven't been published yet, list any variables identifying treatment assignment and flag them as embargoed on the submission form | |
[ __ ] | 2.3 | Remove or embargo any sensitive, potentially identifying information according to survey context. Possible examples include religion and ethnicity. | |
3. Saving Data Set | |||
Initials | #No | Checklist Item | |
[ __ ] | 3.1 | Use the cleaned dataset that does not include constructed variables | |
[ __ ] | 3.2 | Use compress to reduce the file size | |
[ __ ] | 3.3 | Save in the earliest Stata version compatible with your data formats | |
4. Supporting Documents | |||
Initials | #No | Checklist Item | |
[ __ ] | 4.1 | IE Concept Note | |
[ __ ] | 4.2 | Questionnaires | |
[ __ ] | 4.2.1 | Paper format equivalent is better than CTO form | |
[ __ ] | 4.2.2 | Names of villages, schools, health facilities, etc listed as response options should be removed | |
[ __ ] | 4.3 | Enumerator manuals | |
[ __ ] | 4.4 | Field work details: dates on which the field work occurred, total number of households visited, refusal rates, total number of households and individuals included in the final sample, problems that occurred during the administration of the survey (strikes, inclement weather, inability to enter parts of the country) | |
[ __ ] | 4.5 | Data cleaning documentation: | |
[ __ ] | 4.5.1 | Codes for missing in survey and in dataset | |
[ __ ] | 4.5.2 | Record of any corrections made | |
[ __ ] | 4.5.3 | If variables were masked for de-identification, report method used | |
[ __ ] | 4.5.4 | If applicable, describe how to link observations across data files (e.g. through Master Dataset) | |
[ __ ] | 4.6 | Data dictionary and list of datasets included, if applicable | |
[ __ ] | 4.7 | Baseline report, if available | |
[ __ ] | 4.8 | Methodology description | |
[ __ ] | 4.9 | Publications citation | |
5. Submission | |||
Initials | #No | Checklist Item | |
[ __ ] | 5.1 | We recommend publishing data sets as impact evaluation surveys under licensed access | |
[ __ ] | 5.2 | Go to MicroData Library Home Page (http://microdatalib.worldbank.org/) and log in with your UPI and passcode. | |
[ __ ] | 5.3 | Click the link to “Deposit data” and next “Sign in to get started”. | |
[ __ ] | 5.4 | If you are a returning user, all the projects that you have deposited will show up in the list either as “DRAFT” or “PROCESSED”. If you are a first-time user, click “Create New Project” to start with the process. Mandatory fields will be marked with stars. Provide “Title”, “Short name”, one paragraph of “Description” and Collaboration which will the email address of other Bank staff who may be authorized to make future edit and review this project. All the information provided here can be edited later. | |
[ __ ] | 5.5 | Fill each field as much as possible based on project information, which can be found in concept note, baseline report or other project documents. | |
[ __ ] | 5.6 | Load data files and other documents | |
[ __ ] | 5.7 | Review by Team Member: Send the links to project editing page to PIs, project manager, field coordinators and other team members for review and comments before submitting the project. | |
[ __ ] | 5.8 | Review by Data Group: After submitting the project, staff from Development Data Group will review the form and uploaded data files, confirm the successful documentation and access authority, or contact the project creator with further questions. | |
The checklist are edited through Git Hub. This checklist corresponds to the file with the name chk_microdata.js. To read a simple step by step guide on how to edit the checklist, see this documentation: https://github.com/worldbank/DIMEwiki/tree/master/Topics/Checklists. |
Back to Parent
This article is part of the topic Check Lists. It's also related to Microdata Catalog.