LOVD v.3.0 - Leiden Open Variation Database
Online gene-centered collection and display of DNA variants
LOVD 3.0 News
|Introducing a new API that allows you to check and correct your HGVS syntax
||Ivo Fokkema, 2022-09-19|
|We have released a new API,
hosting a service that allows you to check whether your variant descriptions follow the HGVS nomenclature for the description of DNA variants.
While this service does not validate the variant on the sequence level like other available services such as Mutalyzer and VariantValidator,
our API does provide several advantages over those services.
The release of this API will allow developers to use this service and integrate it into their software.
In addition, we will soon release a web page using the same service, allowing non-developers to use our new tool as well.
Our service validates the variant description only on a syntax level and not on the sequence level.
This allows you to submit variant descriptions without reference sequences, and it enables us to support more variant types than all other available services combined.
For instance, variants with uncertain positions, e.g., NC_000017.10:g.(41228632_41234420)_(41234593_41242960)dup,
aren't supported in other tools as they cannot easily be validated on the sequence level.
Our API does correctly interpret and validate this variant description, and checks whether the HGVS nomenclature has been applied correctly.
Our service focuses on providing constructive errors and warnings in case the variant description does not conform to the HGVS nomenclature guidelines.
E.g., the variant mentioned above, when input in the Mutalyzer syntax checker,
results in the error message "Expected "del" (at char 34), (line:1, col:35)",
which doesn't provide you with relevant information - that this service does not support the given variant description.
Our service attempts to correct variant descriptions that do not follow the HGVS guidelines.
We have analyzed hundreds of thousands of variant descriptions to learn what errors are commonly made and how we can automatically correct them.
Corrections are annotated with a 3-tier confidence score, showing the certainty that the modification represents what the user intended to write.
Give the API a try through the Swagger interface, or see the documentation on the GitHub page.
The development of this API was part of a project between LOVD developer Ivo Fokkema and Bioinformatics student Loes Werkman, who obtained her degree with her work on this project.
|LOVD 3.0 build 28 released
||Ivo Fokkema, 2022-07-18|
|Today, LOVD 3.0 build 28 has been released.
New features implemented, amongst others:
Allow passing the classification method to the submission API using the pathogenicity's @source value;
Improved variant recognition functions;
Enabled the "Your submissions" link that was defined but not enabled;
Added a /diseases/[OMIMID] redirect.
Bugs fixed, amongst others:
Applied several fixes to the LOVD2-style API;
Several internal XSS issues were fixed, adding protection against stored XSS;
Fixed warning shown when editing somebody else's data;
Fixed several PHP warnings and notices throughout the code;
Fixed LOVD for PHP8;
Fixed multiple-selection lists display issue on Windows browsers;
Fixed link to LRGs;
Fixed several issues in our Variant Validator library.
Closes #548, #566, #568, #570, #571, #583, #590, #591 and #599.
See the changelog.
Download the new build.
LOVD scripts included: LOVD2 file converter 3.0-22, Reading Frame Checker 3.0-22, RefSeqParser 3.0-22, Variant position fixer 3.0-20, Variant Validation 3.0-25.
Manual version included: June 15th, 2021.
News older than 12 months can be found in the archive.
|Last modified 2022/09/20 10:49:00 CEST
When using or discussing LOVD please refer to:
Fokkema IF, Kroon M, López Hernández JA, Asscheman D, Lugtenburg I, Hoogenboom J, den Dunnen JT.
The LOVD3 platform: efficient genome-wide sharing of genetic variants.
Eur J Hum Genet (2021).