Expectation of metadata from Data Prep to be stored in database.

[grosscol]

Issue or current state

Appears as though the design was to store the enumeration of observed values for: filter, lost of function, and consequence emitted from the data preparation pipeline as metadata in the database. Per comment:

bravo_api/bravo_api/models/variants.py

Lines 350 to 356 in 9e43f4b

	def get_snv_filters():
	# this should be stored somewhere in database and generated during the data import step
	return {
	'filter': filter_values,
	'lof': lof_values,
	'consequence': consequence_values
	}

These are currently hard coded lists. e.g:

bravo_api/bravo_api/models/variants.py

Lines 41 to 46 in 9e43f4b

	filter_values = [
	{ 'value': 'PASS' },
	{ 'value': 'SVM' },
	{ 'value': 'DISC' },
	{ 'value': 'EXHET'}
	]

Resolved when

• Corresponding issue created for Data Prep project.
• Issue or implementation exists for retrieving the metadata from the databse backend.