{"id":968,"date":"2010-08-05T21:28:21","date_gmt":"2010-08-05T15:58:21","guid":{"rendered":"http:\/\/www.prasadgupte.com\/go\/?p=968"},"modified":"2014-01-12T17:57:43","modified_gmt":"2014-01-12T12:27:43","slug":"converting-csvexcel-data-to-doctrine-yaml-fixtures","status":"publish","type":"post","link":"https:\/\/www.prasadgupte.com\/blog\/converting-csvexcel-data-to-doctrine-yaml-fixtures\/","title":{"rendered":"Converting CSV\/Excel data to Doctrine YAML fixtures"},"content":{"rendered":"

I had done some research on this topic and found that some script was available in Python. With no knowledge of Python execution, I sought help from stackoverflow & got the answer there pointed to the same Python script \ud83d\ude41 I decided I had to do something on my own! Ensuring the right no of spaces in the YAML could be a real pain – I haven’t found the error messages to be very friendly.<\/p>\n

My challenge was to be able to generate a YAML for a table\/schema using the nested-set behaviour in Doctrine. Instead of losing my mind on devising a human-readable format, I reverse engineered. I checked the resulting schema in the database and used that as the base for my CSV. Following this I wrote a simple macro that will output in the required format. This has evolved over a week or so, and has been thoroughly tested. I am sharing this file with 2 examples: one for the JobeetJob schema & other from the Hierarchical Data page on Doctrine.<\/p>\n

Let me know if this helps! Vote for the answer on StackOverflow<\/a>.<\/p>\n

To start using:<\/strong><\/h2>\n
    \n
  1. Download the ZIP file CSV\/Excel to YAML Generator v2<\/a> <\/em>& unzip <\/em>it.
    \n<\/em><\/li>\n
  2. Change the model name<\/li>\n
  3. If you need an explicit ‘NestedSet: true<\/em>‘ declaration, then set NestedSet?<\/em> cell to ‘Y<\/strong>‘ or ‘true<\/strong>‘<\/li>\n
  4. If you wish to add any PHP scripts at the beginning and end of data, you can paste it in the respective cells. I often use this to loop for a number of tenants.<\/em><\/li>\n
  5. Specify the sheet where you want the output to the generated.
    \nIf an invalid or empty sheet name is specified, data is printed to the “Output” sheet. Hence, do not delete it.<\/li>\n
  6. Replace the column names for your model, starting from the 3rd column.<\/li>\n
  7. Start entering your data<\/li>\n
  8. Please don’t forget the 2 ‘end<\/strong>‘ markers to mark the end of columns & rows.<\/li>\n
  9. Press the ‘Generate<\/strong>‘ button<\/li>\n
  10. Copy the data and paste it into the fixtures.yml<\/em> file<\/li>\n<\/ol>\n

    Additional information:<\/strong><\/h2>\n
      \n
    1. 1st column (level) denotes the level in the nested-set. When using for flat structures, set level = 0<\/strong> (zero) for all records.<\/li>\n
    2. 2nd column is the key, that you define for every record in the fixture. This is not saved \ud83d\ude42<\/li>\n
    3. Again, please don’t forget the 2 ‘end<\/strong>‘ markers to mark the end of columns & rows.<\/li>\n
    4. If you need to convert data for more than one model, simply ‘Copy’ the worksheet. As long as it caries the ‘Generate<\/strong>‘ button, the macro will intelligently output the data.<\/li>\n
    5. After you press the ‘Generate<\/strong>‘ button, existing data is first deleted – so don’t take the extra pain.<\/li>\n
    6. Data types are not handled in any way! So if your column is formatted as a date in some non-standard format, the macro will print it as is \ud83d\ude41<\/li>\n
    7. To enter dates, you might need an extra tick to escape the first one. So ”2004-10-09′ will output ‘2004-10-09’<\/li>\n<\/ol>\n

      Roadmap:<\/strong><\/h2>\n