quarto-dev / quarto-dev/quarto
Zotero Integration: Scope "Connect Web Library" access to that of API key
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
Bug description
I want to collaboratively work on a .qmd file using a shared Zotero group library. I have generated an API Key scoped to that library with only read access, which I want to share with my collaborators. However, it seems Quarto expects an API key with access to all of the groups and the user library, which is not what I want.
Steps to reproduce
- Configure "Quarto › Zotero: Library" to "web"
- add the group's title to "Quarto › Zotero: Group Libraries",
- run "Quarto: Connect Zotero Web Library"
Actual behavior
I get an "unauthorized access" error for other group libraries which I do not want to share, and for the main user library, which I also do not want to share.
Expected behavior
Only the library/libraries specified in "Quarto › Zotero: Group Libraries" are accessed any synchronized.
Your environment
-
VS Code:
Version: 1.96.4 (user setup)
Commit: cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba
Date: 2025-01-16T00:16:19.038Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045 -
Quarto Version 1.118.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the VS Code Zotero settings for "Zotero: Library" and "Zotero: Group Libraries", then trace the "Quarto: Connect Zotero Web Library" flow. Reproduce the unauthorized-access error with a read-only API key scoped to one group, and consider the issue complete when only the configured group libraries are accessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100