It won't fit in that format

[ishanijerin1]

The above settings are enough to input data into PIM . However, it is not as easy as you can transfer all the data .

Many of the items to be migrated will not be able to be stored properly in PIM without processing .

For example, there are cases where the options for an item value defined in the PIM as "Black, White, Red" are written in a pattern like " Black , White , Red " in why you need this database existing data. In such cases, it may be possible to deal with the problem by first processing the data before loading it, or by using an ETL tool in between, but with Contentserv , it is also possible to specify the following data processing settings.

String Replacement

Converting uppercase / lowercase

Extracting a part of a string

trim

JSON selector

XPATH selector

String Splitting

Addition / subtraction etc.

For items with different wordings for the options mentioned above, it is possible to specify the mapping of corresponding options using a function called "Value Range Mapping".

contentserv-value-range-mapping.png



In addition to the functions introduced here, Contentserv also offers a variety of processing functions , but ( like most systems other than AI ) it is powerless against unorganized data. Unfortunately, if organized data does not exist, you will have to go down the thorny path of manually inputting the data one by one.

In that case, you will need to make compromises such as "not managing old products" or "managing only best-selling products first" rather than trying to prepare all products at once .

This time, we talked about "data migration" while introducing Contentserv 's features. We hope you were able to understand the appeal of Contentserv, which can help you with all your needs . In the next issue, we plan to introduce Contentserv's operational features, such as data quality management.