Minimal necessary changes to run SQL query #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have also proof-read the README and converted it to Markdown format for better legibility. Cheers! Details below.
I attempted to use the SQL query as-is but got errors related to the table
creatorData
which appears to have been renamed tocreators
by Zotero (just my guess). As none of the forks on Github contained newer code, I took it upon myself to attempt a fix.My fix works for me, so I thought I could send you a PR in case you're still maintaing this code.
I also removed the lines referencing
shortName
, as I could not find (at a very quick glance) any such column in the available tables. The query now runs without errors as given above.NB. I'm not at all comfortable with SQL syntax! So please double-check my code. Also, at least for me, the created R dataframe (see above) appears to have many duplicate rows (almost 4000 entries in Zotero but over 8000 rows returned by SQL query) and I have now idea why. Anyway, that's easy enough to work-around in R.
My environment: