{
  "id": 68789,
  "title": "New data preparation",
  "url": "/competitions/ga-customer-revenue-prediction/discussion/68789",
  "author_name": "",
  "post_date": "2018-10-17T07:47:59.748495700Z",
  "votes": 3,
  "comment_count": 2,
  "views": 0,
  "content": "<p>Dear Kaggle team,</p>\n\n<p>As I understand you are busy with preparing new train set now. I would like to ask you to ensure you are using the same procedure for entire train set and not combining currently available data with new ones, which probably created using other script (I am just trying to avoid one more drama in this competition, not teaching how to do your work)</p>\n\n<p>In case you decide to create new procedure, maybe it is a good idea to include more fields that can be relevant in this competition? </p>\n\n<p>For example, part of 'totals' section was removed as it highly correlate to the target. In updated competition future sessions are unknown and cannot leak the target. \nCan we have all fields from 'totals'? For example, totals.timeOnSite, totals.transactions.\nAlso I believe info about products viewed and purchased can be useful too.</p>\n\n<p>P.S. Can you also check that new data will contain all session purchases and not only last one?</p>",
  "messages": [
    {
      "id": "405298",
      "postDate": "10/17/2018 07:47:59",
      "content": "<p>Dear Kaggle team,</p>\n\n<p>As I understand you are busy with preparing new train set now. I would like to ask you to ensure you are using the same procedure for entire train set and not combining currently available data with new ones, which probably created using other script (I am just trying to avoid one more drama in this competition, not teaching how to do your work)</p>\n\n<p>In case you decide to create new procedure, maybe it is a good idea to include more fields that can be relevant in this competition? </p>\n\n<p>For example, part of 'totals' section was removed as it highly correlate to the target. In updated competition future sessions are unknown and cannot leak the target. \nCan we have all fields from 'totals'? For example, totals.timeOnSite, totals.transactions.\nAlso I believe info about products viewed and purchased can be useful too.</p>\n\n<p>P.S. Can you also check that new data will contain all session purchases and not only last one?</p>",
      "rawMarkdown": "Dear Kaggle team,\n\nAs I understand you are busy with preparing new train set now. I would like to ask you to ensure you are using the same procedure for entire train set and not combining currently available data with new ones, which probably created using other script (I am just trying to avoid one more drama in this competition, not teaching how to do your work)\n\nIn case you decide to create new procedure, maybe it is a good idea to include more fields that can be relevant in this competition? \n\nFor example, part of 'totals' section was removed as it highly correlate to the target. In updated competition future sessions are unknown and cannot leak the target. \nCan we have all fields from 'totals'? For example, totals.timeOnSite, totals.transactions.\nAlso I believe info about products viewed and purchased can be useful too.\n\nP.S. Can you also check that new data will contain all session purchases and not only last one?",
      "votes": null
    },
    {
      "id": "405335",
      "postDate": "10/17/2018 08:58:11",
      "content": "<p>As <a href=\"/tpthegreat\">@tpthegreat</a> <a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/68786#405324\">mentioned</a>, people may use demo account to get more fields than available in demo account. So maybe include them all to competition data? </p>",
      "rawMarkdown": "As @tpthegreat [mentioned][1], people may use demo account to get more fields than available in demo account. So maybe include them all to competition data? \n\n\n  [1]: https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/68786#405324",
      "votes": null
    },
    {
      "id": "405339",
      "postDate": "10/17/2018 09:09:52",
      "content": "<p>Seconded, espatially  my web scraping skills are already rusty.</p>",
      "rawMarkdown": "Seconded, espatially  my web scraping skills are already rusty.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 405335,
      "author_name": "alexfir",
      "author_url": "",
      "post_date": "10/17/2018 08:58:11",
      "content": "<p>As <a href=\"/tpthegreat\">@tpthegreat</a> <a href=\"https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/68786#405324\">mentioned</a>, people may use demo account to get more fields than available in demo account. So maybe include them all to competition data? </p>",
      "votes": null,
      "replies": [
        {
          "id": 405339,
          "author_name": "marcuslin",
          "author_url": "",
          "post_date": "10/17/2018 09:09:52",
          "content": "<p>Seconded, espatially  my web scraping skills are already rusty.</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "405298": "Dear Kaggle team,\n\nAs I understand you are busy with preparing new train set now. I would like to ask you to ensure you are using the same procedure for entire train set and not combining currently available data with new ones, which probably created using other script (I am just trying to avoid one more drama in this competition, not teaching how to do your work)\n\nIn case you decide to create new procedure, maybe it is a good idea to include more fields that can be relevant in this competition? \n\nFor example, part of 'totals' section was removed as it highly correlate to the target. In updated competition future sessions are unknown and cannot leak the target. \nCan we have all fields from 'totals'? For example, totals.timeOnSite, totals.transactions.\nAlso I believe info about products viewed and purchased can be useful too.\n\nP.S. Can you also check that new data will contain all session purchases and not only last one?",
    "405335": "As @tpthegreat [mentioned][1], people may use demo account to get more fields than available in demo account. So maybe include them all to competition data? \n\n\n  [1]: https://www.kaggle.com/c/ga-customer-revenue-prediction/discussion/68786#405324",
    "405339": "Seconded, espatially  my web scraping skills are already rusty."
  },
  "source": "meta"
}