-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Zotero: can’t import two items with the same title #11328
Comments
Sadly, in logseq, the title of the details page is taken as the identifier for an entry from Zotero. It follows the usual way that the pape title is treated in Logseq: the unique idetifier to the page. So I think that's an expected behavior. One solution (maybe the only one) is to adjust all the duplicated titles to something different. PS: The similar problem should also happen to PDFs with the same name. They might just be regarded by Logseq as the same one when you make annotations in them. |
Thanks for your answer. I see three possible solutions:
Do you think one of these options could be relevant ? |
Thanks for the ideas. You're right, having more naming styles could solve the name conflicts. |
Hi, as a potential solution, in my plugin I implemented an experimental feature using Zotero title template in the page title. Check it here |
Search first
What Happened?
Two items in Zotero can have the same title. This is especially the case with introductions of collective books, written by the editor(s) and that are often simply titled “Introduction”. I have a lot of these in my collection. But, in Logseq, once you have a page named
@Introduction
, all subsequent tries to add a new document with the same title will simply create a new hyperlink to the first@Introduction
page.Reproduce the Bug
/Zotero
/Zotero
Expected Behavior
A new page, with a different name (eg. Introduction2 or Introduction - Title of the book) is created.
Screenshots
No response
Desktop or Mobile Platform Information
Linux AppImage, v. 0.10.9
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: