Possible Feature - Assistants files
Files metadata, and operations using that metadata
Up to 10000 files per assistant. 100GB/organization. And no hierarchy to the storage system, and no additional data fields beyond the original file name and upload date. Being charged daily if left in a vector store.
{'data': [{'id': 'file-kNeCG3FLIP1OgzSD4apj', 'bytes': 2911, 'created_at': 1713555273, 'filename': 'assistants-file-utility.py', 'object': 'file', 'purpose': 'assistants', 'status': 'processed', 'status_details': None}], 'object': 'list', 'has_more': False}
And one method: list them all.
And one method: delete a single one by ID.
A little customer-side data glitch to their robust tracking system that is used by all organization and project members and chatbots for every API call, and the organization then has thousands of files of unknown source.
The benefit of a metadata layer, allowing arbitrary developer keys and fields like "customer_id" or "job-id" seem obvious. Sublistings and batch deletions then become possible. Structured or generated metadata such as expiration_date project_id would allow query-like operations and deletions.
beta 3?