Refactor corpus import and add model-based topic/emotion visualization#140
Open
MaestroVaqueiro wants to merge 55 commits intotexttechnologylab:developfrom
Open
Refactor corpus import and add model-based topic/emotion visualization#140MaestroVaqueiro wants to merge 55 commits intotexttechnologylab:developfrom
MaestroVaqueiro wants to merge 55 commits intotexttechnologylab:developfrom
Conversation
…lysis result as cache
removed un-used fields
Das Analyse tool nutzt nun das bereits existierende select zur Auswahl zum Speichern. getCurrentUserId returned nun die jetzige User id.
…ew corpora or a already uploaded corpora.
…opics and Backfill sentencetopics.unifiedtopic_id
…re modelle eingespeichert
…on and rag-service flags on existing corporas
…ne, and heatmap views
…th unifiedTopic processing
…timeline and heatmap views. Also added visualization for Annotations for better overview.
…fallback/last-working-state
- Added new 'Others' button to the viz navigation bar (alongside Topic, Sentiment, Emotion) - Moved Semantic Density, Topic Entity, Topic Landscape, Topic Similarity and Sentence Topic Flow from Topic category into Others - Refactored loadTopicMenu() to only handle Topic Models - Added new loadOthersMenu() function to dynamically populate the Others dropdown - Added click handler for others-menu-item to route to correct viz panels - Fixed positioning of viz navigation bar: now left-aligned within sidebar instead of overlapping document area
…fallback/last-working-state
…toggle buttons visible feat: dynamic sentiment menu with 'No models found' fallback matching Topic and Emotion logic
…ing 'document_id' check to the SQL query in createSentenceEmotions. This prevents sentences in newly imported corpora from accidentally linking to emotions of older documents with identical text offsets, which caused foreign key constraint violations during deletion of corporas with the same documents but different models.
…the import modal in an already imported corpus
… Promise.all from failing when individual endpoints return no data
…fallback/last-working-state
…ed state conflict on first user click
…ndered state conflict on first user click
… visible in both landing-page.ftl and corpus-inspector.ftl
… errors when adding documents to one of these corporas. also removed submitCorpusImport() (part of old useless path import)
…fallback/last-working-state # Conflicts: # uce.portal/uce.common/src/main/java/org/texttechnologylab/uce/common/services/PostgresqlDataInterface_Impl.java
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
4 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.
A file-based upload workflow now supports both the creation of new corpora and the addition of documents to existing ones. Support for CorpusConfig.json makes corpus configuration reusable and more consistent across imports. Import progress is tracked through unique import IDs and exposed in the UI with both status and detailed progress views. A central model table normalizes model metadata and enables topic and emotion annotations to be stored as explicit, model-linked entities. In the Document Reader, users can choose an analysis area and a specific model to explore shared and dedicated visualizations for topics and emotions.