Notice: This application will enforce Multi-factor authentication (MFA) for NIH users beginning the evening of Wed Aug 3rd.
NIH | National Cancer Institute | NCI Wiki  

Contents of this Page

This page contains information about the UML tagged values labels used by the SIW and UML Loader for creating content in caDSR.  These tags can be inserted using a UML Modeling tool or the caDSR SIW tool. 

Tag Summary

Key to the summary:

  1. The product is the NCI CBIIT software which creates/adds the tag to the XMI.
  2. The tag name is case sensitive.
  3. The tag value is either the data type, e.g. "text" for free form text, or "enumerated" when a list of permitted values appears in the description.

    The content of lines 1 - 12 is repeated from the caCORE SDK 4.0 Developer's Guide, page 90 - 96. (archived)

Number

Product

Tag Name

Creating Tool and Version(s)

Value Domain

Mandatory? Default Value(s)

Tech Lead of Creating Tool

Description

1

SDK

mapped-constant

---

text

---

---

An ISO 21090 data type specific tag value added to a Logical Model class attribute element which specifies a constant, or default, value to be returned whenever the attribute is not mapped to a table column, or is mapped to a table column, but the column does not have a value for a particular row (i.e., the value is null).
The constants in the logical model are specified at two places: At global level and At the local level. The global constant is applied any time when the attribute is not mapped to the database and there does not exist corresponding local constant value. Whereas the local constant is applied anytime the user has not mapped corresponding attribute to the database. Local constant will checked prior to the global constant.

Tag Value Key: mapped-constant:<fully qualified name of the complex sub-attribute>
Value: constant value

In case of collections, tag value key can be derived in following formats:
<<Fully Qualified Name of the Attribute>>.<<name of collection>>[index].<<name of attribute>>

mapped-constant: <<Fully Qualified Name of the Attribute>>.<<name of collection>>.<<name of attribute>>

mapped-constant: <<Fully Qualified Name of the Attribute>>.<<name of outer collection>>.<<name of inner collection>>[index].<<name of attribute>>

In case of inheritance, constants for inheriting objects can be defined at parent level to override constants set for the parent.

2

SDK

correlation-table

---

text

---

---

A Tag Value added to an Association element (line) drawn between two Logical Model classes within the same diagram. The value specifies the correlation (join) table name.

3

SDK

discriminator

---

text

---

---

A Tag Value added to a Data Model class Attribute element. The value of this tag represents the Logical Model class name that acts as the discriminator in situations when the parent and sub-class are persisted within the same database table. The value of the tag, if present, is placed within the discriminator element of the generated Hibernate mapping file.

Note

The <discriminator> element is required for polymorphic persistence using the table-per-class-hierarchy mapping strategy and declares a discriminator column of the table. The discriminator column contains marker values that tell the persistence layer what subclass to instantiate for a particular row.

4

SDK

id-attribute

---

text

---

---

A Tag Value added to a Logical Model class Attribute. The presence of the Tag Value indicates that the attribute is the class identifier attribute. This Tag Value is required when the identifier attribute is named something other than the default name, id. The value should specify the fully qualified name of the Logical Model class that contains the attribute.

5

SDK

implements-association

---

text

---

---

A Tag Value added to a Data Model class Attribute (column). The value specifies the associated Logical Model class attribute that implements the association. The value must be specified using the following pattern: <fully qualified logical model class name>.< attribute name>.

6

SDK

inverse-of

---

text

---

---

Tag Value added to a Data Model class Attribute (column). Used to identify the inverse attribute (column) of a bi-directional association. The value specifies the corresponding inverse Logical Model class attribute, and must have the same value as the implements-association Tag Value of the bi-directional association. The value must be specified using the following pattern: <fully qualified logical model class name>.< attribute name>.

7

SDK

lazy-load

---

enumerated

---

---

A Tag Value added to an Association element between two Logical Model classes. The value specifies whether the association should be fetched lazily or not. Sets the lazy attribute in the generated .hbm.xml file to either true or false accordingly. Permissible values are

  • yes
  • no (any value other than yes is treated as a no)
8

SDK

mapped-collection-table

---

text

---

---

A Tag Value added to a Logical Model class Attribute. The value specifies the name of the mapped primitive collection (non-domain class - e.g., String, Integer) table.

9

SDK

mapped-attributes

---

text

---

