Please enable JavaScript.
Coggle requires JavaScript to display documents.
DAM: Language - Coggle Diagram
DAM: Language
Key Questions
Can we consolidate Basic: Language with Content Info
Language even thought Content Info Lang is multi-valued or do we keep both and derive what Basic: Language should be?
-
-
-
-
What is the best way to address TITAN-1275 for BSP
Given we aren't changing Correlation language until Flex does can se delete Titan-1035
-
-
Strategy
-
-
Programatically match the legacy LDS Code for languages to the new ISO 3 letter code for as many as possible. The remaining codes will be manually updated using add'l information by PSD and possibly the 2 char format which is the native AEM method.
In AEM the tab display is just a visual so we can shuffle the fields to be more useful and meaningful while also anticipating a restructure of translated assets that get translated while each points back to the same shared binary
-
-
System Updates
AEM
-
-
-
-
ID assets that do not resolve to a unique combination of codes for country, region and script so PSD operations can manually address those
-
-
-
-
Add fields to the AEM Asset Importer table/script :check: Titan-1636
-
-
-
-
-
-
-
Titan
-
-
-
-
Add "Country Code" as a new property with a tool-tip "ISO 3166-1" to Content Info :check: Titan-1643
Add Content Info: Language with tool-tip "(ISO 639-3)" :check: Titan-1643
-
-