{
  "id": 132630,
  "title": "Coaches who share a name?",
  "url": "/competitions/google-cloud-ncaa-march-madness-2020-division-1-mens-tournament/discussion/132630",
  "author_name": "",
  "post_date": "2020-02-27T01:00:36.734985500Z",
  "votes": 2,
  "comment_count": 2,
  "views": 0,
  "content": "<p>I haven't fully inspected TeamCoaches.csv but what is the process for handling coaches who share a first and last name? It may not have happened yet but it's a possibility.</p>\n\n<p>To put the question more technically: Should our scripts assume the possibility of duplicate values in 'CoachName' column of TeamCoaches.csv, where these duplicate values are actually associated with different coaches and not just the same coach listed multiple times</p>",
  "messages": [
    {
      "id": "757631",
      "postDate": "02/27/2020 01:00:36",
      "content": "<p>I haven't fully inspected TeamCoaches.csv but what is the process for handling coaches who share a first and last name? It may not have happened yet but it's a possibility.</p>\n\n<p>To put the question more technically: Should our scripts assume the possibility of duplicate values in 'CoachName' column of TeamCoaches.csv, where these duplicate values are actually associated with different coaches and not just the same coach listed multiple times</p>",
      "rawMarkdown": "I haven't fully inspected TeamCoaches.csv but what is the process for handling coaches who share a first and last name? It may not have happened yet but it's a possibility.\n\nTo put the question more technically: Should our scripts assume the possibility of duplicate values in 'CoachName' column of TeamCoaches.csv, where these duplicate values are actually associated with different coaches and not just the same coach listed multiple times",
      "votes": null
    },
    {
      "id": "757672",
      "postDate": "02/27/2020 02:30:01",
      "content": "<p>I wasn't real thorough with it but I didn't see any. I just assumed it didn't happen - probably a poor assumption on my part. </p>",
      "rawMarkdown": "I wasn't real thorough with it but I didn't see any. I just assumed it didn't happen - probably a poor assumption on my part.",
      "votes": null
    },
    {
      "id": "757678",
      "postDate": "02/27/2020 02:34:06",
      "content": "<p>Edit - Argh - it encodes underlines in what I first wrote.  So in the following paragraph, where you see hyphens, like between john and thompson, I really mean underscores.</p>\n\n<p>There should not be two coaches who share the same CoachName value.  If there were two different coaches that might normally have the same name, such as famous Georgetown coach John Thompson and his son, then I made sure to have something in there to distinguish them - in this case one of them is john-thompson-jr and one is john-thompson-iii .  Or as another example, I noticed that there were two different Jeff Jones coaches, and so I investigated and decided to name one of them jeff-a-jones and the other jeff-jones.  So yes, you should be able to trust that each name string uniquely identifies one exact person, and that person would have the same name throughout the file.  So even if there were a year where there was only one John Thompson coaching, he would still be in there consistently as either john-thompson-jr or john-thompson-iii</p>",
      "rawMarkdown": "Edit - Argh - it encodes underlines in what I first wrote.  So in the following paragraph, where you see hyphens, like between john and thompson, I really mean underscores.\n\nThere should not be two coaches who share the same CoachName value.  If there were two different coaches that might normally have the same name, such as famous Georgetown coach John Thompson and his son, then I made sure to have something in there to distinguish them - in this case one of them is john-thompson-jr and one is john-thompson-iii .  Or as another example, I noticed that there were two different Jeff Jones coaches, and so I investigated and decided to name one of them jeff-a-jones and the other jeff-jones.  So yes, you should be able to trust that each name string uniquely identifies one exact person, and that person would have the same name throughout the file.  So even if there were a year where there was only one John Thompson coaching, he would still be in there consistently as either john-thompson-jr or john-thompson-iii",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 757672,
      "author_name": "btesch",
      "author_url": "",
      "post_date": "02/27/2020 02:30:01",
      "content": "<p>I wasn't real thorough with it but I didn't see any. I just assumed it didn't happen - probably a poor assumption on my part. </p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 757678,
      "author_name": "jeffsonas",
      "author_url": "",
      "post_date": "02/27/2020 02:34:06",
      "content": "<p>Edit - Argh - it encodes underlines in what I first wrote.  So in the following paragraph, where you see hyphens, like between john and thompson, I really mean underscores.</p>\n\n<p>There should not be two coaches who share the same CoachName value.  If there were two different coaches that might normally have the same name, such as famous Georgetown coach John Thompson and his son, then I made sure to have something in there to distinguish them - in this case one of them is john-thompson-jr and one is john-thompson-iii .  Or as another example, I noticed that there were two different Jeff Jones coaches, and so I investigated and decided to name one of them jeff-a-jones and the other jeff-jones.  So yes, you should be able to trust that each name string uniquely identifies one exact person, and that person would have the same name throughout the file.  So even if there were a year where there was only one John Thompson coaching, he would still be in there consistently as either john-thompson-jr or john-thompson-iii</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "757631": "I haven't fully inspected TeamCoaches.csv but what is the process for handling coaches who share a first and last name? It may not have happened yet but it's a possibility.\n\nTo put the question more technically: Should our scripts assume the possibility of duplicate values in 'CoachName' column of TeamCoaches.csv, where these duplicate values are actually associated with different coaches and not just the same coach listed multiple times",
    "757672": "I wasn't real thorough with it but I didn't see any. I just assumed it didn't happen - probably a poor assumption on my part.",
    "757678": "Edit - Argh - it encodes underlines in what I first wrote.  So in the following paragraph, where you see hyphens, like between john and thompson, I really mean underscores.\n\nThere should not be two coaches who share the same CoachName value.  If there were two different coaches that might normally have the same name, such as famous Georgetown coach John Thompson and his son, then I made sure to have something in there to distinguish them - in this case one of them is john-thompson-jr and one is john-thompson-iii .  Or as another example, I noticed that there were two different Jeff Jones coaches, and so I investigated and decided to name one of them jeff-a-jones and the other jeff-jones.  So yes, you should be able to trust that each name string uniquely identifies one exact person, and that person would have the same name throughout the file.  So even if there were a year where there was only one John Thompson coaching, he would still be in there consistently as either john-thompson-jr or john-thompson-iii"
  },
  "source": "meta"
}