integrity check and follow up actions

[ilippert]

Is your suggestion for improvement related to a problem? Please describe.
I like the integrity check. I am frustrated that I cannot find wizards that help me to solve the errors found.

Describe the solution you'd like
I would like to select a finding/warning (or several at once) and then use a right click to select a possible action. E.g. for a file name with an ? offer to repair that, of for a Warning about a latex command (e.g. \enquote) I could "register" the command so that it does not generate a warning anymore.

[HoussemNasri]

Additional fixable finding/warning/reports can include:

• Citation key deviates from generated key --> generate citation key for that entry
• Capital letters are not masked using curly brackets {} --> Basic string manipulation

We can go with the right click approach or an approach similar to the image below or a combination or both: right-click when multiple possible fixes, and single-click when one possible fix (common case).

Random thoughts

• Applied fixes should be transparent to users. This means users should be informed about the previous inconsistent value of a field and the new consistent value that will be applied as a fix, possibly showing a difference (diff).
• Sometimes multiple fixes are possible (.e.g. non-ASCII encoded character found), here we can delete all non-ascii characters, enclosing them in braces, or other actions. The UI should offer multiple choices of fixes when available.
• While not directly related to this feature, integrity checks can sometimes be ignorable. For instance, if I intentionally use non-ASCII characters in a field, I wouldn't want it flagged as inconsistent every time I scan. There should be a column to mark integrity checks as ignored.

[priyanshu16095]

/assign-me

[github-actions]

👋 Hey @priyanshu16095, 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 the issue isn't closed within 90 days (by 12 May 2025). A maintainer can also add the "📌 Pinned"" label to prevent automatic unassignment.

[HoussemNasri]

Hello @priyanshu16095, you currently have four assigned issues. Please ensure those are completed or unassigned before taking on additional tasks.