Re-introduce CitationKey column as default in the entry (main) table

[Siedlerchr]

The main/entry table should show the column citation key by default.

internal issue for refefence: https://github.com/JabRef/jabref-issue-melting-pot/issues/305

Currently, this has to be manually activated using the preferences by adding the field "citationkey" (internal)

It should be added as default value in the preferences. It should be coming before entrytype and it should have a decent width.

https://github.com/JabRef/jabref/blob/c444c739d62737003fd1c178d3aeefb628fe78b1/src/main/java/org/jabref/preferences/JabRefPreferences.java#L606-L607

To test, you can reset your preferences and restart JabRef. Then the column should be visible

[u7288020]

Hi there,

I am new to open source contribution and would love to contribute to this issue. Could you please assign it to me? I'll try my best to resolve the problem - If you have any specific information or steps you'd like me to follow, please feel free to share them.

Thank you!

[tobiasdiez]

I think we removed it since normally it doesn't contain any new information (by default it's authors + year) and users almost never need it (you don't want to copy the key manually but use right click, copy key).

[Siedlerchr]

@tobiasdiez please see the linked issue. @koppor made clear why it should be there

[ThiloteE]

I don't have a strong opinion on this. Our user-base is still largely bibtex/biblatex based, so whatever. It is now easier to remove unwanted columns from the entry table by right-clicking on the column, so this should be no biggy. Once we have more CSL styles, and hence a growth in users and contributors from OpenOffice/LibreOffice, this issue might become slightly more controversal, but for now, whatever.

[ThiloteE]

By the way, one should not have to refer to a non-open issue from "issue-melting-pot" to justify ones proposal. IMHO, all relevant info should be public.

For context, this was the original issue:

Default configuration:

I get following warnings in bibtex:

Warning--empty journal in Hejda2023
Warning--empty journal in Veytsman2020

I could find the entry for searching the key. However, I could also sort the column. I can also use my eyes to follow the entry table. - In general, the entry table provides an overview of entries. My claim: i) Users are interested in a subset of the entries displayed in the entry table and ii) are using the citation keys in LaTeX and check these keys in the entry table. This makes the keys an integal part, which should be shown.

I agree that for "modern" interfaces (such as JabRefOnline or CiteDrive), other approaches might be taken. Our focus is still BibTeX and a unique key is a key part of BibTeX

After the change:

---

Manual config:

[koppor]

I wrote more than 100 papers, my library is more than 1000 entries large. I lead research groups. I worked with dozens of LaTeX newcomers. I discussed with LaTeX experts at the TUG user group. This needs to be implemented. No work arounds

Research groups do not change their citation keys to something JabRef wants; they have their own way. - The sort order of the table is sometimes hard.

[Siedlerchr]

@ThiloteE Copying images fromt he private repo does not work, you need to reupload them

[tobiasdiez]

This is how jabref looks like on a normal-sized laptop screen in fullscreen with the default config:

Already pretty full. Which column do you want to remove to make space for the citation key?

[tobiasdiez]

For context, the same arguments were brought forward in the PR that removed the citation key column: https://github.com/JabRef/jabref/pull/7286. And as far as I can see no user complained in the past 2.5 years.

[Siedlerchr]

What about adding this to the right click menu? as a simple option

[koppor]

Thank you for the link! https://github.com/JabRef/jabref/pull/7286

Hiding a column is possible via right-click menu, thus shrinking is easy. Enlarging is currently an issue. The default configuration should be good. - I am talking to persons not using JabRef anymore or at all - and the confusion with BibTeX keys not shown in the UI is one reason.

[jiaxin0103]

Hello, I am a student at the Australian National University. For our team project, we need to contribute to an open-source project. May I be assigned to this task?

[github-actions[bot]]

Welcome to the vibrant world of open-source development with JabRef!

Newcomers, we're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.

In case you encounter failing tests during development, please check our developer FAQs!

Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.

Happy coding! 🚀

[koppor]

@jiaxin0103 Thank you for your interest. The code should be easy. You also need to add an ADR document to the folder https://github.com/JabRef/jabref/tree/main/docs/decisions outlining the pros and cons of showing/not showing the citation key column as default. With discusisons linked.

[koppor]

It is good to have this in the alpha/beta release to be enabled to gather user feedback.

[suftware]

Hi @koppor , I am part of the same group as @jiaxin0103 and am working on this issue - would I be able to be added as an assignee as well? Thank you!

[koppor]

@suftware @jiaxin0103 I assume, this is a one-line fix - and a line to the CHANGELOG.md. This issue guides you through the process to contribute to an open source project. Please complete this fast - and try to take another issue afterwards to really level-up your coding skills!