Why is it worthwhile to use a classification system such as ETIM or ECLASS?
The Pimcore Classification Store is the perfect platform for such an implementation. While Pimcore object bricks have some issues with duplicate definitions and their performance for such a high number of product attributes, the Pimcore Classification Store is the perfect platform to integrate classification systems like ECLASS or ETIM into Pimcore.
However, some standard features from the Pimcore Classification Store do not comply with ETIM / ECLASS regulations and need to be adapted for integration:
Only one class may be selected from at a time, so we suppressed the collections and introduced a restriction to only one selectable group. Then we introduced the translations of the groups and keys of the classification, based on the translations provided by ETIM or ECLASS including grid view support for translations, batch mapping, and CSV exports. Last but not least, we defined that only certain values are allowed for the same attribute, depending on the class in which the attribute is displayed as well as grid-view support for translations, batch mapping, and CSV exports.
ETIM and ECLASS also provide texts and translations of legends and value legends in many languages as part of the classifications. These translations are automatically imported into the admin translations of Pimcore. These translations can be used to perform exports of the data from Pimcore. Additionally, the translations are visible in the Pimcore backend while maintaining the product data.
API connection by using the specified API or web services from ETIM or ECLASS
Classified integration of ETIM / ECLASS into Pimcore Classification store is done automatically via API / web service or based on XML / CSV data. We can import all required classes with their attributes, values and translations. To avoid flooding the classification store with unneeded attributes, only those classes are imported that are suitable for the specified products. By configuration, a whitelist of these classes can be managed. If additional classes are required, this whitelist can be extended. Similarly flexible is the import and deployment of different versions of the classification. The integration supports different ETIM / ECLASS releases also simultaneously / in parallel.
Implementation of the functionality in Pimcore
Technically, the implementation is provided as a Pimcore bundle. In this bundle you configure the required classes and credentials for the API. Via your API, the import of the entire classification is triggered by console commands.
On our roadmap we have some further developments of ETIM or ECLASS integrations. We would like to connect the non-ETIM or ECLASS attributes in Pimcore to the classification store. This enhancement avoids duplicate content maintenance when you have multiple internal attributes that match some official attributes in ETIM or ECLASS. In addition, we are working on managing the mappings of different ETIM classes to be able to migrate retained values. Also upcoming are the new ETIM-8 modeling classes called "ETIM-MC" to classify BIM data.
Want to submit a guest post to Pimcore's Blog?
Submit a guest post and benefit from our network! With our newsletter, we reach more than 4 000 subscribers and attract more than 50 000 monthly visitors to our website, and we're always looking for more brilliant contributors to join our ranks. Contact us.