config.xml

<?xml version="1.0" encoding="ISO-8859-1" ?>
<!--

  NB: because study and sites elements get merged in a recursive and
  overwriting manner, any time when multiple elements of the same type
  (such as <item/> <item/>) occurs in the study or sites tree, the
  sites tree will overwrite the element entirely instead of simply
  merging - i.e., if the multiple elements are branches, the sites
  branch in its entirely will override the study branch.
-->
<config>
    <include>lorisDB.xml</include>
    <!-- set to 1 if development environment -->
    <dev>
        <sandbox>1</sandbox>
    </dev>

    <!-- MINC TOOLS PATH -->
    <MINCToolsPath>/opt/minc/</MINCToolsPath>


    <!-- study variables -->
    <study>
        <PSCID>
            <!-- PSCID (Study Center ID) generation method possible options: sequential/random/user -->
            <generation>random</generation>
            <structure>
                <seq type="siteAbbrev"/>
                <seq type="numeric" length="3" min='100' max='999'/> <!-- Ex: AAA1-->
            </structure>
        </PSCID>
        
        <ExternalID>
            <generation>random</generation>
            <structure>
                <seq type="siteAbbrev"/>
                <seq type="numeric" length="3" min='100' max='999'/>
            </structure>
        </ExternalID>
        <!--Header table is diplayed on top of instrument list page and instrument pages -->
        <HeaderTable>
            <!--Specify the table as the tag and the field to query as the value inside the tag -->
            <parameter_candidate>candidate_comment</parameter_candidate>
            <candidate>ProbandDoB</candidate>
            <parameter_session>MRI_Done</parameter_session>
        </HeaderTable>
        <!-- defines how visit labels are assigned -->
        <visitLabel subprojectID="1">
            <!-- generation can have either 'user' or 'sequence' to denote user entered or a pre-defined sequence -->
            <generation>sequence</generation>
            <regex>/^[A-Z0-9]{2}$/i</regex>
            <length>2</length>
            <suggest>V%value%</suggest> <!-- %value% will be substituted for the next unique number -->
            <labelSet>
                <item value="V1">V1</item>
                <item value="V2">V2</item>
                <item value="V3">V3</item>
            </labelSet>
        </visitLabel>
        <visitLabel subprojectID="2">
            <!-- generation can have either 'user' or 'sequence' to denote user entered or a pre-defined sequence -->
            <generation>sequence</generation>
        <regex>/^[A-Z0-9]{2}$/i</regex>
        <length>2</length>
        <suggest>V%value%</suggest> <!-- %value% will be substituted for the next unique number -->
        <labelSet>
            <item value="V1">V1</item>
            <item value="V2">V2</item>
            <item value="V3">V3</item>
        </labelSet>
        </visitLabel>
        <visitLabel subprojectID="3">
            <!-- generation can have either 'user' or 'sequence' to denote user entered or a pre-defined sequence -->
            <generation>sequence</generation>
            <regex>/^[A-Z0-9]{2}$/i</regex>
            <length>2</length>
            <suggest>V%value%</suggest> <!-- %value% will be substituted for the next unique number -->
            <labelSet>
                <item value="V3">V3</item>
                <item value="V4">V4</item>
                <item value="V5">V5</item>
                <item value="V6">V6</item>
            </labelSet>
        </visitLabel>
        <visitLabel subprojectID="4">
            <!-- generation can have either 'user' or 'sequence' to denote user entered or a pre-defined sequence -->
            <generation>sequence</generation>
            <regex>/^[A-Z0-9]{2}$/i</regex>
            <length>2</length>
            <suggest>V%value%</suggest> <!-- %value% will be substituted for the next unique number -->
            <labelSet>
                <item value="V3">V3</item>
                <item value="V4">V4</item>
                <item value="V5">V5</item>
                <item value="V6">V6</item>
            </labelSet>
        </visitLabel>
        <!-- Instruments for reliability module -->
        <ReliabilityInstruments>
            <Instrument>
                <Testname>bmi</Testname>
                <Threshold>0.5</Threshold>
                <Displayname>BMI</Displayname>
            </Instrument>

        </ReliabilityInstruments>

         <!-- certification module -->
        <Certification>
            <EnableCertification>1</EnableCertification>
            <CertificationProjects>
                <!-- add project for which certification module should be enabled-->
                <CertificationProject>1</CertificationProject>
                <CertificationProject>2</CertificationProject>
                <CertificationProject>3</CertificationProject>
            </CertificationProjects>

            <CertificationInstruments>
                <test value="bmi">BMI</test>
                <test value="radiology_review">Radiology Review</test>
            </CertificationInstruments>
        </Certification>
        <!--This permission allows users from sites to have access to other sites bvl feedback info -->
        <multiSiteEnabledCenters>0</multiSiteEnabledCenters>

    </study>
    <!-- end of study definition -->

    <gui>
        <showDatabaseQueries>0</showDatabaseQueries>
    </gui>

    <!-- used by _hasAccess in NDB_BVL_Instrument to determine
         what permissions should be required for each instrument
         on a configurable basis. -->
    <instrumentPermissions>
        <!-- By default anyone has permission -->
        <useInstrumentPermissions>false</useInstrumentPermissions>
        <!-- Add one instrument tag for each instrument that is
             having it's permissions configured. If an instrument
             is missing, the default is for users to have access
             -->
        <instrument>
            <!-- Instrument name -->
            <Test_name>sampleInstrument</Test_name>
            <!-- Permission required for accessing instrument.
                 If multiple permissions are added, *any* of
                 them individually will allow access to the
                 instrument -->
            <permission>sampleInstrumentPermissionName</permission>
        </instrument>
        <instrument>
            <Test_name>sampleInstrument2</Test_name>
            <permission>sampleInstrument2PermissionName</permission>
        </instrument>
    </instrumentPermissions>

</config>