Classes Aspects
All relations between classes and aspects are to be documented here. Each line is the relationship of one class to one aspect. If you would like to add x aspects to one class, you have to fill out x lines for each aspects with the same class identifier. The connection is related by either the id_cc_non-existing (if CC is new) or the id_cc_existing (if CC is existing) of the class and either the id_as_non-existing (if AS is new) or id_as_existing (if AS is existing) of the aspect.
ADD CC_AS
ADD CC_AS = An AS (new or existing) shall be related to a class (new or existing).
Mandatory fields:
CR type | ADD CC_AS |
id_cc_non-existing or id_cc_existing | in case of a new CC, insert the unique internal ID mentioned in table classes or the 8-digit CR ID in case of an existing CC, it is the 6-digit identifier |
class coded name | 8-digit ECLASS identifier (optional) |
preferred name CC | the CC’s name (See naming rules) |
preferred name AS | the AS’s name (See naming rules) |
id_as_non-existing or id_as_existing | in case of a new AS, insert the unique internal ID mentioned in table classes or the 8-digit CR ID in case of an existing AS, it is the 6-digit identifier |
CR Proposer | CDP user name |
Reason for request | Your reason for the change |
UNASS CC_AS
UNASS KW = The existing relation between an AS and a class shall be deleted
Mandatory fields:
CR type | UNASS CC_AS |
id_cc_existing | in case of an existing CC, it is the 6-digit identifier |
class coded name | 8-digit ECLASS identifier (optional) |
preferred name CC | the CC’s name (See naming rules) |
preferred name AS | the AS’s name (See naming rules) |
id_as_existing | in case of an existing AS, it is the 6-digit identifier |
CR Proposer | CDP user name |
Reason for request | Your reason for the change |