Jump to content

Module talk:Find sources/Archive 1

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Lowercase sigmabot III (talk | contribs) at 06:14, 3 April 2022 (Archiving 2 discussion(s) from Module talk:Find sources) (bot). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Archive 1

The "news" link hasn't been working for a while. Instead of updating it to match the normal {{find sources}} template, what do you think about scrapping it altogether? The point of this template is the quick link to the RS search, which is included with the {{VG deletion}} delsort template (which also needs to be updated). czar · · 14:41, 22 April 2013 (UTC)

Request for proper capitalization

For proper capitalization, could someone please edit Module:Find sources/templates/Find sources to change "highbeam" to "HighBeam" and "wikipedia" to "Wikipedia"? Thanks! GoingBatty (talk) 18:47, 31 January 2016 (UTC)

 Donexaosflux Talk 19:08, 31 January 2016 (UTC)

Google

Is there any reason that Module:Find sources/links/google sets the results per page to 50 instead of the user’s preference (or if it’s by design, why not 100)? Also, can we document the as_eq parameter with a link to say, this documentation? —LLarson (said & done) 16:33, 5 July 2016 (UTC)

 Done Having waited a sufficient amount of time with no objections, I removed the 50-results-per-page parameter from the Google search. —LLarson (said & done) 03:49, 15 February 2019 (UTC)

Regarding the latest revision to this template

Regarding this revision, “‹ The template below (Find sources mainspace) is being considered for merging. See templates for discussion to help reach a consensus. ›” can be seen in the template itself and on pages which use it, such as Ping (video gaming). Shouldn’t it be surrounded with <noinclude> tags?
PapíDimmi (talk | contribs) 19:40, 10 May 2017 (UTC)

Way too late, but no, it is intentional for TfD tags to show up on uses. {{3x|p}}ery (talk) 22:41, 15 February 2019 (UTC)

The purpose of this edit is to provide increased privacy and security for users by having the Module:Find sources/links/jstor template generate an HTTPS link to JSTOR instead of the current HTTP link. The JSTOR search URL appears to support HTTPS. In Module:Find sources/links/jstor, please change http://www.jstor.org/ to https://www.jstor.org/ instead. --Elegie (talk) 05:53, 17 May 2017 (UTC)

@Elegie:  Done -- John of Reading (talk) 06:11, 17 May 2017 (UTC)

Update Google Images to use new-style URL and forced HTTPS

I switched the Google Image search format string to a newer format at Module:Find sources/links/google free images/sandbox, and was hoping for it to be applied to Module:Find sources/links/google free images.

The current template uses the old-style Google image search URL format, with google.com/image?tbm=isch instead of google.com/search?tbm=isch. Currently the old format redirects to the new format, but I think it would be better to just use the new format to avoid any broken links in the future. Also, the protocol-relative URL scheme is now obsolete so I changed it to use https:// instead. If this is applied and works out I might make some similar changes to the other Google URLs. Thanks, Habst (talk) 15:04, 24 June 2018 (UTC)

Done — JJMC89(T·C) 17:25, 24 June 2018 (UTC)
@Habst: Thank you for the edit request! Fixes like these are very welcome. (And of course thank you to JJMC89 for carrying it out. :) — Mr. Stradivarius ♪ talk ♪ 12:30, 25 June 2018 (UTC)

Highbeam removed

I've removed the Highbeam link from the template, as the service is no longer working - see https://www.questia.com/hbr-welcome for the public statement. — Mr. Stradivarius ♪ talk ♪ 23:41, 4 January 2019 (UTC)

Some google searches using this module have "-wikipedia" at the end

I've noticed an issue occurring with Template:Find sources mainspace that I believe originates with this module..
An example of what is occurring:
On this diff you can see Template:Article for deletion/dated at the top. The first two Find sources links search with "-wikipedia" included in the search term, which seems to negatively affect the results coming back.
I'm hoping that someone may know what is wrong so that this can be corrected. — Preceding unsigned comment added by Vanstrat (talkcontribs) 02:09, 5 January 2019 (UTC)

RfC of potential interest

