Built-in Journal abbreviations list contains multiple errors

[thecaligarmo]

JabRef version

5.10 (latest release)

Operating system

Windows

Details on version and operating system

No response

Checked with the latest development build (copy version output from About dialog)

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

There are many journal abbreviation errors in the built-in list of abbreviations. Some examples:

• Discrete and Computational Geometry
• Differentiial Geometry and Topoloyg, Discrete and Computational Geometry
• Stochastic Analysis in Discrete and Continuous Settings

There seems to be a ton of journals which get mapped to "Lect. Notes. Comput. Sci."

Appendix

...

Log File

Paste an excerpt of your log file here

[Siedlerchr]

I have transfered the issue to the corresponding repo.

[northword]

Just for reference, I got a relatively accurate list of journal abbreviations by modifying the python script that merges the csv:

https://github.com/northword/zotero-format-metadata/blob/98ec494de52c16b4627adfd1c5bdb8e2a538f6d9/src/data/journal-abbr/generate-journal-list-dot.py#L31-L70

Until the checks such as #149 are finally implemented, I thought it might be possible to alleviate the problem with this script first?

[Siedlerchr]

@northword I like the idea, I think this is a good first step. It would be great if you could tackle this here as well

[Enivex]

This is driving me nuts.

Like, for instance the built in list has "American Journal of Mathematics" as "Am. J. Math.", which is not correct according to either the mathematics list, or the ams list. It should be "Amer. J. Math.". However, there seems to be no way to disable the built in list completely, so I have to verify every abbreviation manually.

[koppor]

This is driving me nuts.

I can fully understand and I feel sorry for that!

To increase priorities on our side there are multiple possibilities: I) you could ask your employer to contract a developer to fix it soon. We have a pool of freelancers able to work on JabRef code. Otherwise, the issue will stay on our normal roadmap, which is mainly driven by student volunteers. II) In case you have contact to programming lecturers, you can point them to https://devdocs.jabref.org/teaching.html and convince them to assign a team on this issue.