Repository navigation
feat(topics): a controlled vocabulary of topics, apart from entities - #126
Merged
Merged
Conversation
Each namespace keeps topics as SKOS concepts: a label, other labels, a definition, and broader, narrower and related topics. Recordings are about topics (said by a person, or brought over when a TERM entity becomes a topic, which hides the entity until the topic is deleted). Editors create, edit, merge and delete topics through /api/v1/topics. Topics are in the property graph (Topic, ABOUT, NARROWER, RELATED; TERM entities are labelled Term there) and in RDF (/id/topic/<id>). docs/topics.md. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012Jo1JNziunMs8MgWJSGyyM
This was referenced Oct 4, 2026
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.
Description
Before: a topic was just an entity of type TERM, the same type analysis gives anything it can't classify. Topics and named things were mixed, with no way to say one topic is narrower than another.
After: each namespace keeps a controlled vocabulary of topics, built on SKOS.
POST /entities/{id}/topic). Turning an entity into a topic hides the entity; deleting the topic shows it again./api/v1/topics: create, edit, merge, delete, and say which recordings are about a topic.Topicnodes, linked byABOUT,NARROWERandRELATED. A topic's parents are its broader topics and the recordings about it. TERM entities are now labelledTermthere, so they aren't confused with topics./id/topic/<id>, askos:Conceptin the namespace's vocabulary#topics. Recordings name their topics asdcterms:subject.Motivation and Context
Adeel asked for topics to be separated from entities as a controlled vocabulary. This is the first of four PRs, all listed in DEVLOG. The next ones add a Topics page, topic suggestions from analysis, and
#links in notes pointing at topics. Docs are in docs/topics.md.Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly.## UnreleasedinCHANGELOG.md.Tests:
🤖 Generated with Claude Code
https://claude.ai/code/session_012Jo1JNziunMs8MgWJSGyyM
Generated by Claude Code