I want to set up 2 different media sets so that documents uploaded by front end users land in a different location and can be separate and reviewed by back end users. How do I create a button that uploads to a different media set then the one that currently feeds my RAG pipeline, but still joins into the pipeline, ran, and the information can be used by front end users until reviewed and potentially removed. If there is a better way to set this up I am open to suggestions as well.
Hi Monti,
Yes, this is doable! The cleanest setup depends on whether you actually need two separate media sets, or whether you mainly need a review gate before docs count as approved.
If this is just a review gate, I would keep one media set and add a status property on the document object: pending/approved/rejected/etc. Front-end users upload as normal, a back-end reviewer flips the status with an action. Retrieval on objects can filter on that status. Pending docs are usable immediately, approved docs stay in results, and “removing” a doc can mean setting it to rejected or be cleaned by by deleting the object. That avoids a second set, copying, and extra storage.
It’d also be helpful to get details on your set-up.
How is the media set that feeds the RAG pipeline written into? Is it ingested from a source connector or does it need to accept front-end user upload as well.
Best,
Lucy Wang