I like your approach, and my recommendation is to try and stick with the existing model. The combination between products, parties, stores and roles should be robust for your needs. However, I think you will probably need some custom logic around the processing of buyers and sellers since you're developing an exchange kind of market.
I think maybe your custom logic is going to cover mostly the code _before_ a transaction happens between buyers and sellers. Maybe you can use the "opportunity" or "quote" or "requirement" entity to drive the follow up until a deal is closed at which time you trigger maybe an order which drives everything else. It depends on how you're exactly designing your system. On Tue, Mar 20, 2018 at 1:13 AM, Rajesh Mallah <mallah.raj...@gmail.com> wrote: >> >> My Question is: is the below linkage of products to PartyID ( seller) >> PartyID --> Facility --> Store --> Catalog -> Product Category -> Products. >> feasible? ---- (Q1) >> > > I could see that it is possible to relate a Party with each of the above > entities > via Entities > > FacilityParty , ProductStoreRole , ProdCatalogRole , ProductCategoryRole , > ProductRole > respectively. > > regds > mallah. > > > > > > > On Mon, Mar 19, 2018 at 11:07 PM, Rajesh Mallah <mallah.raj...@gmail.com> > wrote: > >> Hi >> >> I am trying to model a use case with many sellers and buyers. >> >> There is a large intersection in the sets of item that these sellers >> shall be dealing with. >> >> I have gone through some of the resources (documentation) that >> covers entities like Categories , Products , Catalog , Store etc. >> >> My Question is: is the below linkage of products to PartyID ( seller) >> >> PartyID --> Facility --> Store --> Catalog -> Product Category -> Products. >> feasible? ---- (Q1) >> >> We would want to maintain a Global Category Tree/Hierarchy for all sellers >> but I am thinking of duplicating the products from a master list of >> products >> for each Seller (ie, partyID) . As each sellers might want to add their own >> version of content (i.e, marketing pitch) for these generic(OEM) products. >> >> Eg: A concrete product is lets say a "LED Monitor" under "Electronics" >> category , >> there can be many manufactures of LED Monitors with their own specs >> and variations. >> >> The idea of having a global category and catalog is to make their on >> boarding >> easier so that they quickly get started by indicating the items they they >> would >> want to copy into their catalogs. >> >> Q2: Do/Should I also duplicate categories for each seller catalog ? >> >> any comments/guidance are solicited. >> >> regds >> mallah. >>
