Menu
Install Zotero and Zotero Connector Open your browser and navigate to. Start by downloading Zotero 5.0 for your operating system (e.g. After Zotero 5.0 is installed on your device, open the desktop app and click 'Set up syncing'. Log-in using your personal Zotero account. Next, install the Zotero Connector. This add-on or extension will allow you to save sources directly from your browser with a single click of a button.
If you are unsure how to add an extension or add-on, more information can be found on the download page on Zotero's website. Note: You must be using Chrome, Firefox, or Safari to install the Zotero Connector. Save an article to Zotero You are now ready to start saving sources to your Zotero library. You must have the Zotero Desktop app running and open on your computer for saving to be enabled. Start by finding a resource that you would like to save. One there, click on the Zotero Connector button that has been added to your browser.
The newly installed button will change in appearance depending on the resource you are trying to save, but it will always be in the same location. Here are some examples showing the different appearances of the Connector button. Create a bibliography You can create citations for single sources or multiple sources at the same time. For a single article, right-click on the article you want to cite and select 'Create Bibliography from Item'. For multiple items, either ctrl+right-click on the individual sources you need, or right click on the entire collection on the left-hand side of the page.
Feb 14, 2019 - Getting Zotero: Installing Firefox extension. To install the Zotero extension in your Firefox browser, visit and click the big. Jan 10, 2018 - To create your free account go to and click the. Go to Tools >> Preference >> Cite >> Install Microsoft Word Add-in.
Once you make your selection, another window will pop up asking you about the format that you would like for the bibliography. Here, you will want to select the correct citation style that you will be using, as well as the output format. When choosing the output method, the easiest method may be to choose 'Copy to Clipboard'. This copies the bibliography to your computer's clipboard and allows you to paste it into any word processor. Another good option is to 'Save as RTF', which stores the bibliography as.rtf file which can be opened by any word processor (e.g. Microsoft Word).
Zotero Connectors Building. git clone -recursive. cd zotero-connectors. npm install./build.sh -d The connectors are built in build/. Running from the build directory Chrome. Go to chrome://extensions/. Enable 'Developer Mode'.
Click 'Load unpacked extension' and select the build/browserExt directory. Firefox. Go to about:debugging. Click 'Load Temporary Add-on' and select the build/browserExt/manifest.json file.
OR. Get and install the. cd to project root./scripts/firefox/runxpi Safari. In Preferences Advanced check 'Show Develop menu in menu bar'. In menu bar Develop Show Extension Builder.
Press the '+' in the bottom left, choose 'Add Extension'. Select the build/safari.safariextension directory Automatic rebuilding/reloading Chrome on MacOS. brew install chrome-cli. npm install -g gulp. cd to project root. npm install.
build.sh -d. gulp watch-chrome As files are changed, the connectors will be rebuilt automatically and Chrome will reload the extension. Firefox. Get and install the. cd to project root. npm install.
build.sh -d. gulp watch./scripts/firefox/runxpi (in a different terminal window) As files are changed, the connectors will be rebuilt automatically and Firefox will reload the extension. Others. cd to project root. npm install. build.sh -d.
gulp watch As files are changed, the connectors will be rebuilt automatically. You will need to manually reload the extension in the browser being developed for. Requirements for packaging extensions from the command line. Copy config.sh-sample to config.sh and modify as necessary. Safari/Chrome extension certificates. or.
xar with Tests To run tests locally, build the extension with the -d flag, and then run $./test/runtests -p c Test files are located at src/common/test. See src/common/test/testSetup.js for test framework documentation Developing Zotero Connectors are built with standard tools, such as browser extension APIs, but the architecture is quite complex. This section is a short overview of some of the complexities, to make it more accessible for newcomers. Technologies Chrome/Firefox Browser Extension Framework The functionality exposed on Chrome and Firefox is provided by the Chrome extension framework, which has also been adopted by Firefox.
See and for more information. Safari Extension Framework The functionality exposed on Safari is provided by the Safari extensions framework.
See for more information. Zotero Translator Framework The Connectors share code with, to support translation. A basic understanding of how translation works or at least the handlers it exposes in Zotero will be highly useful in understanding the codebase.
Components Saving resources to Zotero library is facilitated by two major components: the Zotero Connector running in the browser and either the Zotero client or zotero.org web api. The Zotero Connector itself is split into two components: code running on the webpage and a background process. A) Injected scripts for individual webpages Each webpage is injected (//) with a full Zotero. A instance orchestrates running individual translators for detection and translation.
The translation framework shares some code with the Zotero codebase and provides custom classes concerning. These custom classes talk to the background process (b) of the Zotero Connector for functionality outside the translation framework, such as retrieving translator code and sending translated items either to Zotero (c) or zotero.org (d). B) Background process The Connector runs a (//) which works as a middle-layer between the translation framework running in inject scripts (a) and Zotero (c) or zotero.org (d).
The background process maintains a cache of translators and performs the initial. Translators whose target regexp matches the URL of a given webpage are then further tested by running detectWeb in injected scripts. A list of translators and their code is fetched either from. The background process is also responsible for updating the extension UI, kicking off translations, storing and retrieving connector preferences and sending translated items to Zotero or zotero.org. Browser specific scripts are available for. C) Connector server in Zotero When Zotero is open it runs a on port 23119.
The HTTP server API accommodates interactions between the Connectors and Zotero client. Calls to in this codebase are translated to HTTP requests to the connector server. Note that Zotero cannot interact with the connectors on its own accord.
All communication is Connector initiated. D) zotero.org API When Zotero is not available item saving falls back to using. The interactions with zotero.org API are defined in Message passing The only way for the background extension process and injected scripts to communicate is using the message passing protocol provided by the browsers (//). Injected scripts often need to communicate to background scripts. To simplify these interactions, calls to functions in background scripts are monkey-patched in injected scripts. These calls are asynchronous and if a return value is required, it is provided either to a callback function as the last argument of the call or as a resolving value of a promise returned. Contains the list of the monkey-patched methods.
If the method value is false no response is expected, otherwise the calls provide a response. An optional pre-send processing on the background end and post-receive processing on the injected end is possible to treat values that cannot be sent as-is via the messaging protocol. The background process registers message listeners in. Zotero.Messaging class also provides a way to send messages to injected scripts and add custom message listeners. The injected scripts monkey-patch methods in messaginginjected.js(/) Zotero.Messaging class also provides a way to send messages to the background process and add message listeners. Build process The build process combines files from the Zotero codebase, common files to all connectors and specific files for Chrome/Firefox/Safari connectors.
At the moment the build process is awkward and uses a SH script and gulp procedures. This will be reconciled in the future to only use gulp.
build.sh and. gulp process-custom-files build.sh performs on copied files Bookmarklet The development of the bookmarklet has been abandoned since early 2015. This is partially due to previous developers departing the Zotero project, partially because a limit to what's possible within a bookmarklet has been hit and partially because the support for bookmarklets is being largely discontinued on platforms where it would be relevant: Edge and Chrome for Android do not support bookmarklets. However, an interest to continue supporting the bookmarklet still exists for IE and iOS devices.
Contact If you have any questions about developing Zotero Connectors you can join the discussion in the.