Product entities and/or product nodes??!! ... how to handle my bookstore catalogue in DCommerce?
Hi, thank for this great work ... but I really feel confused about the new way of handling with product entities and product nodes.
I thought that the D7 structure would have allowed to simply face a product class as a content type node, and a product instance as a node content instance itself,
but it seems not so obvious ... it seems we need the product entity.
I have read all you posts regarding the product entity/node topic, also the brainstorming ones ... to better get the sense and the advantages of this approach. But still I have great doubts if I have succeded in making it mine too.
I have to implement a library catalogue for a publisher (first task), with ecommerce (bookstore) functionalities (second phase task), also with authors and so on ...
The catalogue contains some pubblications (products) and that contain "articles" (1-n relationship) that would be products themeselves too. A structure similar to a music store that sells cds and single tracks belonging to them ...
Now please help me! Because this is not so clear at all.
Is the store the place where I should define just the "product types" entities (with basic information and basic price ... ecc.), and product would be datailed and istanced as nodes, or the store is the place where to input all the single items of the bookstore catalogue, with all the characteristics and details attached to them?
The first approach (define in the store just the product classes with basic attributes) would be for me the best and more flexible one.
In the product nodes I would be able to "extend" the product entities (classes) in the store and instance them several times.
This would also help me to more easily create the library catalogue, without ecommerce functionalities, at the beginning, and implement commerce beaviours and attributes in a second time. Something similar to what is actually possible in Ubercart with classes definition (http://www.ubercart.org/docs/user/10963/understanding_product_classes).
But how to differentiate prices and other characteristics for specific instances (nodes?) of the single products?
I am seriously worrying if in this DC framework I should instead put all the specific definitions (and instances?) of the products in my library catalogue in the store, as product entities …
But I don't see how this store interface would accomplish to manage (list, filter, search, ecc.) a great amount of product classes and instances …
Should we write down all the views for the store lists?
I am worrying also regarding the ones (bookstore managers) that will have to implement the catalogue and the instances of the store.
Their process and workflow should the easiest possible … and for sure shouldn't include a double entries for the same catalogue item …
Sorry for my written english, and for the quite confused explanation, but I feel seriously disoriented:
it seems to me not clear at all the use of the store and the single-product-entity definition workflow in it,
potentially too much complicate, to be real.
I can understand the need from a developer point of you (after reading your posts and video presentation) but should sound really less complicate to the store manager point of you, at the same time. Or at least much more clear …
Really would like to get the proper way in understanding the natural workflow of DC … because I really feel there is something I am not getting,
Hope someone might give "the light" … as really feel in some dark now.
Thanks in advance