Modifying client routes for data validation

[im-prakher]

The goal of this issue is to implement data validation for shapefiles, spreadsheets before API data ingestion by modifying existing API routes functionality.

BETYdb-YABA/app/Meta.py

Lines 52 to 72 in 64b540e

	try:
	user_id=fetch_id(username, table='users')
	if not user_id:
	return 401
	#Reading the CSV file into DataFrame
	data = pd.read_csv(fileName,delimiter = ',')
	#Checking necessary columns are there.
	columns=data.columns.values.tolist()
	accepted_columns=['name','start_date','end_date','description','design']
	if(all(x in accepted_columns for x in columns)):
	data['user_id']=user_id
	data['design'].fillna('some text', inplace=True)
	insert_table(table='experiments',data=data)
	msg = {'Message' : 'Successfully inserted',
	'Table Affected' : 'Experiments',
	'Lines Inserted': data.shape[0]}
	return make_response(jsonify(msg), 201)

#

Like, the code in this function responds to /yaba/v1/experiments (for inserting experiments in the BETY database), we can modify this, by accepting one more parameter as status(which can be true or false), if false then return a valid response after validating data otherwise continue with data insertion. In this example, we can check the status after line 64, if true we can return a response from there only and stop further execution otherwise continue with data insertion.

if(all(x in accepted_columns for x in columns)):
>> if(status == false)
>>>> msg = {'Message' : true }
>>>> return make_response(jsonify(msg), 200)

So, what do you say?
@dlebauer @KristinaRiemer @saurabh1969 @Chris-Schnaufer

[saurabh1969]

Can you elaborate about status parameter?

[im-prakher]

It will be a Boolean. A false value indicates that data should be only validated and a response should be returned accordingly, while a true value tells us that data should also be inserted.

[im-prakher]

Done in #69