Importing an existing model into Knowledge Model Management
- Last Updated: May 13, 2026
- 3 minute read
- Semaphore
- Documentation
If you already have an existing Semaphore installation (or a system supporting “SKOS”, see below) and you wish to copy that model into another system then you will need to export it from the existing installation and import it onto the new system.
Exporting existing models
Using the standard Knowledge Model Management importer functionality the model data can be in any of the following formats:
- SKOS - The model data can be any of the “Turtle”, “RDF/XML” or “N-Triple” file formats for SKOS models.
- Spreadsheet - The model data can also be present in a spreadsheet format (comma-separated files - “*.csv” or “*.tsv” - or Excel formats - “*.xls” and “*.xlsx”) with model information laid out in the spreadsheet in either “Hierarchy” or “Flat List” formats. Many spreadsheet data formats in these general categories are supported.
If your model is managed using an existing application then there are some considerations that need to be made in order for it to be imported into Knowledge Model Management. The preferred method is to use the “SKOS” format to import as much data as possible though if this is not practical or proves impossible a spreadsheet format (as above) can be used).
If you wish to use the SKOS export/import format then there are some aspects that should be considered:
- If using Semaphore 3 Ontology Manager and wish to export a model for use in Semaphore 5 Knowledge Model Management it is first strongly advised to upgrade to the latest version of Ontology Manager, 3.7.4 then use the “Tools”->“Export”->“SKOS” menu option which has a “Semaphore 4 Export” format that should be used.
- If using Semaphore 5 Knowledge Model Management use the “Export” option to generate a version of the model that can be imported into any version of Knowledge Model Management. Note that this will not import any of the existing model history (to see how this might be done, please see Backing up and restoring Semaphore.
- If using a third party tool that generates model exports in SKOS format be aware that there are specific extensions to the format which may require your SKOS to be manually adjusted. Contact Progress for further details.
Importing a model into Knowledge Model Management
Importing a model into Knowledge Model Management consists of simply creating a new model and using the “Import” menu option to import the file. If importing a spreadsheet you will be walked through the process of mapping spreadsheet elements into Semaphore model elements.
Migrate MarkLogic triple store to a different MarkLogic server
If you are using MarkLogic as a triple store for your Semaphore installation and you simply want to move all of your models from one MarkLogic server into another then the simplest and most reliable method to do this is as follows:
- When connected to the old MarkLogic triple store, use the “Backup Models” option from the “Tools” menu when using a user assigned the “SemaphoreSuperAdministrators” role to backup all models and configuration
- Login to the installation server
- Stop Knowledge Model Management (“systemctl stop semaphore-kmm”)
- Ensure the new MarkLogic is configured with a new database to store the model data (as per the old instance)
- Update the “SEMAPHORE_MARKLOGIC_CONFIG” variable (in “/etc/sysconfig/semaphore”) with the new MarkLogic instance information
- Wipe the Semaphore Workbench Home directory “workspace/SemaphoreData” sub-directory tree. The actual “Semaphore Workbench Home” directory name is set in the “SEMAPHORE_WORKBENCH_HOME” variable in “/etc/sysconfig/semaphore” but if this is not set then the default directory is “/opt/semaphore/kmm/webapps/ROOT/WEB-INF/SWH/”.
- Start Knowledge Model Management (“systemctl start semaphore-kmm”)
- After Knowledge Model Management starts use the “Restore Models” option from the “Tools” menu (again, using a user with the “SemaphoreSuperAdministrators” role assigned), ensuring you set the options to overwrite any existing models and configuration from what is in the backup.
There are other more technical options that have an element of risk. Both of these options require you to have previously copied the MarkLogic database onto the new server and stopped Knowledge Model Management (“systemctl stop semaphore-kmm”):
- Manually alert the “connector” files (those files with names “<MODELNAME>.marklogic” and “<MODELNAME>.tch.marklogic”) for every one of your models in the “workspace/SemaphoreData” sub-folder of your Semaphore Workbench Home directory with the relevant MarkLogic connection information for the new MarkLogic server then start Knowledge Model Management (“systemctl start semaphore-kmm”), OR
- Wipe all of the files in the Semaphore Workbench Home directory “workspace/SemaphoreData” sub-directory, update the value of the “SEMAPHORE_MARKLOGIC_CONFIG” system variable, then start Knowledge Model Management (“systemctl start semaphore-kmm”) and re-create all models with same URI as the instance they were copied from (this will have the effect of “magically finding” the model data in MarkLogic using the previous URI).