An RfC is underway that interested "watchers of this page" wound enhance by participating, I hope that many will! The discussion is located at Wikipedia talk:Twinkle#RfC regarding "Ambox generated" maintenance tags that recommend the inclusion of additional sources. Thank you.--John Cline (talk) 07:05, 29 January 2019 (UTC)

Too complicated

This module seems to me like it is needlessly complicated. Why is it a good idea to store the configuration for each template in its own module subpage instead of in the wikitext of the template? That appears to make it harder to edit for no apparent reason. {{3x|p}}ery (talk) 02:32, 15 February 2019 (UTC)

I am guessing because auto-documentation template also uses it? —  HELLKNOWZ   ▎TALK 11:33, 15 February 2019 (UTC)
It would still be possible to implement autodoc even without /templates cfg pages. {{3x|p}}ery (talk) 19:59, 15 February 2019 (UTC)
As I have just done. I also think that the /autodoc template config pages should also be in Wikitext and associated with the template, but it's not clear exactly where. {{3x|p}}ery (talk) 21:09, 15 February 2019 (UTC)

See Wikipedia:Templates for discussion/Log/2019 February 15#Module:Find sources/templates/find sources. {{3x|p}}ery (talk) 21:54, 15 February 2019 (UTC)

Template-protected edit request on 30 July 2020

Please copy Module:Find sources/sandbox to Module:Find sources. This will allow the template to generate search queries for arbitrary page titles (specified by |title=) with parenthetical disambiguators separated from the main part of the title (this is already supported for the current page title).

Please also copy Template:Afd2/sandbox to Template:Afd2, which will make use of this new parameter.

I posted a section on Wikipedia talk:Articles for deletion#Find sources and parenthetical disambiguiators proposing these changes. There has been no response in the past week. The testcases are unaffected. The change is demonstrated in one of my sandboxes. Danski454 (talk) 20:16, 30 July 2020 (UTC)

 Done Please document the new parameter. * Pppery * it has begun... 01:02, 31 July 2020 (UTC)

Template-protected edit request on 19 August 2020

Please add a link to Bing and DuckDuckGo as many people use these search engines as well when looking for sources on Wikipedia. (I use Bing myself.) Aasim 01:06, 19 August 2020 (UTC)

 Not done: please make your requested changes to the module's sandbox first; see WP:TESTCASES. ProcrastinatingReader (talk) 10:32, 19 August 2020 (UTC)

Template-protected edit request on 26 November 2020

Please add a link to the Open Library, a book-oriented project of the Internet Archive. I've drafted the subpage Module:Find_sources/links/openlibrary for review and testing. I would have sandbox tested it, but can't seem to find my way to the right sandbox. LeadSongDog come howl! 17:42, 26 November 2020 (UTC)

This should be discussed at least a little before editing this widely used module. Taking the simple {{Find sources}} example from the {{Find sources}} documentation, what would the new output look like? Has there been any discussion about adding this? Johnuniq (talk) 22:58, 26 November 2020 (UTC)

Change "-wikipedia" to "-site:wikipedia.org"

The former is too broad; mentioning Wikipedia in of itself shouldn't be enough to disqualify a source. If some sources *cite* Wikipedia then the person looking for the sources should just not use those sources themself, rather than potentially being unaware of any source which happens to mention a widely-used website. For any topics *related* to Wikipedia especially, this template would be completely useless.

Also, the "newspapers" link should just add "&tbm=nws" as a query parameter instead of adding "site:news.google.com/newspapers" to the query string.

PBZE (talk) 04:38, 18 January 2021 (UTC)

I was originally considering making the same request, but now I'm uncertain about it. The proposed change should be weighed, pros and cons. Using a negative site keyword, will exclude pages hosted at wikipedia.org only. Using the negative wikipedia keyword, but minus the "site:" prefix, will avoid any pages containing "wikipedia" on them. This could theoretically exclude good pages that happen to have the token "wikipedia", but I suspect that is minimal. On the flip side, it may exclude some forks and mirrors who credit wikipedia, but only if the "site:" prefix is not included. My hunch is that including the "site:" prefix will hurt more than it helps, but this would need some investigation. Mathglot (talk) 19:56, 25 June 2021 (UTC)

Please monitor WT:MED discussion