---

A Tag Value added to a Data Model class Attribute (Column). The value specifies the corresponding mapped Logical Model class Attribute. The value must be specified using the following pattern: <fully qualified logical model class name>.< attribute name>.

10

SDK

mapped-element

---

text

---

---

A Tag Value added to a Data Model class Attribute (Column). The value specifies the name of the mapped primitive collection (non-domain class - e.g., String, Integer) Logical Model class attribute. The value must be specified using the following pattern: <fully qualified logical model class name>.< attribute name>.

11

SDK

nci-not-null

---

text

O

Konka

Set to "true" on a property element to override the SDK default and set the not-null attribute in the generated Hibernate mapping

12SDKmapped-collection-element-type---text---Konka

An ISO 21090 data type specific Tag Value added to a Logical Model class Attribute of ISO data type AD (address), which is a complex data type with nested collection ISO data type ADXP (Address Part) attributes.

The mapped-collection-element-part Tag Value must be specified using the following pattern:

    Tag Value Key: mapped-collection-element-type:part[<index>]
    Value: <name of the ADXP subclass>

13SDKNCI_EAGER_LOAD---text---Konka

A Tag Value assigned to an Association element (link) between two Logical Model classes.  The NCI_EAGER_LOAD Tag Value has a converse meaning of the now obsolete SDK lazy-loadTag Value. The NCI_EAGER_LOAD Tag Value is used to set the "lazy" attribute in the SDK generated hibernate mapping files.  If the NCI_EAGER_LOAD Tag Value is set to "true" or "yes", it actually indicates that the "lazy" attribute should be set to "false"; i.e., to say that an association is eagerly loaded, is the opposite of saying that an association is lazily loaded. Any other value (including "no") for the NCI_EAGER_LOAD Tag Value will cause the "lazy" attribute within the corrsesponding hibernate mapping file to be set to either "true" or "proxy", as detailed below.
 
The Hibernate mapping file "lazy" attribute is set to "proxy" (vs. "true") for the following scenarios where NCI_EAGER_LOAD Tag Value has been set to "no":
 
*  Many-to-One
*  One-to-One
 
It is set to "true" for the other remaining scenarios where NCI_EAGER_LOAD has been set to "no". 

The NCI_EAGER_LOAD Tag Value, when applied to a Logical Model Association element (link), must be specified using the following pattern:

    Tag: NCI_EAGER_LOAD#<fully-qualified logical model class name>.<attribute name> 
     Value  : <yes | no>

14SDKRESTFUL_RESOURCE---text----Konka

This custom tag is used to generate RESTful resources. This custom tag can be added at the package or class level. Class level settings will override package settings. Each domain object represents a RESTful resource.

Custom tag should at least have one of C R U D values

15

SIW, SDK

description

---

text

---

Ludet

An optional Tag Value added to a Class or Attribute element to store documentation/comments for the element. The value describes the element, and is used when creating Java Docs for generated domain objects. 
Note: The description Tag Valuede is only used if the documentation tag value for the element is empty or does not exist.

16

SIW, SDK

documentation

---

text

---

Ludet

An optional Tag Value added to a UML element to store documentation/ comments for the element. The value will be used when creating Java Docs for the generated domain object.
See also the description Tag Value.

17

---

type

---

enumerated

---

---

A Tag Value added to a Data Model class Attribute (Column). The value specifies the DB column type. Valid values include (but are not limited to):

  • CHAR
  • CLOB
  • NUMBER
  • VARCHAR2
18

GME/caAdapter, SIW, SDK

NCI_GME_XML_NAMESPACE

---

text

---

---

Three Tag Values added to an Object Model for mapping purposes:

  1. One tag per project placed at the Model level. The default value is: "gme://{projectName}.{contextName}/{version}". Example: "gme://caMOD.caBIG/3.0"
  2. One tag per package placed at the Package level. The default value must be the full package path. Example: "gme://caMOD.caBIG/3.0/gov.nih.nci.camod.domain"
  3. One tag per per class placed at the Class level. The default value must be the full package path. Example: "gme://caMOD.caBIG/3.0/gov.nih.nci.camod.domain"
19

GME/caAdapter, SIW, SDK

NCI_GME_XML_ELEMENT

---

text

---

---

One Tag Value added to an Object Model for mapping purposes placed at the Class level. The value is the class name from the source model. Example: "Person".

