SOA introduced Grid Editor to Semantics Manager beginning v6.7. The most significant impact is its incompatibility to our implementation of Context Properties. Specifically, when variable MDE assets are concerned, the current configuration requires users to first identify a top-level MDES of which individual properties are to be associated with. In other words, the individual properties are nested under this top-level MDES property. The Grid Editor does not support nested properties. The following screenshot demonstrates how the context properties for CDASH's AEACN are associated to the top-level MDES CDASH^MDES 1.1:
To circumvent this we can adjust the configuration to "flatten" Context Property so that it will no longer appear nested. This approach has impacts to these areas:
- Configuration: Will need to remove the "mdes-name-version" property from the property group
- Existing assets: For assets that already use the nested properties feature, will need to reload their context properties. This includes all versions of SDTM, plus CDASH and SEND.
- Stack exports: Column headers in the export will change to not include the "mdes-name-version" portion
- Programs: Both the import file generation and programmatic QC programs will need to adjusted to reflect this configuration change
No impact to asset versioning scheme is expected. Nested context properties exists only for variable MDE assets, which are bound to domain MDES assets that are eventually bound to the top-level MDES asset.
We will be able to benefit these advantages by pursuing this "flattening" approach:
- Reap the full benefit of the new Grid Editor so that user can edit all classifiers and properties, not partial
- The structure of the exports is notorious to be complex. This will help reduce the complexity.
Other considerations:
- Perform configuration changes first in SHARE-Sandbox
- Reload at least one impacted foundational standards using the flattened context properties
- Perform test to all impacted areas
Overview
Content Tools