This template is within the scope of WikiProject Books. To participate in the project, please visit its page, where you can join the project and discuss matters related to book articles. To use this banner, please refer to the documentation. For guidelines on this template's usage, see its documentation.BooksWikipedia:WikiProject BooksTemplate:WikiProject BooksBook
This template was considered for deletion on 2017 August 29. The result of the discussion was "Withdrawn".
I personally agree (at least as long as a preview is available and allows easy verification of related WP content), but not every author sees it that way. Another issue is Google does not guarantee that the book or the cited pages stay visible. In practice in many cases it is relatively stable, but not always and an additional drawback is that the visibility might depend on your country.--Kmhkmh (talk) 11:50, 10 September 2011 (UTC)[reply]
As I understand it the purpose of this template to merely provide a Google books link to a specific page and not to be (an often messy and much more comprehensive) citation template and to stay away from the "true citation (template)" wars. In other words this is not a citation template, but a template that allows people not using citation templates to provide useful (page based) online links nevertheless. For that reason imho there is no point in extending with your suggested entries, because for that we already have citation templates.
These changes are causing URL errors to appear in citations where there were no errors before. See, for example: [1] and [2]. Please fix this problem if you are able. – Jonesey95 (talk) 03:37, 23 October 2013 (UTC)[reply]
If a plain URL is required, specifying |plainurl=yes (which needs to be documented) will do that. From your 1st example:
* {{cite book|title=System der Asteriden|url={{google books|SDwb-runOSQC|System der Asteriden|page=PR5|plainurl=yes}}|publisher=Friedrich Vieweg und Sohn |location=Braunschweig}} (1842) with [[Franz Hermann Troschel|F. H. Troschel]] will produce
I guess I'm the person who mucked up... My understanding was that the template would never have worked in citation templates anyway, since it always returned the formatted url and I just added an option for it to return a plain one... Anyway shall I undo it? RainCity471 (whack!) 18:21, 25 October 2013 (UTC)[reply]
No, this does not need to be reverted. I was worried that there would be tons of google books templates in citations, but the job queue appears to be adding them to Category:Pages with URL errors at a rate of only about one or two a day, which is easy to keep up with. – Jonesey95 (talk) 21:51, 25 October 2013 (UTC)[reply]
Ok, I'm afraid i don't know why the job queue is doing this. I guessed I was safe because I thought the template would never have worked in citation templates anyway; I considered all I was doing was adding an option to change the output and it wouldn't affect the default (this is disregarding the change that added the page number; that only added to the title and can't have affected this). It was my fault I forgot to document the change—I sort of remembered a bit later and then forgot. If for some reason the job queue spits out a load of broken templates, ask me and I'll be happy to help. Sorry, RainCity471 (whack!) 22:39, 26 October 2013 (UTC)[reply]
The job queue is a background process that, among other things, recategorizes articles when one of the templates contained ("transcluded", in WP jargon) within the article causes that article to be added to or removed from a category. The job queue effectively performs a null edit on each article, "refreshing" it. It appears to be taking 3-4 weeks to travel through all of Wikipedia these days, so if it adds one or two a day, that means about 30-40 articles will pop up with errors. That's not a problem; human editors create a lot more problems than that.
How to deal with "roman" page numbers and front matter?
If instead of using &PA=n one uses &PR=n this will link to pages number using roman numerals.
Also, I just found you can even use &PP=n for pages before the roman numerals start.
Taking the example from the template documentation:
{{Google books|7ydCAAAAIAAJ|History of the Western Insurrection|page=42|plainurl=yes}}
|text= emits …&dq="text" which works for searching a "direct quote". I have added it to the documentation. HTH HAND —Phil | Talk13:00, 29 April 2016 (UTC)[reply]
Should ignore spaces
Most templates ignore spaces before the "|" when specifying parameters, but this template does not. When I enter {{Google books |1T4ORu6EICkC |page=124 |plainurl=yes}} the URL generated has a space before &pg=PA124 which is an invalid URL. It causes further problems when using the template within another template after the parameter |url=. Can someone fix the template to ignore extra spaces within the generated URL? Thanks. CuriousEric20:10, 15 October 2017 (UTC)[reply]
Triming the whitespace seems to work fine now in the mainline template, both before and after the "|". I am not familiar with testing in the sandbox. CuriousEric01:41, 16 October 2017 (UTC)[reply]
Google 'dq' parameter is not the quoted phrase search
An error in the documentation « |text= searches for a quoted phrase (corresponding to the dq parameter in the Google URL) ». That's not true. The Google Book URL's dq parameter is a mystery, not explained in the Google API documentation or any other part. Testing with a few URL, I suppose that dq is something like a « direct search » (from Google Search or Google Books main page) as opposed to q modified by the search formular of a preview (javascript).
The "quoted search" works with quotes in URL : as in &q="fu bar". Same as Google Search. So the template text param may have to generate an URL with q="bla" or dq="bla" (but not dq=bla).
The Google book tool link provided in the template's documentation leads only to an error page, for me:
Error: Server Error
The server encountered an error and could not complete your request.
Please try again in 30 seconds.
I will try again, as suggested, but my hopes are not high. (Correctly, as it turns out, because a reload after ~60 seconds produced the same message.) Though, the error page does still have a favicon that would seem to represent the tool in question.
For others who have more experience with the tool, is this a common issue with it? Are outages temporary, or likely to be longer-term? Should the link be removed from the documentation? (And in the foolish-optimism department: Does anyone have any replacement links to similar, but currently functioning, tools?)
Never mind — Citer, developed by Dalba, is a much better tool that accepts more types of URLs/identifiers, and it runs on the Wikimedia toolforge. I'll update the template docs to point there instead. FeRDNYC (talk) 09:34, 14 January 2022 (UTC)[reply]