20

GME/caAdapter, SIW

NCI_GME_XML_LOC_REF

---

text

---

---

One Tag Value added to an Object Model for mapping purposes placed at the Class Attribute level. The value is the attribute name. Example: "Date of Birth". The default value must be "@".

21

GME/caAdapter, SIW, SDK

NCI_GME_SOURCE_XML_LOC_REF

---

text

---

---

One Tag Value added to an Object Model for mapping purposes. Used for Associations Source.

22

GME/caAdapter, SIW, SDK

NCI_GME_TARGET_XML_LOC_REF

---

text

---

---

One Tag Value added to an Object Model for mapping purposes. Used for Associations Target.

23

caAdapter

XMLNamespace

---

text

---

---

A Tag Value added to an Object Model or Data Model, and placed at the Class Attribute (Column) level. The value specifies the CSV field mapped to that Attribute or Column.
Note: The name of this tag will be changed.

24

SIW

ObjectClassConceptCode

---

text

M

Ludet

This is the Primary Concept Code for the Object Class. There is only one Primary Concept Code per UML Class.

25

SIW

ObjectClassConceptPreferredName

---

text

M

Ludet

This is the Preferred Name of the Primary Concept for the Object Class. One Preferred Name Tag Value must be provided for each Primary Concept Code tag.

26

SIW 

ObjectClassConceptDefinition
ObjectClassConceptDefinition_2
ObjectClassConceptDefinition_3
...
ObjectClassConceptDefinition_8

---

text

M

Ludet

This is the Definition of the Primary Concept for the Object Class. While there can be only one Definition per Object Class (because there can be only one primary concept code per object class), definitions can be lengthy. EA only supports 255 characters per tagged value. Therefore, if a longer definition is needed, the definition can be  split into multiple tags by appending '_n' to the tag name, where 'n' is a number from 2 to 8, for a maximum definition of 2000 characters.

27

SIW

ObjectClassConceptDefinitionSource

---

text

M

Ludet

The Source of the Object Class Concept Definition. There can be only one source per definition. 

28

SIW

ObjectClassQualifierConceptCode
ObjectClassQualifierConceptCode1
ObjectClassQualifierConceptCode2
ObjectClassQualifierConceptCode3

---

text

O

Ludet

This Tag Value identifies the Concept Code(s) used to qualify the Primary Concept Code for an Object Class.  If multiple Qualifier Concepts are needed, 'n' is appended to the concept code tag name, where 'n' is the value starting with 1 through whatever number of qualifiers are needed. Each Qualifier Concept modifies the concept in the next lower level ordinal position; e.g. 1 modifies 0, 2 modifies 1, 3 modifies 2, etc. 
NOTE: Although multiple Qualifier Concepts can be added, if more than 4 are needed, EVS staff should be consulted to ensure that the string of concepts isn't better defined as as new atomic concept in EVS.

29

SIW

ObjectClassQualifierConceptPreferredName
ObjectClassQualifierConceptPreferredName1
ObjectClassQualifierConceptPreferredName2
ObjectClassQualifierConceptPreferredName3

---

text

O

Ludet

This is the Preferred Name of the Qualifier Concept associated with the Qualifier Concept Code at the same appended position (n=1 goes with n=1).  One Preferred Name Tag Value must be provided for each Qualifier Concept Code tag.
NOTE: Although multiple Qualifier Concepts can be added, if more than 4 are needed, EVS staff should be consulted to ensure that the string of concepts isn't better defined as as new atomic concept in EVS.

30

SIW

ObjectClassQualifierConceptDefinition
ObjectClassQualifierConceptDefinition_2
ObjectClassQualifierConceptDefinition_3...8

ObjectClassQualifierConceptDefinition1
ObjectClassQualifierConceptDefinition1_2 ...8

ObjectClassQualifierConceptDefinition2
ObjectClassQualifierConceptDefinition2_2 ...8
ObjectClassQualifierConceptDefinition3
ObjectClassQualifierConceptDefinition3_2 ...8

---

text

O

Ludet

