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#28 - Cannot update \"DNA change\" field

Attached to Project: LOVD 2.0
Opened by Raymond Dalgleish (rwmd) - Thursday, 05 June 2008, 14:21 GMT+1
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 25 June 2008, 17:26 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-08
Due Date 2008-06-27
Percent Complete 100%
Votes 0
Private No


There have been a number of recent changes to the ShowMaxDBID which have yielded improvements. However, I think that there may be an unintended side-effect of these changes which is apparent in version 2.0 build 07, but which is not present in build 05 (I cannot comment on build 06).

In build 05, I can make changes in the \"DNA change\" field to, say, correct an error that I did not notice when first entering the data. This works exactly as expected. However, in build 07, such as change generates an error message of the form \"The given variant ID \"COL1A1_00003\" does not match the variant \"c.64G>A\". It appears that the ShowMaxDBID module is treating the change as a new variant and expecting a new variant ID to be assigned, even though it\'s a correction that\'s being made. I hope that this is a bug, not a feature.
This task depends upon

Closed by  Ivo F.A.C. Fokkema (ifokkema)
Friday, 27 June 2008, 16:33 GMT+1
Reason for closing:  Fixed
Comment by Ivo F.A.C. Fokkema (ifokkema) - Friday, 06 June 2008, 15:02 GMT+1
Whether this is a bug or a feature depends... if you have just one entry that you need to correct, I would agree that this is a bug. However, if there are three variant entries and you\'re correcting one, there will be created a situation where one DB-ID will be shared with different DNA changes. How will LOVD know whether or not you are going to edit the other two also?

To edit multiple variants all in once and bypass the DB-ID check, use the Find & Replace functionality from the Configuration area. This will \"solve\" your problem for now, until I have worked out a fix :)