Production Package features (5h)

[GoogleCodeExporter]

What do we need from Production?
  * products (unit is missing)
  * product categories
  * manofacturers
  * product tags (action, discount, sale, homepage, ...)
  * additional product attributes (metadata)
  * attributes groups (attributes can be added singled or in groups)
  * product variations
  * related products (one way or both way relation? - one way)
  * product discussions (comments)
  * product rating

Original issue reported on code.google.com by horak.honza@gmail.com on 20 Nov 2009 at 8:52

[GoogleCodeExporter]

action products, new products, ... can be defined by chackbox or on the basis of
properties (inserted in the last month, action price is set, ...)

Original comment by horak.honza@gmail.com on 20 Nov 2009 at 9:18

[GoogleCodeExporter]

metadata can be added more times to one object (for example images)

Original comment by horak.honza@gmail.com on 24 Nov 2009 at 1:00

[GoogleCodeExporter]

Original comment by horak.honza@gmail.com on 24 Nov 2009 at 1:01

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Items in the store, avaibility (hours, days)

Original comment by horak.honza@gmail.com on 7 Dec 2009 at 9:40

[GoogleCodeExporter]

Properties sets can be set to category and all products from the category uses 
this set.

Original comment by horak.honza@gmail.com on 10 Dec 2009 at 11:23

[GoogleCodeExporter]

properties defined in db?

Original comment by horak.honza@gmail.com on 22 Dec 2009 at 7:37

[GoogleCodeExporter]

Definition in the DB is good way, it has following advantages:
  * properties defined specialy for project
  * maybe all metadata can be defined in db in the future, aparat will be done
  * easier definition of groups and variations
  * possible properties groups

So there are following tables:
  * products (standard attributes - price, quantity unit, name, text, store items,
main image, ...)
  * product_units (foreign key)

  * categories (has foreign key to prop_groups)
  * products_categories (connection)

  * prop_definition (property can "specifies" the product or only "describes" it)
  * prop_options
  * prop_values

  * prop_groups
  * prop_groups_connect (connection)

  * groups
  * products_group (connection)

  * tags
  * product_tag (connection)

  * comments

Original comment by horak.honza@gmail.com on 2 Jan 2010 at 9:07

[GoogleCodeExporter]

- We don't need tags.
+ we will use price history in one attribute.

Original comment by horak.honza@gmail.com on 2 Jan 2010 at 9:09

[GoogleCodeExporter]

we need to add: 
+ VAT
+ price definition (price with/without VAT, action price, discount, discount 
price...
when one is defined, other is computed)

Original comment by horak.honza@gmail.com on 2 Jan 2010 at 10:01

[GoogleCodeExporter]

Discount and VAT is count with the same algorithm, while first is count 
discount,
then VAT:

1. price_with_discount | discount + price_without_discount => 
price_with_discount +
price_without_discount + discount
2. price_with_vat      | vat      + price_without_vat => price_with_vat +
price_without_vat + vat

Cannot be filled all three values (check by javascript or validation while 
sending form)

Original comment by horak.honza@gmail.com on 2 Jan 2010 at 10:16

[GoogleCodeExporter]

Check will be done by javascript and by validation while sending form.

Original comment by horak.honza@gmail.com on 3 Jan 2010 at 6:36

[GoogleCodeExporter]

So we need JS functions something like that:

... onchange="price.auto(this, 2, ['auto', 'price_without_vat'])" ...

where: 2 is general price precision (defined in Config)

Note: "onchange" can be changed to "onkeydown" or "onblur" for beware of cycling

Original comment by horak.honza@gmail.com on 3 Jan 2010 at 7:31

[GoogleCodeExporter]

What about another picture by all variants? black camera, pink camera, etc... 
How to
do that? 

Not necessary to implement it now, but maybe in the future...

Generally attributes could be specific to variation (which is only property
specifying the product itself). So we should have a possibility to establish a
connection between two properties.

So.. properties_definition will have relation N:M to properties_definition, 
which
will say: "prop1=image_red.jpg only when prop2=id_red"

Original comment by horak.honza@gmail.com on 6 Jan 2010 at 6:56

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Filtering will be detached by categories.
Only full-text search will be implements across the categories.

Original comment by horak.honza@gmail.com on 10 Jan 2010 at 12:19

[GoogleCodeExporter]

Subcategory implementation (function like tags)

Original comment by horak.honza@gmail.com on 10 Jan 2010 at 12:21

[GoogleCodeExporter]

Price settings:
  * we will not set the final price (with vat/without vat), always there is both
  * in config the price ordering will be set (which prices are editable and which are
computed)
    * without discount, discount -> final price | original price
    * without discount, final price -> discount | original price
    * discount, final price -> without discount | original price
  * in the future settings can be set by product and stored in session

Original comment by horak.honza@gmail.com on 10 Jan 2010 at 1:20

[GoogleCodeExporter]

There must not be both prizes, because if the vat value changes, one price 
would have
to be re-counted - bad idea. 

So there will be only one price (with vat) + original + without discount.

Original comment by horak.honza@gmail.com on 13 Jan 2010 at 10:48

[GoogleCodeExporter]

Original comment by horak.honza@gmail.com on 28 Jan 2010 at 11:53

• Changed state: Started

[GoogleCodeExporter]

Original comment by horak.honza@gmail.com on 12 Mar 2010 at 1:08

• Changed title: Production Package features (5h)

[GoogleCodeExporter]

Original comment by horak.honza@gmail.com on 30 May 2010 at 7:30

• Added labels: Priority-Medium
• Removed labels: Priority-High