Model Import Options - Revision history

Chris: /* Retain Auto Generated Content */

2026-09-10T13:55:57Z

Retain Auto Generated Content

← Older revision		Revision as of 09:55, 10 September 2026
Line 125:		Line 125:
	\|summary=Preserves any automatically generated content PHENOM may have added during export.		\|summary=Preserves any automatically generated content PHENOM may have added during export.

	\|details=In some cases during model export, PHENOM may add some innocuous content to ensure the validity of the exported model. Such content is labeled as being auto-generated by PHENOM. When this option is selected, PHENOM will keep this content when importing the model. As an example of when this occurs, consider the case when a query joins ''though'' an entity but does not reference any of its attributes (this is a valid possibility). When this occurs, a corresponding platform entity is created, but it does not have any attributes and fails validity checks. In this case, PHENOM would add an attribute (typically an identifier) to ensure validity.		\|details=In some cases during model export, PHENOM may add some innocuous content to ensure the validity of the exported model. Such content is labeled as being auto-generated by PHENOM. By default, this content is removed upon import. When this option is selected, PHENOM will keep this content when importing the model. As an example of when this occurs, consider the case when a query joins ''though'' an entity but does not reference any of its attributes (this is a valid possibility). When this occurs, a corresponding platform entity is created, but it does not have any attributes and fails validity checks. In this case, PHENOM would add an attribute (typically an identifier) to ensure validity.

	\|language=ini		\|language=ini

Chris: /* Retain Entity Models */

2026-09-10T13:54:50Z

Retain Entity Models

← Older revision		Revision as of 09:54, 10 September 2026
Line 112:		Line 112:
	\|summary=Retains all Logical and Platform Entities and Associations.		\|summary=Retains all Logical and Platform Entities and Associations.

	\|details=Except in some special cases, the Logical and Platform entity models can be fully derived. The only downside is that this can change the values of the element's GUIDs. Typically, this only happens once when a model is imported into PHENOM. However, if it is necessary to retain the original entity model, this option should be selected.		\|details=Except in some special cases, the Logical and Platform entity models can be fully derived. The only downside is that this can change the values of the element's GUIDs. Typically, this only happens once when a model is imported into PHENOM. However, if it is necessary to retain the original entity model, this option should be selected. This should be used in conjunction with the corresponding Model Export Option.

	\|language=ini		\|language=ini

Chris: /* Retain Queries */

2026-09-10T13:50:29Z

Retain Queries

← Older revision		Revision as of 09:50, 10 September 2026
Line 97:		Line 97:
	\|values=Checked / Unchecked		\|values=Checked / Unchecked

	\|summary=~~This will retain all platform queries. Upon export, if these queries remains unchanged, they will be exported "as~~-~~is." When not enabled, exported queries may look slightly different (but will retain~~ the ~~same semantic)~~.		\|summary=Preserves query nodes in their entirety for re-introduction into the model at time of export.

	\|details=On import, ~~PHENOM transforms platform~~ queries ~~into~~ a		\|details=Normally, PHENOM’s import discards queries and re-generates them upon export. This approach, however, fails to preserve the exact values stored in query element attributes, including the GUID, name, description, and specification. By choosing to retain queries, a user is able to re-introduce them upon export. This preserves the GUID, name, and description of the queries. Additionally, if the semantics of the related view were not changed by the user, the specification will also be preserved.
	This ~~will retain all platform~~ queries. ~~Upon export~~, if ~~these queries remains unchanged~~, ~~they~~ will be ~~exported "as-is." When not enabled, exported queries may look slightly different (but will retain the same semantic)~~.

	\|language=ini		\|language=ini

Chris: /* Process CDM Queries */

2026-09-10T13:48:40Z

Process CDM Queries

← Older revision		Revision as of 09:48, 10 September 2026
Line 73:		Line 73:
	\|summary=Process Conceptual Queries so they are retained on import.		\|summary=Process Conceptual Queries so they are retained on import.

	\|details=Phenom does not natively maintain conceptual queries. However, it can capture the projections encoded in those queries by turning them into views in which each of the query’s select clauses is turned into a field. The logical and platform attributes will be filled in with placeholder values; updating these provides an easy way to realize the imported conceptual queries into exported logical and platform queries and templates.		\|details=Phenom does not natively maintain conceptual queries. However, it can capture the projections encoded in those queries by turning them into views in which each of the query’s select clauses is turned into a field. The logical and platform attributes will be filled with placeholder values; updating these provides an easy way to realize the imported conceptual queries into exported logical and platform queries and templates.

	\|language=ini		\|language=ini

Chris: /* Process LDM Queries */

2026-09-10T13:48:24Z

Process LDM Queries

← Older revision		Revision as of 09:48, 10 September 2026
Line 86:		Line 86:
	\|summary=Process Logical Queries so they are retained on import.		\|summary=Process Logical Queries so they are retained on import.

	\|details=~~PHENOM~~ does not ~~store or process Logical Queries, however~~, it ~~is possible to import~~ the ~~data~~ in ~~such~~ a ~~way that this data is retains. This ensures Logical Queries are retained when imported~~. ~~This uses the query-specified measurements and creates generic~~ platform ~~elements in~~ the ~~model with "placeholders" where~~ platform ~~type would otherwise be specified~~.		\|details=Phenom does not natively maintain logical queries. However, it can capture the projections encoded in those queries by turning them into views in which each of the query’s select clauses is turned into a field. The platform attributes will be filled with placeholder values; updating these provides an easy way to realize the imported logical queries into exported platform queries and templates.

	\|language=ini		\|language=ini

