Repository navigation
feat(entities): entity setup per namespace or collection, and types of your own - #63
Merged
Merged
Conversation
…f your own Entities gets Types and Setup tabs. A namespace's setup says which entity types it keeps (names of other types are left out when a recording is analysed) and what it is about; any collection can have its own setup, which holds for the collections inside it too. Namespaces can add their own entity types with a description of what counts as one; retyping and moving mentions accept them, and lists show their labels. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VmPYPheY7aGQv9TiA563P5
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 namespace kept every entity type the extractors found, and the nine built-in types were the only ones.
After: the Entities page has Types and Setup tabs.
CLIENT_TEAM) with a description of what counts as one. Retype and move-mention accept them, lists show their labels, and a type can be deleted once no entity has it.API:
GET/PUT /api/v1/namespaces/{name}/entity-setup,DELETE …/entity-setup/collections/{cid},POST/PATCH/DELETE /api/v1/namespaces/{name}/entity-types[/{code}], andGET /api/v1/entities/types?ns=now includes the namespace's own types with descriptions. All changes are audited. New tablesentity_scopeandentity_kindare defined in the schema (SurrealDB server needs them). The default setup reproduces today's behaviour.The setup's mode is only
selffor now; fixed and hybrid modes (with Unknown and Unlabeled) come in the next PRs, which is why the API accepts just that one value.Motivation and Context
Third of a series of small PRs for per-namespace and per-collection entity modes.
Types of changes
!in the title)Checklist:
tests/api/test_entity_setup.py,entities-model.test.ts).docs/accordingly (processing.md, Entity setup).## UnreleasedinCHANGELOG.md.Local checks: backend 342 passed (only
test_office_and_text_files_become_documentsfails, as on main: this machine's LibreOffice can't load the .docx); frontend jest 544 passed. Checked both tabs in a browser against a seeded archive.🤖 Generated with Claude Code
https://claude.ai/code/session_01VmPYPheY7aGQv9TiA563P5
Generated by Claude Code