(a) find DOI on page; (b) lookup properties on server; (c) save data and notes to the cloud.
DOIs are automatically identified from the page you are viewing. You cannot customize this aspect of the extension (maybe in the future you will be able to). If a DOI is returned, it will be submitted to the following URL. The string %%DOI%% will be filled in with the doi. It must be accessible via an https connection or else allow cross-origin requests. DOI_LOOKUP_URL: <specified in options> Whether or not data is successfully obtained automatically, the next stage is to submit comments and data to another URL, which will be responsible for saving the data somewhere in your personal space online. Again, it must be accessed via an https connection or else allow cross-origin requests. There are two separate URLs here, one for the case that data was successfully obtained (SAVE_DATA_URL_AUTO), and one for the fallback case (SAVE_DATA_URL_MANUAL). Here %%someThINg%% will be replaced by data.somEthIng, where data is the JSON object returned by the DOI_LOOKUP_URL, and something is case insensitive. As before, %%DOI%% will be substitued with the doi. In addition %%URL%% will be substituted with the page's URL and %%COMMENT%% will be substitued with the text in the comment box. SAVE_DATA_URL_AUTO: <specified in options> SAVE_DATA_URL_MANUAL: <specified in options> If you wish, you can specify the URL of where you can view the saved data. This is only so that a link can be provided for your convienience. DOCUMENT_URL: <specified in options> The following field is provided as a convience. If you give it, you can then use %%DOC%% to refer to it in SAVE_DATA_URL_AUTO, SAVE_DATA_URL_MANUAL, and DOCUMENT_URL. DOC_ID: <specified in options>
- (2013-01-19) Tao Ye: great tool to resolve DOI in webpage, thanks very much! But I met one problem: DOI: 10.1016/B978-0-12-398309-1.00006-8 cannot be resolved by the app.