Repository navigation
Conversation
Author
|
Closing at the requester’s direction; the proposed patch is withdrawn. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prefer Zotero's native
citationKeyfield when naming pages imported with/Zotero. If the native field is blank or unavailable, continue reading the legacyCitation Key:line from Extra.Zotero 8 and later store Better BibTeX keys in the native field. With Zotero 10,
Use citekey as your page titlecurrently falls back to the full title because the extractor only checks Extra.Validation
citationKeyfields and noCitation Key:lines in Extra.git diff --checkpasses.Related: #31 proposes the same native-field lookup. This version also covers a blank native field and includes regression tests.