Content Onboarding: Enhance Field Mapping with Source-Based View and Localization Filters

How

Enhance the Content Onboarding field mapping experience by introducing a Source-Based Mapping View in addition to the current Target-Based Mapping View.

Currently, the target fields are fixed and users map source columns from the uploaded file. Provide an option to switch between:

• Target-Based Mapping (current experience)

• Source-Based Mapping (display source columns first and allow users to map them to target fields)

Additionally, introduce a filter to:

• Show or hide locale-specific fields.

• Display only the default language (for example, English) fields by default.

• Allow users to expand and view localized fields only when needed.

This would give users the flexibility to choose the mapping approach they are most comfortable with while improving usability for multilingual data onboarding.

Why

From a business user perspective, the current target-based mapping approach can be difficult to navigate, especially when dealing with large data sets and entities containing numerous localized fields.

Users often need to scroll through an extensive list of target fields to find the appropriate mappings. The presence of locale-specific fields further increases complexity and makes field selection more time-consuming.

Providing a source-based mapping option and localization filters would:

• Make the mapping process more intuitive.

• Reduce scrolling and search time.

• Improve usability for non-technical users.

• Simplify onboarding of multilingual content.

• Allow users to focus on relevant fields during the mapping process.

Who Benefits

• Content Editors

• Product Owners

• Business Users responsible for content onboarding and bulk content updates

• Data Migration Teams

• Translation and Localization Teams

Impact

This enhancement would significantly improve the efficiency of the content onboarding process by making field mapping faster and easier to manage.

Key benefits include:

• Reduced time spent searching for target fields.

• Improved user experience for business users and content editors.

• Faster onboarding of large data files.

• Better handling of multilingual content through localization filters.

• Potential performance improvements by displaying only relevant fields instead of loading all available fields by default.