Ability to disable the built-in JabRef journal abbreviation list

[Enivex]

Is your suggestion for improvement related to a problem? Please describe.
The built-in list has several issues (see e.g. JabRef/abbrv.jabref.org#150).

Not to mention that different authorities have different opinions about the "correct" abbreviation for a given journal.

Describe the solution you'd like
While fixing those should ultimately be done, it would be useful to be able to disable it and rely only on lists I've downloaded from https://github.com/JabRef/abbrv.jabref.org/tree/main/journals instead.

[Siedlerchr]

This refs #12364

[SihasA]

Hey there I am part of a student team working with @LinusDietz can I work on this issue?

[LinusDietz]

Hey there I am part of a student team working with @LinusDietz can I work on this issue?

@SihasA I'm not sure about this one. Overall, the idea/rationale proposed in the issue seems to be a bit unclear to me.

[koppor]

@SihasA since you seem to have some more time (than just 5 hours), please work on #12364

[zikunz]

Hi @Siedlerchr @LinusDietz @koppor,

I would like to self-assign this issue (i.e., #12468: Ability to disable the built-in JabRef journal abbreviation list). After reviewing the issue and trying out JabRef's abbreviation feature over the past week, I believe I mostly understand the requirements and would like to implement a solution.

I have thoroughly read the CONTRIBUTING.md guidelines and understand the project's contribution standards.

I aim to submit a PR within the next 7 days. I will provide regular updates on my progress in this thread.

Thank you for maintaining this project. I am excited about the opportunity to contribute to JabRef's abbreviation functionalities.

/assign-me

[github-actions]

👋 Hey @zikunz, thank you for your interest in this issue! 🎉

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! 🚀

⏳ Please note, you will be automatically unassigned if there is not a (draft) pull request within 14 days (by 09 April 2025).

[koppor]

@zikunz I have no clue how to solve this. I think, this is impossible with my current knowledge. Maybe, you could work on #12364?

However, I see #12606 and #12544 going on, which are all related. Maybe, you can bring light into this current state and submit a clean PR based on the feedbacks of the other PRs?