Grid form and reference form edits

[taylor13]

Issue Type

Not specified

Affected Areas

All/Multiple Areas

Description

Issues pertinent to multiple forms:

• I think “Issue Handling Metadata”, which appears at the bottom of the form, should be moved to the top and renamed “Initial Submission or Update?”. If the user selected “Update”, then we could ask the user to select from a drop-down listing the model, grid, model component, or whatever to be revised, and then pre-populate the form with the already registered information. The user would then simply enter any missing information or revise whatever existing information was incorrect. [If this is a big job, leave it until March.]
• At the bottom of some forms appears a list of tags (e.g., “Assignee”, “Labels”, “Issue type”, “Project”, “Miilestone”). Can we remove these? Some folks might think they’re supposed to do something with them.
• Under some items listed on a form are bulleted lists of apparently explanatory sentences, but I didn’t find them generally useful. They didn’t seem to correspond to the list of items you’re supposed to select from. I would simply point users to the appropriate section of the EMD document where the items are described.
• At the top of each form, I think we should link to the section of the EMD document where the information is described that we want entered on the form. We should make it clear that we don’t expect users to fill out the form without first referencing the EMD document.

Reference Registration:

• We should provide an example of what should appear in the “Add a title” box. It says “Add/Modify: Reference: ”. Should this be the source_id the references support? Should it be the source_id + model component? Should it be the name of the person submitting the reference information?

Vertical Computational Grid Registration:

• Since we say the “vertical grid IDs are automatically generated” what should a user enter for the title which says to “Type grid ID here”? Perhaps the title for a new grid should always be “New Grid”. For revision of an existing grid, the known grid i.d. could be entered as the title, and we could pre-populate the form with all the existing grid characteristics of the already existing grid. Revisions to these could be then made without re-entering all the information.
• Under “Vertical Coordinate”, I don’t think we should show the bulleted information. I don’t see how it is helpful. We could point to section 7.11 of the EMD document for further information.
• Under “Number of Layers”, replace text with “For grids with a fixed number of layers in the vertical, enter number of mass layers; leave blank otherwise”
• “Under Layer Range”, replace text with “For grids for which the number of layers in the vertical varies spatially and/or temporally, enter the minimum and maximum number layers”

Horizontal Grid Cells Registration

• Since we say the “Grid cell IDs are automatically generated” what should a user enter for the title which says to “Type grid ID here”? Perhaps the title for a new grid should always be “New Grid”. For revision of an existing grid, the known grid i.d. could be entered as the title, and we could pre-populate the form with all the existing grid characteristics of the already existing grid. Revisions to these could be then made without re-entering all the information.

Horizontal Subgrid Registration

• Not sure what to enter for subgrid ID (see above)
• How will we know which “horizontal grid cells” definition goes with each registered Subgrid?

Horizontal Computational Grid registration

• Not sure what to enter for subgrid ID (see above)
• How will we know which “horizontal Subgrid” definitions go with each horizontal computational grid?

I wonder if all 3 of the grid forms shouldn’t be combined into a single form so we could associate a particular set of subgrids or grid cell definitions with each of the higher level grids definitions?

Expected/Desired Behavior

No response

Steps to Reproduce (for bugs)

No response

Priority

Not specified

Help Needed

No response

[wolfiex]

Tags labels and metadata options are not for users. These are automatically preset based on the entry point to the form and are the only way to allow issue handling. Otherwise the script does not know what do with with the form and the reviewers are unable to extract a list of relevant submissions to look over.

The title is also automatically set and they do not need to enter anything, but I agree that the default (legacy) placeholder is misleading and was intending to change it. The title issue persists across all files. The field is required in order not to duplicate forms for modification. I agree that it should be made clearer. Ideally I would hide the issue title box but this is not possible.

We had already planned to include the relevant sections of the EMD in collapsable sections of the forms and @davidhassell has made a start on writing this.