Large amounts of data require a structure that is as easily understandable as possible. The filters allow for a multidimensional assignment of attributes. The types are different.
Each media object can only be assigned one type.
Why is that?
Our concept of data storage is based on the quick findability of media objects while simultaneously assigning attributes to enable a structured distribution.
The types should ensure that the entirety of the data can be reduced with a click on the relevant part and then further refined via the filters, resulting in a quick access to the selection one needs.
Here is an example
Typical type structuring:
Product Images
Secondary Images
Videos
Audios
Mood
Safety Data Sheets
Miscellaneous
In this case, the overall selection of media data, often tens of thousands of records for our customers, can be reduced to, for example, product images. Then, through the filter, the brand can be selected and the sub-brand. This way one reduces from several thousand media data to a smaller selection needed with three clicks.
Structural Guidelines for Types
Types have a defined number and structure:
Up to 3 levels
Up to 7 types per level
This allows for a total of 21 types, distributed over 3 levels with a maximum of 7 types each.
Why do we limit the number of types and levels?
Humans can only quickly process a limited number of data options. Additionally, the layout (UI/UX) must look simple and tidy. Following this principle achieves a system that is easy to operate without needing to read manuals or how-tos beforehand.
The learning curve is extremely low. The challenge is that in advance an appropriate and goal-oriented concept for data storage based on the filters and types is developed. This work is exactly what the agency facilitates in advance.
The functions of filters and types are extremely powerful; however, they should be carefully coordinated and structured in advance.
More stories
The importer in the PIM system
1 minute
The importer in the PIM system
Import Routines
The importer in the PIM system uses the API function of the application. In this process, logics are integrated via JSON file that automatically retrieves a provided CSV or Excel file. Many of our customer applications use this functionality to automatically enrich data in the PIM system or to create new records. The functionality corresponds to the procedure of output via API. However, the import routine offers additional possibilities for data manipulation.
Mapping of Import Data
Data often comes from global systems within a company. There, they are stored in various databases, making it necessary to incorporate multiple importers.
Each import requires a primary characteristic to know which items the data should be enriched with.
The imports can be adjusted by our development team. For example, if specific fields in the import are allocated with acronyms that have a different meaning, this will be mapped with the import. Another use case can be the construction of a product title that is to be assembled from several fields.
Many other scenarios can be realized using this functionality.
The importer in the PIM system
1 minute
The importer in the PIM system
Import Routines
The importer in the PIM system uses the API function of the application. In this process, logics are integrated via JSON file that automatically retrieves a provided CSV or Excel file. Many of our customer applications use this functionality to automatically enrich data in the PIM system or to create new records. The functionality corresponds to the procedure of output via API. However, the import routine offers additional possibilities for data manipulation.
Mapping of Import Data
Data often comes from global systems within a company. There, they are stored in various databases, making it necessary to incorporate multiple importers.
Each import requires a primary characteristic to know which items the data should be enriched with.
The imports can be adjusted by our development team. For example, if specific fields in the import are allocated with acronyms that have a different meaning, this will be mapped with the import. Another use case can be the construction of a product title that is to be assembled from several fields.
Many other scenarios can be realized using this functionality.
The importer in the PIM system
1 minute
The importer in the PIM system
Import Routines
The importer in the PIM system uses the API function of the application. In this process, logics are integrated via JSON file that automatically retrieves a provided CSV or Excel file. Many of our customer applications use this functionality to automatically enrich data in the PIM system or to create new records. The functionality corresponds to the procedure of output via API. However, the import routine offers additional possibilities for data manipulation.
Mapping of Import Data
Data often comes from global systems within a company. There, they are stored in various databases, making it necessary to incorporate multiple importers.
Each import requires a primary characteristic to know which items the data should be enriched with.
The imports can be adjusted by our development team. For example, if specific fields in the import are allocated with acronyms that have a different meaning, this will be mapped with the import. Another use case can be the construction of a product title that is to be assembled from several fields.
Many other scenarios can be realized using this functionality.
The importer in the PIM system
1 minute
The importer in the PIM system
Import Routines
The importer in the PIM system uses the API function of the application. In this process, logics are integrated via JSON file that automatically retrieves a provided CSV or Excel file. Many of our customer applications use this functionality to automatically enrich data in the PIM system or to create new records. The functionality corresponds to the procedure of output via API. However, the import routine offers additional possibilities for data manipulation.
Mapping of Import Data
Data often comes from global systems within a company. There, they are stored in various databases, making it necessary to incorporate multiple importers.
Each import requires a primary characteristic to know which items the data should be enriched with.
The imports can be adjusted by our development team. For example, if specific fields in the import are allocated with acronyms that have a different meaning, this will be mapped with the import. Another use case can be the construction of a product title that is to be assembled from several fields.
Many other scenarios can be realized using this functionality.
Why do we develop PIM and DAM systems?
2 min
Why do we develop PIM and DAM systems?
Digital agency for many years
Through years of work for large corporations such as Procter & Gamble, Unilever, Merz, Duracell, De’Longhi, Coty, Wella, BASF, Knauf, L’Oréal, dm Drogerie, etc., we have learned a lot and recognized that the old patterns of separating data into the respective functional areas still occur and far too frequently.
In this context, the DAM system is seen as the media database of marketing. Product information is firmly in the hands of logistics or R&D, legal information is found in the database of the legal department, and marketing texts are lying dormant in various Word files. Just to name a few examples …
Structural change and rethinking
A key factor is, therefore, providing data on a central platform. We call this Single Point Of Information.
Sounds simple, but it is highly complex. Because technically, data often lies in various places and not always in the best quality. Ten or more sources are not uncommon.
Many specialist areas need to be addressed. We repeatedly notice a certain inertia here.
PIM and DAM systems are a crucial step in the digitization of the company. They lead to significant resource and efficiency advantages and are the foundation for quality, completeness and distribution of product data of all kinds.
Interfaces create performance
Our strategy, therefore, primarily concerns the central provision of data, which should be able to do one thing above all. Sell!
In the establishment, the following aspects must also be fundamentally considered:
Communication within the company, showcasing advantages and disadvantages, breaking down barriers
Making systems as simple as possible to use
Enabling content syndication, API, output containers, gradually implementing download formats
Providing product data and media data in an integrated manner, allowing no media breaks and avoiding duplicate data
Establishing workflows (Traffic Light Indicator, editing, importer, API, approvals, GDSN, etc.)
Here is a statement from our owner Oliver Dietz to conclude:
Experience counts, we notice this every hour and every day of our work. The implementation of a PIM and DAM system is a big step and must be desired, lived, and supported by the management. Only then can barriers be broken down and employees be taken along. This is a communication task that has at least the same importance as the purely technical work. We cover both areas as dietz.digital, as we are a digital agency that has been driving communication for many years and lives digitalization and programming on a daily basis.
Why do we develop PIM and DAM systems?
2 min
Why do we develop PIM and DAM systems?
Digital agency for many years
Through years of work for large corporations such as Procter & Gamble, Unilever, Merz, Duracell, De’Longhi, Coty, Wella, BASF, Knauf, L’Oréal, dm Drogerie, etc., we have learned a lot and recognized that the old patterns of separating data into the respective functional areas still occur and far too frequently.
In this context, the DAM system is seen as the media database of marketing. Product information is firmly in the hands of logistics or R&D, legal information is found in the database of the legal department, and marketing texts are lying dormant in various Word files. Just to name a few examples …
Structural change and rethinking
A key factor is, therefore, providing data on a central platform. We call this Single Point Of Information.
Sounds simple, but it is highly complex. Because technically, data often lies in various places and not always in the best quality. Ten or more sources are not uncommon.
Many specialist areas need to be addressed. We repeatedly notice a certain inertia here.
PIM and DAM systems are a crucial step in the digitization of the company. They lead to significant resource and efficiency advantages and are the foundation for quality, completeness and distribution of product data of all kinds.
Interfaces create performance
Our strategy, therefore, primarily concerns the central provision of data, which should be able to do one thing above all. Sell!
In the establishment, the following aspects must also be fundamentally considered:
Communication within the company, showcasing advantages and disadvantages, breaking down barriers
Making systems as simple as possible to use
Enabling content syndication, API, output containers, gradually implementing download formats
Providing product data and media data in an integrated manner, allowing no media breaks and avoiding duplicate data
Establishing workflows (Traffic Light Indicator, editing, importer, API, approvals, GDSN, etc.)
Here is a statement from our owner Oliver Dietz to conclude:
Experience counts, we notice this every hour and every day of our work. The implementation of a PIM and DAM system is a big step and must be desired, lived, and supported by the management. Only then can barriers be broken down and employees be taken along. This is a communication task that has at least the same importance as the purely technical work. We cover both areas as dietz.digital, as we are a digital agency that has been driving communication for many years and lives digitalization and programming on a daily basis.
Why do we develop PIM and DAM systems?
2 min
Why do we develop PIM and DAM systems?
Digital agency for many years
Through years of work for large corporations such as Procter & Gamble, Unilever, Merz, Duracell, De’Longhi, Coty, Wella, BASF, Knauf, L’Oréal, dm Drogerie, etc., we have learned a lot and recognized that the old patterns of separating data into the respective functional areas still occur and far too frequently.
In this context, the DAM system is seen as the media database of marketing. Product information is firmly in the hands of logistics or R&D, legal information is found in the database of the legal department, and marketing texts are lying dormant in various Word files. Just to name a few examples …
Structural change and rethinking
A key factor is, therefore, providing data on a central platform. We call this Single Point Of Information.
Sounds simple, but it is highly complex. Because technically, data often lies in various places and not always in the best quality. Ten or more sources are not uncommon.
Many specialist areas need to be addressed. We repeatedly notice a certain inertia here.
PIM and DAM systems are a crucial step in the digitization of the company. They lead to significant resource and efficiency advantages and are the foundation for quality, completeness and distribution of product data of all kinds.
Interfaces create performance
Our strategy, therefore, primarily concerns the central provision of data, which should be able to do one thing above all. Sell!
In the establishment, the following aspects must also be fundamentally considered:
Communication within the company, showcasing advantages and disadvantages, breaking down barriers
Making systems as simple as possible to use
Enabling content syndication, API, output containers, gradually implementing download formats
Providing product data and media data in an integrated manner, allowing no media breaks and avoiding duplicate data
Establishing workflows (Traffic Light Indicator, editing, importer, API, approvals, GDSN, etc.)
Here is a statement from our owner Oliver Dietz to conclude:
Experience counts, we notice this every hour and every day of our work. The implementation of a PIM and DAM system is a big step and must be desired, lived, and supported by the management. Only then can barriers be broken down and employees be taken along. This is a communication task that has at least the same importance as the purely technical work. We cover both areas as dietz.digital, as we are a digital agency that has been driving communication for many years and lives digitalization and programming on a daily basis.
Why do we develop PIM and DAM systems?
2 min
Why do we develop PIM and DAM systems?
Digital agency for many years
Through years of work for large corporations such as Procter & Gamble, Unilever, Merz, Duracell, De’Longhi, Coty, Wella, BASF, Knauf, L’Oréal, dm Drogerie, etc., we have learned a lot and recognized that the old patterns of separating data into the respective functional areas still occur and far too frequently.
In this context, the DAM system is seen as the media database of marketing. Product information is firmly in the hands of logistics or R&D, legal information is found in the database of the legal department, and marketing texts are lying dormant in various Word files. Just to name a few examples …
Structural change and rethinking
A key factor is, therefore, providing data on a central platform. We call this Single Point Of Information.
Sounds simple, but it is highly complex. Because technically, data often lies in various places and not always in the best quality. Ten or more sources are not uncommon.
Many specialist areas need to be addressed. We repeatedly notice a certain inertia here.
PIM and DAM systems are a crucial step in the digitization of the company. They lead to significant resource and efficiency advantages and are the foundation for quality, completeness and distribution of product data of all kinds.
Interfaces create performance
Our strategy, therefore, primarily concerns the central provision of data, which should be able to do one thing above all. Sell!
In the establishment, the following aspects must also be fundamentally considered:
Communication within the company, showcasing advantages and disadvantages, breaking down barriers
Making systems as simple as possible to use
Enabling content syndication, API, output containers, gradually implementing download formats
Providing product data and media data in an integrated manner, allowing no media breaks and avoiding duplicate data
Establishing workflows (Traffic Light Indicator, editing, importer, API, approvals, GDSN, etc.)
Here is a statement from our owner Oliver Dietz to conclude:
Experience counts, we notice this every hour and every day of our work. The implementation of a PIM and DAM system is a big step and must be desired, lived, and supported by the management. Only then can barriers be broken down and employees be taken along. This is a communication task that has at least the same importance as the purely technical work. We cover both areas as dietz.digital, as we are a digital agency that has been driving communication for many years and lives digitalization and programming on a daily basis.
Data fields in the PIM system
2 minutes
Data fields in the PIM system
What field types are available in the PIM system?
Single-line text
Multi-line text
Selection fields, dropdowns
Radios
Checkboxes
Units of measurement
etc.
They are available to import, edit, and provide data as structured as possible.
The filters and types also ensure that data can be selected and found.
Units of Measurement
The units of measurement field is a special type consisting of three field types.
Precision (is equal to, approximately, less than, more than)
the value (price, weight, content, quantity, etc.)
and the format (€ , kg, g, cm, mm, etc.).
This can ideally represent ingredients, allergens, vitamins, prices, etc.
Validations, Validities
Fields can be validated based on criteria, such as the input of “text only” or “numbers only”.
The validity of fields is also adjustable. For example, prices or certain characteristics can be set according to a time period. The visibility in the system can also be controlled. This makes it possible to have fields in the system, but only display them in the backend.
Field Limitations
Field limitations are adjustable for multi-line and single-line text. Here, based on bytes or characters. The byte limit is a special case and is, for example, needed to limit the search terms for the Amazon A9 backend keywords to 249 bytes. If it were more, Amazon currently ignores all keywords.
Data fields in the PIM system
2 minutes
Data fields in the PIM system
What field types are available in the PIM system?
Single-line text
Multi-line text
Selection fields, dropdowns
Radios
Checkboxes
Units of measurement
etc.
They are available to import, edit, and provide data as structured as possible.
The filters and types also ensure that data can be selected and found.
Units of Measurement
The units of measurement field is a special type consisting of three field types.
Precision (is equal to, approximately, less than, more than)
the value (price, weight, content, quantity, etc.)
and the format (€ , kg, g, cm, mm, etc.).
This can ideally represent ingredients, allergens, vitamins, prices, etc.
Validations, Validities
Fields can be validated based on criteria, such as the input of “text only” or “numbers only”.
The validity of fields is also adjustable. For example, prices or certain characteristics can be set according to a time period. The visibility in the system can also be controlled. This makes it possible to have fields in the system, but only display them in the backend.
Field Limitations
Field limitations are adjustable for multi-line and single-line text. Here, based on bytes or characters. The byte limit is a special case and is, for example, needed to limit the search terms for the Amazon A9 backend keywords to 249 bytes. If it were more, Amazon currently ignores all keywords.
Data fields in the PIM system
2 minutes
Data fields in the PIM system
What field types are available in the PIM system?
Single-line text
Multi-line text
Selection fields, dropdowns
Radios
Checkboxes
Units of measurement
etc.
They are available to import, edit, and provide data as structured as possible.
The filters and types also ensure that data can be selected and found.
Units of Measurement
The units of measurement field is a special type consisting of three field types.
Precision (is equal to, approximately, less than, more than)
the value (price, weight, content, quantity, etc.)
and the format (€ , kg, g, cm, mm, etc.).
This can ideally represent ingredients, allergens, vitamins, prices, etc.
Validations, Validities
Fields can be validated based on criteria, such as the input of “text only” or “numbers only”.
The validity of fields is also adjustable. For example, prices or certain characteristics can be set according to a time period. The visibility in the system can also be controlled. This makes it possible to have fields in the system, but only display them in the backend.
Field Limitations
Field limitations are adjustable for multi-line and single-line text. Here, based on bytes or characters. The byte limit is a special case and is, for example, needed to limit the search terms for the Amazon A9 backend keywords to 249 bytes. If it were more, Amazon currently ignores all keywords.
Data fields in the PIM system
2 minutes
Data fields in the PIM system
What field types are available in the PIM system?
Single-line text
Multi-line text
Selection fields, dropdowns
Radios
Checkboxes
Units of measurement
etc.
They are available to import, edit, and provide data as structured as possible.
The filters and types also ensure that data can be selected and found.
Units of Measurement
The units of measurement field is a special type consisting of three field types.
Precision (is equal to, approximately, less than, more than)
the value (price, weight, content, quantity, etc.)
and the format (€ , kg, g, cm, mm, etc.).
This can ideally represent ingredients, allergens, vitamins, prices, etc.
Validations, Validities
Fields can be validated based on criteria, such as the input of “text only” or “numbers only”.
The validity of fields is also adjustable. For example, prices or certain characteristics can be set according to a time period. The visibility in the system can also be controlled. This makes it possible to have fields in the system, but only display them in the backend.
Field Limitations
Field limitations are adjustable for multi-line and single-line text. Here, based on bytes or characters. The byte limit is a special case and is, for example, needed to limit the search terms for the Amazon A9 backend keywords to 249 bytes. If it were more, Amazon currently ignores all keywords.