Contrib.social

AI Search, AI Assistant, AI Vector DB Explorer: Not able to see URI data anywhere

Open on Drupal.org →
Created on 31 October 2024, about 2 months ago

Problem/Motivation

First, I want to thank you for the incredible job you've done on this module, it truly represents the future of Drupal!
I’m excited to be using it, testing, and helping with further testing.
My issue: Currently, I'm unable to retrieve the value of the node/content URI anywhere.

Steps to reproduce

1. Created Server: DB - Zilliz
2. Created Index:
- Content: All nodes
- Fields: Added search_api_url as a field (tried all indexing options) and other fields like description , summary (these work fine)
3. Indexed the content.
4. Checked in AI Vector DB Explorer by requesting a small set of nodes. (search prompt: "Show me first 10 training resources found and their URI"
- Issue: URI data is not present.
5. Created an Assistant and set it to include the content URL (following the example shown in your video).
- Issue: The URL is returned with the correct title but an incorrect node ID.

With AI Vector DB Explorer, I can’t confirm URI data because it’s not showing up.

I plan to continue testing but wanted to start a conversation in case I may be doing something wrong or missing a step.

Planning to test betta1 to see if it works there.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

AI Search

Created by

🇺🇸United States vlyalko

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @vlyalko
  • Comment about 2 months ago →
    🇺🇸United States vlyalko

    Update. It started working. AI assistant started to return correct url. And URI started to show in AI Vector DB Explorer. I am not sure what worked. Still using alpha8. Will try to figure out what change made it work. Thanks

  • Comment about 1 month ago →
    🇬🇧United Kingdom scott_euser

    Thanks for raising. I guess you're trying to get the LLM to return the URI? It'll depend on prompt and model how reliably it'd do that. Within the process the vector database results give you the actual entity which would be a more reliable way to get the URI.

    Since you've got it working though, seems like we should close and if someone has a similar issue maybe they can reopen with further steps on latest codebase.

  • Comment about 1 month ago →
    🇺🇸United States vlyalko

    Yes, it is working. The issue can be closed

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024