Date

06 Jun 2018

Attendees

• user-c2913

• Amy Steiker

• Frank Schaffer
• David Auty
• Timothy Goff
• user-787a4

Goals

• Discuss "required nodes"
• Discuss "related nodes"
• Ensure we have a plan or good idea for handling the echoforms performance issues detailed in EDSC-1596.
• Discuss read-only fields within an echoform to develop plan for EDSC-1690

Discussion items

• Related nodes
  • C1236303848-NSIDC_ECS
    
    • If you choose GeoTiff, some parameters are not available (not relevant)
  • Relevant nodes?
  • Every time you check something, we re-draw the tree
    • Key question: Will selecting something (anything) in the parameter tree ever result in another node in the tree being required/not available?
      • If no, we would not need to re-draw the tree upon every mouse click
    • If we ignore a click event for some period of time we could limit the number of events/re-draws that are fired.
  • We default the tree to everything being selected.
    • In general, users want everything. Previous selections are saved.
• Simplification
  • What if we turned off simplification?

Documentation Notes

From Tim Goff:

The ECHO forms specification document.  This is years out of date and only covers the echo forms core functionality and doesn't cover things like the tree widget which is both a newer feature and an extension to the spec:https://cdn.earthdata.nasa.gov/conduit/upload/1478/ECHO_Forms_Specification_0.pdf

The ECHO forms schema, which can be used to validate forms can be found at https://api.echo.nasa.gov/legacy-services/wsdl/EchoForms.xsd, and is documented at https://api.echo.nasa.gov/legacy-services/echoforms/index.html.  This schema includes new extensions such as the tree widget.  

The echo forms plugin itself is implemented at https://github.com/nasa/edsc-echoforms, and the README there includes info on compiling and using the plugin.  

The most useful thing within the echo forms repo for users of the echo forms plugin (i.e. providers and SDPS) is the forms demo page.  This page, at `demo/index.html` within the repo can be opened in a browser and will allow you to paste in a form and test it out.  It also provides a sample form which attempts to show many of the features of echo-forms.  This can be an invaluable resource when trying to implement a form and see what it looks like to the end user.  The output is not skinned exactly the way it will appear in EDSC, but is functionally the same.

Action items

• user-c2913 follow up on the EDO issues related to form modifications and default selections. (EDO-1063 and EDO-1064).
• David Auty answer the following: Will selecting something (anything) in the parameter tree ever result in another node in the tree being required/not available?
• Ryan Abbott to look into an alternate to current tree viewer.
• Amy Steiker to confirm the assumption that users want or don't want everything as a default. The answer to this could help initial loading times.
• Amy Steiker consult with NSIDC team to discuss updating spatial subsetting fields to be read only and adding verbiage to the form communicating what users are doing when using that option.