[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913184#comment-16913184 ]
Pierre Smits commented on OFBIZ-10966:
--------------------------------------
Having had a look at the images provided in this ticket I would say that the user experience can be enhanced more. Currently the menubar at [
https://demo-trunk.ofbiz.apache.org/webtools/control/EntityImport |
https://demo-trunk.ofbiz.apache.org/webtools/control/xmldsdump]shows a lot of choices that are basically (from the user perspective) doing the same thing:
# XML Data Export
# XML Data Export All
# JSON Data Export
# JSON Data Export All
# XML Data Import
# JSON Data Import
For many of these the user experienced can be enhanced by a simple refactoring so that the user has less options in the menu bar and is guided in the screens form to get to the desired result (e.g. via a drop-down field), leading to e.g:
# Menu Item: 'Import'
# Import Form
## All
## XML
## JSON
## etc. (e.g. csv)
And the same can be applied to the export choices.
> JSON entity data import and export utility
> ------------------------------------------
>
> Key: OFBIZ-10966
> URL:
https://issues.apache.org/jira/browse/OFBIZ-10966> Project: OFBiz
> Issue Type: New Feature
> Components: framework
> Reporter: Jayansh Shinde
> Assignee: Mathieu Lirzin
> Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch, OFBiz-Web-Tools-JSON-Data-Export-All.png, OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
> <Party partyId="123456" partyTypeId="PERSON" statusId="PARTY_ENABLED"/>
> {code}
> {code:java}
> {“Party”: {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for this)
> 2.) On successful validation, convert JSON to OFBiz's entity model (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for e.g we can write JsonDataHandler, it will convert given JSON to List<GenericValue>, and finally write it to database (Similar pattern is used in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
Locked
