Merging imported components with existing database
| Export/Import enhancements | ||
|---|---|---|
| Previous | Next | |
| Local code systems | User guide update: Use cases for collaborative authoring | |
After export, you can choose to update the effective date for the exported artefacts. This will update all unpublished artefacts to the date you set as target time. If you don't check the box, the effective time will not be updated.
Support for importing and exporting metadata has been added to Local code sets, Value domains and Mapping sets. Metadata will be exported as additional rows under the mandatory properties in a format similar to mandatory properties as property/value pairs in the consecutive cells. In case of multiple keywords, multiple rows with the same property but different values are exported. In case of the import, the Source organisation field in Snow Owl will be automatically set to MOHH and the id is automatically generated.
The import for value domains, mapping sets and local code systems now allows to merge the content of the import file with the existing database. During the import, the existing data is compared to the content of the import file, so that only new components are added to the database. No merge is performed at the property level.
To import local code systems to an existing database
The import wizard now summarises the imported content. A small blue plus decorator indicates that a component was added. The screenshot shows different local codes that were added as well as the local code system. When clicking on a component, the details are displayed in the bottom section (e.g. imported metadata of the local code system). The icons indicate the type of component (e.g.
for metadata). The middle section contains details about the import (e.g. time, user name, date, file name).
When selecting the "Merging imported components with existing database" option, the following merge strategy is applied:
Note: No merge is performed at the property level.
To import value domains into an existing database
The import wizard displays the imported content. Click on a component to see details in the bottom part. In the screenshot, you can see that a value domain (Occupation) was added. The bottom section displays different value domain members that were added as well as the meta data of the value domain. A small blue plus decorator indicates that a component was added. The icon indicates the type of component (e.g.
for value domain members). The middle section contains details about the import (e.g. user name, date, file name).
When selecting the "Merging imported components with existing database" option, the following merge strategy is applied:
Note: No merge is performed at the property level.
To import mapping sets into an existing database
The import wizard displays the imported content. Click on a component to see details in the bottom part. In the screenshot, you can see that two mapping sets were added. The bottom section displays different mappings as well as the metadata of the selected mapping set. For mappings, the source member is displayed in the "Changes" column. A small blue plus decorator indicates that a component was added. The middle section contains details about the import (e.g. user name, date, file name).
When selecting the "Merging imported components with existing database" option, the following merge strategy is applied:
Note: No merge is performed at the property level.
| Previous | Top | Next |
| Local code systems | User guide update: Use cases for collaborative authoring |