Thanks for the json file @ypriverol , as I mentioned the other day, this data does not belong to the application configuration domain.
For the software to apply translation / mapping between Ensembl assemblies and UCSC assemblies, the best way to go, for the benefit of the pipeline architecture, is creating a Translation / Mapping service that will show a uniform interface, with a couple of methods at the beginning to map Ensembl -> UCSC and UCSC -> Ensembl, and different implementation strategies, the first of them will provide the mapping services using the content in this json file, that I'll make available via HTTPS.
Thanks for the json file @ypriverol , as I mentioned the other day, this data does not belong to the application configuration domain. For the software to apply translation / mapping between Ensembl assemblies and UCSC assemblies, the best way to go, for the benefit of the pipeline architecture, is creating a Translation / Mapping service that will show a uniform interface, with a couple of methods at the beginning to map Ensembl -> UCSC and UCSC -> Ensembl, and different implementation strategies, the first of them will provide the mapping services using the content in this json file, that I'll make available via HTTPS.
Thanks ^_^ Manuel