Consider URL structure for passing query data from frontend

[ctgraham]

The Multiple Village Download URL is currently structured to concatenate the villages and the topic with underscores as a GET request.

For example:
http://backend.tld/advancesearch/download/1_3_2_economy

Here 1, 2, and 3 are village ids and economy is the topic.

This does not align well with REST principles as it combines different query terms (objects) together.

This might be better represented as:
http://backend.tld/advancesearch/download/1_3_2/economy
or
http://backend.tld/advancesearch/download/1,3,2/economy
or
http://backend.tld/advancesearch/download/?village=1,3,2&term=economy

It might be tempting to pass query data via POST, so that you can hand of a JSON object directly, like:

{
  "village": [1, 2, 3],
  "term": "economy"
}

But a POST request should represent a data-change event, and this limits the ability for effective caching because the query context is removed from the URI.

[ctgraham]

Converted to querystring here:

ccvgd-backend/app_func/villageDetails.py

Lines 854 to 865 in 9e08e87

	@village_blueprint.route("/download/", methods=["GET"], strict_slashes=False)
	def downloadData():
	dir_path = os.getcwd()
	single_dir = os.path.join(dir_path,"app_func","single_csv")
	# print("path is",os.path.join(single_dir, path))
	village_id = request.args.get("village")
	topic = request.args.get("topic", None)
	path = village_id+"_"+topic
	if os.path.exists(os.path.join(single_dir, path)):
	return send_from_directory(single_dir, path, as_attachment=True)
	return jsonify({"code":4003,"message":"File is not exist or file can't download"})