Zotero and pubmed files now have a cache invalidation timeframe on them, but this won't work for the github hosted cache files since the timestamp won't update if they are the same, which means they will be redownloaded everytime it runs. This makes a mockery of the cache! Short term hack might be to set the cache invalidation to a very big number (10000+) on some datasets where I know zotero is static.
Zotero and pubmed files now have a cache invalidation timeframe on them, but this won't work for the github hosted cache files since the timestamp won't update if they are the same, which means they will be redownloaded everytime it runs. This makes a mockery of the cache! Short term hack might be to set the cache invalidation to a very big number (10000+) on some datasets where I know zotero is static.