[Brainstorming] Groups / keywords architecture

[ThiloteE]

There has been a lot of discussion and confusion about folders, groups, tags, keywords and labels and what differentiates them. See for example https://github.com/JabRef/jabref/issues/11026#issuecomment-2370583648 and https://github.com/JabRef/jabref/issues/8739#issuecomment-1123621570

What we have right now in JabRef 5.15:

1. A Frankenstein groups feature that is actually something in between groups and keywords (more keyword than group, to be honest), but we call it groups and the information is stored in the "groups" field, but also partially in binary information in JabRef internal syntax at the bottom of the library file. Entries can be added and removed to groups via the entry editor and via the groups sidepane on the left. See https://docs.jabref.org/finding-sorting-and-cleaning-entries/groups.
2. The field "keywords", whose definition follows the bibtex standard. Those keywords are accessible via the entry editor.

What primary characteristics differentiate group/keyword systems?

• Can groups/keywords be nested? (Is there a hierarchy?)
  • Currently, yes, but groups and sub-groups cannot have the same name.
• Can entries be part of multiple groups?
  • Currently, yes, that's why it might be more accurate to call it a keyword system.
• Are groups/keywords associated with the entry itself?
  • Currently, yes. that's why it might be more accurate to call it a keyword system.

What secondary characteristics exist? Those are qualities that depend on how the primary qualities are implemented.

• If you change the entry's keyword, will it change the name of the group(s)?
• If you change the entry's keyword, will it create a new group, if it doesn't already exist?
• Can entries be automatically assigned to groups/keywords?
• Where is the data stored? In a (.bib) library file or a database?
• What happens if entries / groups / keywords are shared remotely? Will remote (server) take precedence or the local file? What preferences have to be shared?

Database structure of JabRef

• As far as I am aware, JabRef 5.15 stores everything in the library file.

Database structure of external Apps

• Thunderbird's experiments with MySQL. See https://bugzilla.mozilla.org/show_bug.cgi?id=1921394. It's interesting. I basically opened this issue to post that link, lol. Didn't know where to put it.

[koppor]

This refs https://github.com/JabRef/jabref/issues/11026#issuecomment-2370583648.

[ThiloteE]

Koppor, you think like me. Funny. I referenced the same comment in my second sentence of this issue here.

[koppor]

For a structured approach, one needs to write down what existing tools are doing. For instance: BibDesk.

They are are good in distinguishing automatic and non-autoamtic groups:

I think, users need both: automatic (e.g., based on citations, keywords, ...) and non-automatic (manual categorization)

---

This also refs https://github.com/JabRef/jabref/blob/main/docs/decisions/0019-implement-special-fields-as-separate-fields.md. Thus, the dimenstion is not only automatic and manual, but also how to render in the entry table.

[koppor]

To really come up with a solution, one needs to have a minimal example showing the different options. One can start with Chocolate.bib. In other words requirements analysis 😅

[ThiloteE]

This issue here is not yet about a solution. Just brainstorming for now. I wanted you to look at the Thunderbird link I posted.

[koppor]

We need "Draft issues" 🤣🤣

I personally use OneNote for such things, but in the Web Browser, its aweful 🙈.