The tsv headers are difficult to work with, because they're so long. Do we need them to be this long? We could code descriptions into the app, for display purposes.
The trouble with them now is that we have to write code like this:
row["'Citations or URLs for clinical significance without database identifiers"]
Note there are two spaces between "for" and "clinical". That cost me about half an hour.
At minimum, I think we should map spaces to underscores. Then we can map it back to spaces in the Detail display. Better would be to use short identifiers, and add a table of descriptions for use in the Detail display.
based on this discussion with Brian:
The tsv headers are difficult to work with, because they're so long. Do we need them to be this long? We could code descriptions into the app, for display purposes.
The trouble with them now is that we have to write code like this:
row["'Citations or URLs for clinical significance without database identifiers"]
Note there are two spaces between "for" and "clinical". That cost me about half an hour.
At minimum, I think we should map spaces to underscores. Then we can map it back to spaces in the Detail display. Better would be to use short identifiers, and add a table of descriptions for use in the Detail display.