-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Citation Key Generator does not work as described #12312
Comments
@subhramit changed it in #11614. You can check the current behavior at jabref/src/test/java/org/jabref/logic/citationkeypattern/CitationKeyGeneratorTest.java Line 511 in 4b7ac10
Maybe you can (re-)join the discussion at #11614 I don't read out if you like the new behavior more or if you really like the old one more? |
Sorry for that. I am more a fan of the old behavior. It allows me to better compare the references of my LaTeX documents (where I use the alpha style) and the JabRef database. I would therefore like to ask whether it would be possible to reintegrate the old style into JabRef (this may of course be done under a different name). |
Yes, that can be done. @koppor We are back to an old question again - two "AuthorsAlpha" then? This seems to be the simplest way. |
The feature to generate citation keys should be available on all places where citation keys can be used. This included LibreOffice and the filename patterns. Thus, we need two variants. Maybe |
Keeping this free to take for students. I'll come back to this in the next two weeks to if nobody takes it. |
Implementation notes for anyone interested:
|
I am interested in this issue- can i be assigned this? |
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. ⚠ Note that this issue will become unassigned if it isn't closed within 30 days. 🔧 A maintainer can also add the Happy coding! 🚀 |
This refs JabRef/user-documentation#453 |
@subhramit "Revert Fix authorsAlpha #11614 (including tests). This will give us back the original authorsAlpha." Can you please elaborate this. Do i need to rollback any changes? |
Open the linked PR. Look at the changes there. They need to be reverted. |
@kushagradwi This issue does not seem to making any progress... Since i am waiting for this feature (and can spare some time at the moment): Do you need any help with the realisation of this? |
@lionfood alright, I'll take this up. Should be fixed by the weekend. @kushagradwi since this has been asked for, I am un-assigning you. You can take up any other first issue. |
We always need help 😅 Be it improving documentation, reviewing pull requests (including testing of the feature), and working on a good first issue. It seems you are both a developer and a user with UX feeling @lionfood, thus I would really appreciate if you would look into our pull requests - https://github.com/jabref/jabref/pulls 😅 |
Hi @lionfood, should be fine now. You can check the latest development version (https://builds.jabref.org/main/). |
Thank you very much. Did you have any idea, when there will be an JDK-EA version including this changes? |
You are using JabRef's JDK-EA builds (availble at https://builds.jabref.org/jdk-ea/). Do they work better for you? They should be generated on each Monday at 6pm - https://github.com/JabRef/jabref/blob/87f3f43e9c0da2412b7b88a17cff858d102b5d1b/.github/workflows/deployment-jdk-ea.yml#L8C14-L8C24. |
They work better for me because of the problem described in #11668.
Many thanks. |
Interesting... I commented there to move a step forward.
I manually re-triggered a build - should be available now 😅 And I changed the workflow to update that daily. (Since you seem to rely on these builds) |
JabRef version
Other (please describe below)
Operating system
GNU / Linux
Details on version and operating system
JabRef 6.0--2024-12-16--a3b2efb / openSUSE Leap 15.6
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
[authorsAlpha]
[authorsAlpha]
the following should hold:Appendix
Screenshots
Screenshot 1:

Screenshot 2:

Bib file
The text was updated successfully, but these errors were encountered: