[ensembl-dev] differences in vep field types

William McLaren wm2 at ebi.ac.uk
Thu Nov 2 13:37:23 GMT 2017

Hi Michael,

Any fields that can have multiple values should be returned as a list, not a comma-separated string, so I’d say this is a bug in the  old code which has not been comprehensively fixed in the new.

Can you please provide a complete list of those fields you’ve found a problem with? We’ll then get these fixed for release/91.


Will McLaren
Ensembl Variation

On 1 November 2017 at 12:56:13 pm, D'Eletto, Michael (michael.d'eletto at ynhh.org) wrote:

Hi Ensembl team,

I've been using VEP for the past year (release 83) and I'm trying to test / validate the latest VEP version (release 90).  We use the "--json" flag as the method of output, but noticed that the field types changed between release 83 and release 90.  Is this due to changes in the new "vep" script versus the "variant_effect_predictor.pl" script?  Specifically, some fields like "pubmed" and "clin_sig" were converted from arrays / lists to concatenated strings in the latest version, and other fields like "trembl" and "swissprot" were converted from concatenated strings to arrays / lists.  Just curious if this was intentional or a bug.  For example:

"pubmed": [20632448, 21356067]


"pubmed": "20632448,21356067"

Thank you,

Mike D'Eletto

This message originates from the Yale New Haven Health System. The information contained in this message may be privileged and confidential. If you are the intended recipient you must maintain this message in a secure and confidential manner. If you are not the intended recipient, please notify the sender immediately and destroy this message. Thank you. _______________________________________________  
Dev mailing list Dev at ensembl.org  
Posting guidelines and subscribe/unsubscribe info: http://lists.ensembl.org/mailman/listinfo/dev  
Ensembl Blog: http://www.ensembl.info/  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20171102/990c3c9e/attachment.html>

More information about the Dev mailing list