Hi. It's brand new yet, but you may wish to monitor WT:MED#Announcing new template Find medical sources. If and when it stabilizes, we can discuss what to do at that point. Mathglot (talk) 01:59, 10 August 2021 (UTC)

Discussing wording for the expansion proposal

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Hi Sdkb As mentioned here, here's my first draft for a proposal to present to the projects, VPP, etc, as you suggested. Let's try for as neutrally worded a proposal as possible, laying out the current situation, and summarizing the various ideas we've come up with. (Signed by both of us together, if that's possible; 4 tildes, ampersand, 4 tidles?) Following the neutral proposal, we could each add our own comment/!vote stating our own preference and reasons; which could be different. As you said, this affects a lot of pages, so I've gone into some detail in the 'Background' section after the proposal question. Here's my first draft for wording:

Draft 1 by Mathglot
Proposal to facilitate use of different sets of links for different search domains

Proposal question: Do you favor an expansion of the find sources template/module to be able to facilitate generation of different sets of links for different search domains (such as medical, video games, etc.) and if so, which approach do you favor?

  1. by param
  2. by auto-detection of WikiProject
  3. by WikiData property
  4. some other approach (please specify and add to list (with datestamp)).

Votes can be combinations of more than one of the above.


Background This is a proposal to expand the current functionality of {{find sources}} to include knowledge of different flavors of "find sources", and generate different sets of links according to some scheme of selection, either automatic, parametric, or by data property.

Currently, we have three flavors of find sources links:

  • {{find sources}}, the basic set of sources starting with five Google links, plus JSTOR, NYT, and a couple more
  • {{find video game sources}}, this contains the basic set above, plus three more links targeted to video gaming[a]
  • {{find medical sources}}, a completely different set of links aimed at supporting WP:MEDRS-compliant sourcing

One could imagine other possible search domains in the future: perhaps other academic subect areas, biographies, country or region, and so on. This would involve creating a new {{find NewDomain sources}} template, and an update to the wrapper template to transclude it under the right conditions.

Approaches

The first area where this proposal was discussed in some detail is at Template talk:Talk header. Two approaches were tried in its sandbox and tested, each delivering the expanded functionality by different methods:

  1. by proposed new parameter |search-domain=: set to one of the values 'medical' or 'video' ('general' being the default case)
  2. by auto-detection of WikiProject: if the TP header transcludes the WikiProject 'Video games' or 'Medicine' (neither one = default)

Both of these were found to work as expected, delivering the desired expanded functionality as shown in the testcases page (here, and here; current sandbox revision uses method 2, so testcases for method 1 currently fail, but pass successfully with the correct sandbox revision in place.)

A third approach was discussed but not tested:

3. detection of search domain by WikiData property associated with the article.

Design

Implementation is via a wrapper template (here) which does all the detection of search domain, and transcludes the correct flavor of template. By placing the wrapper template at the current title (Template:Find sources) and moving the old content to Template:Find general sources, this remains transparent at the top level; all current transclusions of Template:Find sources after the changeover will invoke the wrapper, which invokes {{Find general sources}} by default. Outside of the Talk header template, this means a seamless transition for all other transclusions which will do exactly the same thing after go-live as they did before; that is, they will continue to invoke the basic "Find sources" link set, albeit by one extra call where {{Find sources}} transcludes {{Find general sources}} which invokes the Module.

Currently Template:Talk header includes the basic set of source links for all articles where it is not suppressed by parameter. After go-live, the behavior of "find sources" in Template:Talk header may change, depending which solution is chosen. If the parameter method is chosen, then the links in the Talk header would remain the same, until someone added the parameter. If auto-detect by WikiProject is chosen, then the links in the Talk header of pages on medically-related topics will switch to the medical links, and on video-related topics will switch to the video links; all other Talk headers would remain as before.

Impact on other templates

Other templates use the {{find sources}} templates, such as {{unsourced}} and other maintenance templates, as well as many others. Depending which approach was chosen, this could affect whether the other templates could take advantage of them. A combined approach allowing auto-detect and via param would permit both.

Thanks. /sig: Sdkb & Mathglot/

Notes

  1. ^ Currently not very effective, but that's an implementation or design detail with that particular template construction which doesn't affect this proposal

Please either add your own below, or change the one above to your liking. Thanks, Mathglot (talk) 19:48, 12 August 2021 (UTC)

