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

Extend Citavi6 translator to also import BibTex-Keys #3371

Closed
wants to merge 2 commits into from

Conversation

JAC28
Copy link

@JAC28 JAC28 commented Oct 10, 2024

  • Workaround to work with syntax of Better BibTex plugin
  • Writes Keys into Extra-Field
  • Provided Sample-Data contains Demo-Project with auto-generated Keys. First entry is without Key for testing.

Note: First try failed due to included test cases.

JAC28 added 2 commits October 10, 2024 15:51
- Workaround to work with syntax of Better BibTex plugin
- Writes Keys into Extra-Field
- Provided Sample-Data contains Demo-Project with auto-generated Keys. First entry is without Key for testing.

Note: First try failed due to included test cases.
run ```npm run lint ".\Citavi 5 XML.js``` without error
@JAC28
Copy link
Author

JAC28 commented Oct 10, 2024

Reason for the extension:

When transferring from Citavi to Zotero, the existing BibTex keys are not transferred, if I see it correctly. Using the Better BibTex plug-in ensures that the keys are re-issued, which means that compatibility with previous work based on the Citavi BibTex keys is lost.
If the extra fields contain a Citation Key: BibTeyKey pair, Better BibTex will adopt it. This ensures backwards compatibility of the keys even after transfer to Zotero.

Note This is the same change as initially proposed in #3370 but failed due to linting problems

@JAC28
Copy link
Author

JAC28 commented Oct 11, 2024

I think this can be closed, as the change is included in the still open PR #3183

@JAC28 JAC28 closed this Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant