Which chunking provider to use, r2r or unstructured. Selecting unstructured is generally recommended when parsing with unstructured or unstructured_api.
Retrieve high-level document information, restricted to user files, except when called by a superuser where it will then return results from over all users:
[{'text':'Aristotle[A] (Greek: Ἀριστοτέλης Aristotélēs, pronounced [aristotélɛːs]; 384–322 BC) was an Ancient Greek philosopher and polymath...','user_id':'2acb499e-8428-543b-bd85-0d9098718220','document_id':'9fbe403b-c11c-5aae-8ade-ef22980c3ad1','extraction_id':'aeba6400-1bd0-5ee9-8925-04732d675434','fragment_id':'f48bcdad-4155-52a4-8c9d-8ba06e996ba3''metadata':{'title':'aristotle.txt', 'version':'v0', 'chunk_order':0}}},...]
A list of logical filters to perform over input documents fields which identifies the unique set of documents to delete (e.g., {"document_id": {"$eq": "9fbe403b-c11c-5aae-8ade-ef22980c3ad1"}}). Logical operations might include variables such as "user_id" or "title" and filters like neq, gte, etc.