Changes from a Leaf (Code) Selection
Move Code
Retire Code
Update Code Description
Update Code PrintName
Add PrintName to Code
|
|
|
- Now is the time for all good men to come to the aid of their country, or forever hold their peace, so that I can create a really long description to force the table to the right.
|
 Add Print Name: enter name, language, preference |
|
Data Specification for Move Code
|
|
Moving a Code in the Subsumption Hierarchy
- [Exposed under VS in application]
Concept codes can be rearranged within the concept subsumption hierarchy. moveCode can be used to assert that one concept code is a “kind of” or “is implied by” a second concept code. It can also remove this assertion.
As with all update operations, moveCode has a separate, optional ballotStatus node. The moveCode attributes specify the operation to be performed:
|
|
|
| conceptCode
|
The code of the concept to be moved.
|
| conceptName
|
A valid designation for the concept to be moved. Optional, and if supplied it will be validated against the database before the operation occurs.
|
| fromParentCode
|
The current direct parent of the concept code, if any. This attribute should be omitted if conceptCode doesn’t currently occur under any other node.
|
| fromParentName
|
A valid designation for the from parent code. Optional, but validated if supplied.
|
| toParentCode
|
The new parent of conceptCode. If omitted, conceptCode no longer has a parent in the subsumption hierarchy.
|
| toParentName
|
A valid designation for the to parent code. Optional, but validated if supplied.
|
|
|
|
|
|
 Retire Code: Select "Delete permanent" and verify |
|
|
|
|
|
 Update Description: enter new description |
|
|
 Update Code Print name: menu |
|
|
 Update Code Print name: Enter new name, language and preference. |