This Tag Value provides the Definition for each Qualifier Concept used to qualify the Primary Concept Code for an Object Class. As with the Preferred Name tag described above, the Definition numbering convention is such that the Qualifier Concept Definition is associated with the Qualifier Concept Code at the same appended position (n=1 goes with n=1). 
While there can be only one Definition per Concept Code, definitions can be lengthy. EA only supports 255 characters per tagged value. Therefore, if a longer definition is needed, the definition can be  split into multiple tags by appending '_n' to the tag name, where 'n' is a number from 2 to 8, for a maximum definition of 2000 characters.
For example, if you need to have multiple definition tags for the 1st qualifier concept, the tag names would be: ObjectClassQualifierConceptDefinition1, ObjectClassQualifierConceptDefinition1_2, ObjectClassQualifierConceptDefinition1_3, etc..

31

SIW

ObjectClassQualifierConceptDefinitionSource
ObjectClassQualifierConceptDefinitionSource1
ObjectClassQualifierConceptDefinitionSource2
ObjectClassQualifierConceptDefinitionSource3

---

text

O

Ludet

The Source for the Definition of a Qualifier Concept. There can be only one Source tag per Qualifier Concept Definition. The Source numbering convention is such that if multiple Qualifier Concepts are used, the Definition Source is associated with the Qualifier Definition at the same appended position (n=1 goes with n=1). 

32

SIW

PropertyConceptCode

---

---

M

---

This is the Primary Concept Code for the Property. There is only one Primary Concept Code per UML Attribute. 

33

SIW

PropertyConceptPreferredName

---

text

M

Ludet

This is the Preferred Name of the Primary Concept for the Property. One Preferred Name Tag Value must be provided for each Primary Property Concept Code tag.

34

SIW

PropertyConceptDefinition
PropertyConceptDefinition_2
PropertyConceptDefinition_3
...
PropertyConceptDefinition_8

---

text 

M

Ludet

This is the Definition of the Primary Concept for the Property. While there can be only one Definition per Property (because there can be only one primary concept code per property), definitions can be lengthy. EA only supports 255 characters per tagged value. Therefore, if a longer definition is needed, the definition can be  split into multiple tags by appending '_n' to the tag name, where 'n' is a number from 2 to 8, for a maximum definition of 2000 characters.

35

SIW

PropertyConceptDefinitionSource

---

text

M

Ludet

The Source of the Property Concept Definition. There can be only one Source per Definition. 

36

SIW

PropertyQualifierConceptCode
PropertyQualifierConceptCode1
PropertyQualifierConceptCode2
PropertyQualifierConceptCode3

---

text

O

Ludet

This Tag Value identifies the Concept Code(s) used to qualify the primary Concept Code for a Property. If multiple Qualifier Concepts are needed, 'n' is appended to the concept code tag name, where 'n' is the value starting with 1 through whatever number of qualifiers are needed. Each Qualifier Concept modifies the concept in the next lower level ordinal position; e.g. 1 modifies 0, 2 modifies 1, 3 modifies 2, etc. 
NOTE: Although multiple Qualifier Concepts can be added, if more than 4 are needed, EVS staff should be consulted to ensure that the string of concepts isn't better defined as as new atomic concept in EVS.

37

SIW

PropertyQualifierConceptPreferredName
PropertyQualifierConceptPreferredName1
PropertyQualifierConceptPreferredName2
PropertyQualifierConceptPreferredName3

---

text 

C

Ludet

This is the Preferred Name of the Qualifier Concept associated with the Property Qualifier Concept Code at the same appended position (n=1 goes with n=1).  One Preferred Name Tag Value must be provided for each Qualifier Concept Code tag.
NOTE: Although multiple Qualifier Concepts can be added, if more than 4 are needed, EVS staff should be consulted to ensure that the string of concepts isn't better defined as as new atomic concept in EVS.

38

SIW 

PropertyQualifierConceptDefinition
PropertyQualifierConceptDefinition_2
PropertyQualifierConceptDefinition_3
...
PropertyQualifierConceptDefinition_8

PropertyQualifierConceptDefinition1
PropertyQualifierConceptDefinition1_2 ...8
PropertyQualifierConceptDefinition2
PropertyQualifierConceptDefinition2_2 ...8
PropertyQualifierConceptDefinition3
PropertyQualifierConceptDefinition3_2 ... 8

---

text 

C

Ludet

