We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The data cleaning part of the document-to-podcast workflow could be made more robust, as currently it does not take into account all possible cases.
Have also considered: https://github.com/VikParuchuri/marker, which could be an interesting alternative to 'markitdown'.
Re-implementing the data cleaning component to use markitdown
This would make the data cleaning component for robust, and potentially re-useable across many Blueprints.
There is potential to submit a PR related to updating the data cleaning compoenent to leverage markitdown
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Motivation
The data cleaning part of the document-to-podcast workflow could be made more robust, as currently it does not take into account all possible cases.
Alternatives
Have also considered: https://github.com/VikParuchuri/marker, which could be an interesting alternative to 'markitdown'.
Contribution
Re-implementing the data cleaning component to use markitdown
This would make the data cleaning component for robust, and potentially re-useable across many Blueprints.
There is potential to submit a PR related to updating the data cleaning compoenent to leverage markitdown
Have you searched for similar issues before submitting this one?
The text was updated successfully, but these errors were encountered: