[jira] Created: (OFBIZ-560) Seperate Product Store Settings from Product Store

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (OFBIZ-560) Seperate Product Store Settings from Product Store

Nicolas Malin (Jira)
Seperate Product Store Settings from Product Store
--------------------------------------------------

                 Key: OFBIZ-560
                 URL: http://issues.apache.org/jira/browse/OFBIZ-560
             Project: OFBiz (The Open for Business Project)
          Issue Type: Wish
          Components: product
            Reporter: Chris Howe
            Priority: Minor


ProductStore is maintaining settings information that you might wish to keep track of changes of or have time dependencies.  While it would be my preference to have all of these settings stored in ProductStoreAttributes, I think the best bet to be able to achieve a consensus on this is to break off those settings into their own entity with .fromDate and .thruDate.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (OFBIZ-560) Seperate Product Store Settings from Product Store

Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463833 ]

Chris Howe commented on OFBIZ-560:
----------------------------------

I've committed an initial data model concept for this in the ofbiz-sandbox project.  

http://ofbiz-sandbox.svn.sourceforge.net/viewvc/ofbiz-sandbox/ofbiz-sandbox/trunk/hot-deploy/ProductStoreSettings/entitydef/entitymodel.xml?revision=8&view=markup

I'm really quite fond of using this approach for denormalized data.  I also think this is a good way to handle denormalized data that is being introduced from other components.  The numerous extend-entity definitions would naturally be in the components near their related application logic.

This implementation would greatly help in reporting and the creation of custom time periods as you may be able to more easily create reports that reflect changes in store policies to see how those changes are affecting results of your business.

(community) Please let me know your thoughts on this and if anyone would like to collaborate with me to complete this integration.  

> Seperate Product Store Settings from Product Store
> --------------------------------------------------
>
>                 Key: OFBIZ-560
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-560
>             Project: Apache OFBiz (The Open for Business Project)
>          Issue Type: Wish
>          Components: product
>            Reporter: Chris Howe
>            Priority: Minor
>
> ProductStore is maintaining settings information that you might wish to keep track of changes of or have time dependencies.  While it would be my preference to have all of these settings stored in ProductStoreAttributes, I think the best bet to be able to achieve a consensus on this is to break off those settings into their own entity with .fromDate and .thruDate.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira