Consider creating a metdataio top level subdirectory

[jprestop]

Describe the Task

Look into what would need to change to create a metdataio subdirectory at the top level of the repository so that METdataio can be easily imported. This issue came up when testing on WCOSS2 Acorn. A pytest for METreformat was trying to import METdataio, however, the top level directory was named METdataio-2.0.0 from obtaining the released package. The METcalcpy, METplotpy, and METplus repositories currently have metcalcpy, metplotpy, and metplus subdirectories to allow for easy importing.

How big of a code change is this? It would be good to have consistency across repositories and to handle this in the Pythonic way. Note there will likely be code changes needed in the other repositories due to this change (if it is made).

Additionally, there needs to be a way for METviewer, METplus, and other entities to access version information

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

??

Funding Source

??

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 PROJECT 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.
• 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.