Thanks for writing all that out, Mathglot! It looks pretty good; the main suggestion I have is to give a little more background so that it's clearer what the proposal is. I also think that we should ask for discussion, rather than bolded !votes, around the approaches question, since it's the sort of thing that's complex enough that discussion tends to work better than a survey. Here's my draft trying to do these things:
Draft 2 by Sdkb
Proposal to improve customization of Template:Find sources

Background

This is a proposal to expand the functionality of {{find sources}}, a template frequently used in {{Talk header}} (example) to help editors find sources to improve articles. Specifically, we seek to make it possible for different sets of links to appear for different types of articles, such as links to medical sources for medical articles.

Currently, there are three related templates that generate find sources links:

  • {{find sources}}, the basic set of sources starting with five Google links, plus JSTOR, NYT, and a couple more
  • {{find video game sources}}, which contains the basic set above, plus three more links targeted to video gaming
  • {{find medical sources}}, a completely different set of links aimed at supporting WP:MEDRS-compliant sourcing

We anticipate that additional templates in this family for other subject areas may be created in the future. Under this proposal, talk header will choose between the available templates, either automatically or on the basis of a manually set parameter, to display the one most appropriate for a given page.

Approaches for selection

We are considering several possible approaches for how to select which set of links to use:

  1. Through a new parameter that can be manually set (i.e. to display medical links at Talk:Giardiasis, we'd change {{talk header}} to {{talk header|search-domain=medical}} at that page)
  2. Through auto-detection of WikiProject banners (i.e. Talk:Giardiasis would switch to using medical links because it includes the {{WikiProject Medicine}} banner)
  3. Through auto-detection of Wikidata properties (i.e. Talk:Giardiasis would switch to using medical links because an automated analysis of its Wikidata item identifies it as a medical topic)

It would be possible to combine these approaches, such as through using option 2 with the option to manually override via a manual parameter. Previous discussion is at Template talk:Talk header, and we have created functional prototypes of options 1 and 2 in the talk header sandbox, which can be seen at the associated test page. (Current sandbox revision uses method 2, so testcases for method 1 currently fail, but pass successfully with the correct sandbox revision in place.)

Which approach(es) would you prefer?

Design

We are considering implementation via a wrapper template (here) which does all the detection of search domain, and transcludes the correct flavor of template. By placing the wrapper template at the current title (Template:Find sources) and moving the old content to Template:Find general sources, this remains transparent at the top level; all current transclusions of Template:Find sources after the changeover will invoke the wrapper, which invokes {{Find general sources}} by default. Outside of the Talk header template, this means a seamless transition for all other transclusions which will do exactly the same thing after go-live as they did before; that is, they will continue to invoke the basic "Find sources" link set, albeit by one extra call where {{Find sources}} transcludes {{Find general sources}} which invokes the Module.

Currently Template:Talk header includes the basic set of source links for all articles where it is not suppressed by parameter. After go-live, the behavior of "find sources" in Template:Talk header may change, depending which solution is chosen. If the parameter method is chosen, then the links in the Talk header would remain the same, until someone added the parameter. If auto-detect by WikiProject is chosen, then the links in the Talk header of pages on medically-related topics will switch to the medical links, and on video-related topics will switch to the video links; all other Talk headers would remain as before.

Impact on other templates

Other templates use the {{find sources}} templates, such as {{unsourced}} and other maintenance templates, as well as many others. Depending which approach is chosen, this could affect whether the other templates will be able to take advantage of them. A combined approach allowing auto-detect and via param would permit both.

We look forward to your feedback on the considerations above and the proposal overall. Thanks! /sig: Sdkb & Mathglot/

Let me know if it looks good! I'm thinking we can hold it at WP:VPR, with invites to the affected WikiProjects and other relevant pages. Does that seem best? {{u|Sdkb}}talk 21:10, 12 August 2021 (UTC)
Sdkb, I like your changes overall, especially the additional background and expansion of the items in the Approaches section with the parenthetical explanations, the wording about "anticipat[ing]" future stuff, and other additions; all good! The only quibble I have, is minor, and results, I believe, from a slight difference in focus that we have in how we look at it. The way I see the focus, is that it's all about "Find sources" expanded to support all sorts of other templates, with the "Talk header" playing the role of "happens to be the first example" but with one eye fixed firmly further afield to include all the maintenance and other templates.
If I understand you correctly, you see it focused more on "getting {{Talk header}} improved" (because we're practically there already), and worrying about other stuff later. They both amount to the same thing, really, and I'm okay with going with your approach, but I just wanted to make sure our description includes enough material about future expansion, so that any decision taken now doesn't lock us out of future expansion with other templates because it wasn't explained clearly enough at the outset.
I think you tried to address that in the "override" comment in the first sentence after "Approaches" point 3, although I misread it at first as meaning "normally WikiData detect, but you can turn off the links entirely using 'none' in param 1". I only realized after a couple of re-reads, that you didn't mean it that way at all (amirite?). I'd like that part to be clearer about what "combined approach" is. How bout changing that sentence to:

It would be possible to combine these approaches, such as implementing a combined option 2&nbsp;–&nbsp;1 approach, which in the case of {{Talk header}} would default to option&nbsp;2 (project auto-detect) with the option[a] possibility of including the parameter (e.g., {{talk header|domain=medical}}) which would then take precedence over the project auto-detect. Having the parameter available would also be extensible to use by other Templates on article pages where project detection isn't applicable; see below.[b]

That's a bit clunky, but I think you see where I'm trying to go with it; maybe you can come up with something smoother? Practically speaking, I think the approach of going with what we have now because it's already working makes good sense, so I'm fine with it.
Other than that, all good. Also, I agree with VPR as venue. One last, tiny detail: I'd like to try the "combined sig" thing if possible, so we should sign within seconds of each other or a minute or two; I've never used the #IRC channels, but maybe we could coordinate that way; otherwise, maybe an "appointment" of when to first place it, including a ping right at the end, to be replaced by the other person's sig? Or do you have a better idea? (Not married to the idea of a double-sig; just thought it would be nice.) Mathglot (talk) 22:33, 12 August 2021 (UTC)

Notes

  1. ^ confusing duplication of 'option' used in two different ways in one sentence; maybe 'possibility'? Something else?
  2. ^ Would need to have an anchor added to the bold "Impact" header.
Sounds good! So how is this for a final draft?
Final draft
Proposal to improve customization of Template:Find sources

Background

This is a proposal to expand the functionality of {{find sources}}, a template frequently used in {{Talk header}} (example) to help editors find sources to improve articles. Specifically, we seek to make it possible for different sets of links to appear for different types of articles, such as links to medical sources for medical articles.

Currently, there are three related templates that generate find sources links:

  • {{find sources}}, the basic set of sources starting with five Google links, plus JSTOR, NYT, and a couple more
  • {{find video game sources}}, which contains the basic set above, plus three more links targeted to video gaming
  • {{find medical sources}}, a completely different set of links aimed at supporting WP:MEDRS-compliant sourcing

We anticipate that additional templates in this family for other subject areas may be created in the future. Under this proposal, talk header will choose between the available templates, either automatically or on the basis of a manually set parameter, to display the one most appropriate for a given page.

Approaches for selection

We are considering several possible approaches for how to select which set of links to use:

  1. Through a new parameter that can be manually set (i.e. to display medical links at Talk:Giardiasis, we'd change {{talk header}} to {{talk header|search-domain=medical}} at that page)
  2. Through auto-detection of WikiProject banners (i.e. Talk:Giardiasis would switch to using medical links because it includes the {{WikiProject Medicine}} banner)
  3. Through auto-detection of Wikidata properties (i.e. Talk:Giardiasis would switch to using medical links because an automated analysis of its Wikidata item identifies it as a medical topic)

It would be possible to combine these approaches, such as implementing a combined option 2 – 1 approach, which in the case of {{Talk header}} would default to option 2 (project auto-detect) but would allow any editor to set a parameter (e.g., {{talk header|search-domain=medical}}) which would then take precedence over the project auto-detect. Having the parameter available would also be extensible to use by other templates on article pages where project detection isn't applicable; see below.

Previous discussion is at Template talk:Talk header, and we have created functional prototypes of options 1 and 2 in the talk header sandbox, which can be seen at the associated test page. (Current sandbox revision uses method 2, so testcases for method 1 currently fail, but pass successfully with the correct sandbox revision in place.)

Which approach(es) would you prefer?

Design

We are considering implementation via a wrapper template (here) which does all the detection of search domain, and transcludes the correct flavor of template. By placing the wrapper template at the current title (Template:Find sources) and moving the old content to Template:Find general sources, this remains transparent at the top level; all current transclusions of Template:Find sources after the changeover will invoke the wrapper, which invokes {{Find general sources}} by default. Outside of the Talk header template, this means a seamless transition for all other transclusions which will do exactly the same thing after go-live as they did before; that is, they will continue to invoke the basic "Find sources" link set, albeit by one extra call where {{Find sources}} transcludes {{Find general sources}} which invokes the Module.

Currently Template:Talk header includes the basic set of source links for all articles where it is not suppressed by parameter. After go-live, the behavior of "find sources" in Template:Talk header may change, depending which solution is chosen. If the parameter method is chosen, then the links in the Talk header would remain the same, until someone added the parameter. If auto-detect by WikiProject is chosen, then the links in the Talk header of pages on medically-related topics will switch to the medical links, and on video-related topics will switch to the video links; all other Talk headers would remain as before.

Impact on other templates

Other templates use the {{find sources}} templates, such as {{unsourced}} and other maintenance templates, as well as many others. Depending which approach is chosen, this could affect whether the other templates will be able to take advantage of them. A combined approach allowing auto-detect and via param would permit both.

We look forward to your feedback on the considerations above and the proposal overall. Thanks! /sig: Mathglot/ {{u|Sdkb}}talk 23:20, 12 August 2021 (UTC)

Regarding co-signing, I'll set my sig to ten minutes from now; if that works, you can do the same and then just copy to VPR when it comes time. {{u|Sdkb}}talk 22:55, 12 August 2021 (UTC)
Sounds great! (sig time check: Mathglot (talk)) Looks good; here we go.... Mathglot (talk) 23:23, 12 August 2021 (UTC)
@Sdkb:  Done! Eager to read the feedback.
 Courtesy link: WP:VPR § Proposal to improve customization of Template:Find sources
Feel free to comment there whenever you want. I might hold off a bit, till I see if and what kind of feedback we get. One last thing: was thinking of either collapsing this thread or archiving it now, as the main action will be at VPR. What do you think? Mathglot (talk) 23:35, 12 August 2021 (UTC)
I'll put an archive box around this, just to make sure further discussion is centralized. {{u|Sdkb}}talk 05:36, 13 August 2021 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Proposal: add an icon linked to a project page with more detailed find sources information

At WP:WikiProject Women, Ipigott had an idea in this discussion (diff ) about adding a link to the list generated by "find sources" that would target a project page where more detailed information about how to find sources could be found. I think this is a really good idea, and worth considering here.

Piggy-backing on Ipigott's idea, I had a couple of thoughts about how to make it even more useful:

  • to save horizontal space and also highlight the different nature of the link, we could use an icon image for it (such as )
  • the icon link could default to a standard location (perhaps Help:Find sources), and could be parametrizable, so that the link could go somewhere more specific for those articles where it made sense to do that.

Here's some mocked-up links for the Talk header of Talk:Isadora Duncan, designed to simulate a proposed inclusion of an icon with parameterized override of the default destination, to point instead to a page under WP:WikiProject Women in Red, which is specifically about finding biographical sources for women:

Thoughts? Adding SusunW, who was involved in these discussions. Mathglot (talk) 01:44, 17 August 2021 (UTC)

I definitely like the thought of {{find sources}} adjusting by project; that's what the {{Find video game sources}} and {{Find medical sources}} already do. My sense is, though, that structuring it as a separate click people will need to make will likely greatly reduce the number who do so.
There are a bunch of possible changes currently up in the air, so if you want to pursue this further, waiting for those to settle first might make it easier. {{u|Sdkb}}talk 02:45, 17 August 2021 (UTC)
Yah, probably so. This just happened to come up when it did, and thought it best to raise it while I still remembered it. We can shelve this till some later point when other things shake out one way or the other. Although I didn't get the part about "structuring it as a separate click" so remind me to ask about that when (if) it comes up again later. This isn't meant to be any kind of separate click, just a link like the others, except instead of going to an offsite database search page that generates search results for a particular topic, this would go to an on-site project page that has links to multiple sources, unrelated to the search keywords. Somewhat like TWL is now. Mathglot (talk) 10:59, 17 August 2021 (UTC)

Mathglot and Sdkb previously came up with a great proposal to improve Template:Find sources. By adding some simple logic to the template that pivots off WikiProject banners, Template:Find sources can produce a RS link set that is more relevant to each topic. A manual override would be built in to disable this at the topic level.

The Village Pump Proposal received consensus to move forward. One lingering question from that discussion was how to handle topics that might benefit from multiple RS link sets. For example, Talk:Medtronic is part of both WikiProject Medicine and WikiProject Companies. The topic could benefit from both MEDRS and standard RS links.

Approaches

We could stack the best matching link sets (temporary mockup) or detect a conflict and revert to the basic set. I have no preference.

Thoughts? - Wikmoz (talk) 04:54, 22 September 2021 (UTC)

I had thought about this, and came up with the same approaches you identified:
  • include two (or multiple) stacked "find source" link sets, as in the mockup
  • define a WikiProject hierarchy based on "source strictness" and include only the most general one. In this approach, if Medtronic is in projects Companies and Medicine, and sourcing for "Companies" is defined as 'RS' (general) while sourcing for "Medicine" is 'MEDRS' (strict) then Talk:Medtronic would get only the more general {{Find sources}} list.
Of these two approaches (there may be others), I think I prefer the first, in order to address Spicy's comment of 19:54, 13 August (diff, perma) at the proposal. Whether it (or either one) should be implemented in the initial launch or as a refinement later is a separate question. Mathglot (talk) 05:31, 22 September 2021 (UTC)
Unless a better solution is proposed, I support this approach. Seems clean and transparent in its functionality. - Wikmoz (talk) 03:12, 23 September 2021 (UTC)
I think having multiple link sets would be best. I don't think it's helpful to exclude specialized sources in favour of general sources, or vice versa, if both might be useful for the article. The current mockup looks a little clunky but I'm sure the presentation can be improved. Spicy (talk) 16:34, 22 September 2021 (UTC)

Priority

This seems like a lower priority edge case. So whatever the resolution, it seems safe to defer this to a future update. The previously-discussed manual override could be used as a short term fix in some topics. - Wikmoz (talk) 03:12, 23 September 2021 (UTC)

Repeating the search in what's displayed

Sometimes I add a second or third to an AfD when I think that searching for references by an alternate name (often in a different script such as Cyrillic or Chinese) would be helpful. It would be helpful if {{Find sources AfD}} could display what's being searched for so that readers recognize that the second or third instance is looking for a variant spelling or different script. Eastmain (talkcontribs) 19:58, 27 September 2021 (UTC)

Wikipedia Library text

"TWL" is not a widely known acronym, even among experienced Wikipedians. I'd suggest changing it to "Wikipedia Library". {{u|Sdkb}}talk 05:08, 10 August 2021 (UTC)

@Sdkb:That's a pretty long name, and might cause the "find sources" links to wrap at some window widths, when space is at a premium. Sample links currently for {{find sources|Egypt}}:
Find sources: Google (books · news · scholar · free images · WP refs· FENS · JSTOR · TWL
Sample links including Wikipedia Library instead of TWL:
Find sources: Google (books · news · newspapers · scholar · free images · WP refs· Wikipedia:Free English newspaper sources · Digital library of academic journal articles, books, and documents. · The New York Times · Top subscription-only databases, free for enrolled Wikipedians.
How 'bout, "WikiLib", instead? Alternatively, I've been thinking about adding tooltips and this would be a good candidate for one. (Tooltips active in the last four links in second row above.) I know, I know; a tooltip won't help mobile users, but I can't see a mobile user going through the long and involved sequence of steps starting from a list of find source links, to TWL (heh heh...), and then the whole procedure required to log in, find a source, generate a citation, and come back to the original article and add it. I do some intricate stuff on mobile, but this would be just too much for me. If there's anyone who would attempt it on their smartphone, I know who it is. Let's see what Cullen328 says. Mathglot (talk) 21:28, 10 August 2021 (UTC)
I consider my smartphone to be a miniature computer capable of doing almost any type of edit that can be done on a desktop computer. The problem is not the devices. It is the crappy mobile sites and mobile apps that the WMF has cooked up. That is why I always use the desktop site on my mobile phone, and I go though the process described above all the time. It is not really difficult. Cullen328 Let's discuss it 21:36, 10 August 2021 (UTC)
I think tooltips definitely has potential! If we need a slightly shorter name, we could use WP Library. If there's agreement to remove Google newspapers as I propose below, that'll reclaim some space. {{u|Sdkb}}talk 22:00, 10 August 2021 (UTC)
@Mathglot, following up, per the documentation at {{tooltip}} and MOS:NOHOVER, there are some accessibility concerns around using the tooltip to provide information about the sources, rather than just providing the abbreviation. But the counterargument is that something for some users is better than nothing for everyone. I'll implement the abbreviations now, and if we find consensus for including explanations in the tooltips, I'm fine with adding that element, but I just want to be cautious given that this is an 800k-transclusion template. {{u|Sdkb}}talk 20:05, 30 September 2021 (UTC)
@Sdkb:, yes, and I have always been on the fence about tooltips because of NOHOVER. I tend to favor inclusion due to the "some users" issue you raised (and also because of Cullen328's comment; he's quite right that it is an interface issue, not a device issue; tooltips *do* work on mobile in Desktop view). One of the reasons I lean towards inclusion, is that if we didn't include stuff merely because of inability of "some other users" inability to see it due to their chosen interfaces being unable to render it, then we should stop leaving user warning messages on user talk pages entirely; obviously, that won't fly. The other reason is that NOHOVER seems directed more at article than talk space. WP:THEYCANTHEARYOU is a larger issue for another venue, but it explains why I lean towards inclusion of tooltips here. Note that the new {{Find biographical sources}} uses tooltips extensively, but I won't squawk if consensus is opposed and removes them (but I would like to see and participate in that consensus). Mathglot (talk) 21:18, 30 September 2021 (UTC)
Just a side note on this - since we started rolling out some design improvements this month, I think the best place to link to for TWL is now https://wikipedialibrary.wmflabs.org/ rather than the current destination. In terms of names, I'll just quickly say that I think "WikiLib" would be confusing, it's not a term we've used anywhere else, but "WP Library" is probably fine. Samwalton9 (WMF) (talk) 09:12, 13 August 2021 (UTC)
Sorry I missed this before; changing the link sounds fine to me! {{u|Sdkb}}talk 01:13, 1 September 2021 (UTC)
Support renaming "TWL" to "WP Library". I don't have template editor permissions but perhaps Mathglot or Sdkb could implement the change? - Wikmoz (talk) 17:54, 30 September 2021 (UTC)

Template-protected edit request on 30 September 2021

@Wikmoz: I think there's consensus to change TWL to WP Library, FENS to FENS, and NYT to NYT. However, looking at the code, I'm not sure how to get the tooltips to work properly in the module, so I'm opening an edit request to draw in someone who knows how. {{u|Sdkb}}talk 20:24, 30 September 2021 (UTC)

I've made edits to the sandboxes, it looks like this:
Lua error in Module:Find_sources/sandbox at line 88: invalid template name 'Find sources/sandbox'; no template config found at Module:Find sources/templates/Find sources/sandbox/sandbox.
Can someone please copy Module:Find sources/sandbox and Module:Find sources/templates/Find sources/sandbox to their respective main pages. Danski454 (talk) 16:48, 1 October 2021 (UTC)
 Done User:GKFXtalk 18:46, 4 October 2021 (UTC)
Sorry I missed this earlier, @Danski454; thanks for coding and thanks @GKFX for implementing. I just switched to non-breaking spaces, and the other change it'd be nice to see is for The New York Times to be properly italicized if either of you know how to do that.
I am noticing that this is causing {{Find sources}} to go onto two lines on many pages, at least on my display. If either of you have thoughts on the proposal immediately below, it'd be nice to implement that soon to get it back on one line. {{u|Sdkb}}talk 01:55, 5 October 2021 (UTC)