Reorganizing the menu : split Report and AI Menu

[qwertygc]

Hello,
I have a suggestion regarding the interface, specifically the menu. Of course, this is still up for discussion, which is why I am opening this issue.

I find that the “report” tab is misleading, in the sense that it combines two distinct functions. On the one hand, there is the analysis—that is, the ability to “view” our data from a different angle, which helps us reflect on the typology and analysis work (how I explain my codes). On the other hand, there are the reports—that is, the final output to be exported (how I present my codes for an article for example). I propose creating a new tab and a new menu item for the analysis, splitting the “Report” content into two. Also, I propose to split AI menu between Projet, Coding, Analysis, because it's it is an integral part of the software.

The idea it's the menu is differents steps of analysis: We create a project (Project), import data (Manage), Coding, Analysis and writing article (Reports).

Project

• Database queries : For me, it's not in Reports.
• AI Setup Wizard, Settings, Rebuild Internal Memory, Prompt Library -> for me it's in software Settings

Coding

• AI Assisted Coding

Analysis:

• AI Chat
• Coding Reports (for me, it is more Coding analysis but, we need to have discussion about it)
• Code relations
• Code co-occurences
• Code text exact matches
• Code by text segments
• Graph

Reports :

• Coding comparaison
• Coding comparaison by file
• Coding counts by file/case
• Code frequencies
• Files summary
• Code summary
• Charts

What do you think ?

Regards
Justin

[ccbogel]

Hello J.

Yes we can look at reviewing the organisation of the menu.
I think a few viewpoints are needed.
I do like that the AI functions are all in the AI tab, even if they replicate menu options in other areas.
I have attached an Excel file of the menu options, and maybe in other Excel sheets alternatives can be put together - for discussion.

Menus.xlsx

regards Colin

[Salomon-Mazatlan]

Hello J and Colin,

I find the idea of reorganizing the main menus quite interesting. I agree with J. that a new menu and tab called “Analysis” could be introduced.

This would make it easier to navigate through the central tabs during the coding process, analytical querying, and report generation.

As an example, a possible preview could look like the following (although this is not a definitive proposal):

Regarding the “Import Survey” module, I believe it could be replaced by the new survey import options within “Manage Files.”

Saludos cordiales,

Kind regards,
Psic. Lorenzo Salomón.

[qwertygc]

Hello Lorenzo and Colin,

Nice the schema @Salomon-Mazatlan .

I agree with the idea of replacing the new survey import options in "Manage Files".

Concerning Code organiser, for me, it is a part of the analysis: we make sense of data. This schema is good to explain the methodology:

SALDAÑA, Johnny, 2025. The coding manual for qualitative researchers. 5E. London ; Thousand Oaks, California : Sage. ISBN 978-1-5296-8001-0. H62 .S31856 2025

The code Organiser is the second cycle coding, when we purpose a means of interpreting, with category, etc.

What are the arguments for a dedicated AI menu?

Dedicated menu: This gives the feature visibility (almost "marketing-oriented"), with the option to ignore/disable it if desired.

Distributed across different menus: This integrates AI more deeply into the software, treating it as an option, a feature like any other.

Kinds regards,
Justin

[Salomon-Mazatlan]

Hi Justin,

What are the arguments for a dedicated AI menu?

Dedicated menu: This gives the feature visibility (almost "marketing-oriented"), with the option to ignore/disable it if desired.

Distributed across different menus: This integrates AI more deeply into the software, treating it as an option, a feature like any other

I believe that AI functionalities should be grouped within a dedicated menu, rather than being distributed throughout the software. This allows for a clear distinction between traditional CAQDAS tools and AI-assisted processes.

Additionally, given that access to free APIs is limited, these features tend to be used at specific moments in the research process. A dedicated menu enables more intentional use without disrupting the main workflow (In my opinion).

[kaixxx]

Yes, adding an "analysis" tab could be helpful. The report tab and menu are getting a bit overloaded.

