Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

integrity check and follow up actions #11419

Open
ilippert opened this issue Jun 23, 2024 · 1 comment
Open

integrity check and follow up actions #11419

ilippert opened this issue Jun 23, 2024 · 1 comment

Comments

@ilippert
Copy link
Contributor

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
Copy link
Member

HoussemNasri commented Oct 14, 2024

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).

Image

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Free to take
Status: Normal priority
Development

No branches or pull requests

3 participants