Uploaded image for project: 'OFBiz'
  1. OFBiz
  2. OFBIZ-6976

Updating data sets

    XMLWordPrintableJSON

    Details

      Description

      This is a placeholder issue.

      Having correct data shipped with OFBiz is key to not only

      1. have a good operational state (meaning adopters can work with OFBiz out of the box)
      2. have a good data set for demonstration purposes
      3. have a good data set to enable unit, system integration and acceptance testing

      Re aspect 1:
      This encompasses all security, system property and other seed data sets

      Re aspect 2:
      This encompasses all data records in the various DemoData.xml files. This kind of data needs to be coherent from the perspective of the main internal organisation (or the legal demo party) that operates the OFBiz implementation.

      Re aspect 3:
      The data set for this aspect encompasses all data under aspect 1 and 2.

      With a good data set for demonstration purposes it is easier for potential adopters (and their influencers) to see the added value of implementing OFBiz in their company/organisation, while at the same time it helps developers to understand the coherence between widgets, templates, services, functions and other data counter parts. Also, good demo data helps contributors to identity issues regarding the usability of OFBiz, work to resolve them and ultimate improve OFBiz.

      Demo data sets should be grouped in accordance to the component load order (as defined in e.g. component-load.xml, see links below). The first appearance of a data record of the demo kind should also (as much as possible) be in accordance with where the related entity is defined and where the first appearance of related seed data records are defined. For guidance see the entity reference (per link below)

      Example 1:
      The ProductStore entity is defined in the entity model for the Product component (the product-entitymodel.xml).

      Thus any new demo record regarding this ProductStore entity should first appear in the ProductDemoData.xml file.

      Example 2:
      Following record is defined in WorkEffortTypeData.xml

      <WorkEffortType description="Project" hasTable="N" workEffortTypeId="PROJECT"/>
      

      Thus any first appearance of a demo record for the WorkEffort entity with the defined workEffortTypeId="PROJECT" should appear in the WorkEffortDemoData.xml file

      With the above we minimise the risk of duplication and dependency mismatches

        Attachments

        1. ORRTIZ-OFBiz-6976.pdf
          247 kB
          Pierre Smits

          Issue Links

          1.
          Update content type data - sql queries Sub-task Closed Michael Brohl  
          2.
          move base component demo data from specialpurpose/ecommerce to base components Sub-task Closed Michael Brohl  
          3.
          Improve Content Component data set Sub-task Patch Available Pierre Smits  
          4.
          load demo data failure Sub-task Closed Deepak Dixit  
          5.
          Improve Rental DemoData Sub-task Closed Pierre Smits

          100%

          Original Estimate - Not Specified Original Estimate - Not Specified
          Time Spent - 20m
          6.
          Have TaxAuthority demo data for the Tax Authority of China Sub-task Closed Pierre Smits  
          7.
          Improve WebPOS data set Sub-task In Progress Pierre Smits  
          8.
          Improve Product Component data sets Sub-task Patch Available Pierre Smits  
          9.
          Improve Party Component data set(s) Sub-task Patch Available Pierre Smits  
          10.
          Improve Order Component data set(s) Sub-task Patch Available Pierre Smits  
          11.
          Improve WorkEffort data set(s) Sub-task Patch Available Pierre Smits  
          12.
          Improve Accounting Component data set(s) Sub-task Patch Available Pierre Smits  
          13.
          Improve Humanres plugin data set(s) Sub-task Patch Available Unassigned  
          14.
          Improve Manufacturing plugin data set(s) Sub-task Patch Available Pierre Smits  
          15.
          Improve Marketing plugin data set(s) Sub-task Patch Available Pierre Smits  
          16.
          Improve CommonExt Component data set(s) Sub-task Patch Available Pierre Smits  
          17.
          Improve SecurityExt Component data set(s) Sub-task Open Unassigned  
          18.
          Improve AssetMaint plugin data set(s) Sub-task Patch Available Pierre Smits  
          19.
          Improve the ProjectMgr plugin data set(s) Sub-task Patch Available Pierre Smits  
          20.
          Improve ecommerce component data set(s) Sub-task Patch Available Pierre Smits  
          21.
          Improve myportal component data set(s) Sub-task Patch Available Pierre Smits  
          22.
          Improve ebay component data set(s) Sub-task Patch Available Pierre Smits  
          23.
          Improve scrum component data set(s) Sub-task Patch Available Pierre Smits  
          24.
          Improve webpos component data set(s) Sub-task In Progress Pierre Smits  

            Activity

              People

              • Assignee:
                pierresmits Pierre Smits
                Reporter:
                pierresmits Pierre Smits
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m