Sorry, your CSV did not pass validation. Please review the errors and warnings below:
Total Rows Processed = 100Download Standardised CSV
Context problem: Incorrect content type
Your CSV file is being delivered with an incorrect
We recommend that you configure your server to deliver CSV files with a
Content-Type header of
Structural problem: Missing Columns on row 66
titles01/tt0057012,tt0057012,Dr. Seltsam\, oder wie ich lernte\, die Bombe zu lieben (1964),dr seltsam oder wie ich lernte die bombe zu lieben,http://www.imdb.com/title/tt0057012/,8.6,263157,5700,1964,video.movie,13,4,56,432,782,2,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0
Row 66 contains a different number of columns to the first row in the CSV file.
This may indicate a problem with the data, e.g. an incorrectly escaped value, or that you are mixing together different tables of information.
Dialect: Non standard dialect
Although your CSV validates, to make it as easy as possible for your data to be reused, we recommend using commas as delimiters, double quotes to enclose fields, and autodetecting line endings.
Structural problem: Possible title row detected
Your CSV seems to contain unstructured text at the beginning of the file.
It is important that your CSV only contains structured data - any background information or metadata should be included on a referring web page or accompanying document.
Structural problem: Non-standard Line Breaks on row 1
Your CSV appears to use
LF line-breaks. While this will be fine in most cases, RFC 4180 specifies that
CSV files should use
CR-LF (a carriage-return and line-feed pair, e.g.
\r\n). This may be labelled as "Windows line endings" on some systems.
Publish and transform your data using DataGraft, either as enhanced CSV or Linked Data.