Chris: /* Process CDM Queries */

2026-09-10T13:47:38Z

Process CDM Queries

← Older revision		Revision as of 09:47, 10 September 2026
Line 73:		Line 73:
	\|summary=Process Conceptual Queries so they are retained on import.		\|summary=Process Conceptual Queries so they are retained on import.

	\|details=~~PHENOM~~ does not ~~store or process Conceptual Queries, however~~, it ~~is possible to import~~ the ~~data~~ in ~~such~~ a ~~way that this data is retains~~. ~~This ensures Conceptual Queries are retained when imported. This uses the query-specified observables and creates generic~~ logical and platform ~~elements~~ in the ~~model with "placeholders" where~~ logical and platform ~~type would otherwise be specified~~.		\|details=Phenom does not natively maintain conceptual queries. However, it can capture the projections encoded in those queries by turning them into views in which each of the query’s select clauses is turned into a field. The logical and platform attributes will be filled in with placeholder values; updating these provides an easy way to realize the imported conceptual queries into exported logical and platform queries and templates.

	\|language=ini		\|language=ini

Chris: /* Unbounded CDM Mode */

2026-09-10T13:44:13Z

Unbounded CDM Mode

← Older revision		Revision as of 09:44, 10 September 2026
Line 58:		Line 58:
	\|summary=Applies PHENOM's recommended bounds to imports element ''if not explicitly specified''.		\|summary=Applies PHENOM's recommended bounds to imports element ''if not explicitly specified''.

	\|details=PHENOM best practices recommend bounds that differ from the defaults defined by the FACE Technical Standard. This will apply the PHENOM-recommended bounds - (1..) for all composed attributes/participants and (0..) for all participant source roles. NOTE: this will not overwrite existing bounds - this only applies the PHENOM-recommended values when no explicit bounds are set.		\|details=PHENOM best practices recommend bounds that differ from the defaults defined by the FACE Technical Standard. This will apply the PHENOM-recommended bounds - (0..) for all composed attributes/participants and (0..) for all participant source roles. NOTE: this will not overwrite existing bounds - this only applies the PHENOM-recommended values when no explicit bounds are set.

	\|language=ini		\|language=ini
	}}		}}


	=Query Processing & Content Retention Options=		=Query Processing & Content Retention Options=

Chris: /* Fix View Characteristics w/o name */

2026-09-10T13:43:08Z

Fix View Characteristics w/o name

← Older revision		Revision as of 09:43, 10 September 2026
Line 30:		Line 30:
	\|summary=Ensures that each view characteristic has a name. When a name is not specified, it is taken from the corresponding platform attribute.		\|summary=Ensures that each view characteristic has a name. When a name is not specified, it is taken from the corresponding platform attribute.

	\|details=The FACE Technical Standard allows the name to be omitted from a view attribute. When this is done and a name is needed (e.g., during data type generation), the names are used from the corresponding attribute in the entity model. This option makes the names explicit at the time of import. Note: this ~~option~~ only ~~affects~~ FACE v2.1 models.		\|details=The FACE Technical Standard allows the name to be omitted from a view attribute. When this is done and a name is needed (e.g., during data type generation), the names are used from the corresponding attribute in the entity model. This option makes the names explicit at the time of import. Note: this only applies to FACE v2.1 models.

	\|language=ini		\|language=ini

Chris: /* Fix View Characteristics w/o name */

2026-09-10T13:42:50Z

Fix View Characteristics w/o name

← Older revision		Revision as of 09:42, 10 September 2026
Line 24:		Line 24:
	===Fix View Characteristics w/o name===		===Fix View Characteristics w/o name===
	{{Checkbox Option		{{Checkbox Option
	\|name=Fix ~~paths not ending in Observable~~		\|name=Fix View Characteristics w/o name
	\|default=Checked		\|default=Checked
	\|values=Checked / Unchecked		\|values=Checked / Unchecked
Line 30:		Line 30:
	\|summary=Ensures that each view characteristic has a name. When a name is not specified, it is taken from the corresponding platform attribute.		\|summary=Ensures that each view characteristic has a name. When a name is not specified, it is taken from the corresponding platform attribute.

	\|details=The FACE Technical Standard allows the name to be omitted from a view attribute. When this is done and a name is needed (e.g., during data type generation), the names are used from the corresponding attribute in the entity model. This option makes the names explicit at the time of import.		\|details=The FACE Technical Standard allows the name to be omitted from a view attribute. When this is done and a name is needed (e.g., during data type generation), the names are used from the corresponding attribute in the entity model. This option makes the names explicit at the time of import. Note: this option only affects FACE v2.1 models.

	\|language=ini		\|language=ini

Chris: /* Fix paths not ending in Observable */

2026-09-10T13:41:59Z

Fix paths not ending in Observable

← Older revision		Revision as of 09:41, 10 September 2026
Line 18:		Line 18:
	\|values=Checked / Unchecked		\|values=Checked / Unchecked
	\|summary=If a path ends in an entity or association, this will find an attribute in the entity and terminate on that instead.		\|summary=If a path ends in an entity or association, this will find an attribute in the entity and terminate on that instead.
	\|details=Although allowed by the FACE Technical Standard, pointing to an entire entity (or association) limits model extensibility. This import option fixes your model by moving that endpoint from the entity to an attribute.		\|details=Although allowed by the FACE Technical Standard, pointing to an entire entity (or association) limits model extensibility. This import option fixes your model by moving that endpoint from the entity to an attribute. Note: this only applies to FACE v2.1 models.
	\|language=ini		\|language=ini
	}}		}}