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#49 - Locking out new submitters temporarily

Attached to Project: LOVD 2.0
Opened by Raymond Dalgleish (rwmd) - Thursday, 07 July 2011, 14:22 GMT+1
Task Type Feature Request
Category Backend / Core
Status Assigned
Assigned To Ivo F.A.C. Fokkema (ifokkema)
Operating System All
Severity Low
Priority Normal
Reported Version 2.0-31
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


I sometimes have a problem whereby a person registers as a submitter and goes ahead and submits data without understanding what they doing. I recently had such a submitter who entered a single patient with six dominant disease-causing variants, any one of which would have been sufficient to cause the disease in question. The problem is that there is no mechanism, at present, to prevent this.

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.
This task depends upon