Better module organization

[jbusecke]

@andersy005 @norlandrhagen since I expect that we will add a bunch more stuff here as part of the data-management/catalog refactor I would like to organize things a bit better.

As far as I can see we will have the following categories of code (each of which should probably have its own module?):

• Custom Beam Stages for CMIP 'cmip-transforms.py' Refactor out cmip specific tools #9
• Custom Beam Stages for data-management 'data-management-transforms.py'. Refactor out Copy and Inject_Attrs Transforms. LEAP_template_feedstock#31 is related.
• Custom Code for the Catalog (are there several categories here?) 'catalog.py'
• Python code for data-management (e.g. this helper function in Deactivate Copy stage on local run LEAP_template_feedstock#27) -> Move to 'data-management-stages'

Can you add to the list of things here, and also naming suggestions are very welcome ☺️

[norlandrhagen]

This seems great! @jbusecke do you think Custom Code for the Catalog and Python code for data-management should live in separate repos?

[jbusecke]

This seems great! @jbusecke do you think Custom Code for the Catalog and Python code for data-management should live in separate repos?

At this point data-management is explicitly the repo that builds our catalog, and where people request new datasets, nothing else? I am thinking we might actually consolidate this repo in data-management too? Lets discuss this.