anchor.diff:  Use the following OSGi command to start the import process:
   
   --------------------------
  -osgi> sctimport rf2_release -l <languageRefSetId> -t <type> [-b <branch>] <file>
  ---------------------------
  -
  -<languageRefSetId>:: The language reference set identifier to use, selected from the list available identifiers in the
  +osgi> sctimport rf2_release -l <languageRefSetId> -t <type> -b <branch> -cv true <file>
  +--------------------------
  +
  +-l <languageRefSetId>:: The language reference set identifier to use, selected from the list available identifiers in the
   previous step
  -<type>:: One of `FULL`, `SNAPSHOT` or `DELTA`, depending on the import type the administrator wants to use
  -<branch>:: The existing branch to import the content onto. Optional. When omitted, content will be imported to the MAIN branch
  +-t <type>:: One of `FULL`, `SNAPSHOT` or `DELTA`, depending on the import type the administrator wants to use
  +-b <branch>:: The existing branch to import the content onto. Use 'MAIN' for the MAIN branch.
  +-cv <true|false>\t\tShould versions be created for each effective time found in the release.
   <file>:: The absolute path of the release archive file to import, +
   `{import_zip_directory}/SnomedCT_Release_XXX_xxxxxxxx.zip`
   
  
positive.code: |SNOMED CT reference set import from delimiter-separated file (includes RF1 subset files)
  |`sctimport dsv_refset`
  |✔
  |✔
  
  |Value domain import from Excel spreadsheet
  
negative.code: 
  --------------------------
  osgi> sctimport rf2_release -l 900000000000509007 -t FULL /opt/SnomedCT_Release_INT_20130131.zip
  --------------------------
  
  === Importing a national extension
  National extension can be imported onto any existing base version of the international release.
  
  Use the following OSGi command to start the extension import process:
  
  --------------------------
  osgi> sctimport rf2_release -l <languageRefSetId> -t <type> -bv <base int. version tag> -cv <true|false> <international_release_archive_file> <extension_metadata_file_path>
  --------------------------
  
  <extension_metadata_file_path>\t\tPath to the metadata file describing the extension.
  
  -l <languageRefSetId>:: The language reference set identifier to use, selected from the list available identifiers in the
  previous step.
  -t <type>:: One of `FULL`, `SNAPSHOT` or `DELTA`, depending on the import type the administrator wants to use
  -bv <base int. version tag>:: The existing international version to import the extension onto. For example: '2016-01-01'.
  -cv <true|false>\t\tShould versions be created for each effective time found in the release. False is recommended for extension imports.
  <international_release_archive_file>:: The absolute path of the release archive file to import, +
  `{import_zip_directory}/SnomedCT_Release_XXX_xxxxxxxx.zip`
  <extension_metadata_file_path>:: The extension terminology meta-data file
  
  Where the meta data file contains properties in key-value format:
  
  
   name = XYZ National Extension
   shortname = XYZ
   OID = 123
   language = la
   maintaining_org_link = 
   icon_path = 
   citation = This is short description of the extension
  
  An example for the Danish extension:
  
  --------------------------
  osgi> sctimport rf2_extension -l 554461000005103 -t FULL -bv MAIN/2016-01-31 -cv false /SnomedCT_Release_DK1000005_20160215.zip /dk_extension.properties
  --------------------------
  
  == Single administrator operations
  