Overview
This page describes the steps required to update a refset to a new version.
Prerequisites
- A refset must exist and be populated with refset members. It also must be assigned to a user.
Updating a Refset
The process to migrate a refset to a new version is as follows:
- Select the assigned refset.
- Click on the 'Migration' icon
on the Terminology row.
- Enter the new version and click the 'Test' button.
- Click the 'Migrate' button. Migration report will be displayed as shown below.
- The migration can be 'Finished', 'Saved for later', 'Resumed', 'Canceled' or the report can be exported.
Migration Report
Only some of these sections will be relevant or displayed on each migration report.
- Members in Common - These are the refset members that have not changed in the migration from the older version to the newer version.
- New Members - These are refset members that are in the newer version, but were not in the original version.
- Old Members - These are refset members that were in the original version, but are not in the newer version.
- Valid Exclusions - Exclusions on the original version that are still valid exclusions on the upgraded refset.
- Invalid Exclusions: Concepts specifically excluded from the older version that are not resolved by the definition when using the new version.
- ACTION: no action
- Migrated Exclusions - New members that are manually excluded from the upgraded refset.
- Valid Inclusions - Inclusions on the original version that are still valid inclusions on the upgraded refset.
- Invalid Inclusions: Concepts specifically included in the old version that are now resolved by the definition when using the new version.
- ACTION: no action
- Migrated Inclusions - Old members that are manually included in the upgraded refset.