Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Add a 'switch' functionality to change between mines #21
added a commit
Jul 17, 2018
@yochannah @rachellyne Hi, I've made a quick test by changing the browser to work with FlyMine instead with HumanMine, and I've found that the following concepts, that work in HumanMine, don't exist in FlyMine ontology:
Gene.alleles.type + Gene.alleles.clinicalSignifance (Used for ClinVar filter)
Am I doing something wrong or indeed that filters are not applicable for FlyMine, for instance? The rest is working smoothly.
Actually, we were talking about this recently at the meeting! I think I remember you saying in the past that you were thinking of having json config for mine settings, is that right? We were thinking something along the lines of:
Does that make sense?
Yes, those are both examples that are specific to HumanMine. I am struggling to know how this can be made generic as the data are just different between mines - that's the nature of biological data. I think it would be better to make it more mine specific.
@yochannah @rachellyne I think that for the moment, we can handle this by using the defensive approach, and instead of having the filter layout defined beforehand, use jQuery to dinamically add the filters during page load, checking if for the current mine, all the required fields exist. When the mine is switched, remove all the filters and reconstruct again. Only for those that are not GO annotation, dataset, organism and pathway.
Is there a way to check if a certain concept exists in a mine by querying the service, apart from catching that the response is a error code? For instance check if Genes.alleles.type exist?