LOVD 2.0

Welcome to the LOVD 2.0 bug tracking system. Please note that this bug tracking system is not for LOVD 3.0!

If you have any issues, please read the documentation and Frequently Asked Questions.
Please note that you need to register before you can submit bugs or feature requests.

Information By default, all closed tasks are hidden from view.
Click here to see all tasks.


FS#27 - Incorrect DB-ID can often not be fixed

Attached to Project: LOVD 2.0
Opened by Ivo F.A.C. Fokkema (ifokkema) - Tuesday, 13 May 2008, 17:26 GMT+1
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Monday, 19 May 2008, 14:44 GMT+1
Task Type Bug Report
Category Backend / Core → Variant submission
Status Closed
Assigned To Ivo F.A.C. Fokkema (ifokkema)
Operating System All
Severity Medium
Priority Normal
Reported Version 2.0-06
Due in Version 2.0-07
Due Date 2008-05-30
Percent Complete 100%
Votes 0
Private No


When a certain DNA change has ended up with two different DB-ID values, of which the lower value is incorrect, LOVD 2.0-06 does not allow you to change the value to the higher (correct) value, only to the lower value.
Also, if you have a incorrect value that you want to change to a new correct value that has not been used yet, this is also impossible.

It should be implemented in a more intelligent way. Users should be allowed to pick any ID that matches the DNA variant, or assign the variant to any free DB-ID. This will also solve  FS#26 .
This task depends upon

View Dependency Graph

This task blocks these from closing
 FS#26 - Cannot use DBID out of sequence 
Closed by  Ivo F.A.C. Fokkema (ifokkema)
Friday, 30 May 2008, 13:57 GMT+1
Reason for closing:  Fixed