This Tag Value provides the Definition for each Qualifier Concept used to qualify the Primary Concept Code for a Property. As with the Preferred Name tag described above, the Definition numbering convention is such that the Qualifier Concept Definition is associated with the Qualifier Concept Code at the same appended position (n=1 goes with n=1). 
While there can be only one Definition per Concept Code, definitions can be lengthy. EA only supports 255 characters per tagged value. Therefore, if a longer definition is needed, the definition can be  split into multiple tags by appending '_n' to the tag name, where 'n' is a number from 2 to 8, for a maximum definition of 2000 characters.
For example, if you need to have multiple definition tags for the 1st qualifier concept, the tag names would be: ObjectClassQualifierConceptDefinition1, ObjectClassQualifierConceptDefinition1_2, ObjectClassQualifierConceptDefinition1_3, etc.

39

SIW 

PropertyQualifierConceptDefinitionSource
PropertyQualifierConceptDefinitionSource1
PropertyQualifierConceptDefinitionSource2
PropertyQualifierConceptDefinitionSource2

---

text

C

Ludet

The Source for the Definition of a Qualifier Concept. There can be only one Source tag per Qualifier Concept Definition. The Source numbering convention is such that if multiple Qualifier Concepts are used, the Definition Source is associated with the Qualifier Definition at the same appended position (n=1 goes with n=1). 

40

SIW

CADSR_DE_ID

---

text

O

Ludet

The Public ID (CDE_ID) of a Data Element if the item is mapped to an existing CDE.

41

SIW

CADSR_DE_VERSION

---

text

C

Ludet

The Version (VERSION) of a Data Element. Mandatory if a data element is mapped to an attribute.

42

SIW

CADSR_VD_ID

---

text

O

Ludet

The Public ID (VD_ID) of a Value Domain if the item is mapped to an existing Value Domain

43

SIW

CADSR_VD_VERSION

---

text

C

Ludet

The Version (VERSION) of a Value Domain. Mandatory is a Value Domain is mapped to an attribute or a Value Domain

44

SIW

NCI_VD_UOM

---

text

O

Ludet

The desired Value Domain Unit Of Measure

45

SIW

NCI_VD_DISPLAY_FORMAT

---

text

O

Ludet

The desired Value Domain Display Format

46

SIW

NCI_VD_MIN_LENGTH

---

text

O

Ludet

The desired Value Domain Minimum Length

47

SIW

NCI_VD_MAX_LENGTH

---

text

O

Ludet

The desired Value Domain Maximum Length

48

SIW

NCI_VD_DECIMAL_PLACE

---

text

O

Ludet

The desired Value Domain Decimal Place

49

SIW

NCI_VD_HIGH_VALUE

---

text

O

Ludet

The desired Value Domain High Value

50

SIW

NCI_VD_LOW_VALUE

---

text

O

Ludet

The desired Value Domain Low Value

51

SIW

CADSR Local Value Domain

---

text

O

Ludet

Indicates that the UML attribute should use a value domain defined within in a package along with the model being loaded. Its value is the name assigned to the Value Domain class.

52

SIW

CADSR_ValueDomainDefinition

---

text

M

Ludet

The Definition (PREFERRED_DEFINITION) of a value domain.Tagged Value on the class with stereotype = 'CADSR Value Domain'

53

SIW

CADSR_ValueDomainDatatype

---

enumerated

M

Ludet

