Scott Gray wrote: > On 21/04/2010, at 10:59 AM, Adam Heath wrote: > >> Adrian Crum wrote: >>> Scott Gray wrote: >>>> On 21/04/2010, at 10:46 AM, doo...@apache.org wrote: >>>> >>>>> Author: doogie >>>>> Date: Tue Apr 20 22:46:14 2010 >>>>> New Revision: 936100 >>>>> >>>>> URL: http://svn.apache.org/viewvc?rev=936100&view=rev >>>>> Log: >>>>> Add a releaseDate to a product, mostly informational, intended to mean >>>>> when the product was first assembled for purchase, or, for books, when >>>>> it was published initially. >>>> You could always consider adding this description to the field >>>> definition. >>> Wouldn't that make more sense in an inventory item? Our houses have >>> release dates (when they are ready to ship) but they are inventory items >>> - not products. >> There's no inventory available to be purchased yet, so no inventory >> record can possibily exist. This is a completely different situation >> then an book being under current publication, but out of stock. >> >> We use this field to filter products from display, within a window of >> 4 months into the future, and allow users to back-order the product >> before it has been published. > > So would it be correct to say that in your situation: > introductionDate + 4months = releaseDate? > > So you can buy a product as soon as the introductionDate has passed but the > user is informed that it won't be shipped until at least the releaseDate?
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.
