steps to run the build *.json file program

[konica-mulani]

steps to build a json file.docx

Please let me know if you do/don't see the application as described in step 2 after double clicking on the file mentioned in step 1 by commenting in this thread

@ONLfwood @LessGoudarzi @sshowalter-OL @ekrall2 @DarekImadi @okmhygv

[LessGoudarzi]

@dgriswold12

[konica-mulani]

Hello All,

I created an application that outputs a json file that can be used to make charts on NEMS DV. It's a user interface that intakes grafnem table number & names; row number & names to generate the corresponding stub of labels among other input parameters (like chart type, years etc.) and returns a json block to plot the label in NEMS DV.

Please check if you can run the application. The steps to run it are written in the comment above and if there's anything that I didn't explain clearly please mention here so I can make corrections in the documentation. I hope you can tell me by the end of this week if you were able to run it.

Thank you.

@ONLfwood @LessGoudarzi @sshowalter-OL @ekrall2 @DarekImadi @okmhygv @dgriswold12

[sshowalter-OL]

Thanks Konica. The application opened on Dolphin with no issues and I was able to use it to create a .json file with a bar graph. It was generally pretty easy to use, but I would suggest the following updates that would make it even easier:

• The input boxes for Title and Chart Type are far to the right of the "Title" and "Type" labels. These should be next to the labels if possible. The same is true for the input box for "Years".
• For chart type, I would suggest a drop down menu with the options.
• When you type "enter", the cursor should move to the next input box (if possible)
• I would change "Optname" to "Label"
• If possible, add some limited instructions to the application box itself, such as an example of what "Optsym" should be, and a note to choose as many tables and rows as needed.
• The name of the output file should include the chart title and chart type (for example, Capacity_Bar.json).
• You might want to note somewhere that the current application is designed for AEO19 charts. The stubs and table options can change from AEO to AEO. You may need to update the application for use with the AEO2020 when we have it up and running.