This repo was forked from https://github.com/beloglazov/zotero-scholar-citations and https://github.com/MaxKuehn/zotero-scholar-citations.
This repo aims to make ZSC works better with Google Scholar, especially in China, and fix some minor problems by the way.
New features:
For example, if a paper titled "Explaining and Exploiting Adversarial Examples" has a year of "2013" in Zotero, the original version will produce a URL that results in an incorrect query (https://scholar.google.com/scholar?q=Explaining+and+Harnessing+Adversarial+Examples&hl=en&as_sdt=0%2C5&as_ylo=2013&as_yhi=2013), while a looser range, such as 2012 - 2014, will hit the correct query (https://scholar.google.com/scholar?q=Explaining+and+Harnessing+Adversarial+Examples&hl=en&as_sdt=0%2C5&as_ylo=2012&as_yhi=2014).
v2.0.5
v2.0.6
v2.1.0
[email protected]
. The file contents should be the absolute path to the root of your plugin source code directory, where your install.rdf file is located.extensions.lastAppBuildId
and extensions.lastAppVersion
. Save the file and restart Zotero. This will force Zotero to read the extensions' directory and install your plugin from source, after which you should see it listed in Tools → Add-ons. This is only necessary once.-purgecaches -ZoteroDebug
, for example:
./zotero.exe -purgecaches -ZoteroDebug
This is an add-on for Zotero, a research source management tool. The add-on automatically fetches numbers of citations of your Zotero items from Google Scholar and makes it possible to sort your items by the citations. Moreover, it allows batch updating the citations, as they may change over time.
Read about how the add-on was made: http://blog.beloglazov.info/2009/10/zotero-citations-from-scholar-en.html
When updating multiple citations in a batch, it may happen that citation queries are blocked by Google Scholar for multiple automated requests. If a blockage happens, the add-on opens a browser window and directs it to http://scholar.google.com/, where you should see a Captcha displayed by Google Scholar, which you need to enter to get unblocked and then re-try updating the citations. It may happen that Google Scholar displays a message like the following "We're sorry... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now." In that case, the only solution is to wait for a while until Google unblocks you.
The add-on supports Zotero Standalone. To install it:
Currently, Zotero doesn't have any special field for the number of citations, that's why it is stored in the "Extra" field. To sort by this field you have to add it in the source listing table.
In version 1.8 the field for storing the number of citations has been changed from "Call Number" to "Extra" -- please update your column configuration.
Version 2.0.0 introduced a new format for storing the citation count, i.e. ZSCC: 0000001
. Unfortunately that means existing pre 2.0.0 entries are incompatible in terms of sorting and you have to update them.
If you just straight up update your entire collection you're bound to run into a captcha. Once you do run into one, all following queued update request will fail and you will be prompted for each and every one of them. Consider updating your collection in batches of 5-10 items at a time.
This limitation is a major inconvenience and fixing or at least alleviating it is the first thing on the priorty list (see the RoadMap).
As of Version 2.0.2 items whose citation count could not be updated will be marked with a staleness counter [s0]
, e.g. ZSCC: 0000042[s0]
, to signal the user that ZSC was unable to update the number of citations.
If ZSC continuesly fails to update an item, it increases the staleness count up to a maximum of 9 and then wraps around.
The format of the staleness counter allows you to search for items with stale citation data by entering [s
in Zoteros search bar.
ZSC will
Consider temporary cutting out/deleting the "Extra" content. ZSC will update the citation count. After that you can simply append the previously removed information.
The most likely culprit is that ZSC search is too precise :^). Some Items do not have as complete of an author list on google scholar as they have in Zotero.
Here's how you can find out weather that's the problem
Help > Debug Output Logging > enable
Help > Debug Output Logging > View Output
[scholar-citations] GET https://scholar.google.com/scholar?hl=en&as_q=THE_TITLE_OF_YOUR_ITEM&as_epq=&as_occt=title&num=1&as_sauthors=AUTHOR1+AUTHOR2+AUTHOR3
One combination of authors will certainly yield the correct search.
You can also temporarly recreate that combination in Zotero. ZSC will then successfully query that item. Once you re-add the author however, updates will fail again. :(
The RoadMap can be found here.
The original maintainer Anton Beloglazov seems semi-active.
Texot fixed some stuff that needed fixing BADLY, that is
No Citation Data
in failure cases instead of 00000
But there's more that should be done!
Copyright (C) 2011-2013 Anton Beloglazov
Distributed under the Mozilla Public License 2.0 (MPL).