{
  "id": 42953,
  "title": "Did new member data has feature \"expiration_date\" ?",
  "url": "/competitions/kkbox-churn-prediction-challenge/discussion/42953",
  "author_name": "",
  "post_date": "2017-11-07T17:52:12.479000300Z",
  "votes": 1,
  "comment_count": 7,
  "views": 0,
  "content": "<p>There is not a feature called <code>expiration_data</code> in the member_v2.csv.</p>\n\n<p>But the old one it does. Why?</p>",
  "messages": [
    {
      "id": "240952",
      "postDate": "11/07/2017 17:52:12",
      "content": "<p>There is not a feature called <code>expiration_data</code> in the member_v2.csv.</p>\n\n<p>But the old one it does. Why?</p>",
      "rawMarkdown": "There is not a feature called `expiration_data` in the member_v2.csv.\n\nBut the old one it does. Why?",
      "votes": null
    },
    {
      "id": "241575",
      "postDate": "11/09/2017 09:00:14",
      "content": "<p>They removed expiration_date column in member_v2.csv\nNo reasons were stated</p>",
      "rawMarkdown": "They removed expiration_date column in member_v2.csv\nNo reasons were stated",
      "votes": null
    },
    {
      "id": "243897",
      "postDate": "11/15/2017 05:26:23",
      "content": "<p>I think because it's a <strong>future</strong> feature.</p>",
      "rawMarkdown": "I think because it's a **future** feature.",
      "votes": null
    },
    {
      "id": "243929",
      "postDate": "11/15/2017 06:37:41",
      "content": "<p>the expiration date in member.csv is taken as a snapshot of our member table. The field is constantly changing as it is based on user transaction. So the expiration date in member.csv does not reflect user churn behavior. Further, we observed that having the field introduced confusion and controversy. Hence we decided to remove it. </p>",
      "rawMarkdown": "the expiration date in member.csv is taken as a snapshot of our member table. The field is constantly changing as it is based on user transaction. So the expiration date in member.csv does not reflect user churn behavior. Further, we observed that having the field introduced confusion and controversy. Hence we decided to remove it.",
      "votes": null
    },
    {
      "id": "243996",
      "postDate": "11/15/2017 11:31:10",
      "content": "<p>It is in member_V2</p>",
      "rawMarkdown": "It is in member_V2",
      "votes": null
    },
    {
      "id": "247495",
      "postDate": "11/23/2017 07:36:52",
      "content": "<p>Can you return the original member.csv? This creates unequal opportunities for those who, started this competition earlier, and others, who do not have access to that file, even if that field introduced confusion and controversy. </p>",
      "rawMarkdown": "Can you return the original member.csv? This creates unequal opportunities for those who, started this competition earlier, and others, who do not have access to that file, even if that field introduced confusion and controversy.",
      "votes": null
    },
    {
      "id": "249129",
      "postDate": "11/27/2017 19:22:44",
      "content": "<p>So, it is allowed to use that information, or not?</p>",
      "rawMarkdown": "So, it is allowed to use that information, or not?",
      "votes": null
    },
    {
      "id": "255094",
      "postDate": "12/08/2017 09:25:20",
      "content": "<p>Based on post in <a href=\"https://www.kaggle.com/c/kkbox-churn-prediction-challenge/discussion/44363#250087\">https://www.kaggle.com/c/kkbox-churn-prediction-challenge/discussion/44363#250087</a> </p>\n\n<p>I don't think we can use <code>expiration_data</code> in the member.csv.</p>\n\n<p>@admin, can you confirm this statement? </p>",
      "rawMarkdown": "Based on post in https://www.kaggle.com/c/kkbox-churn-prediction-challenge/discussion/44363#250087 \n\nI don't think we can use `expiration_data` in the member.csv.\n\n@admin, can you confirm this statement?",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 241575,
      "author_name": "chiayii",
      "author_url": "",
      "post_date": "11/09/2017 09:00:14",
      "content": "<p>They removed expiration_date column in member_v2.csv\nNo reasons were stated</p>",
      "votes": null,
      "replies": [
        {
          "id": 243929,
          "author_name": "ardenkkbox",
          "author_url": "",
          "post_date": "11/15/2017 06:37:41",
          "content": "<p>the expiration date in member.csv is taken as a snapshot of our member table. The field is constantly changing as it is based on user transaction. So the expiration date in member.csv does not reflect user churn behavior. Further, we observed that having the field introduced confusion and controversy. Hence we decided to remove it. </p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 247495,
          "author_name": "ezherko",
          "author_url": "",
          "post_date": "11/23/2017 07:36:52",
          "content": "<p>Can you return the original member.csv? This creates unequal opportunities for those who, started this competition earlier, and others, who do not have access to that file, even if that field introduced confusion and controversy. </p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 249129,
          "author_name": "aloisiodn",
          "author_url": "",
          "post_date": "11/27/2017 19:22:44",
          "content": "<p>So, it is allowed to use that information, or not?</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 255094,
          "author_name": "soundwaveli00",
          "author_url": "",
          "post_date": "12/08/2017 09:25:20",
          "content": "<p>Based on post in <a href=\"https://www.kaggle.com/c/kkbox-churn-prediction-challenge/discussion/44363#250087\">https://www.kaggle.com/c/kkbox-churn-prediction-challenge/discussion/44363#250087</a> </p>\n\n<p>I don't think we can use <code>expiration_data</code> in the member.csv.</p>\n\n<p>@admin, can you confirm this statement? </p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 243897,
      "author_name": "vasttao",
      "author_url": "",
      "post_date": "11/15/2017 05:26:23",
      "content": "<p>I think because it's a <strong>future</strong> feature.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 243996,
      "author_name": "sandreds",
      "author_url": "",
      "post_date": "11/15/2017 11:31:10",
      "content": "<p>It is in member_V2</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "240952": "There is not a feature called `expiration_data` in the member_v2.csv.\n\nBut the old one it does. Why?",
    "241575": "They removed expiration_date column in member_v2.csv\nNo reasons were stated",
    "243897": "I think because it's a **future** feature.",
    "243929": "the expiration date in member.csv is taken as a snapshot of our member table. The field is constantly changing as it is based on user transaction. So the expiration date in member.csv does not reflect user churn behavior. Further, we observed that having the field introduced confusion and controversy. Hence we decided to remove it.",
    "243996": "It is in member_V2",
    "247495": "Can you return the original member.csv? This creates unequal opportunities for those who, started this competition earlier, and others, who do not have access to that file, even if that field introduced confusion and controversy.",
    "249129": "So, it is allowed to use that information, or not?",
    "255094": "Based on post in https://www.kaggle.com/c/kkbox-churn-prediction-challenge/discussion/44363#250087 \n\nI don't think we can use `expiration_data` in the member.csv.\n\n@admin, can you confirm this statement?"
  },
  "source": "meta"
}