{"action":"created","issue":{"url":"https://api.github.com/repos/fedspendingtransparency/USASpending-Issue-Tracker/issues/70","labels_url":"https://api.github.com/repos/fedspendingtransparency/USASpending-Issue-Tracker/issues/70/labels{/name}","comments_url":"https://api.github.com/repos/fedspendingtransparency/USASpending-Issue-Tracker/issues/70/comments","events_url":"https://api.github.com/repos/fedspendingtransparency/USASpending-Issue-Tracker/issues/70/events","html_url":"https://github.com/fedspendingtransparency/USASpending-Issue-Tracker/issues/70","id":89011907,"number":70,"title":"TSV files no longer have different separator for row and column; SSIS does not allow this.","user":{"login":"JohnEFreeman","id":12041978,"avatar_url":"https://avatars.githubusercontent.com/u/12041978?v=3","gravatar_id":"","url":"https://api.github.com/users/JohnEFreeman","html_url":"https://github.com/JohnEFreeman","followers_url":"https://api.github.com/users/JohnEFreeman/followers","following_url":"https://api.github.com/users/JohnEFreeman/following{/other_user}","gists_url":"https://api.github.com/users/JohnEFreeman/gists{/gist_id}","starred_url":"https://api.github.com/users/JohnEFreeman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JohnEFreeman/subscriptions","organizations_url":"https://api.github.com/users/JohnEFreeman/orgs","repos_url":"https://api.github.com/users/JohnEFreeman/repos","events_url":"https://api.github.com/users/JohnEFreeman/events{/privacy}","received_events_url":"https://api.github.com/users/JohnEFreeman/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-06-17T13:07:18Z","updated_at":"2015-06-17T17:00:00Z","closed_at":null,"body":"TSV FULL Archive files  use a TAB x09 for both column delimiter and row delimiter. This is a change from previous TSV files.  When using a TAB to separate columns, you should use a different separator for rows such as CR-LF (as was the case in the past).  This allows for control of rows even if one row is missing a TAB or has an extra TAB.  Products like SSIS, which I am using, does not allow the same separator for both columns and rows, so I am effectively dead in the water using .tsv files.\r\n\r\nFortunately, a sample of CSV files shows that they do maintain the distinction between column separator (',') and row separator (CR-LF).  So I will download all of the files using csv versions.  TSV in the current archive format is not useful to me anymore.  \r\n\r\nWhat do other people think?  Are current tsv files of use to you?"},"comment":{"url":"https://api.github.com/repos/fedspendingtransparency/USASpending-Issue-Tracker/issues/comments/112877274","html_url":"https://github.com/fedspendingtransparency/USASpending-Issue-Tracker/issues/70#issuecomment-112877274","issue_url":"https://api.github.com/repos/fedspendingtransparency/USASpending-Issue-Tracker/issues/70","id":112877274,"user":{"login":"USAspendingalice","id":11790090,"avatar_url":"https://avatars.githubusercontent.com/u/11790090?v=3","gravatar_id":"","url":"https://api.github.com/users/USAspendingalice","html_url":"https://github.com/USAspendingalice","followers_url":"https://api.github.com/users/USAspendingalice/followers","following_url":"https://api.github.com/users/USAspendingalice/following{/other_user}","gists_url":"https://api.github.com/users/USAspendingalice/gists{/gist_id}","starred_url":"https://api.github.com/users/USAspendingalice/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/USAspendingalice/subscriptions","organizations_url":"https://api.github.com/users/USAspendingalice/orgs","repos_url":"https://api.github.com/users/USAspendingalice/repos","events_url":"https://api.github.com/users/USAspendingalice/events{/privacy}","received_events_url":"https://api.github.com/users/USAspendingalice/received_events","type":"User","site_admin":false},"created_at":"2015-06-17T17:00:00Z","updated_at":"2015-06-17T17:00:00Z","body":"@JohnEFreeman Quick question from the Tech Team -- did this issue occur with the June TSV files? Are you able to use the May TSV files? "}}