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

Field properties for context menu, cleanup actions, and integrity checker #59

Closed
oscargus opened this issue Nov 26, 2015 · 3 comments
Closed
Labels

Comments

@oscargus
Copy link

The current integrity checkers are executed based on a hard-coded file name. I was thinking that maybe it makes sense to add methods and variables in BibtexFields such that one can set which integrity checkers should be used for specific fields.

The background is that I tried this approach for checking numeric fields, based on isNumeric, but it turns out that "author" is set in the default preferences to be numeric, so that branch will never show up as a PR... Part of the reason is also that the IEEEtranBSTCTL type has some rather well specified fields, but I do not want to clutter IntegrityCheck with those hardcoded...

Looking at a bigger picture, for a Biblatex article there are fields like "translator", "annotator", "commentator", "editora", "editorb", "editorc" for which the AuthorNameChecker should be run, but one do not really want to have eight (with author and editor) if statements. There's "subtitle", "titleaddon", "maintitle", "mainsubtitle", "maintitleaddon" for the TitleChecker.

It's not really clear how BibtexFields relate to Biblatex though, but it may become clearer...

@oscargus oscargus changed the title Integrity checker properties Field properties for context menu, cleanup actions, and integrity checker Nov 30, 2015
@oscargus
Copy link
Author

This approach could also be applied for the right-click menu and cleanup actions. The idea is to let the fields define their own properties rather than switching over all possible combinations.

@matthiasgeiger
Copy link
Collaborator

👍

See also JabRef#416 and JabRef#419 - some checks are sensible only for BibTeX but not for BibLaTex.

@oscargus
Copy link
Author

I close this in preference of JabRef#978

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants