Formatting a CSV for View Import - Revision history

Annie: RM platform_type_guid

2026-01-02T22:11:53Z

RM platform_type_guid

← Older revision		Revision as of 18:11, 2 January 2026
Line 81:		Line 81:
	''See Nested Views for changes to other columns''		''See Nested Views for changes to other columns''

	=== View GUID, Characteristic ~~GUID, and Platform Type~~ GUID ===		=== View GUID and Characteristic GUID ===

	* A GUID must be associated with an existing node of the relevant xmi:type in the model.		* A GUID must be associated with an existing node of the relevant xmi:type in the model.

Annie: RM platform_type_guid

2026-01-02T22:11:34Z

RM platform_type_guid

← Older revision		Revision as of 18:11, 2 January 2026
Line 29:		Line 29:
	* View_GUID		* View_GUID
	* Characteristic_GUID		* Characteristic_GUID
	* Platform_Type_GUID

	The order of the columns is not enforced, it does not have to be in the same order as the suggested format above.		The order of the columns is not enforced, it does not have to be in the same order as the suggested format above.

Annie at 22:16, 17 December 2025

2025-12-17T22:16:23Z

← Older revision		Revision as of 18:16, 17 December 2025
Line 39:		Line 39:
	== Column-specific Requirements ==		== Column-specific Requirements ==
	=== DM_Name ===		=== DM_Name ===
	* Leaving this column blank will default ~~Datamodel~~ to the first available ~~Datamodel~~.		* Leaving this column blank will default to the first available Data Model.
	* Setting this column to an existing ~~Datamodel~~ will default to the first matching ~~Datamodel~~ within the ~~model~~.		* Setting this column to the name of an existing Data Model node will default to the first matching Data Model node within the project.
	* If there is no matching ~~Datamodel~~, a new ~~Datamodel~~ will be created.		* If there is no matching Data Model, a new Data Model will be created.

	=== Package Name ===		=== Package Name ===

Annie: /* General Column/Data Requirements */

2025-11-14T18:21:41Z

General Column/Data Requirements

← Older revision		Revision as of 14:21, 14 November 2025
Line 11:		Line 11:

	The following columns are optional (for example, the Package columns are only there to specify destination if desired):		The following columns are optional (for example, the Package columns are only there to specify destination if desired):
			* DM_Name
	* Package_Name		* Package_Name
	* Package_Description		* Package_Description
Line 18:		Line 19:
	* Characteristic_Description		* Characteristic_Description
	* Characteristic_Tags		* Characteristic_Tags
			* Characteristic_Foreign
			* Primitive_Bound_Length
			* Primitive_Bound_Scale
			* Optional
	* Lower_Bound		* Lower_Bound
	* Upper_Bound		* Upper_Bound
	* Nested_View		* Nested_View
			* Platform_Type
			* View_GUID
			* Characteristic_GUID
			* Platform_Type_GUID

	The order of the columns is not enforced, it does not have to be in the same order as the suggested format above.		The order of the columns is not enforced, it does not have to be in the same order as the suggested format above.
Line 29:		Line 38:

	== Column-specific Requirements ==		== Column-specific Requirements ==
			=== DM_Name ===
			* Leaving this column blank will default Datamodel to the first available Datamodel.
			* Setting this column to an existing Datamodel will default to the first matching Datamodel within the model.
			* If there is no matching Datamodel, a new Datamodel will be created.

	=== Package Name ===		=== Package Name ===
	* Leaving this column blank will default Package to the "Phenom" package.		* Leaving this column blank will default Package to the "Phenom" package.
Line 60:		Line 74:
	=== Lower Bound and Upper Bound ===		=== Lower Bound and Upper Bound ===

	* This row must have both a Source and a Path for these values to be valid		* This row must have both a Source and a Path for these values to be valid.
			* The bound can be set to "unbounded", which will set the bound to -1.

	=== Nested View ===		=== Nested View ===
Line 66:		Line 81:
	* The Nested View must exist in the model and must be the name of a View.		* The Nested View must exist in the model and must be the name of a View.
	''See Nested Views for changes to other columns''		''See Nested Views for changes to other columns''

			=== View GUID, Characteristic GUID, and Platform Type GUID ===

			* A GUID must be associated with an existing node of the relevant xmi:type in the model.

	== Tagging New Elements (Optional) ==		== Tagging New Elements (Optional) ==

Nathalie at 15:58, 14 November 2025

2025-11-14T15:58:17Z

← Older revision		Revision as of 11:58, 14 November 2025
Line 80:		Line 80:

	By default, all sub-structure nesting view field rows will be inferred to be representing a "private" nesting. This can be made explicit, or toggled off to accomplish a sub-structure import, by using the '''Characteristic_Foreign''' column: if set to "false", the view sub-structure will be private to its nesting view, and an independent import if set to "true".		By default, all sub-structure nesting view field rows will be inferred to be representing a "private" nesting. This can be made explicit, or toggled off to accomplish a sub-structure import, by using the '''Characteristic_Foreign''' column: if set to "false", the view sub-structure will be private to its nesting view, and an independent import if set to "true".

			== Union Views Requirements ==
			Union views are not supported by the CSV import yet.

	== Additional Requirements ==		== Additional Requirements ==

