Consider creating an XML schema for mv_batch.sh's XML configuration file

[bikegeek]

Describe the Task

The current XML configuration file used by the MVBatch code (via mv_batch.sh) does not conform to a
schema.

• There are examples of XML config files that define which plots to generate either by defining everything under one element, or multiple elements, with one element as a parent and other elements that inherit from the parent (via an inherits attribute).

• For some other config files, the <plot_fix> (used to define the fixed values) can be formatted differently for MODE via an additional element that is absent in non-MODE configuration files.

• By creating a schema, this clarifies to end-users what is expected and can be validated to ensure that no malicious code can be inserted into the database.

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 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

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

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

Labels

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)

Milestone and Projects

• Select Milestone as a METviewer-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a METviewer-X.Y.Z version, select the METviewer-X.Y.Z Development project

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.
• 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 issue
  Select: Milestone as the next official version
  Select: METviewer-X.Y.Z Development project for development toward the next official release
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.