Add 'no kilosort label' to ClusterQualityLabel contents#22
Merged
Conversation
This label already exists in the production database for units created by merge or split during manual curation. Adding it to the code-level contents prevents a skip_duplicates INSERT on schema activation, which fails for read-only database users.
ttngu207
approved these changes
May 13, 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
2 participants
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.
Summary
The
ClusterQualityLabellookup table'scontentslist was missing the "no kilosort label" entry that already exists in the production database. This label is assigned to units created by merge or split during manual curation.When a read-only database user (e.g., the
coscientistservice account) imports this schema, DataJoint detects the mismatch betweencontents(5 rows) and the database (6 rows) and attempts askip_duplicates=TrueINSERT. That INSERT fails with a permission error, blocking schema activation for any user without write access to the ephys schema.Adding the sixth label to
contentsbrings the code in sync with the database and eliminates the spurious INSERT attempt.