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: 
  --------------------------
  osgi> sctimport rf2_release -l 900000000000509007 -t FULL /opt/SnomedCT_Release_INT_20130131.zip
  --------------------------
  
  == Single administrator operations
  
negative.code: |SNOMED CT reference set import from delimiter-separated file (includes RF1 subset files)
  |`sctimport dsv_refset`
  |✔
  |✔
  
  |SNOMED CT extension import from RF2 files
  |`sctimport rf2_extension`
  |
  |✔
  
  |Value domain import from Excel spreadsheet
  