Hi Andy (cc-ed the public jalview-dev list for posterity) We are wrestling with Jalview's Ensembl abstraction and wondering whether the struggle is worth it. We currently provide two Ensembl 'data sources' - Ensembl and EnsemblGenomes - and are also having to do some additional work to resolve the EnsemblFungi/etc Division based cross-references that Uniprot serve.
>From a UX perspective it is (IMHO) preferable to have a single 'Ensembl' >datasource for resolution of any identifier, but because there are separate >endpoints, under the hood we still need to distinguish identifiers for >divisions held at EnsemblGenomes. I seem to remember you mentioning that there was a plan that once ES-Ensembl was up and running, EnsemblGenomes would probably disappear (or just proxy to the same endpoint as Ensembl). Is that still going to be the case ? If yes, and it is going to happen in the next year, then that might help us decide the most appropriate technical solution here. Jim. PS. It just occured to me that the only reason Uniprot holds division-specific Ensembl identifiers is that it allows the Uniprot web site to provide web-links to the different division front-ends. I guess that reason is good enough for Jalview to do the same - but the multiple end-point discussion still stands ;) -- ------------------------------------------------------------------- Dr JB Procter, Jalview Coordinator, The Barton Group Division of Computational Biology, School of Life Sciences University of Dundee, Dundee DD1 5EH, UK. +44 1382 388734 | www.jalview.org<http://www.jalview.org> | www.compbio.dundee.ac.uk<http://www.compbio.dundee.ac.uk> The University of Dundee is a registered Scottish Charity, No: SC015096
_______________________________________________ Jalview-dev mailing list [email protected] http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev
