Configuration

Katmandoo can be configured by modifying following:

• .config File
• Sub-system
• System Column
• Virtual Column
• Reserved Keywords

IMPORTANT NOTE: ONLY THE SYSTEM ADMINISTRATION WITH ADVANCED KNOWLEDGE OF CONFIGURATION FILE SHOULD MAKE THE CHANGES IN THE .CONFIG FILE.
 
Configuration file (Katmandoo.exe.config) is stores setting and configuration information. It is an XML file that is used by the executable file (Katmandoo.exe) to obtain the customisation information. It has following sections:

• appSettings: This section is used for the system level customisation. Example:
  
         <!-- StartupForm -->
       <add key="MaxNoOfFormsToOpen" value="6" />
       <add key="MaxNoOfStatusBarMsg" value="32" />
             
       <!-- max number of records that will be returns when quick search is used! Changed to 100 (hundred only) on 29Dec06/Avi -->
       <add key="MaxQuickSearchReturn" value="256" />
   
• connectionStrings: This section stores the connection strings that are used to connect external data source (SQL Server Database, Excel File, CSV File and XML File). Example:
  
      <add name="SQLServer" connectionString="data Source=(Local)\KatmandooMSDE;uid=sa;pwd=sa;" providerName="System.Data.SqlClient" />
      <add name="AdminSQLServer" connectionString="data Source=(Local)\KatmandooMSDE;uid=sa;pwd=sa;" providerName="System.Data.SqlClient" />
      <!-- XL - see connectionSettingsReader for detail  -->
      <add name="XLExport" connectionString="Provider=Microsoft.Jet.OLEDB.4.0;data Source=FileNameWithCompletePath;Extended Properties='Excel 8.0;HDR=YES;IMEX=0';" />
      <add name="XLImport" connectionString="Provider=Microsoft.Jet.OLEDB.4.0;data Source=FileNameWithCompletePath;Extended Properties='Excel 8.0;HDR=YES;IMEX=1;ImportMixedTypes=Text';" />
   
• externalAppSettings: This section has the template file names that are cloned to export data from the system. Example: 
  
        <add key="XLDataEntryTemplateFileName" value="XLDataEntryTemplate_v2.1.0802.02.xls" />
      <add key="XLReportingTemplateFileName" value="XLReportingTemplate_v2.1.0802.02.xls" />
      <add key="XLTrialDesignMapTemplateFileName" value="XLTrialDesignMapTemplate_v2.1.0802.01.XLS" />
   
• codeToDatabaseMappings: This section is used to map the value used in the code with the value in the database. Example:
  
        <!-- An UNKNOWN contact name -->
      <add key="UnknownContactLastName" value="UNKNOWN" />
      <add key="UnknownContactFirstName" value="xxxx" />
  
      <!-- An Unknown location acronym -->
      <add key="UnknownLocationAcronym" value="UNKN0" />
  
      <!-- An UNKNOWN met station name -->
      <add key="UnknownMetStationName" value="UNKNOWN METEOROLOGY STATION" />
     
      <!-- An UNKNOWN sample supplier / seed source -->
      <add key="UnknownOrganisationName" value="UNKNOWN ORGANISATION" />

Katmandoo can be customised to shadow System Column using KSCMN (Katmandoo System Column Mapping Name) ie while exporting and importing data, Katmandoo will use the Alias of the System Column prefixed as "KSCMN_".

Use [ Record > Update System Column Alias ] in the System Column Main Form. Then just add an alias with KSCMN_ prefixed (ie to shadow SampleEntryNumber as PlotNo, add KSCMN_PlotNo alias). Then save it.

When you export data, you will see PlotNo as the column heading instead of SampleEntryNumber.

DDL Script can be used to safely make following changes in database to customised Katmandoo.

1. Alternate key for Trial Type can be changed to Trial Type Name + Sub-system Id. Katmandoo is designed to handle this alternate key as well as just Trial Type Name as Alternate Key.
   
   DROP index dbo.TrialType.AlternateKey
   GO
   CREATE unique index AlternateKey on dbo.TrialType (TrialTypeName, SubSystemId) ON 'PRIMARY'
   GO
2. Weight column in TrialMean table can be changed to allow Null.
   
   ALTER table dbo.TrialMean alter column Weight decimal(16, 6) null