{
  "id": 484002,
  "title": "The record date in the train_tax_registry_table_a is always later than the decision date",
  "url": "/competitions/home-credit-credit-risk-model-stability/discussion/484002",
  "author_name": "",
  "post_date": "2024-03-15T03:35:58.777982Z",
  "votes": null,
  "comment_count": 1,
  "views": 0,
  "content": "<p>Hi, I have a question is that since the data is used for application scoring. I have seen that the record date in the train_tax_registry_table_a is always later than the decision date? This means that the info won't be available at the time of the scoring. How would the table be useful? or it's just that the data has been transformed and the true date is actual before the decision date so I can continue to use it in my model without any issues?<br>\nYou don't have to disclose the transformations, just a yes/no is suffice thank you.</p>",
  "messages": [
    {
      "id": "2697636",
      "postDate": "03/15/2024 03:35:58",
      "content": "<p>Hi, I have a question is that since the data is used for application scoring. I have seen that the record date in the train_tax_registry_table_a is always later than the decision date? This means that the info won't be available at the time of the scoring. How would the table be useful? or it's just that the data has been transformed and the true date is actual before the decision date so I can continue to use it in my model without any issues?<br>\nYou don't have to disclose the transformations, just a yes/no is suffice thank you.</p>",
      "rawMarkdown": "Hi, I have a question is that since the data is used for application scoring. I have seen that the record date in the train_tax_registry_table_a is always later than the decision date? This means that the info won't be available at the time of the scoring. How would the table be useful? or it's just that the data has been transformed and the true date is actual before the decision date so I can continue to use it in my model without any issues?\nYou don't have to disclose the transformations, just a yes/no is suffice thank you.",
      "votes": null
    },
    {
      "id": "2698213",
      "postDate": "03/15/2024 10:54:39",
      "content": "<p>Hi, have you seen <a href=\"https://www.kaggle.com/competitions/home-credit-credit-risk-model-stability/discussion/472866#2649736\" target=\"_blank\">https://www.kaggle.com/competitions/home-credit-credit-risk-model-stability/discussion/472866#2649736</a>?</p>",
      "rawMarkdown": "Hi, have you seen https://www.kaggle.com/competitions/home-credit-credit-risk-model-stability/discussion/472866#2649736?",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 2698213,
      "author_name": "dimakoshman",
      "author_url": "",
      "post_date": "03/15/2024 10:54:39",
      "content": "<p>Hi, have you seen <a href=\"https://www.kaggle.com/competitions/home-credit-credit-risk-model-stability/discussion/472866#2649736\" target=\"_blank\">https://www.kaggle.com/competitions/home-credit-credit-risk-model-stability/discussion/472866#2649736</a>?</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "2697636": "Hi, I have a question is that since the data is used for application scoring. I have seen that the record date in the train_tax_registry_table_a is always later than the decision date? This means that the info won't be available at the time of the scoring. How would the table be useful? or it's just that the data has been transformed and the true date is actual before the decision date so I can continue to use it in my model without any issues?\nYou don't have to disclose the transformations, just a yes/no is suffice thank you.",
    "2698213": "Hi, have you seen https://www.kaggle.com/competitions/home-credit-credit-risk-model-stability/discussion/472866#2649736?"
  },
  "source": "meta"
}