Describe the Task

Modify the format of the METplus Components Python Requirements table. At the METplus Engineering meeting on 20240109 (and at previous meetings) it was noted that this table is difficult to read because users have to scroll over and it is hard to keep track of the information in the row.

A drop down format was suggested in place of the table. Mark up a few rows of the table (to start) in a feature branch to be in a drop down style format and get feedback from the team to see if this is a better way to proceed. Please start by only doing a few rows and getting feedback from the team, before proceeding with converting the whole table.

Time Estimate

1 to 3 days of work.

Sub-Issues

Consider breaking the task down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

None

Funding Source

Per Tara, Lisa should split her time between
2702691 | JNT DTC NSF BASE FUN…
2784543 | NOAA R2O METp SW2
2799991 | Met Office METplus S…

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Task Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Add any new Python packages to the METplus Components Python Requirements table.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.