Select "better" value in MultiMergeEntries dialog

[koppor]

There is org.jabref.logic.bibtex.comparator.plausibility.PlausibilityComparatorFactory#getPlausibilityComparator.

It is currently not used in org.jabref.gui.mergeentries.multiwaymerge.

Should be added.

---

This issue is more an "adventure" to analyze the existing code and test and play around etc.

[Shreyasdone]

/assign-me

[jabref-machine]

Thank you for your continued work in JabRef. At this point, you probably already know the basics and the important links. If not, our contributing guidelines is the place you should go to.

[github-actions]

⏰ Assignment Reminder

Hi @Shreyasdone, this is a friendly reminder about your assignment to this issue.

Warning

This issue will be automatically unassigned in 7 days if there's no activity.

Remember that you can ask the JabRef Guru or DeepWiki about anything regarding JabRef.
Additionally, our contributing guide has hints on creating a pull request and a link to our Gitter chat.

How to keep your assignment

If you are working on it, you can prevent automatic unassignment by:

• Submitting a draft pull request with your progress within 7 days
• Asking for the 📌 Pinned label if you need more time

We appreciate your contribution and are here to help if needed!

[Shreyasdone]

Hey @koppor can you please tell me where I can get the files to test/replicate this

[koppor]

@Shreyasdone This is a "good third issue" - as said

This issue is more an "adventure" to analyze the existing code and test and play around etc.

But I give you the initial start:

1. Open Chocolate.bib from https://github.com/JabRef/jabref-demonstration-libraries/tree/main/chocolate
2. Select entry "Richard_2017`
3. Tools -> Update with bibliographic information via entry data
   
4. see
   
5. See that "date" of OpenAlex is NOT selected
   

In step 5, a date with a day is better than a date without a day. Thus, it should be selected as soon as a fetcher reports that better data.

[github-actions]

📋 Assignment Update

Hi @Shreyasdone, due to inactivity, you have been unassigned from this issue.

Next steps

If you still want to work on this:

• Submit a pull request showing your current state. You will be automatically assigned again.
• Ask a maintainer to assign you again.