chronicle-etl
chronicle-etl copied to clipboard
📜 A CLI toolkit for extracting and working with your digital history
Simplest idea: displaying parsed README.md in CLI. Todos: - strip out badges - look into parsing bug for sequence of markdown headers
As identified in #24, activating all installed plugins at the same time will lead to dependency problems. We often need to know which connectors are available (eg. `$ chronicle-etl connectors:list`)...
- description and basic readme - installed? - latest version - installed version - connectors and authorizers - link to repo - link to source
A plugin might have different ways of extracting the same type of records. For example, youtube history can come from a Google Takeout export, the official API, or a scraper....
For investigating structure of extractor results Could also just add a flag to show only headers for json/table/csv loaders.
And raise an exception if not provided. Typically oauth authorizers need at minimum a `client_id` and `client_secret`.