{"id":47389,"date":"2013-09-05T11:13:48","date_gmt":"2013-09-05T11:13:48","guid":{"rendered":"https:\/\/www.akeneo.com\/blog\/inside-akeneo-2-data-quality-completeness\/"},"modified":"2024-07-04T06:55:47","modified_gmt":"2024-07-04T06:55:47","slug":"inside-akeneo-2-data-quality-completeness","status":"publish","type":"post","link":"https:\/\/www.akeneo.com\/fr\/blog\/inside-akeneo-2-data-quality-completeness\/","title":{"rendered":"Inside Akeneo #2 – Data quality & completeness"},"content":{"rendered":" \n \n
\n
\n
\n
\n
\n
\n
\n
\n
\n Product Experience<\/span>\n <\/div>\n

Inside Akeneo #2 – Data quality & completeness<\/h1>\n
\n\n

We talked in our previous post about the relation between channels and scoped attributes in Akeneo.Another important channel-related mantra to keep in…<\/p>\n <\/div>\n <\/div>\n <\/div>\n

\n
\n \"\" <\/div>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n <\/section>\n \n We talked in our previous post<\/a> about the relation between channels and scoped attributes in Akeneo.
Another important channel-related mantra to keep in mind for our future users is : \u00ab\u00a0There is no mandatory attribute in Akeneo<\/em>\u00ab\u00a0. It means that an user will never be prevented to create or save a product because he only has a small part of the required data for your product.\r\n\r\nIn Akeneo we are making a clear distinction between \u00ab\u00a0working with products<\/em>\u00a0\u00bb and \u00ab\u00a0exporting products<\/em>\u00ab\u00a0. PIM is all about product lifecycle – so we believe that it’s perfectly OK to work with incomplete products. But not to export incomplete products.<\/strong>\r\n\r\nSo we need to define what is a complete product. This definition can vary :\r\n