datafile Import support for mapping categories
---------------------------------------------- Key: OFBIZ-2583 URL: https://issues.apache.org/jira/browse/OFBIZ-2583 Project: OFBiz Issue Type: New Feature Affects Versions: SVN trunk Reporter: BJ Freeman this is code and an entity that uses simple key map to convert the Categories that an Import file may have to categories in the particular of biz. example the import file has leisure and sport|camping/hiking|accessories as the key and hik_acc would be the returned value. this is setup to import a cvc file or input key map from the UI I took the base code from address map. I did add a feature to look up the categories in the ui At this point the services are not tied into the datafile code but is called from the custom import routine. I will probably edit this after I look at it later. :D -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[ https://issues.apache.org/jira/browse/OFBIZ-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BJ Freeman updated OFBIZ-2583: ------------------------------ Priority: Minor (was: Major) > datafile Import support for mapping categories > ---------------------------------------------- > > Key: OFBIZ-2583 > URL: https://issues.apache.org/jira/browse/OFBIZ-2583 > Project: OFBiz > Issue Type: New Feature > Affects Versions: SVN trunk > Reporter: BJ Freeman > Priority: Minor > > this is code and an entity that uses simple key map to convert the Categories that an Import file may have to categories in the particular of biz. > example the import file has > leisure and sport|camping/hiking|accessories as the key and hik_acc would be the returned value. > this is setup to import a cvc file or input key map from the UI > I took the base code from address map. > I did add a feature to look up the categories in the ui > At this point the services are not tied into the datafile code but is called from the custom import routine. > I will probably edit this after I look at it later. :D -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BJ Freeman updated OFBIZ-2583: ------------------------------ Attachment: OFBIZ-2583ProdImportCategoryMatchEntity.patch this is the entity to support the service it has been tested on 9.04 next will provide the service and simple methods. then the import examples used with datafiles. > datafile Import support for mapping categories > ---------------------------------------------- > > Key: OFBIZ-2583 > URL: https://issues.apache.org/jira/browse/OFBIZ-2583 > Project: OFBiz > Issue Type: New Feature > Affects Versions: SVN trunk > Reporter: BJ Freeman > Priority: Minor > Attachments: OFBIZ-2583ProdImportCategoryMatchEntity.patch > > > this is code and an entity that uses simple key map to convert the Categories that an Import file may have to categories in the particular of biz. > example the import file has > leisure and sport|camping/hiking|accessories as the key and hik_acc would be the returned value. > this is setup to import a cvc file or input key map from the UI > I took the base code from address map. > I did add a feature to look up the categories in the ui > At this point the services are not tied into the datafile code but is called from the custom import routine. > I will probably edit this after I look at it later. :D -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BJ Freeman updated OFBIZ-2583: ------------------------------ Description: when importing data using the datafile code, the data may have different categories or a hierachy of categories that need to be translated to ofbiz categories. this will augment the datafile code to match data catagories to the ofbiz categories. first one will use a datafile record to create the ProdImportCategoryMatch entity from the datafile with a default "auto" for the prodCategory field. when the data record is read, the service will see the auto and parse the category string and create categories, not already created with the rollup. as the last operation it will add the string with the last category as in the string as the prodCategory field in the entity. next when the data is read in, it will look for the category string in the ProdImportCategoryMatch entity and replace the ImportCategoryString with the prodCategory field if there is more than one entry in the ProdImportCategoryMatch it will walk down the sequence and add the product to each category. was: this is code and an entity that uses simple key map to convert the Categories that an Import file may have to categories in the particular of biz. example the import file has leisure and sport|camping/hiking|accessories as the key and hik_acc would be the returned value. this is setup to import a cvc file or input key map from the UI I took the base code from address map. I did add a feature to look up the categories in the ui At this point the services are not tied into the datafile code but is called from the custom import routine. I will probably edit this after I look at it later. :D Affects Version/s: Release Candidate Branch 10.04 Release Branch 9.04 > datafile Import support for mapping categories > ---------------------------------------------- > > Key: OFBIZ-2583 > URL: https://issues.apache.org/jira/browse/OFBIZ-2583 > Project: OFBiz > Issue Type: New Feature > Affects Versions: Release Branch 9.04, Release Candidate Branch 10.04, SVN trunk > Reporter: BJ Freeman > Priority: Minor > Attachments: OFBIZ-2583ProdImportCategoryMatchEntity.patch > > > when importing data using the datafile code, the data may have different categories or a hierachy of categories that need to be translated to ofbiz categories. > this will augment the datafile code to match data catagories to the ofbiz categories. > first one will use a datafile record to create the ProdImportCategoryMatch entity from the datafile with a default "auto" for the prodCategory field. > when the data record is read, the service will see the auto and parse the category string and create categories, not already created with the rollup. as the last operation it will add the string with the last category as in the string as the prodCategory field in the entity. > next when the data is read in, it will look for the category string in the ProdImportCategoryMatch entity and replace the ImportCategoryString with the prodCategory field > if there is more than one entry in the ProdImportCategoryMatch it will walk down the sequence and add the product to each category. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BJ Freeman updated OFBIZ-2583: ------------------------------ Attachment: OFBIZ-2583ProdImportCategoryMatchEntity.patch this is the right version. > datafile Import support for mapping categories > ---------------------------------------------- > > Key: OFBIZ-2583 > URL: https://issues.apache.org/jira/browse/OFBIZ-2583 > Project: OFBiz > Issue Type: New Feature > Affects Versions: Release Branch 9.04, Release Candidate Branch 10.04, SVN trunk > Reporter: BJ Freeman > Priority: Minor > Attachments: OFBIZ-2583ProdImportCategoryMatchEntity.patch > > > when importing data using the datafile code, the data may have different categories or a hierachy of categories that need to be translated to ofbiz categories. > this will augment the datafile code to match data catagories to the ofbiz categories. > first one will use a datafile record to create the ProdImportCategoryMatch entity from the datafile with a default "auto" for the prodCategory field. > when the data record is read, the service will see the auto and parse the category string and create categories, not already created with the rollup. as the last operation it will add the string with the last category as in the string as the prodCategory field in the entity. > next when the data is read in, it will look for the category string in the ProdImportCategoryMatch entity and replace the ImportCategoryString with the prodCategory field > if there is more than one entry in the ProdImportCategoryMatch it will walk down the sequence and add the product to each category. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BJ Freeman updated OFBIZ-2583: ------------------------------ Attachment: (was: OFBIZ-2583ProdImportCategoryMatchEntity.patch) > datafile Import support for mapping categories > ---------------------------------------------- > > Key: OFBIZ-2583 > URL: https://issues.apache.org/jira/browse/OFBIZ-2583 > Project: OFBiz > Issue Type: New Feature > Affects Versions: Release Branch 9.04, Release Candidate Branch 10.04, SVN trunk > Reporter: BJ Freeman > Priority: Minor > Attachments: OFBIZ-2583ProdImportCategoryMatchEntity.patch > > > when importing data using the datafile code, the data may have different categories or a hierachy of categories that need to be translated to ofbiz categories. > this will augment the datafile code to match data catagories to the ofbiz categories. > first one will use a datafile record to create the ProdImportCategoryMatch entity from the datafile with a default "auto" for the prodCategory field. > when the data record is read, the service will see the auto and parse the category string and create categories, not already created with the rollup. as the last operation it will add the string with the last category as in the string as the prodCategory field in the entity. > next when the data is read in, it will look for the category string in the ProdImportCategoryMatch entity and replace the ImportCategoryString with the prodCategory field > if there is more than one entry in the ProdImportCategoryMatch it will walk down the sequence and add the product to each category. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847929#action_12847929 ] Jacques Le Roux commented on OFBIZ-2583: ---------------------------------------- As you know BJ, as a new feature it will be commited only in trunk. > datafile Import support for mapping categories > ---------------------------------------------- > > Key: OFBIZ-2583 > URL: https://issues.apache.org/jira/browse/OFBIZ-2583 > Project: OFBiz > Issue Type: New Feature > Affects Versions: Release Branch 9.04, Release Candidate Branch 10.04, SVN trunk > Reporter: BJ Freeman > Priority: Minor > Attachments: OFBIZ-2583ProdImportCategoryMatchEntity.patch > > > when importing data using the datafile code, the data may have different categories or a hierachy of categories that need to be translated to ofbiz categories. > this will augment the datafile code to match data catagories to the ofbiz categories. > first one will use a datafile record to create the ProdImportCategoryMatch entity from the datafile with a default "auto" for the prodCategory field. > when the data record is read, the service will see the auto and parse the category string and create categories, not already created with the rollup. as the last operation it will add the string with the last category as in the string as the prodCategory field in the entity. > next when the data is read in, it will look for the category string in the ProdImportCategoryMatch entity and replace the ImportCategoryString with the prodCategory field > if there is more than one entry in the ProdImportCategoryMatch it will walk down the sequence and add the product to each category. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847937#action_12847937 ] BJ Freeman commented on OFBIZ-2583: ----------------------------------- the only way I can provide patches is against a relative stable code, and the code I work with. So I will submit them as working with 9.04 so if someone want to add them, they may. also if someone want submit them to the trunk they are aware that they will have to check it out first. the only other way I know of is to put these patches on my site. > datafile Import support for mapping categories > ---------------------------------------------- > > Key: OFBIZ-2583 > URL: https://issues.apache.org/jira/browse/OFBIZ-2583 > Project: OFBiz > Issue Type: New Feature > Affects Versions: Release Branch 9.04, Release Candidate Branch 10.04, SVN trunk > Reporter: BJ Freeman > Priority: Minor > Attachments: OFBIZ-2583ProdImportCategoryMatchEntity.patch > > > when importing data using the datafile code, the data may have different categories or a hierachy of categories that need to be translated to ofbiz categories. > this will augment the datafile code to match data catagories to the ofbiz categories. > first one will use a datafile record to create the ProdImportCategoryMatch entity from the datafile with a default "auto" for the prodCategory field. > when the data record is read, the service will see the auto and parse the category string and create categories, not already created with the rollup. as the last operation it will add the string with the last category as in the string as the prodCategory field in the entity. > next when the data is read in, it will look for the category string in the ProdImportCategoryMatch entity and replace the ImportCategoryString with the prodCategory field > if there is more than one entry in the ProdImportCategoryMatch it will walk down the sequence and add the product to each category. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847943#action_12847943 ] Jacques Le Roux commented on OFBIZ-2583: ---------------------------------------- As I already said there are not much changes in this component so I hope most of it can be commited to trunk without much work. And as I'm used to do such work I will do it if it is worth it > datafile Import support for mapping categories > ---------------------------------------------- > > Key: OFBIZ-2583 > URL: https://issues.apache.org/jira/browse/OFBIZ-2583 > Project: OFBiz > Issue Type: New Feature > Affects Versions: Release Branch 9.04, Release Candidate Branch 10.04, SVN trunk > Reporter: BJ Freeman > Priority: Minor > Attachments: OFBIZ-2583ProdImportCategoryMatchEntity.patch > > > when importing data using the datafile code, the data may have different categories or a hierachy of categories that need to be translated to ofbiz categories. > this will augment the datafile code to match data catagories to the ofbiz categories. > first one will use a datafile record to create the ProdImportCategoryMatch entity from the datafile with a default "auto" for the prodCategory field. > when the data record is read, the service will see the auto and parse the category string and create categories, not already created with the rollup. as the last operation it will add the string with the last category as in the string as the prodCategory field in the entity. > next when the data is read in, it will look for the category string in the ProdImportCategoryMatch entity and replace the ImportCategoryString with the prodCategory field > if there is more than one entry in the ProdImportCategoryMatch it will walk down the sequence and add the product to each category. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847947#action_12847947 ] BJ Freeman commented on OFBIZ-2583: ----------------------------------- yes since this is using simple methods should not cause to much of problem I appreciate your support, as always. > datafile Import support for mapping categories > ---------------------------------------------- > > Key: OFBIZ-2583 > URL: https://issues.apache.org/jira/browse/OFBIZ-2583 > Project: OFBiz > Issue Type: New Feature > Affects Versions: Release Branch 9.04, Release Candidate Branch 10.04, SVN trunk > Reporter: BJ Freeman > Priority: Minor > Attachments: OFBIZ-2583ProdImportCategoryMatchEntity.patch > > > when importing data using the datafile code, the data may have different categories or a hierachy of categories that need to be translated to ofbiz categories. > this will augment the datafile code to match data catagories to the ofbiz categories. > first one will use a datafile record to create the ProdImportCategoryMatch entity from the datafile with a default "auto" for the prodCategory field. > when the data record is read, the service will see the auto and parse the category string and create categories, not already created with the rollup. as the last operation it will add the string with the last category as in the string as the prodCategory field in the entity. > next when the data is read in, it will look for the category string in the ProdImportCategoryMatch entity and replace the ImportCategoryString with the prodCategory field > if there is more than one entry in the ProdImportCategoryMatch it will walk down the sequence and add the product to each category. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
Free forum by Nabble | Edit this page |