Adam Heath-2 wrote: > > introductionDate is when the store actually added the product to their > catalog, and started making it available, which may be completely > different then when it was first published. >
What struck me about this is that products in all sorts of enterprise verticals may have a whole host of "dates" and other product metadata that may be pertinent. As a result, I would have thought use of ProductFeature or perhaps a ProductAttribute might be have been a better fit from a business pov (ignoring benefits with a strongly typed field). When selling books, is it not possible that you have a "publish date" which may be different from a "pre-order" date (which appears to be your use case here)? I would want to look at the model but I would have thought that there is some control of what products may be back-ordered (aka a pre-order) already in place ... perhaps the only support is a boolean flag at this time ... hmmm Definitely willing to be completely wrong here; but those things struck me when I read this a few hours ago ... -- View this message in context: http://n4.nabble.com/Re-svn-commit-r936100-in-ofbiz-trunk-applications-product-entitydef-applications-product-servicedef--tp2018179p2018370.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
