Pamela Fox

IndexedDB is only persisted in the browser, which means that if the user switches browsers/computers, they no longer have the history. CosmosDB would be persisted in the server, and if...

@fujita-h has added support for persistence using CosmosDB, tied to the user's entra ID: https://github.com/Azure-Samples/azure-search-openai-demo/releases There's no user consent there, but I think that will be fine given that the...

If your search index already exists, then you'll need to add additional fields in this if block: https://github.com/Azure-Samples/azure-search-openai-demo/blob/023dc1b6486cb974909a2eaf022f782c5ca7e005/app/backend/prepdocslib/searchmanager.py#L218 Then, once those search fields exist, you need to change the update_content...

Ooo, very interesting approach with the IndexedDB! It sounds like you've designed it very thoughtfully, I'll take a look soon.

The prepdocs script can be used with modifiers to remove a file and add a new file, per the documentation here: https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/data_ingestion.md#indexing-additional-documents Can you specify what you mean by automate?

You might also look into integrated vectorization if you're looking for scheduled ingestion. That's also detailed in the same guide.

We have now made a custom skillset that runs our own code instead, mirroring the local ingestion in Azure Functions. We will deprecate the previous integrated vectorization and recommend the...

To implement this sort of feature in our codebase, I'd take this approach: 1) Add an additional function to the query rewriting tools definition like "search_web" so that the LLM...

I believe you're running into this issue: https://github.com/Azure-Samples/azure-search-openai-demo/issues/1603 which is caused by an azd issue: https://github.com/Azure/azure-dev/issues/3920 However, if you do employ the workaround suggested there, then you'll run into the...

Interesting feature! Thanks @mrmueller for chiming in. Love to hear other developer's thoughts about what they/customeres want. I'm concerned this might make the local developer experience difficult as I'm fairly...