Regarding the AI features: I see AI as a supportive tool that should be used in conjunction with classic methodologies, not as a replacement or a totally new approach to qualitative data analysis. This is why I decided to integrate the features into a classic QDA-app like QualCoder instead of building something completely new. Given this background, a bit more integration into the QualCoder menus would be desirable.
On the other hand, I do like the UI principle the menus correspond with the different tabs. So we should definitely keep the AI menu, as we also have an "AI Chat" tab. But I would argue that "AI assisted coding" still belongs to the coding menu. If the user decides to disable the AI features, these menu options should be grayed out.

[qwertygc]

I agree with both points of view. However, I don’t think that integrating it into other menus is incompatible with making the use of AI optional within the workflow.

The question to ask is whether it is practical to find the right tool quickly (for the power user) or intuitively (for the new user).

[ccbogel]

Yes all good ideas originally I was not keen on having more tabs. but if the end users find this Ok , we sure can do that. Actually, originally I was thinking of cutting back to 2 tabs - a log, and a working tab - similar to how the statistics program, SPSS does this. But I guess this is not desired.

"The question to ask is whether it is practical to find the right tool quickly (for the power user) or intuitively (for the new user)." Yes, I feel that the same function (eg AI coding) can be displayed in multiple menus, for easier finding.

[qwertygc]

I my opinion, we can decorrelate tabs and menu. We can have seven items in menu and two tabs, one tabs and seven item, or seven tabs and seven menus.

We can have three tabs :
Journal / works (import data, coding. analysis, report) and IA for i.e.

[ccbogel]

We need a consensus

[Salomon-Mazatlan]

I support Justin’s initial proposal, add a Analysis tab/menu:

This would be more intuitive for both new users and those already familiar with QualCoder, as it maintains a consistent structure.

Additionally, this interface makes it easier to navigate between tabs. For example:

While coding, users can simultaneously generate visualizations and reports (queries). From my perspective, this makes it easier to make adjustments at any point in the process.

Note: In the updates to the view_graph.py module, a function is being added to update coded segments through the “Refresh view” option.

[qwertygc]

It's very good Lorenzo, thank you !

[kaixxx]

Adding an "analysis" tab seems to be the consensus, right? Other than that, I lean towards keeping the interface as it is for now to not confuse users too much.

BTW, I like to talk about the tabs as different "workspaces" inside QualCoder. This is very similar to other apps, e.g. video editors, that have a color grading workspace, an audio workspace, an editing workspace with a timeline, etc.

Something to keep in mind: If we have several workspaces open at the same time, we must make sure to keep them in sync, which is not trivial. I have started working on this here: #1232 For now, only changes to the code system are reflected in other tabs/workspaces. We must extend this to basically every single change to the database, so that new coding, memos, etc. also show up in other workspaces.
I will continue working on this. But please keep in mind that every report analysis or report dialog must subscribe to the new project_data_changed signal and update its UI accordingly.

[ccbogel]

I was just working out a new menu structure, then saw your comment above.

Menus.xlsx

If we have several workspaces open at the same time, we must make sure to keep them in sync.
Yes, maybe have a changed menu, and maybe reduce to 2 tab worklspaces?

[Salomon-Mazatlan]

I like the new organization:

Menus.xlsx

---

and maybe reduce to 2 tab worklspaces?

I think that (in terms of tabs) it could be somewhat impractical for users to rely on the menu for every query or action, especially when they are repeatedly navigating between the same modules.

In that sense, an alternative could be to keep the QTabWidget initially empty, with only the “Action Log” tab, and dynamically add new tabs as different modules are opened, similar to how tabs work in a web browser.

[ccbogel]

Re-organising the menu options would be easier.

Dynamically adding tabs I think would be more of a technical problem.
Having only 2 tabs, an action log for recording the actions performed and an active workspace tab that does everything else (coding, reports, analyses), would avoid the need to sync across tabs, when files and coding changes.
Or may be 3 tabs - action log, manage tab (files, cases etc) and active workspace tab (coding, analyses, reports).

Keeping the journal windows as it is, as a modal window, so that it is easy to enter thoughts into it, when looking at files, cases, coding, reports.