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.
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.
 |
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+2
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 25 June 2008, 17:26 GMT+2
Opened by Raymond Dalgleish (rwmd) - Thursday, 05 June 2008, 14:21 GMT+2
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 25 June 2008, 17:26 GMT+2
|
DetailsThere 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
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 :)