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#11 - Allow submission of variant without patient data
Attached to Project:
LOVD 2.0
Opened by Mark Catalano (mark) - Friday, 01 December 2006, 16:29 GMT+2
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 06 December 2006, 11:21 GMT+2
Opened by Mark Catalano (mark) - Friday, 01 December 2006, 16:29 GMT+2
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 06 December 2006, 11:21 GMT+2
|
DetailsOne of the ways I would like to implement LOVD is to managed a reference variant database. This type of database would not hold patient data, but would act as a repository of variant data. Not requiring Patient data during the submission process would make using LOVD in this way possible.
|
This task depends upon
Closed by Ivo F.A.C. Fokkema (ifokkema)
Wednesday, 06 December 2006, 11:26 GMT+2
Reason for closing: Won't implement
Additional comments about closing: This is regarded not important enough to implement, at least for now. I may want to add that most likely this can be accomplished by a somewhat experienced developer by accessing the MySQL database directly, and dropping the HGVS standard patient columns. Then you can hide or remove the rest. You probably don\'t even need a change in de code, as long as there is at least one patient field.
In short: we won\'t implement this, but you can accomplish it yourself. Feel free to contact me if you need more information.
Wednesday, 06 December 2006, 11:26 GMT+2
Reason for closing: Won't implement
Additional comments about closing: This is regarded not important enough to implement, at least for now. I may want to add that most likely this can be accomplished by a somewhat experienced developer by accessing the MySQL database directly, and dropping the HGVS standard patient columns. Then you can hide or remove the rest. You probably don\'t even need a change in de code, as long as there is at least one patient field.
In short: we won\'t implement this, but you can accomplish it yourself. Feel free to contact me if you need more information.