Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Input data validation tool #20

Closed
c-w opened this issue Apr 13, 2018 · 1 comment
Closed

Input data validation tool #20

c-w opened this issue Apr 13, 2018 · 1 comment

Comments

@c-w
Copy link

c-w commented Apr 13, 2018

We recently tried to deploy this solution with a partner, using the sample C# console app client.

We faced several issues massaging the partner's data into the correct format for the SAR service and found the error messages from the service not extremely helpful at tracking down data issues. For example, the input data looks like CSV but doesn't seem to support standard CSV-encoded commas in columns.

As such, it would be super valuable to have a little tool that verifies that the input data is in the correct format for the SAR service so that data issues can be precisely located and fixed instead of trying to run the model and having to wait for a while until the bad data is hit which greatly slows down iteration speed.

@natinimni
Copy link
Contributor

Hi @c-w ,
The project uses .NET's "TextFieldParser" class to parse the input CSV files (see UsageEventsFilesParser for example).

I should be straight forward to create such a validation tool in C# by referencing the Recommendations.Core project and calling the UsageEventsFilesParser class (you might need to change it from being 'internal' to 'public', depending on your implementation).

If you do find a bad pattern use or a way to make the parsing support more standard escaping etc., we would truly appreciate any contributions back to this project!

I hope this helps,
Nati

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants