Repository navigation
feat(entities): a fixed list of entities, with Unknown and Unlabeled - #64
Merged
Merged
Conversation
A namespace or collection can now use a fixed list. Editors define its entities (name, type, other ways it's said, description), for the whole namespace or one collection and those inside it. When a recording is analysed each name found goes to the defined entity it names (also when written in lower case), else to Unlabeled when it is of a type that belongs, else to Unknown; nothing new is created. Unknown and Unlabeled are always there and can't be renamed, merged, hidden or deleted. People's corrections still win, and moving a mention to a new name adds it to the list. The Entities page gets Add entity, defined and always-there badges, other names and the fixed-list switch in the side panel, and the setup's mode with Apply to analysed recordings. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VmPYPheY7aGQv9TiA563P5
…hing is half-saved Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VmPYPheY7aGQv9TiA563P5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before: every name the extractors found became an entity of its own; there was no way to say "these are the entities here".
After: Entities → Setup offers a Fixed list mode next to Self-organizing, for a namespace or any collection.
API:
POST /api/v1/namespaces/{name}/entities,DELETE /api/v1/entities/{id},PATCH /api/v1/entities/{id}gainsaliasesanddefined,POST /api/v1/namespaces/{name}/entity-setup/apply, and setups acceptmode: "fixed". Mapping lives in a newentity_map.py, called fromanalyze_recording, so workflow extraction nodes (save entities) go through it too; the workflow executor is untouched. Self-organizing behaviour is unchanged.Motivation and Context
Fourth of the small PRs for entity modes. Next: self-organizing mapped by descriptions with assistant tools, then hybrid.
Types of changes
!in the title)Checklist:
tests/api/test_entity_fixed.py,entities-model.test.ts).docs/accordingly (processing.md).## UnreleasedinCHANGELOG.md.Local checks: backend 344 passed on the first commit (only
test_office_and_text_files_become_documentsfails, as on main: this machine's LibreOffice), entity, routine, workflow, chat and MCP suites re-run after the fix commit; frontend jest 546 passed. Walked through Add entity → Fixed list → Apply in a browser against a seeded archive.🤖 Generated with Claude Code
https://claude.ai/code/session_01VmPYPheY7aGQv9TiA563P5