...
At no stage in this process are previously written records ever amended. Once a record has been released in a
| Gloss |
|---|
| PreSpace | false |
|---|
| t | release file, |
|---|
|
it will continue to be released in exactly the same form in future | Gloss |
|---|
| PreSpace | false |
|---|
| t | release files. |
|---|
|
Changes are only recorded at the point of release in the
| Gloss |
|---|
| PreSpace | false |
|---|
| t | release files. |
|---|
|
If a record is changed a number of times between releases (during an edit and review process), only the most recently amended record will be appended to the | Gloss |
|---|
| PreSpace | false |
|---|
| t | release file, |
|---|
|
not individual records showing each separate edit to the released In the last example, as well as inactivating the concept (active=0), the
| Specref |
|---|
| RefType | (field) |
|---|
| t | definitionStatusId |
|---|
|
is changed from | Concept |
|---|
| t | 900000000000073002|Defined| |
|---|
| ShowFormat | inline |
|---|
|
to | Concept |
|---|
| t | 900000000000074008|Primitive| |
|---|
|
. In practice this change is not essential since the value of data columns is ignored when a is inactive. Although the change is unnecessary and insignificant, it typically occurs since all the relationships of an inactive concept must also be inactive, and as a result, from the perspective of the authoring environment the concept cannot be regarded as | Concept |
|---|
| t | 900000000000073002|Defined| |
|---|
|
.