Flyspray:: Thu, 21 Feb 2013 15:26:52 +0100 Flyspray::LOVD 2.0: Recently opened tasks FS#57: Unescaped ampersands in XML output Adam Webb Tue, 03 Jul 2012 17:43:24 +0200
Example gene feed:


Dr. Johan T. den Dunnen

Sue Povey & Rosemary Ekong


name:Tuberous sclerosis 2

The ampersand in root>entry>contributor>name should be escaped. Unescaped ampersands can defeat XML parsers :(]]>
FS#56: ability to import multi-gene variants for high throughput tests Ammar Husami Wed, 16 May 2012 20:48:40 +0200 Description of the problem: the current filed of genetic testing is moving from single gene testing to multi gene testing where handful of gene variants are reported at once. The current LOVD submission scheme is limited to uploading single gene variants. Thus if I have variants for 50 samples for 24 genes, the most efficient way is to create variant import file for each gene adding considerable time to the submission process while it is technically possible to do in one step
solution: add subsection to /config_import.php to identify gene and separate variant tables based on gene symbol allowing import of multiple genes from one file
FS#55: Variants reported as uncurated Raymond Dalgleish Fri, 20 Apr 2012 15:09:03 +0200
I suggest that the Uncurated Quicklink be replaced by Quicklinks for 'Submitted', 'Non-public' and 'Marked'. This would improve the usability of LOVD.]]>
FS#54: NoCurrDB at HCI-LOVD Russell Bell Sat, 31 Mar 2012 03:34:20 +0200 and are having the following trouble with the installation:

when Im on a the gene home page,
,and select type, or simple or advanced
the next page is the select gene database
which will send me back to a gene home page depending on which I select

another behavior:
If I go to a gene page and select Unique sequence variants it will take me to

but if I click on Hide Specific Columns I get this error:
Error: NoCurrDB (Logged)
Currently, no gene was selected or sent, but the currdb class has been initiated. This is a in LOVD or in one of it's modules.
Debug: /views_columns.php?action=view_all&hide=true

any ideas would be greatly appreciated
FS#53: Editing the list of available detection techniques Raymond Dalgleish Fri, 24 Feb 2012 14:56:48 +0100
'In new LOVD installations, the following columns are now on the variant side: "Detection/Template", "Detection/Technique", "Detection/Tissue".'

I have just created a new installation of LOVD 2.0 and find that I cannot edit the contents of the "Detection/Technique" column now that it's "Variant/Detection/Technique" using the box at the bottom of 'LOVD Setup - Systems settings' page. Of course, the list of techniques can still be edited using the column data type wizard, but the box which was formerly used for editing the list now seems to be non-functional and redundant.
FS#52: Support for Google Analytics Raymond Dalgleish Thu, 06 Oct 2011 16:07:21 +0200
Would it be possible to provide direct support for Google Analytics by providing a box into which the tracking code could be pasted by the database curator. Some thought might need to be given for the situation where a single shared-installation hosts genes which need to be tracked individually because these genes belong to different curators. A single-installation wide solution is not the answer, but neither is one which does it gene by gene.]]>
FS#51: Link to exon table during variant submission Raymond Dalgleish Wed, 31 Aug 2011 15:09:02 +0200 FS#50: Display patient number on Status page Raymond Dalgleish Tue, 23 Aug 2011 10:10:30 +0200 FS#49: Locking out new submitters temporarily Raymond Dalgleish Thu, 07 Jul 2011 14:22:34 +0200
Ideally, I would like the submitter to be automatically presented with the "How to" document which I send out manually to new submitters. Submitters would hopefully read these guidance notes and would have to tick a check-box to indicate that they'd done so before being allowed to submit data. This type of solution probably needs to wait for version 3.

In the meantime, version 2 could be modified so that new submitters are temporarily locked out from submitting data until approved by the database manager. That would give me time to intervene and send guidance notes to potential submitters.]]>
FS#48: Reply-To header for submitter registrations Raymond Dalgleish Thu, 07 Jul 2011 14:07:01 +0200