Replies: 10 comments
|
hey <@315485233287790602> what version of cognee are you running? also can you print what fields you're actually getting?
if you don't see document info in there, try using the get dataset data endpoint at https://docs.cognee.ai/api-reference/datasets/get-dataset-data - it shows all files with their names and IDs. or try also you can check the blog here might help a bit https://dev.to/chinmay_bhosale_9ceed796b/search-types-in-cognee-1jo7 |
|
<@1373135538147692604>
I find that I can get data by API On the other hand, the search result looks like this: How can I map this search result back to the corresponding file-level metadata (such as the file ID or name)? |
|
hey <@315485233287790602> if your goal is to find the best matching pdf overall not just individual chunks I'd suggest using from the discussions here https://discord.com/channels/1120795297094832337/1356574585398759467 <@508682252595626015> recommends it for most general questions since it does graph traversal and gives you better context. |
|
<@1373135538147692604> thanks. it looks like exactly I was looking for 🙂 After I've upgraded cognee to v0.5.0, when I curl to local cognee server, I get |
|
I found this warning but can't figure out where should I put |
|
nevermind, I found a way in https://docs.cognee.ai/setup-configuration/permissions. nice docs! |
|
with However, none of these uids are pointing document object directly. 🥹 |
|
can you try this this uses the graph store structural search capabilities to navigate from chunks to documents. lmk if this helps |
|
Thanks for the snippet. |
|
After add memify after cognify, connections are created and finally can find document name! |
Uh oh!
There was an error while loading. Please reload this page.
=```python
PDF_DIRECTORY="./data"
All reactions