Upgrade StorageZotero button for web pages
Some journals have import button for reference managers directly on their pages. Mendeley provides a mechanism for importing of articles based on some basic information: an article URL or DOI. With this mechanism it is possible to embed an "Add to Mendeley" button on the journal website (https://www.mendeley.com/import/information-for-publishers). I see this buttons also for different reference managers.
Is anything similar available for Zotero?
Is anything similar available for Zotero?
html tag can be this:
<a title="Add this article to your Zotero library" href="javascript:var d=document,s=d.createElement('script');s.src='https://www.zotero.org/bookmarklet/loader.js';(d.body?d.body:d.documentElement).appendChild(s);void(0);"><img src="https://www.zotero.org/static/images/theme/zotero_icons/zotero-z-16px.png"></a>
I use available Zotero picture for this example. For final version can be prepared new icon.
And information for the publisher can be like something this: "Please note that import button will only work if your website is supported by the Zotero bookmarklet."
But for your question: Zotero identifies the translator by first matching on URL (some translators are completely generic, some for a very specific URL range, some in between) and then running code to detect whether the page contains the right data to import and what type of resource it contains (multiple, book, article, et.c).
This is tricky, because if sites aren't targeting specific clients, we don't want to encourage them to do so by providing a Zotero button. But for the ones who are (and I'm not sure how widespread that actually is), it's a shame to miss out on that publicity.
Users who have Zotero installed will not need a button, so the target audience of the clickable part of it would be people who have not yet installed Zotero.
The setup and presentation would be similar to another product's download button: a snippet of code configured (optionally) with an end-point for citation data. The code would crawl the current page and the endpoint, and if it turns up something that Z can work with, the "badge" goes smiley. If the end-point fails but there is data in the page (COinS, or useful-looking embedded metadata), it goes puzzled. If nothing is found, it looks terribly unhappy.
If Zotero is not installed, clicking on the badge would jump to this site; otherwise, click would be disabled, and the badge would just offer its opinion of the likelihood of finding data.
If the badge had a stable ID across all installs of a given version, it could provide a hook to the end-point (RIS, BibTeX or whatever) that could be picked up by a generic translator. Sites that want to support Zotero, but aren't keen on implementing their own translator, could just deploy the badge on their pages.
Do you mean for the benefit of people using the bookmarklet? To be clear, the bookmarklet is the choice of last resort, and it's not really something we want people using — anyone doing real work with Zotero should be using one of the browser extensions, which already provide this indicator. The bookmarklet can be useful on mobile, where we don't currently have native apps, but I don't see us starting to ask sites to embed indicators in their UIs just to make up for the inherent limitations of bookmarklets. The bookmarklet should also just fall back to webpage saving if there's no metadata (not sure if it does now).
A button like this would actually be more confusing for people using the bookmarklet for legitimate reasons, because, assuming the button didn't do client-less saving itself, clicking on it would tell them to install Zotero.
Now, I suppose we could make a button that did both: function equivalently to the normal save button if Zotero was installed and otherwise function like the bookmarklet and save directly to the API. That still risks giving people a faulty impression of Zotero. But we do have other opportunities for encouraging people to install the client (e.g., on the website, where people who used the button would eventually end up to interact with their data). We could probably even detect the user agent and, if we saw that someone was using a browser that there was an extension for, offer a subtle suggestion to install it in the saving progress window.
One thing to keep in mind: there is probably a not-insignificant risk of confusing people here. "Which of these two buttons do I click?" Or, worse, "I'd love to use Zotero, but I almost never see a Zotero button..."
The way I see it, the benefit for sites and existing Zotero users would be having a prominent save button in a convenient spot in the page — maybe even as part of search results, where the Select Items dialog is kind of awkward (though we could probably improve that separately). We could probably offer, in addition to a button, some kind of JS hook that sites could fit into their existing interface. (Not that they'd do it, but imagine that you could add Zotero to the list of reference managers in Google Scholar, such that you could click "Import into Zotero" and have that be equivalent to clicking the Zotero button, choosing the right item in the Select Items dialog, and clicking OK.)
The benefit for people on mobile would be a way to save from the page without pulling up the bookmarklet (which, let's face it, they're probably not using, because who knows how to install a bookmarklet on a phone?).
The benefit for the project would be introducing Zotero to more people.
If you're concerned about users of the button failing to discover the full Zotero client, I think a prompt/reminder "Have you tried the full version of Zotero?" at the saving dialogue would work well. The Mendeley button takes users to the login page where it advertises/prompts them to download the full client.
Besides the free advertising, a button would also help greatly with use on mobile devices. The bookmarklet is hard to use on mobile.
"All SafetyLit records are available for automatic download to Zotero & Mendeley"
For example see:
http://www.safetylit.org/citations/index.php?fuseaction=citations.viewdetails&citationIds[]=citjournalarticle_511438_24
Perhaps this could be stated more eloquently but I think it gets the point across. On other pages, I acknowledge the value of Zotero in the SafetyLit production process. I am open to suggestions that might increase Zotero's visibility on the SafetyLit site.
Could some similar statement be useful to recommend for other sites?
What I would love to see is some sort of logo that could be placed on sites where (yet to be determined) minimum metadata content and standards are met. How standards compliance would be assessed could be a problem. I consider the possibility of this being a role of the CSL working group.
For this thread, I think the relevant question is just what we present to users. Yeah, that's frustrating. So I guess given the choice between more or fewer opportunities to get people in the door (after which we have other opportunities to show them better workflows), we should opt for more.
I'm pretty strongly opposed to a button that would would do bookmarklet saves even when someone had Zotero installed, though, so I think that leaves a modal button like I suggest above, which triggered client saving when available and otherwise performed a bookmarklet save (with a suggestion on appropriate platforms to get the client).