Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-21 01:25:28 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #593] [FEAT]: Add support to the JSON with Metadata {single chunk option} #343

New Issue
Closed
opened 2026-02-22 18:19:03 -05:00 by yindo · 2 comments
yindo commented 2026-02-22 18:19:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @sumitsodhi88 on GitHub (Jan 13, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/593

What would you like to see?

I want to upload JSON files and include metadata with each JSON as I am using legal documents. Each JSON {} can be one chunk and the Database can go through a Metadata first to pick correct chunk. The LLM confuses different chunks and mixes them together to give answers. E.g. If I ask what happened in a case - It mixes other case with it and shows issues from there too.
My only solution was to divide the documents into separate txts to get some reliable results although not very perfect as it picks up wrong txt altogether - as it is not pciking up the metadata

Originally created by @sumitsodhi88 on GitHub (Jan 13, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/593 ### What would you like to see? I want to upload JSON files and include metadata with each JSON as I am using legal documents. Each JSON {} can be one chunk and the Database can go through a Metadata first to pick correct chunk. The LLM confuses different chunks and mixes them together to give answers. E.g. If I ask what happened in a case - It mixes other case with it and shows issues from there too. My only solution was to divide the documents into separate txts to get some reliable results although not very perfect as it picks up wrong txt altogether - as it is not pciking up the metadata
yindo added the enhancementfeature request labels 2026-02-22 18:19:03 -05:00
yindo closed this issue 2026-02-22 18:19:03 -05:00
yindo commented 2026-02-22 18:19:03 -05:00
Author
Owner
Copy Link
Copy Source

@sumitsodhi88 commented on GitHub (Jan 13, 2024):

Screenshot 2024-01-14 101523

@sumitsodhi88 commented on GitHub (Jan 13, 2024): ![Screenshot 2024-01-14 101523](https://github.com/Mintplex-Labs/anything-llm/assets/149290101/135fc109-a772-4a2b-97a1-7ab639f1f8b0)
yindo commented 2026-02-22 18:19:03 -05:00
Author
Owner
Copy Link
Copy Source

@sumitsodhi88 commented on GitHub (Jan 13, 2024):

metadata and tags from my file
Screenshot 2024-01-14 101727

@sumitsodhi88 commented on GitHub (Jan 13, 2024): metadata and tags from my file ![Screenshot 2024-01-14 101727](https://github.com/Mintplex-Labs/anything-llm/assets/149290101/5e1443ef-ffe9-4ea5-b32c-95afa4342e57)
yindo changed title from [FEAT]: Add support to the JSON with Metadata {single chunk option} to [GH-ISSUE #593] [FEAT]: Add support to the JSON with Metadata {single chunk option} 2026-06-05 14:34:49 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#343
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?