The datatype (DTL_NAME) of a Value Domain. The list of datatypes is on a wiki page: [https://wiki.nci.nih.gov/x/ypV8]
Tagged Value on the class with stereotype = 'CADSR Value Domain

54

SIW

CADSR_ValueDomainType

---

enumerated

M

Ludet

The Type (VD_TYPE_FLAG) of a Value Domain.  Valid Types are:

  • 'E' -- Enumerated
  • 'N' -- Nonenumerated
    |
    | 50 | SIW | CADSR_ConceptualDomainPublicIDTagged Value on the class with stereotype = 'CADSR Value Domain
55

SIW

CADSR_ConceptualDomainPublicID

---

text

M

Ludet

The Public ID of a Conceptual Domain. Tagged Value on the class with stereotype = 'CADSR Value Domain'

56

SIW

CADSR_ConceptualDomainVersion

---

text

M

Ludet

The Version (VERSION) of a Conceptual Domain. Tagged Value on the class with stereotype = 'CADSR Value Domain'

57

SIW

CADSR_RepresentationPublicID

---

text

M

Ludet

The Public ID (REP_ID) of a Representation. Tagged Value on the class with stereotype = 'CADSR Value Domain'

58

SIW

CADSR_RepresentationVersion

---

text 

M

Ludet

The Version (VERSION) of a Representation. Tagged Value on the class with stereotype = 'CADSR Value Domain'

59

SIW

CADSR_Description
CADSR_Description2
CADSR_Description3
..
CADSR_Description8

---

text 

M

Ludet

Replaces previous "Description" and "Documentation" tags.   Syntactic description provided by model owner. This tag can be split into multiple tags by appending n to the name, where n is a number from 2 to 8.

60

SIW

CURATOR_REVIEWED

---

text

----

Ludet

Indicates if the Curator has reviewed the item

61

SIW

OWNER_REVIEWED

---

text

---

Ludet

Generated by SIW. Indicates if the Model Owner has reviewed the item

62

SIW

ValueDomainConceptCode

---

text

O

Ludet

Use to denote a concept mapped at the Value Domain level.  The meaning of this concept association depends on whether the Value Domain is a Non-enumerated "N", or Enumerated, "E", VD. For "N" VDs, Non-enumerated VD, the presence of a one ConcpetCode is permitted at the Value Domian level and  represents a 'Referenced Enumeration', or "Enumerated by Reference", meaning that the of value list is not managed within the registry, but a parent concept exists in EVS by which a program implementing the value domain could constrain data collection.  For an "E", Enumerated VD, one or more concepts can be created by which the enumerated value meanings managed within caDSR have been restricted/constrained. See SIW and UML Loader technical guide for details. Tagged Value on the class with stereotype = 'CADSR Value Domain'

63

SIW

ValueDomainConceptDefinition
ValueDomainConceptDefinition_2 .... _8

---

text

C

Ludet

The definition for the concept associated with the Value Domain.  There can be up to 8 of these tags to hold definitions up to 2000 characters. Tagged Value on the class with stereotype = 'CADSR Value Domain'

64

SIW

ValueDomainConceptDefinitionSource

---

text

C

Ludet

The source of the definition. Tagged Value on the class with stereotype = 'CADSR Value Domain'

65

SIW

ValueDomainConceptPreferredName

---

text

C

Ludet

The Preferred Name for the concept associated with Value Domain. Tagged Value on the class with stereotype = 'CADSR Value Domain'

66

SIW

ValueDomainQualifierConceptCode
ValueDomainQualifierConceptCode2
ValueDomainQualifierConceptCode3
ValueDomainQualifierConceptCode4

---

text

O

Ludet

For "E", enumerated value domains, the Value Domain concepts restrict the permissible value/value meaning list.  There can be multiple concepts that restrict the value meaning list. These are entered/created using EA by creating Qualifiers as tagged values on the class with stereotype = 'CADSR Value Domain'

67

SIW

ValueDomainQualifierConceptDefinition
ValueDomainQualifierConceptDefinition_2
ValueDomainQualifierConceptDefinition_3
...
ValueDomainQualifierConceptDefinition_8

If multiple tags for a single definition:
ValueDomainQualifierConceptDefinition2
ValueDomainQualifierConceptDefinition2_2
ValueDomainQualifierConceptDefinition2_3 ... _8
ValueDomainQualifierConceptDefinition3
ValueDomainQualifierConceptDefinition3_2 ... _8
ValueDomainQualifierConceptDefinition4
ValueDomainQualifierConceptDefinition4_2 ... _8

---

text

C

Ludet

The Value Domian Restricti9on concept definition that goes with each concept entered as "qualifiers" concepts.  This is mandatory if a Qualifier concept is present. Tagged Value on the class with stereotype = 'CADSR Value Domain'

68

SIW

ValueDomainQualifierConceptDefinitionSource
ValueDomainQualifierConceptDefinitionSource2
ValueDomainQualifierConceptDefinitionSource3
ValueDomainQualifierConceptDefinitionSource4

---

text

C

Ludet

The qualifier concept definition source. This is mandatory if a Qualifer concept is present. Tagged Value on the class with stereotype = 'CADSR Value Domain

69

SIW

ValueDomainQualifierConceptPreferredName
ValueDomainQualifierConceptPreferredName2
ValueDomainQualifierConceptPreferredName3
ValueDomainQualifierConceptPreferredName4

---

text

C

Ludet

The qualifier concept preferred name. This is mandatory if a Qualifer concept is present. Tagged Value on the class with stereotype = 'CADSR Value Domain

70

SIW

ValueMeaningConceptCode

---

text

O

Ludet

The primary concept code associated with a Value Meaning in an enumerated Value Domain.

71

SIW

ValueMeaningConceptDefinition
ValueMeaningConceptDefinition_2 ... _8

---

text

C

Ludet

The concept definition associated with the referenced concept.

72

SIW

ValueMeaningConceptDefinitionSource

---

text

C

Ludet

The concept definition source associated with the referenced concept.

73

SIW

ValueMeaningConceptPreferredName

---

text

C

Ludet

The concept preferred name associated with the referenced concept.

74

---

ValueMeaningQualifierConceptCode
ValueMeaningQualifierConceptCode2
ValueMeaningQualifierConceptCode3
ValueMeaningQualifierConceptCode4

---

text

O

Ludet

The qualifier concept(s) associated with the value meaning.

75

---

ValueMeaningQualifierConceptDefinition
ValueMeaningQualifierConceptDefinition_2
ValueMeaningQualifierConceptDefinition_3 ... _8


If multiple tags for a single definition:
ValueMeaningQualifierConceptDefinition2
ValueMeaningQualifierConceptDefinition2_2
ValueMeaningQualifierConceptDefinition2_3 ... _8
ValueMeaningQualifierConceptDefinition3
ValueMeaningQualifierConceptDefinition3_2 ... _8
ValueMeaningQualifierConceptDefinition4
ValueMeaningQualifierConceptDefinition4_2 ... _8

---

text

C

Ludet

The value meaning qualifier concept definition.

76

---

ValueMeaningQualifierConceptDefinitionSource
ValueMeaningQualifierConceptDefinitionSource2
ValueMeaningQualifierConceptDefinitionSource3
ValueMeaningQualifierConceptDefinitionSource4

---

text

C

Ludet

The value meaning qualifier concept definition source.

77

---

ValueMeaningQualifierConceptPreferredName
ValueMeaningQualifierConceptPreferredName2
ValueMeaningQualifierConceptPreferredName3
ValueMeaningQualifierConceptPreferredName4

---

text

C

Ludet

The value meaing concept reference preferrred name.

78

SIW

CADSR_Inherited.{1}.OWNER_REVIEWED

---

text

C

Ludet

Generated by SIW. Indicates if the Model Owner has reviewed the item (Inherited Attributes)

79

SIW

CADSR_Inherited.{1}.CURATOR_REVIEWED

---

text

C

Ludet

Generated by SIW. Indicates if the Curator has reviewed the item (Inherited Attributes)

80

SIW

CADSR_Inherited.{1}.DE_ID

---

text

C

Ludet

Generated by SIW. The Public ID (CDE_ID) of a Data Element.(inherited attributes)

81

SIW

CADSR_Inherited.{1}.DE_VERSION

---

text

C

Ludet

Generated by SIW. The Version of a Data Element.(inherited attributes)

82

SIW

CADSR_Inherited.{1}.VD_ID

---

text

C

Ludet

Generated by SIW. The Public ID of a Value Domain.(inherited attributes)

83

SIW

CADSR_Inherited.{1}.VD_VERSION

---

text

C

Ludet

Generated by SIW. The Version of a Value Domain.(inherited attributes)

84

SIW

CADSR_Inherited.{1}.Local Value Domain

---

text

C

Ludet

Generated by SIW.  Allows Local Value Domain Mapping for Inherited Attributes.

Metadata

The following tag names reflect previously existing tag names and new tag names that conform to the naming convention using NCI_. Over time the tag names will be changed to universally conform to the standard naming convention. Normal naming migration will introduce the new tag name, the old tag name will be marked for deprecation, dependent software will have a full major release to migrate references to the new tag name and finally the old tag name will be dropped. It may also be necessary to perform text substitution on older XMI files to maintain compatibility with the products.

For each tag, enter the following information:

  • Name
    • Use all upper-case letters
    • Start with NCI and an underscore (NCI_)
    • Separate words with underscores (_)
    • Be meaningful
    • Be unique
  • Optional / Mandatory
  • Default Value
  • Creating Tool(s) + Tool Version(s) that support the tag
  • Description and Comments; including value examples
  • Tag Value Domain Metadata
  • Tech Lead of the Creating Tool

 

  • No labels