|
LOVD v.2.0 - Leiden Open Variation Database
Online gene-centered collection and display of DNA variants
|
|
|
Please note that LOVD2 is no longer supported. The last security release is from October 2020. Upgrade to LOVD3 to continue receiving updates. |
LOVD Setup
Custom columns
Creating new columns
Using the "Create new custom column" link from the setup area you can create a new variant or patient custom column, which will be inactive unless you explicitly add it to either a variant table or the patient table.
Column name and descriptions
Category: Select if this column is a patient or variant column. You can't change this value later on!
Column ID: Choose a simple unique name for your column, consisting of only letters, numbers and underscores. Subcategories must be divided by a slash (/), such as "Phenotype/Disease". Do NOT add 'Patient/' or 'Variant/' here.
Column heading: This will appear above the column on the variant listings and on the legend. In principle, this is free text, but try to keep it short, because a long name will increase the width of the column.
Description on form: If you think this field may require some explanation on the submission form about what to put in there, you can add a description here.
Description on short legend: Describe the meaning of the column in short. This will appear in the short legend, below the variant tables.
Description on full legend: Describe the meaning of the column. You can be more elaborate here. This text will be shown on the full legend.
Data settings
There are two ways to define the data type of your custom column. The recommended way is to use the data type wizard, which will fill in the MySQL and the form type values. Only if you really know what you're doing, you can edit the MySQL data type and the form type directly.
To use the data type wizard, you first need to select what type of field you want to create for your custom column:
Basic form style: Select what type of field you want to create:
- Text/numeric input field for a standard input field allowing textual or numerical free text input.
- Integer input field for a standard input field allowing only whole numbers.
- Decimal input field for a standard input field allowing only numbers with a certain number of decimals.
- Large multi-row textual input field for a large text field with multiple rows, allowing large amounts of text to be filled in.
- Drop down list (one option selected) for a drop down list with a set of options of which the user must choose one value.
- Selection list (multiple options selected) for a selection list where the user can select one or more options (like the detection technique list).
- Date input field for a standard input field allowing for dates (year, month, day), optionally also storing time (hours, minutes, seconds).
- On/off checkbox for a simple checkbox allowing only a yes/no answer.
The next page shows you some additional options that depend on the type of field you've chosen:
Column name on form (all field types): The name the column will have on the submission form.
Width on form (all input fields and text area): The input field width on the form, in number of characters.
Maximum input length (text and integer input field types): The maximum number of characters allowed the be filled in. If a user tries to enter more characters in your field, an error is issued.
Regular expression pattern (text input only): For advanced users, you can enter a full regular expression pattern (PHP's Perl-compatible regular expression syntax), including the / delimiters and possible modifiers. Using this, you can force a certain format for the input.
Number of digits before the decimal point (decimal field only): The maximum number of digits allowed before the decimal point. This practically limits the maximum value of the field.
Number of digits following the decimal point (decimal field only): The maximum number of digits allowed at the right of the decimal point. This limits the maximum precision of values in the field.
Allow only positive values (integer and decimal fields): Select this to allow only positive whole numbers to be entered.
Also store time (date field only): Select this to also store time (hours, minutes, seconds) in this date field.
Height on form (text area and multiple selection list): The height of your field on the submission form, in lines.
Provide "-- select --" option (drop down list only): Adds a "-- select --" option to the list of options, that will be selected by default. If this option is not set, the first option of the list will be the default selected option.
Provide "select all" link (multiple selection list only): Adds a "select all" link, which allows the user to select all available options in the list with one click of a button.
List of possible options (both list types): Enter the options available for this field, one options per line. If you want to use abbreviations, use: Abbreviation = Long name, like "DMD = Duchenne Muscular Dystrophy".
Default value (all input fields except text area): A default value that will appear in the field for new submissions.
When you click the "Finish" button, the data type wizard will fill in the "MySQL data type" and "Form type" fields for you.
Column settings
Standard for new genes: This controls whether new variant columns that you create will be added to newly created genes by default or not. All variant columns with this option set, will be added to the variant tables of newly created genes.
Mandatory field: With this option selected, users can't leave your column empty.
Show contents to public: With this option selected, only authorized viewers can see the contents of this column.
Show field on public forms: This option controls whether or not submitters can submit a value for this column.
Include in search form: This option controls whether or not this column shows on the special search overview that allows the public to find the number of entries in the database (including hidden entries) matching one or more search terms on a specified set of columns.
Last modified 2014/08/25 14:48:31 CEST |
When using or discussing LOVD please refer to:
Fokkema IF, Taschner PE, Schaafsma GC, Celli J, Laros JF, den Dunnen JT (2011). LOVD v.2.0: the next generation in gene variant databases.
Hum Mutat. 2011 May;32(5):557-63.
|
|