Catalog personalization: Integration to the catalog management UI

VirtoCommerce / vc-platform

Virto Commerce B2B Innovation Platform

https://virtocommerce.com

Other

1.23k stars 845 forks source link

Catalog personalization: Integration to the catalog management UI #1142

Closed tatarincev closed 7 years ago

tatarincev commented 7 years ago

[ ] Extend Product and Category details meta-forms with new listbox field User groups which support multi selection and gets available data from UserGroups setting defined in customer module. Actual selected data for host objects should be taken from personalization module API. api/personalization/taggeditems/{id}/{type}
[ ] All of this 'User groups' field changes does not a part of the host product changes transaction and all of these changes must be immediately send to the API.

megafreeman commented 7 years ago

@tatarincev @IgorisB @Woland2k As an alternative implementation of UI, I propose to consider the option using a widget and two new blades to assign and manage tags. new wireframe 1

This blades can be used to manage tags for both users, and for products, categories, etc.

OlegoO commented 7 years ago

megafreeman commented 7 years ago

@IgorisB @Woland2k Do we need to support a large number of tags? It depends on whether we need searching, sorting and pagination in blades.

Woland2k commented 7 years ago

@megafreeman

Ticket should be moved under personalization module
UI proposed by @OlegoO is good with grid list (that way we can support unlimited number of tags).
Create UI for adding/removing tags from list of available tags.

megafreeman commented 7 years ago

@Woland2k @OlegoO After discussion with @tatarincev we came to the conclusion that in this case, we need to create just one blade to assign and remove tags. For managing all tags we will use the standard settings dictionary editor blade. new wireframe 1 copy

megafreeman commented 7 years ago

@Woland2k About the first item of your message, this ticket is a part of Epic and Sprint. So, if I will move this ticket under personalization module, then I should move other tickets from this Sprint too. Maybe we should finish this Sprint in current repository, and new tickets will create under personalization module?

Woland2k commented 7 years ago

@megafreeman tickets should be created in the module they are related to, so yes, move them, right now they are in platform which they don't have any connection to

UI doesn't look very user friendly, as it is not clear when you need to click save and when you need to click delete and to what those action correspond, UI by @OlegoO is more intuitive

megafreeman commented 7 years ago

Issue moved to VirtoCommerce/vc-module-catalog-personalization #1 via ZenHub