Connect One Drive to your preprocessing pipeline, and batch process all your documents using unstructured-ingest
to store structured outputs locally on your filesystem.
unstructured
API. For this you’ll need to use the --partition-by-api
flag and pass in your API key with --api-key
.
--partition-endpoint
if you’re running the API locally. You can find more information about the unstructured
API here.
For a full list of the options the CLI accepts check unstructured-ingest onedrive --help
.
NOTE: Keep in mind that you will need to have all the appropriate extras and dependencies for the file types of the documents contained in your data storage platform if you’re running this locally. You can find more information about this in the installation guide.