Add a code to multiple categories

[qwertygc]

I had a discussion with a group of QualCoder users. One of the feedback points, which was particularly important and on which there was a consensus, was the ability to assign a code to multiple categories. For example, if I am working on a corpus about fishing, I might have the codes ‘angling’, ‘trawler’, ‘pot fishing’, ‘beach fishing’ and ‘electric fishing’. If I can assign a code to the ‘fishing techniques’ category, I would also like to be able to assign it to ‘ecological fishing’ or ‘non-ecological fishing’, as these codes can be analysed in different ways (by technique, by ecology, but one can imagine other possibilities too).

This would allow us to move the codes away from a hierarchical structure towards a more rhizomatic/network-based structure. This would complement the work on improving the graphs carried out by Lorenzo (#1229), by enriching the various possible relationships.

[Salomon-Mazatlan]

the ability to assign a code to multiple categories

I think this could be implemented by introducing an intermediate table, for example code_cat_link, that acts as a bridge between codes (cid) and categories (catid). This way, instead of a code belonging to a single category, it could be linked to multiple categories simultaneously, enabling a more flexible, network-like structure rather than a strictly hierarchical one.

However, this change would require modifying several key parts of the system, since the current relationship appears to be designed as one-to-many. The main adjustments would include:

• Query and search logic: queries would need to be updated to use the new intermediate table and correctly retrieve all categories associated with each code (and vice versa).
• User interface: the views where codes and categories are displayed and organized (e.g., the tree) would need to support showing the same code under multiple categories, while maintaining visual clarity and avoiding ambiguity.
• Reports and statistics: counts and aggregations would need to be reviewed to prevent double-counting when a code belongs to multiple categories.
• Import/export: input and output formats would need to be updated to reflect this many-to-many relationship, ensuring that links are preserved when sharing or migrating projects (REFI-QDA)

Perhaps for version 4.1, once the overall (new) structure of QualCoder has been defined and the features currently in progress have been implemented.

[qwertygc]

For me, a category it's a specific code. Maybe we can consider this in the architecture of database?

User interface: the views where codes and categories are displayed and organized (e.g., the tree) would need to support showing the same code under multiple categories, while maintaining visual clarity and avoiding ambiguity.

We can see the same code in different categories on the tree. If we have the same colour and same name, it's ok.

[kaixxx]

I would support this idea and think we should implement it together with #1210 (introducing subcodes).

But yes, version 4.x is more realistic.

[ccbogel]

Yes, as there are a lot of changes coming in the next version.
These alone will take some time to pay with and ensure there are minimal problems.

The graph-like rather than tree like structure could be considered in a later version,
Also, as a part of this change, the use of separate category and code tables could be redundant, and simply have codes linking to codes.
However, this would be quite complex to fix everywhere and test everywhere.