Nathalie: /* Nested Views */

2025-11-14T15:57:39Z

Nested Views

← Older revision		Revision as of 11:57, 14 November 2025
Line 74:		Line 74:
	Package_Tags will tag whichever package is chosen - this includes the Phenom package when a package isn't specified in the Package_Name column.		Package_Tags will tag whichever package is chosen - this includes the Phenom package when a package isn't specified in the Package_Name column.

	== Nested Views ==		== Nested Views Requirements ==
	By referencing the name of another view, whether already existing in the model or being added by the same CSV file, in the '''Nested_View''' column, the import can create view sub-structuring or nesting.		By referencing the name of another view, whether already existing in the model or being added by the same CSV file, in the '''Nested_View''' column, the import can create view sub-structuring or nesting.

Nathalie: /* Nested View */

2025-11-14T15:57:05Z

Nested View

← Older revision		Revision as of 11:57, 14 November 2025
Line 65:		Line 65:

	* The Nested View must exist in the model and must be the name of a View.		* The Nested View must exist in the model and must be the name of a View.
	* See Nested Views for changes to other columns		''See Nested Views for changes to other columns''

	== Tagging New Elements (Optional) ==		== Tagging New Elements (Optional) ==

Dmitry: /* Nested Views */

2024-05-02T18:19:51Z

Nested Views

← Older revision		Revision as of 14:19, 2 May 2024
Line 75:		Line 75:

	== Nested Views ==		== Nested Views ==
	~~In order to create a nested~~ view ~~attribute~~, the Nested_View column ~~will need to reference an existing~~ view ~~in the model~~.		By referencing the name of another view, whether already existing in the model or being added by the same CSV file, in the '''Nested_View''' column, the import can create view sub-structuring or nesting.

	~~For~~ nested views, the Primitive, Platform_Type, and Measurement ~~columns cannot have a value~~.		In view field rows representing nested views, the '''Source''' and '''Path''' columns represent the perspective path under which the view sub-structure is nested. At the same time, the '''Primitive''', '''Platform_Type''', and '''Measurement''' are not applicable.

	~~For nested views~~, the ~~Source now corresponds~~ to the ~~Perspective of the nested~~ view.		By default, all sub-structure nesting view field rows will be inferred to be representing a "private" nesting. This can be made explicit, or toggled off to accomplish a sub-structure import, by using the '''Characteristic_Foreign''' column: if set to "false", the view sub-structure will be private to its nesting view, and an independent import if set to "true".

	== Additional Requirements ==		== Additional Requirements ==

Josh: /* Column-specific Requirements */ Specify how to create nested views via CSV import

2024-04-30T20:12:49Z

Column-specific Requirements: Specify how to create nested views via CSV import

← Older revision		Revision as of 16:12, 30 April 2024
Line 18:		Line 18:
	* Characteristic_Description		* Characteristic_Description
	* Characteristic_Tags		* Characteristic_Tags
			* Lower_Bound
			* Upper_Bound
			* Nested_View

	The order of the columns is not enforced, it does not have to be in the same order as the suggested format above.		The order of the columns is not enforced, it does not have to be in the same order as the suggested format above.
Line 53:		Line 56:
	* Measurement must in the model and realize the Observable at the end of the Path.		* Measurement must in the model and realize the Observable at the end of the Path.

	''For example: '''AirSystemType''' is projected (through payload) from '''elementID''' which is realized by ''UniqueID_Unbounded_Integer'~~'''~~		''For example: '''AirSystemType''' is projected (through payload) from '''elementID''' which is realized by ''UniqueID_Unbounded_Integer'

			=== Lower Bound and Upper Bound ===

			* This row must have both a Source and a Path for these values to be valid

			=== Nested View ===

			* The Nested View must exist in the model and must be the name of a View.
			* See Nested Views for changes to other columns

	== Tagging New Elements (Optional) ==		== Tagging New Elements (Optional) ==
Line 61:		Line 73:

	Package_Tags will tag whichever package is chosen - this includes the Phenom package when a package isn't specified in the Package_Name column.		Package_Tags will tag whichever package is chosen - this includes the Phenom package when a package isn't specified in the Package_Name column.

			== Nested Views ==
			In order to create a nested view attribute, the Nested_View column will need to reference an existing view in the model.

			For nested views, the Primitive, Platform_Type, and Measurement columns cannot have a value.

			For nested views, the Source now corresponds to the Perspective of the nested view.

	== Additional Requirements ==		== Additional Requirements ==

Nathalie: /* Column Specific Requirements */

2022-10-18T19:30:53Z

Column Specific Requirements

← Older revision		Revision as of 15:30, 18 October 2022
Line 25:		Line 25:
	Bulk import can currently import Package, View, and Characteristic elements.		Bulk import can currently import Package, View, and Characteristic elements.

	== Column ~~Specific~~ Requirements ==		== Column-specific Requirements ==
	=== Package Name ===		=== Package Name ===
	* Leaving this column blank will default Package to the "Phenom" package.		* Leaving this column blank will default Package to the "Phenom" package.