# Release of JabRef 5.4

**URL:** <https://discourse.jabref.org/t/release-of-jabref-5-4/3097>\
**Category:** News\
**Tags:** release\
**Created:** [December 20, 2021, 10:07pm UTC](https://discourse.jabref.org/t/release-of-jabref-5-4/3097 "2021-12-20T22:07:25Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\
**Post date:** [December 20, 2021, 10:07pm UTC](https://discourse.jabref.org/t/release-of-jabref-5-4/3097/1 "2021-12-20T22:07:25Z")

</div>

We are proud to announce the release of the next milestone of JabRef, this time JabRef 5.4, just in time for the holidays! It’s been roughly half a year since the previous release of 5.3, and we are happy to announce that despite the still ongoing Covid-19 waves we were all fortunately able to continue working on JabRef.

## Notable Changes and New Features

Thanks to this year’s Google Summer of Code, JabRef now has a PDF-fulltext search and improved metadata support. This allows you to search across libraries and linked files. Search results across several libraries can now also be shown again in a new window. It’s also possible to keep the search string when switching between libraries. Another major improvement is the metadata extraction and writing for PDFs. When generating an entry from a PDF, JabRef now checks different sources and provides an improved merge dialog to combine the extracted metadata.

Further work focused on improving the user experience in the GUI. For example, we added an icon picker to the Groups dialog to easily search for a suitable group icon. We also added the possibility to search all available citation styles together with a sample preview.

Additionaly to these, we also fixed many bugs. For a complete list of all our changes, take a look at the [Changelog](https://github.com/JabRef/jabref/blob/main/CHANGELOG.md) since our last official release!

**You can get it from [FOSShub](https://www.fosshub.com/JabRef.html).**

In case you notice any bugs or problems, please check our [bug tracker](https://github.com/JabRef/jabref/issues) and consider submitting a new bug report if nobody else has been reporting the failure before.

## Special Thanks

The [JabRef Maintainers](https://github.com/JabRef/jabref/blob/main/MAINTAINERS) would like to give special thanks to all new and old contributors. We are delighted to see so many new contributors opening pull requests and making translations or simply answering questions in our [support forum](https://discourse.jabref.org/). The Release 5.4 now also includes Korean (한국어) as a new language. As we all work on JabRef in our free time, we feel honored that people share our enthusiasm for free software and work together to make research easier.

A big thanks also to all our donators!

We also want to thank all universities [including JabRef in their academic teaching](https://devdocs.jabref.org/teaching).

Finally, we want to thank all the users who are constantly testing the latest snapshots and giving feedback!

The JabRef Maintainers wish everyone Happy Holidays and a Happy New Year! 🎉🍾🎆 Stay safe everyone!

_**You like it? Foster JabRef development with [Knowledge](https://help.jabref.org/en/FAQcontributing) or [Money](https://donations.jabref.org).**_

---

<div class="post-metadata">

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\
**Post date:** [December 20, 2021, 10:09pm UTC](https://discourse.jabref.org/t/release-of-jabref-5-4/3097/2 "2021-12-20T22:09:34Z")

</div>



---

<div class="post-metadata">

**Author:** ![ThiloteE](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/thilotee/32/1008_2.png) [@ThiloteE](https://discourse.jabref.org/u/ThiloteE)\
**Post date:** [December 21, 2021, 8:13pm UTC](https://discourse.jabref.org/t/release-of-jabref-5-4/3097/3 "2021-12-21T20:13:36Z")

</div>

Good Job everybody and thank you very much 🙂 🎉🎇🎁

I have followed the development versions since 5.3 and this release should be a lot more stable! 🙂 A lot of annoying bugs were fixed and things that did not work before now do or do even better (looking at you in particular, entry preview and metadata export/import).

Jabref now allows a very easy and smooth workflow for most generic writing purposes with a very low amount of clicks by offering the new `Import from ID` dialogue

1. Find bibliographic data **somewhere**

2. Copy and paste the DOI, ISBN or another ID into the newly added `Import from ID`  
 ![image](https://canada1.discourse-cdn.com/flex030/uploads/jabref/original/2X/4/40a3a5d249d55d3e28eda76508e7b2e3cbb0a793.png)

3. Check for correctness and missing data and fix it, if necessary.

4. Push entries to the external application.

Done. Easy.

To add to this minimalistic workflow, I personally have made extensive use of the linked files feature.

After having attached all my pdf-files to my entries (via regular expression search) it allowed me to not only open a pdf easily from within Jabref, but it also allowed me to use another new and very cool feature the Jabref maintainers brought to us: Fulltext search.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/jabref/original/2X/5/592f52b7777d8c14a8def3053d82d98cde42411d.png)

Yes indeed, now whenever you are about to write a paper and you know exactly what you want to write but you can’t remember the source for the information that is in your head … and you know the source is definitely somewhere in the hundreds of pdf-documents on your computer … Jabref can do it! Enable the button, search and Jabref will show you which of the documents have your search expression within. Awesome news for anybody who is really serious about sources 🙂

Finally, if you are working within a team and you have to exchange bibliographic data and you are not working with a shared database/bibfile (yet), there is another old/new way that allows you to share your data: The feature `write metadata to pdf files (F6)` now works again (Please do not try to write from two distinct entries to the same linked file 😅).  
 ![image](https://canada1.discourse-cdn.com/flex030/uploads/jabref/original/2X/5/5e46e08df175b71143ae035c65709d94ce742a02.png)

Since Jabref is now much better at importing bibliographic data, these features combined allow you to send that single pdf-file to your colleagues instead of having to send both the pdf file AND a library file (or raw bibliographic data).

Greetings to everybody and i hope i have provided a glimpse of the things that are new in Jabref 5.4 and how they could be used to help you 🙂 There is more!

---

<div class="post-metadata">

**Author:** ![J-U-B](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/j-u-b/32/1186_2.png) [@J-U-B](https://discourse.jabref.org/u/J-U-B)\
**Post date:** [December 22, 2021, 1:16pm UTC](https://discourse.jabref.org/t/release-of-jabref-5-4/3097/4 "2021-12-22T13:16:08Z")

</div>

# Signatures (MD5, SHA1, SHA256) on FOSSHUB do not match for the download on the GITHUB releases page.

I prefer the download of the install packages from [GitHub](https://github.com/JabRef/jabref/releases/tag/v5.4).  
To check the itegrity for my [OPSI packages](https://github.com/J-U-B?tab=repositories) I check against the signatures provided on FossHub.

However, for JabRef version 5.4 the signatures do not match!

It would build trust if the signatures match.

Thank you,  
Jens

---

<div class="post-metadata">

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\
**Post date:** [December 22, 2021, 1:34pm UTC](https://discourse.jabref.org/t/release-of-jabref-5-4/3097/5 "2021-12-22T13:34:45Z")

</div>

@J-U-B We first uploaded to Fosshub and then to github releases. The problem probably occurred because the build run twice (for the tag and for the main) . We used the tag builds for fosshub and probably mixed this up when uploading the files to Github

> **[index - powered by h5ai v0.29.0 (https://larsjung.de/h5ai/)](https://builds.jabref.org/tags/v5.4/)**
>
> index - powered by h5ai v0.29.0 (https://larsjung.de/h5ai/)

vs

> **[index - powered by h5ai v0.29.0 (https://larsjung.de/h5ai/)](https://builds.jabref.org/main/)**
>
> index - powered by h5ai v0.29.0 (https://larsjung.de/h5ai/)

---

<div class="post-metadata">

**Author:** ![J-U-B](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/j-u-b/32/1186_2.png) [@J-U-B](https://discourse.jabref.org/u/J-U-B)\
**Post date:** [December 22, 2021, 1:53pm UTC](https://discourse.jabref.org/t/release-of-jabref-5-4/3097/6 "2021-12-22T13:53:23Z")

</div>

Is it possible to align this so that the signatures match again?  
Or could you please provide signatures also on github?

---

<div class="post-metadata">

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\
**Post date:** [December 22, 2021, 2:05pm UTC](https://discourse.jabref.org/t/release-of-jabref-5-4/3097/7 "2021-12-22T14:05:51Z")

</div>

Yes, I am currently re-uploading the changes files to GitHub Releases.

---

<div class="post-metadata">

**Author:** ![J-U-B](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/j-u-b/32/1186_2.png) [@J-U-B](https://discourse.jabref.org/u/J-U-B)\
**Post date:** [December 22, 2021, 3:36pm UTC](https://discourse.jabref.org/t/release-of-jabref-5-4/3097/8 "2021-12-22T15:36:26Z")

</div>

Thank you for the quick reponse! 👍

---

<div class="post-metadata">

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\
**Post date:** [December 22, 2021, 4:25pm UTC](https://discourse.jabref.org/t/release-of-jabref-5-4/3097/9 "2021-12-22T16:25:08Z")

</div>

Should be the same files now.