Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase ««12

Data Science Sanity Checks Expand / Collapse
Posted Wednesday, May 15, 2013 2:31 AM

Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Yesterday @ 3:10 PM
Points: 662, Visits: 2,926
The fact is the end users of those data are the domain experts who can tell what is rogue data and what is real trend better than anybody else, including the data scientist who has generic data knowledge but not necessarily the domain knowledge.

I agree that this should be the case, but if it is your experience, then you've been far more fortunate than I have! The data scientist may not have the necessary domain knowledge in some cases but he, or she, knows of all the specialist expertise that can be alerted in order to investigate. It would, I believe, be very wrong to neglect this and just leave it to individual areas of the business to figure it out. The data scientist has to check anyway that the changes in data aren't due to error within IT, and that requires a measure of understanding of the business domain..

Best wishes,

Phil Factor
Simple Talk
Post #1452974
Posted Wednesday, May 15, 2013 9:14 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, June 17, 2013 9:49 AM
Points: 3, Visits: 18
Hi Phil

Thanks for the response. Don't get me wrong, I'm not saying we don't need Data Scientists, and I totally agree that the Data Scientists should do the investigations you described in those circumstances.

I was just a bit reserved about having to put things on hold until the investigation is complete, as the timeliness of some of these information could be crucial for the business. My thinking is along the line of using intelligent tools to help highlighting these anomalies and warn the users to take those data with a pitch of salt (or even allow them to do they own analysis). This way users have the data, but are also warned about the possible flaws. The data scientist could then tell them the result after finishing his investigation.

I think we are more or less on the same page.

Post #1453172
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse