anchor.diff:  
   == Importing content from a release archive
   
  -To import a `SnomedCT_Release_XXX_xxxxxxxx.zip` release archive, the file must be present in the Snow Owl Server host
  -file system, which we will refer to as {import_zip_directory}.
  -
  -=== Choosing the language reference set
  -
  -To list the available language reference set identifiers, use the following command:
  -
  ---------------------------
  -osgi> sctimport rf2_languages {import_zip_directory}/SnomedCT_Release_XXX_xxxxxxxx.zip
  -[...]
  -900000000000508004  Great Britain English language reference set
  -900000000000509007  United States of America English language reference set
  ---------------------------
  -
  -Available language reference sets will be displayed as above, after parsing the archive is completed.
  +To import a `SnomedCT_Release_XXX_xxxxxxxx.zip` release archive, the file must be present in the Snow Owl Server host file system, which we will refer to as {import_archive}.
   
   === Starting the import
   
   Use the following OSGi command to start the import process:
   
   --------------------------
  -osgi> sctimport rf2_release -t <type> -b <branch> -v <path to archive file> <path to release descriptor file>
  ---------------------------
  -
  --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. In case of extension import, an effective time from the base SNOMED CT release (e.g. 2016-01-31). If omitted 'MAIN' will be used.
  --v\t\tCreates versions for each effective time found in the release archive. If omitted no versions will be created.
  -<path to archive file>:: Specifies the release archive to import (must be a .zip file with a supported internal structure, such as the release archive of the International Release)., +
  -`{import_zip_directory}/SnomedCT_Release_XXX_xxxxxxxx.zip`
  -<path to release descriptor file>:: The path to the release descriptor json file.
  -
  -Where the release descriptor json file contains the key/values as:
  -
  - {
  -	"name": "Systematized Nomenclature of Medicine Clinical Terms International Version",
  -	"shortName": "SNOMEDCT",
  -	"language": "ENG",
  -	"codeSystemOID": "2.16.840.1.113883.6.96",
  -	"baseCodeSystemOID": "2.16.840.1.113883.6.96",
  -	"maintainingOrganizationLink": "http://www.ihtsdo.org",
  -	"releaseType": "INTERNATIONAL",
  -	"citation": "SNOMED CT contributes to the improvement of patient care by underpinning the development of Electronic Health Records that record clinical information in ways that enable meaning-based retrieval. This provides effective access to information required for decision support and consistent reporting and analysis. Patients benefit from the use of SNOMED CT because it improves the recording of EHR information and facilitates better communication, leading to improvements in the quality of care."
  +osgi> sctimport rf2_release -t <type> -b <branch> -v /path/to/{import_archive} /path/to/{release_descriptor_file}
  +--------------------------
  +
  +-t <type>:: One of `FULL`, `SNAPSHOT` or `DELTA`, depending on the import type the administrator wants to use. The parameter is case-insensitive.
  +-b <branch>:: The existing branch to import the content onto. In case of extension import, an effective time from the base SNOMED CT release (e.g. 2016-01-31). If omitted `MAIN` will be used.
  +-v:: Creates versions for each effective time found in the release archive. If omitted no versions will be created.
  +/path/to/{import_archive}:: Specifies the release archive to import. Must be a `.zip` file with a supported internal structure, such as the release archive of the International Release.
  +/path/to/{release_descriptor_file}:: The path to the release descriptor `.json` file.
  +
  +==== Release decriptor file
  +
  +The release descriptor `.json` file could contain the following attributes as key/value pairs:
  +
  +Name:: Descriptive name of the code system.
  +Short name:: Short name of the code system. Must *not* contain any whitespaces, must be *unique* among the other code systems already present in Snow Owl.
  +
  +TIP: See `terminologyregistry listall` OSGi command to list all existing code systems.
  +
  +Language:: Three letter language code of the code system.
  +Code system OID:: The OID of the code system.
  +Base code system OID:: The OID of the base code system / release this SNOMED CT release depends on.
  +Maintaining organization link:: Maintaining organization link.
  +Release type:: The type of the release. Either `INTERNATIONAL` or `EXTENSION`.
  +Citation:: Citation.
  +
  +=== Examples
  +
  +==== International import
  +
  +--------------------------
  +osgi> sctimport rf2_release -t FULL /path/to/{international_import_archive} /path/to/snomed_ct_international.json
  +--------------------------
  +
  +Where `snomed_ct_international.json` looks like:
  +
  +[source,json]
  +----
  +{
  +  "name": "Systematized Nomenclature of Medicine Clinical Terms International Version",
  +  "shortName": "SNOMEDCT",
  +  "language": "ENG",
  +  "codeSystemOID": "2.16.840.1.113883.6.96",
  +  "baseCodeSystemOID": "2.16.840.1.113883.6.96",
  +  "maintainingOrganizationLink": "http://www.ihtsdo.org",
  +  "releaseType": "INTERNATIONAL",
  +  "citation": "SNOMED CT contributes to the improvement of patient care by underpinning the development of Electronic Health Records that record clinical information in ways that enable meaning-based retrieval. This provides effective access to information required for decision support and consistent reporting and analysis. Patients benefit from the use of SNOMED CT because it improves the recording of EHR information and facilitates better communication, leading to improvements in the quality of care."
   }
  -
  -Example `FULL` import with US language reference set:
  -
  ---------------------------
  -osgi> sctimport rf2_release -t FULL /opt/SnomedCT_Release_INT_20130131.zip
  ---------------------------
  -
  -An example for the Danish extension:
  -
  ---------------------------
  -osgi> sctimport rf2_extension -t FULL -b MAIN/2016-01-31 -c false /SnomedCT_Release_DK1000005_20160215.zip /dk_extension.properties
  ---------------------------
  -
  -NOTE: While the import is running, there is no feedback on the OSGi console until the process is finished; log output
  -can be observed throughout the import session in the file `serviceability/logs/log.log`. The import may take several
  -hours depending on your hardware and JVM configuration.
  +----
  +
  +==== Extension import
  +
  +An extension import based on the 2015-01-31 version of the international release:
  +--------------------------
  +osgi> sctimport rf2_release -t FULL -b 2015-01-31 -v /path/to/{extension_import_archive} /path/to/snomed_ct_extension.json
  +--------------------------
  +
  +Where `snomed_ct_extension.json` looks like:
  +
  +[source,json]
  +----
  +{
  +  "name": "SNOMED CT Special Extension",
  +  "shortName": "SNOMEDCT-SE",
  +  "language": "ENG",
  +  "codeSystemOID": "2.16.840.1.113883.6.96.2",
  +  "baseCodeSystemOID": "2.16.840.1.113883.6.96",
  +  "maintainingOrganizationLink": "http://www.snomed-special-extension.org",
  +  "releaseType": "EXTENSION",
  +  "citation": "Long citation about the details of SNOMED CT special extension"
  +}
  +----
  +
  +NOTE: While the import is running, feedback might be delayed on the OSGi console. Log output can be observed throughout the import session in the file `serviceability/logs/log.log`. The import may take several hours depending on your hardware and JVM configuration.
   
   == Single administrator operations
   
  
positive.code: mode of `/storage/backups/snowowl_full_backup_mysql.sh' changed to 0744 (rwxr--r--)
  --------------------------
  
  Add the script to the backup user's crontab (the example runs the script at 4 AM, and outputs log entries to logfiles 
  with a year-month-date suffix in /var/log/snowowl-backup):
  
  --------------------------
  
negative.code: $ mysql -u (username) -p(password) bugs < /path/to/bugzilla-backup.sql
  --------------------------
  
  In addition to the contents of the database, the `data` directory and the `localconfig` file from Bugzilla's
  installation directory should also be preserved.
  