>Contributing Data>Example Uploads>Maize-pigeon pea farms in Myanmar

Maize-pigeon pea farms in Myanmar

Dataset

The Food Security Policy Project surveyed 935 farms in the southern Shan region of Myanmar in June-October 2018. These farms cultivated maize and/or pigeon peas often using intercropping. Data were captured by interviewing farmers and asking them to recall information about the prior production cycle(s). Data were stored in an Excel spreadsheet after removing personally identifying information such as coordinates.

Conversion steps

  • We added a new row in the Excel sheet below the existing column headers. In this row, we added field names from the schema.
  • We restructured the dataset so each row represents one Cycle. Cycles where maize and pigeon peas were intercropped had two Products.
  • The surveyed farms had already been given a unique identifier, and we used these for site.id and cycle.id. We then linked cycles to the sites they occurred on using cycle.site.id.
  • Added new columns for the data Source, and added bibliographic information to it. Set this as the defaultSource for all Cycles and Sites.
  • Added the required fields for Cycles and Sites which were not included in the original spreadsheet. Specifically, we added endDate and functionalUnit to the Cycle, and country.name and siteType to the Site.
  • Added a new column called site.region.name and matched each of the townships surveyed with the most specific geographical region in the HESTIA Glossary.
  • For each Input and Product, converted the units to those defined in the HESTIA glossary (e.g., kilograms), and then expressed them per functional unit defined by the schema (here 1 ha).
  • Requested new Terms were added to the Glossary to allow better representation of the data (e.g., Family labour, and Hired labour).
  • Added columns for the data Completeness assessment and filled them in based on the rules defined at the schema.
  • Initially we set dataPrivate to true for all nodes, so we could check the data first without it becoming public. When we were ready to share the data publicly, we reuploaded with dataPrivate set to false .

Validation

The upload pipeline detected fields and terms had typos in which we corrected. A full stop symbol (.) was mistakenly used to mark data as not available, and we changed this to a dash (-) which represents no data in HESTIA along with blank cells.

Downloads

Help us improve. Send us a message