Upgrade StorageGoogle Docs - moving items between word processors
Hello all,
This is super-helpful: https://www.zotero.org/blog/move-zotero-citations-between-google-docs-word-and-libreoffice/.
I noticed that the code inserted by the transfer function is this:
ITEM CSL_CITATION {"citationID": ....}
This doesn't seem to have an 'end' marker, which means that the json would need to be parsed to determine the end of the insertion. (Am I right in this?)
Though I wonder whether the insertion is guaranteed to end in "]]}}}]}"? Or are there more complex cases there this is not the case?
(I suppose more generally itwould be amazing if there was an option to have an 'end' marker. For example, something like {"citationID": ....}
I sometimes insert little-used UTF characters, say γ...γor β ...β or similar to create beginning/end markers that I need to parse later. Of course, here we only need an end-marker.
Though, if the citations always end in "]]}}}]}" then that would work for me.)
Many thanks!
This is super-helpful: https://www.zotero.org/blog/move-zotero-citations-between-google-docs-word-and-libreoffice/.
I noticed that the code inserted by the transfer function is this:
ITEM CSL_CITATION {"citationID": ....}
This doesn't seem to have an 'end' marker, which means that the json would need to be parsed to determine the end of the insertion. (Am I right in this?)
Though I wonder whether the insertion is guaranteed to end in "]]}}}]}"? Or are there more complex cases there this is not the case?
(I suppose more generally itwould be amazing if there was an option to have an 'end' marker. For example, something like {"citationID": ....}
I sometimes insert little-used UTF characters, say γ...γor β ...β or similar to create beginning/end markers that I need to parse later. Of course, here we only need an end-marker.
Though, if the citations always end in "]]}}}]}" then that would work for me.)
Many thanks!
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
I'm not entirely sure if you're requesting something, and if so, what that is? Either way, the transfer doc should not be used for anything other than transferring between editors and any edits to the document in the transfer format are not supported.
https://www.zotero.org/google-docs/?some_code
Basically, within the google doc, that would allows me to extract the actual Zotero item IDs, which then allows me to create a collection on Zotero
It relates back to the earlier discussion here https://forums.zotero.org/discussion/81432/google-docs-plugin-how-to-the-urls-relate-to-zotero-items#latest and your kind follow-up via zotero-dev (and ref to this piece of code:
https://github.com/zotero/zotero-google-docs-integration/blob/master/src/apps-script/Code.js#L85-L157 ).
Thank you @adomasven !
(1) We want to be able to make a bibliography outside the doc (as a folder on Zotero). The ref-extractor could work great for that (as long as it gives us group/itemkeys - but we can probably adjust that!)
(2) More complicated, we want to be able to insert refs into the gdoc, and then link to our kerko installation: e.g. https://docs.edtechhub.org/lib/XI5PXVB3. So far we have done this via a separate plugin, but the above "transfer" function would allow us to use the Zotero citation mechanism (in gdocs), then run transfer, and then run a tidy-up function that converts the anchor/json appropriately.
To explain: Have a look at this doc, https://docs.edtechhub.org/lib/HE2Q6Z8Y/download/SVBHUHZQ/Adam et al. - 2020 - The Maldives and Sri Lanka Question & Answer Sess.pdf, page 7. You'll see two links, that take you back to https://docs.edtechhub.org.
These links are produced within the Google doc, as part of our referencing system (and the Google doc is then used to produce the PDF directly).
Hope that makes sense :)