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

format of zotero:// links #53

Open
damiencourousse opened this issue Jan 4, 2021 · 8 comments
Open

format of zotero:// links #53

damiencourousse opened this issue Jan 4, 2021 · 8 comments

Comments

@damiencourousse
Copy link

Reading from the source code, I understand that this extension uses the following format for zotero:// links:

  • with zotero cite keys: zotero://select/items/ + key

However, exports from better bibtex can generate links with two different formats, as follows (see here)

  • with the citation key: zotero://select/items/ + citekey
  • with the zotero reference key: zotero://select/library/items + key

However, I could not find a specification of the different link formats, so I don't know how to handle this inconsistency.

Currently, if i drag'n drop a reference from Zotero into an org document, with better bibtex, to generate a zotero:// link, I cannot open those links with zotxt-emacs. I use zotxt-emacs to open zotero:// links, and I would like to have the possibility to use both better bibtex and zotxt-emacs to insert links to references.

@egh
Copy link
Owner

egh commented Jan 15, 2021

Hi @damiencourousse ! Sorry for the late response. I think this is mistake in the BBT export. It should look like zotero://select/items/[LIBRARY]_[KEY]. This was an internal format used by Zotero itself - it may still be. I don't use the translators - I insert links directly from emacs - so I hadn't seen this issue.

@damiencourousse
Copy link
Author

Thanks for your feedback. I have opened an issue in BBT. Feel free to comment!

@damiencourousse
Copy link
Author

You are right. The current format is zotero://select/items/[LIBRARY]_[KEY]. It was a misunderstanding from me, since on my setting, [LIBRARY] is 1.

As reported in the BBT issue, this format is still supported but deprecated. Do you plan updating the format of zotero links in zotxt-emacs?

@egh
Copy link
Owner

egh commented Jan 22, 2021

As reported in the BBT issue, this format is still supported but deprecated. Do you plan updating the format of zotero links in zotxt-emacs?

Ah, I didn't know that! I will fix this. Thank you.

@brunoperdigao
Copy link

Hi, I hope it is related to this topic, but I am wondering if zotxt can handle zotero links created by zotfile. Their format is zotero://open-pdf/library/items/. These links open the pdf in a specific page, related to the annotations.
I tried to open with the org-zotxt-open-attachment command but It didn't work.

@egh
Copy link
Owner

egh commented Apr 14, 2021

@brunoperdigao Good question! Right now it can't, but it would be very easy to implement. I assume the item key follows after /items/?

@brunoperdigao
Copy link

@egh Yes, the item key and the page number, which directs to the specific page, for example zotero://open-pdf/library/items/XXXXXXXX?page=3
I tried to find more information on their documentation, but they don't go into much detail about it: http://zotfile.com/#extract-pdf-annotations
It would be great to have this implemented! Thanks

@zzeitt
Copy link

zzeitt commented Sep 15, 2023

I had the similar issue on the iOS platform.
It seems like the link generated by zotxt cannot be recognized by Zotero iOS.
However, links formatted like : zotero://select/library/items/XXXXXXXX is valid (you can jump to the expected item after click the link).

Infomation about the Zotero iOS link/url processing could be found here: https://github.com/zotero/zotero-ios/blob/5d0816061a5ed9849c82ac8ca087c4dc2ee489d2/Zotero/Controllers/CustomURLController.swift#L37

So I wonder what is the status of the link format upgrading plan?

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

No branches or pull requests

4 participants