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#32 - Hide genes in an installation

Attached to Project: LOVD 2.0
Opened by Raymond Dalgleish (rwmd) - Wednesday, 25 June 2008, 09:43 GMT+1
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Tuesday, 18 August 2009, 16:20 GMT+1
Task Type Feature Request
Category Backend / Core → Setup area
Status Closed
Assigned To No-one
Operating System All
Severity High
Priority Normal
Reported Version 2.0-07
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


My LOVD installation has mutation information for four genes and I\'m about to add a fifth. At present, the entire installation is hidden from the public at server level because the data are only complete for one of the four current genes. It would be nice to open up the installation to the public, but hide the genes for which the data are still being entered. The logical place to control this would a check box on the \"LOVD Configuration - Manage Gene\" page for each individual gene.
This task depends upon

Closed by  Ivo F.A.C. Fokkema (ifokkema)
Tuesday, 18 August 2009, 16:20 GMT+1
Reason for closing:  Won't implement
Additional comments about closing:  After discussions we have decided not to add this option. New genes should appear on the website immediately. The HGVS recommendation is to, even before you start, to notify the HGVS, tell about your planned effort and ask them to put the database on the HGVS LSDB list. The purpose of this is to prevent that duplicates emerge. In this light
there is no reason to hide an LSDB under construction, in fact it is