Closed ericbusboom closed 8 years ago
Similar to #149, but extend the content manager to navigate the entire library, not just a single bundle.
The paths that the content manager handles would start with sources, then bundles, ( the cache_key paths )
Inside a bundle, there would be:
sources source_tables <one entry per source table> destination_tables <one entry per dest table> bundle.py bundle.yaml test.py Notebooks <one entry per notebook>
The user could navigate around to edit files. Tables would open a table editor. The bundle.yaml would open a dedicated metadata editor.
There would also have to be a control pane to run the bundle.
Similar to #149, but extend the content manager to navigate the entire library, not just a single bundle.
The paths that the content manager handles would start with sources, then bundles, ( the cache_key paths )
Inside a bundle, there would be:
The user could navigate around to edit files. Tables would open a table editor. The bundle.yaml would open a dedicated metadata editor.
There would also have to be a control pane to run the bundle.