Who would benefit? |
Data administration / PIM users |
What impact would it make? |
Reduction of hours of mapping or allow for re-mapping projects to take place. Would also allow for an overview of the current mappings without having to do multiple exports and then lookups in excel |
How should it work? |
As a data administrator I want to be able to handle multiple entity relations at one time and in bulk so that the relations can be consistent and require as few clicks as an upload/export allows to achieve Upload file with column headings of the relation. Cells include the entity system id or unique identifier that can be delimited so multiples can be linked at once. Should allow for Product, Node, Resources and related items Have attached an image of an excel file that uses the idea of the system ids of each of the entity relations towards an item The export file for relations could be separate from the current data export file as usually data fixes and relationship fixes are separately handled. It would be better if it wasn't using the system id but something like an item code field or product code field etc. It would also be ideal if relations can be removed via the upload as if a product has 50 out of 100 incorrectly linked items, this means each have to be removed one by one from the product |
Why is it needed? |
Currently relating entities together can be very time consuming as it can only be done in the inriver interface. There is an extension that can do item to product but can't work if you need multiple entities linked together; therefore won't work for resources and related items. Related items also cannot be exported from inriver therefore all work surrounding them must be done in the system - checking this information for each item on a large scale is very time consuming The current way relations works is ok if focusing on one item but scaled up to thousands, the ability to fix errors or map new entities is better off avoided. |
Additional feedback, background or context: